I am currently developing an Android app, and am now approaching the ads part of development.
I am using Firebase for my app, and I need to know what the best approaches are for implementing the following advertising requirements for the respective scenarios (I have never done this before and the wealth of information and approaches is a little overwhelming) :
Scenario 1: Initial release
Initially, the app will be used by students of a single university, and as such we want the adverts to be arranged personally with local businesses, for adverts that will actually be of interest to the students.
What do I have to do in Firebase/AdMob to provide this?
What do the businesses have to do to utilize this after we have made an agreement with them?
Scenario 2: Progressed release
The end-goal is to have this app, in personalized form, for every university that is interested in using it for its students. Each university's app users would receive ads that are relevant to them (ie. a user at MIT wouldn't receive ads about a 20%-off restaurant deal in a South African town)
Again:
What do I have to do in Firebase/AdMob to provide this?
What do the businesses have to do to utilize this after we have made an agreement with them?
And how would I make certain users get certain ads?
Thanks!
Sounds like there are two concerns here.
For the first, if your app already uses location information for its intended functions (and has the location permission turned on), the Mobile Ads SDK will use that info to fetch geographically relevant ads. That happens automatically. Not every ad will be for a local business though--if a national advertiser is the highest bidder for your impression, that's the ad that will be served.
For the second concern (how to do direct deals with local businesses), I'd recommend AdMob's direct-sold campaigns. Once you have regular AdMob ads serving, you can mix in your own campaigns that you directly negotiate with businesses (e.g. "We'll give you 100,000 impressions for XXX dollars" or 10% of traffic, or whatever). Your business would be in charge of entering campaign details and uploading the creatives sent to you by those whom you're advertising.
Related
I have been working on nearby notifications. deployed n number of beacons in our work area. i have been trying to track the user analytics. I am able to track the click analytics of the url. I want to track the impressions for beacon campaigns.
I had done some research on finding analytics of notification reach in users device.there is no straightforward way to track the analytics.we have been getting log entries on PWS accessing the campaign url.but the access frequency is not accurate.
is there any to find the accurate user impression from the pws access logs or is there any other way to find the impressions.?
I know this is a bit old but I'll share what I have come to believe. While testing using bit.ly addresses in the nearby url I get exactly 2 hits. Not sure why 2 but it appears that google parses the url provided and caches the result. If it's a redirect it will follow it and cache the resulting page thus eliminating the ability to track hits via middle redirect page. If you use EURL (Physical web) then it never goes to Google first and you can track the hits via redirector like bit.ly. There are advantages and disadvantages to both EURL and EUID. I am quite certain google records each time a device requests the attachment data for a nearby but for some reason they chose not to give it to us. I am not pleased that google does not expose that data to the owner.
To be frank: No... you can't get accurate impressions.
Reason:
Google cache that beacon's URL + Message on their end for approx 3-5 minute even for different devices.
As Google Nearby is in Beta phase, there are many bugs and important concept that are missed. And Impression count is one of them.
My client want to make sure that his marketers meet some of their specific clients on a regular basis. I had thought of that this could be possible by getting the clients fingerprints. But as I read in several pages, the fingerprint api is available in android api 23+ and in Samsung devices it is not possible to check the fingerprints of people other than the phone owner.
Is there any alternatives that one can use for physical authentication (not like password)?
I want to aim as many devices possible and as lower android api level possible.
I also have the option to authenticate on server side based on information received from the device (if there are ways to do it that is not possible by the device itself)
Note:
It looks like that you get strange ideas of my question. although it is not related but let me explain to clear things:
In our country each factory has its own marketers that visit markets on regular basis (daily, weekly, monthly,...) based on their product (milk, biscuit, chips, bread, juice, ....), while the factory wants their marketers visit every markets (as they'll loose their shares to their competitives) marketers think differently (as they receive a small percent of their sale), they just visit those markets which will buy for example a thousand of apple juice and skip those who will buy only 10 (which for them the percentage they get doesn't cover the gas money) and when factory calls this markets to see why they were not buying their products anymore, they get to know that their marketers has not visited them for months.
This is the way they want to make sure that their marketers visit every market and not only the good buyers.
Idea is strange, but anyway: You can use (GPS tagged) photo of client, or/and his sign (by stilus on mobile device screen).
I'm nearing the end of creating an app that alters images for colour blind users. I'm now wondering how I can collect usage info from all users of the app.
In the app, the user chooses settings based on their specific level and type of colour vision deficiency. The only data I would need to collect is these two values (type and strength), the data would then of course need to be sent to me somehow for analysis.
Google analytics is good; either that or you have the app post data back to a web server you've set up somewhere.
IF you want to ship into Europe, you'll have to present users with a privacy policy that describes what data you capture and what you do with it, and allow them to opt in or opt out. That's a legal requirement. Probably also a moral requirement I think.
American companies used to bury these kinds of notices about 14 pages deep in an End User License Agreement, and gather all kinds of data. THe European Union now requires a separate Privacy Policy document.
Nothing wrong with collecting the data, as long as you allow users to opt in. Lots of apps gather lots of data for all kinds of purposes. But all the decent and respectable ones provide an opt-in/opt-out option.
have you looked at google analytics ? https://www.google.co.za/analytics/
Is it reasonable to give a user an option to either purchase the full version or click on an advertisement to unlock a feature in the application. From my understanding, AdMob pays based on clicks, not impressions. Also is it possible to listen for ad clicks in Android?
From the AdMob terms of use available here
If User is a publisher, User shall not, and shall not authorize or encourage any third party to generate fraudulent impressions of or fraudulent clicks on any advertisement,
You should not ask your users to click on the advertisement. It's against the terms of service.
You do need to carefully read your agreement with the advertisement provider. For example, I know that Google Adsense would not allow this. I admit this may not apply to AdMob (of whom I have no experience) but for those who find this question some time down the line, read the fine print. Here's the part of Adsense's Terms and Conditions I'm thinking of (Section 5):
You shall not, and shall not authorize or encourage any third party to: (i) directly or indirectly generate queries, Referral Events, or impressions of or clicks on any Ad, Link, Search Result, or Referral Button...
Aside from breaking Terms and Conditions, your users may still not click on them. New study has some interesting numbers to keep in mind...
I'm writing a social game for mobile devices. The overall interaction would work like an online Risk or Scrabble game (invite friends to a game, take a few turns per day, view results of friends' games).
I'm trying to decide how to handle logins, invites, and "friends".
Options:
Have users sign up with a username specific to my game. Invite people by username/e-mail.
Automatically identify users based on some the Device ID or their primary e-mail address.
Use an existing service like Facebook.
Option 3 automatically gets me the user's real name, a profile picture, and a list of the user's "friends". But maybe with Option 1 or 2 I could still get that information from the phone? (E.g. derive friends list from the user's address book.)
Option 2 might have the lowest barrier-to-entry. Just start the game and you're already good to go (don't have to create a username or type in Facebook credentials).
(Though I'm currently writing it for Android, I might do an iPhone version and want the two versions to play well together.)
Advice?
IMO, unless you want to develop some niche social features, yhy not delegate the socializing part to a third-party SDK like Skiller or Score Loop. Such SDKs would automatically handle the social interaction part for your app. For example, in Skiller, all you need to do is to hook up your app with the SDK by defining a few configuration attributes and it requires simplistic changes to your app source code.