There is heightened speculation that console moguls Sony and Microsoft are pursuing in-game ads, specifically in non-disruptive forms.
While the console and PC spaces are no stranger to F2P, there are considerable differences in player bases and means of engagement between console and mobile audiences, and with Microsoft’s reported commitment to preventing “irritating” experiences, this may be a harsh road for Microsoft and Sony to take. But it is one the mobile games industry has traversed extensively.
PocketGamer.biz spoke with AudioMob’s Wilfrid Obeng, Dataseat’s Rich Jones, and Kempt&Co’s Chris Kempt on the mobile game industry’s journey through F2P in-game ads and the crucial lessons Microsoft and Sony must acknowledge if they are to successfully implement in-game ads.
The first essential lesson is to focus on non-interrupting ad experiences. Consumers realise there is no such thing as a free lunch (such as ‘ads keep the game free’). However, formats which interrupt the user’s experience will cause a fall in game retention.
Secondly, ads should be attached to incentives. Users prefer to engage with an ad in exchange for in-game rewards such as in-game items, currency, or premium content. These are known as rewarded ad formats and AudioMob has seen higher user engagement on these ad formats.
Last but not least, respect user privacy. We made privacy a core focus at AudioMob, given user sentiment towards the data collection over the past five years. Although laws and technical implementations will differ across regions, the sentiment of the general public and governments is clear: user privacy must be respected.
While the core proposition here is seeking third-party revenue to monetise F2P games, this also presents a fresh opportunity to increase user LTV across their respective ecosystems if they can leverage cross-promotion to drive users into the best content that suits their business goals.
With the wealth of user data and extensive content libraries available to the triple-A platforms, they are well positioned to use this to optimise the profitability of all titles, per user – whether this means driving them into another F2P game, or the latest paid title.
However, a key learning from mobile would be that achieving satisfactory results will likely require more than the non-intrusive ad strategy they are currently indicating they intend to pursue. More-so than in mobile, the real challenge here is not in the data science, but the user experience.
It’s all about reasonable levels of control. Mobile advertising inherited a lot of its practices from web/digital and, as such, remains a ‘wild west’ in nature. Users have therefore had to grapple with things like misleading creative, close buttons that are difficult/impossible to hit successfully, audio which doesn’t respect the mute settings on the device, and a multitude of other issues which often make the experience annoying and intrusive.
Compare this to the much more regulated environment of TV or radio where there are higher barriers to entry due to its more “broadcast” nature, content has to conform to strict production standards and the ratio of advertising to content is strictly limited. We can easily see that reasonable control has clear benefits to the audience.
The problem, of course, is adoption of the new platform. Until such time as the demand for inventory matches or exceeds the supply, it’s difficult to create a clear business case around having such a regulated environment. However, it may be that Sony and Microsoft can overcome this.
Where possible, get the ad strategy and structure into your game design as early as possible. Rewarded placements are a great way to give IAP benefits to players that don’t or won’t make an in-game purchase, as long as they’re put in the right place, and offered at the right price!
Retention is the most important aspect of F2P, so test your ad frequencies, rewards, and placements as much as your budgets and timescales allow. We never get this right first time! Don’t just look at short-term retention, if you can: test for 14-30 day retention too. What might be just about okay in the short term might be far too much in the long term.
But the biggest lesson from mobile? Control or have a stake in the ad selling and serving side and you can’t fail to make some money!
For further thoughts on F2P monetisation, including many of the player frustrations discussed by Kempt, you can read Edd Coates’ feature on avoiding “purposefully neglectful” dark patterns in F2P games.
window.fbAsyncInit = function() {
// init the FB JS SDK FB.init( appId : 250161755076617, // App ID //channelUrl : '//'+window.location.hostname+'/channel.php', // Path to your Channel File status : true, // check login status cookie : true, // enable cookies to allow the server to access the session xfbml : true // parse XFBML );
FB._PG = url: "/useractions/loginfb/", response: "allowed",
// Common handler to fetch FB details and reload the page process: function(me) $.post( FB._PG.url, username: me.username, uname: me.name, uid: me.id, uimg: 'https://graph.facebook.com/' + me.id + '/picture?type=large' ) .done(function(xml) if ( $("status", xml).text() == FB._PG.response ) window.location.reload(); else alert('Error: Something bad just happened. Our tech department has been notified. Please try again later.');
) .fail(function(xml)
alert("Error: something wasn't right there, please try again.");
); ,
// Used by event subscriptions to handle the response handleResponse: function(response) if (response.authResponse) FB.api('/me', function(me) if (me.name) FB._PG.process(me); );
,
post: function(text, image) $("#fb-image").attr("src"); FB.ui( method: 'feed', display: 'popup', link: 'https://www.pocketgamer.biz/mobile-mavens/78682/mobile-mavens-microsoft-and-sony-in-game-ads/', description: text, picture: image );
;
FB.Event.subscribe('auth.statusChange', FB._PG.handleResponse);
FB.Event.subscribe('edge.create', function(response) $.post('/ajax/social-links/', site: 'facebook' ); ); };
(function(d, s, id) var js, fjs = d.getElementsByTagName(s)[0]; if (d.getElementById(id)) return; js = d.createElement(s); js.id = id; js.src = "http://connect.facebook.net/en_US/all.js"; fjs.parentNode.insertBefore(js, fjs); (document, 'script', 'facebook-jssdk'));