Our partners spoke and we listened. In this case, mobile application publishers said they don't like losing eyeballs. Unless, Je tells me, it's part of a really rad game like Inferi Dii. But when it comes to users exiting an app because they've clicked on a banner ad, that's not so cool.
So, please allow me to introduce m-Ads . . . banner ads that open inside an application.
How does it work?
Participating publishers simply need to download our SDK (software developer kit) and install the code in their application. They only need to do this once.
Advertisers meanwhile can create a landing page when setting up their campaign.
That's it.
Then the ads start appearing inside applications, publishers receive a share of the revenue for each ad clicked and users have a more streamlined experience.
And, oh, the landing pages inside an app load quicker than ads on external pages.
With the SDK, publishers can also choose when the ads should appear -- before an app is launched, within the application itself or before a user exits the app.
Let's take a look at an example. Suppose JamSked -BuzzCity's - mobile internet directory of live music events and independent musicians - wanted to run an ad campaign. The JamSked campaign manager would log into her account at www.buzzcity.com, choose the Advertiser dropdown menu and click on "Landing Page".
From here, the advertiser can write copy, insert a hyperlink, numbers for Click-to-Call or Click-to-SMS as well as a photo, video or audio clip.
m-Ads work in Android, Blackberry and J2ME applications.
Here's a look at graphic and text banners within an application . . .
And here's what a landing page looks like inside Android . . .
