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.
Related
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.
I have run into a Problem.
Basically, google web services allows a maximum amount of 1000 requests per day unless you verify your credit card (which I as a student, don't have).
I am building an android application which will help you find food near you and give you tips and whatnot. But heres the problem. I have reached the daily cap multiple times just due to testing the app & debugging it... And that is a serious issue...
I know how SQLite databases & so on work, and how to use them, but is that the way one would go when using google places web services? Is that even allowed?
Here is the basic process of what is happening:
Open App & Get the users location
Search and Mark nearby food sources (restaurants & whatnot)
This is done via getting a HTTP request with "Place Search"
Place search itself deliveres little information, not enough, so I get a "Detail Search" for every place it finds.
All the results (Max. 60) are marked on the map and saved in a DataHolder class storing all the DataModel classes.
this works fine and as intended, also if I close and restart the app, it will "work". But it will redownload all the data and the details. As you can imagine, this busts my 1000 request limit pretty damm fast.
So is there a common practice/structure on how developers persist this "Google API" data? I feel the way im doing it very inefficient both for me and the user...
Thanks.
If you are developing a web based application that only needs to search for places, and does not submit new places, you should use the Places Library of the Google Maps Javascript API rather than the Google Places API Web Service. The Places library assigns a quota to each end user rather than to each key. This means that your available quota increases with your user base rather than being capped at a fixed amount.
You can use Places API for Javascript https://developers.google.com/maps/documentation/javascript/places
It has all features of server version. You could try to use it with invisible WebView, or better with Rhino.
The Google Play Developer Console offers the Tracked Channels (UTM) view under User Acquisition → Performance which should be able to show a breakdown of which tagged links users clicked to get to the store listing, etc.
I have generated several different links to my app using the Google Play URL Builder, e.g.:
https://play.google.com/store/apps/details?id=com.vandenmars.colortrek&referrer=utm_source%3Dso%26utm_medium%3Dlink%26utm_campaign%3Dlink%26utm_content%3DTBk
I did a couple of tests last week where I opened the Play Store using these links and installed the app on new devices immediately from there. Still, the Tracked Channels (UTM) list shows no entries.
A bit more background that may be relevant:
My app itself does not use the Google Analytics SDK and does not register a receiver for the INSTALL_REFERRER intentI would assume that the Play Store handles the links directly without requiring app interaction, especially since it can track store listing views that don't lead to installs, but maybe this is incorrect? Or maybe the store disables tracking based on the app manifest?
I opened the links in Chrome on my PC and clicked "Install" thereMaybe the links only get tracked if they are opened in the Play Store App on the actual device? Seems strange, but I am running a test on that right now, the data just hasn't updated yet.
The tagged installations I did were on days that have been processed alreadyIt sometimes takes Google a long time to update the "Performance" data, but the data I can see already includes this Sunday and the tests were done on Friday. So, unless the UTM tracking data takes even longer to get processed, it should already show up.
Do I need to enable something somewhere for this to work? Or am I doing something else wrong?
UPDATE 1:
Meanwhile, one entry has started showing up in the Tracked Channels (UTM) list. Unfortunately, as the help-text states, "UTM-tagged links that have a single store listing visitor [...] are included in the “Other” category." So I have no idea which of my test links it is, if any. The entry is only showing as a Store Listing Visitor, but not as an Installer.
The last day included in the stats is Wednesday (supposedly), which is also the day when I did the test of opening the link directly in the Play Store app on a device for the first time. I did install the app during that visit, but it was after I had uninstalled a previous installation.
So, here's what I learned from this:
It doesn't look like there is some on/off switch for UTM tagging that I need to enable.
Including the Analytics SDK and registering an INSTALL_REFERRER is not strictly needed for just the tracking of Store Listing Visitors, but it might be needed to track Installers/Buyers.
There may be a difference between visits to tagged links from a PC vs. from the Play Store app on a device.
This leaves the following questions:
Are UTM links only tracked by the Play Store app, or also by visits to http://play.google.com/...?
Does an app need to use the Analytics SDK to forward information about installs and purchases to the Play Store, or do these get tracked independently of the app like the store listing visitors?
Is only the first installation of an app on a specific device counted under Installers, or is a fresh install after an uninstall also counted? How about after a factory reset of the device?
Bonus question: Is there a way to expand the "Other" category? :)
UPDATE 2:
Now I'm back to square one: 3 days ago, I opened more test-links on different devices (including the one that I thought was the one that showed up last time), directly in the app store, installing the app immediately. The data shown includes everything up to and including two days ago, so these visits and installs should be tracked by now. Yet, the list does not show any additional entries beyond the one from update 1 above.
So, either I have absolutely no clue what should be going on, or this whole tracking system is one giant buggy mess... Some things I've read in random forums suggest the latter, but maybe I am missing something, too?
UPDATE 3:
This is getting stranger and stranger. Now, all of a sudden, I see an entry showing 14 store visits and 10 installs for "zedge/android"! Why would someone make their own utm tagged link for my app?!? On top of that, none of my other tests have ever shown up (still just the original entry under "Other") and I don't even see the 10 installs in the statistics... Looks like this whole thing is just plain broken... Correction welcome.
We're in the same situation too now. No Google Analytics set up, need to run some ads this weekend, so I'm going to try to use UTM tags to track the app installs.
There may be a difference between visits to tagged links from a PC vs.
from the Play Store app on a device.
Found this in their documentation
"Note: Over-the-air and web (play.google.com) impressions aren’t
tracked on your app’s User Acquisition page at this time."
If you want, send the link over and I can test it out.
Before direct user to Google Play app page, send GET request with UTM params to your own site. Register this site to Google Analitics. It will count page visits only.
I am going through the same problem. I wanted to test if the UTM source and UTM campaign from the new Dashboard required some SDK or API installed in the app itself. So I contacted Google Play Devs, I asked specifically if we needed Google Analytics and their response was:
this not the case and also there is nothing further that you can add to the app itself.
I did try downloading my own app and sent the link over to a couple of dozen people (bare in mind that the app does have a Google Analytics setup, but it is from 2016, so old version) with the following link
Power my Robot with UTM links setup
I put random words, and all the visits and downloads on both UTM Campaign and UTM Source showed under "Other" and not the words I put. I managed to get around 20 downloads from this link.
However, after questioning Google why it was showing under "Other" and not the word I put in the link, they said it is because of a minimum threshold, which they don't know the amount.
As mentioned above, I used this form to get the Google Play with the UTM tags.
And also, I agree with a comment above, that Apple simply works. From the campaign section in the dashboard, you can open the "Link Generator" and they specifically say that the minimum amount in order to show the number is at least 5 installs using the link in order to protect users' privacy. Google Play can learn something from Apple in this case.
I will try to keep this updated if anything changes on my stats. And feel free to click on the link above and install the app, open and then de-install, just to build up the numbers and see if I can cross the threshold and discover what is the minimum amount they require.
I confirm that the Google Play Store UTM tracking doesn't work with your configuration, as I have the same (no Google Analytics SDK, but firebase-core) and I can't see any installation listed in the Acquisition view of the Play Store.
I note that the Play Store documentation part about UTM tag has a link to an url builder on the Google Analytics Guide, so may be the solution in to install GA SDK.
Have found google page that suggest how to build url with utms: https://developers.google.com/analytics/devguides/collection/android/v4/campaigns?hl=es#google-play-url-builder
This is an example:
https://play.google.com/store/apps/details?id={application_id}&referrer=utm_source%3D{source_id}%26utm_medium%3D{medium}%26utm_term%3D{term}
I'm surprise to see statistics in Google Analytics page for one of the Android app and noticed the following strange informations
Apple iPhone in Top Device Models
Strange OS names entry in OS Versions :
Macintosh Intel 10.10
Linux x86_64
Windows 7
(not set) (not set)
Note:
I have answered the the current possible solution, but that doesn't make corrections to the available old data sets please let me know any ways to correct the old data sets and get out of the cons mentioned in my answer!
Bots and referral spam are two different things, the answer you posted will only help with bots. I am going to refer to the article about removing referral spam here
Normally we say there are three types of junk visits:
Ghost referrals like the darodar / ilovevitaly / cenoval
Creepy crawlers like semalt (a.k.a. best-seo-solution.com) and fake referrals like maridan.com.ua and blog.ranksonic.com.
Well behaved bots and spiders
Issue Number 1
I suspect data being inserted directly into the Analytics account directly though the measurement protocol. I say this because I have several old Google analytics accounts that are showing hits, the websites for these accounts no longer exist and haven't existed in years. I also have an old application account like yours that no longer has any data sent to it that shows data daily. The only way for data to be inserted into them is if someone is doing it directly, the hits are coming from known referral spam sites (the big list). There has been a lot of talk on the net lately on how to deal with the first two problems. Google has not come with any solution as of my writing this. The article gives a few very good ways of dealing with it. here
Idea of how its done google+ post
Tip: It appears that they are currently only targeting Web Property 1. so if you say make UA--xxxx-2 there will be no spam inserted.
Issue Number 2:
This will be hard to detect, they are actually thing your site. A filter on the known bad crawlers helps.
Issue Number 3
The answer you posted is correct but will only help with this: Bot and Spider Filtering. Its also kind of old.
Note: I have answered my own question for Bot and Spider Filtering , please provide if any better solution for the Cons mentioned below and avoid referral spam
Google Analytics Google team announced Introducing Bot and Spider Filtering to get away with referral spams,bots in Analytics Entries !
Introducing Bot and Spider Filtering
Many of you have shared with us that it’s hard to identify the real
traffic that comes to your pages. That’s why I’m pleased to announce
that we’re adding bot and spider filtering.
You can simply select a new checkbox option which would be included in
the view level of the management user interface. This option would be
labeled "Exclude traffic from known bots and spiders". Selecting this
option will exclude all hits that come from bots and spiders on the
IAB know bots and spiders list. The backend will exclude hits matching
the User Agents named in the list as though they were subject to a
profile filter. This will allow you to identify the real number of
visitors that are coming to your site.
Nestlé has been testing it and has found great benefit:
“The Bot filter solution is essential for getting deeper insights.
View level availability let us stay fully aligned with Best Practices
provided to all site owners. Very easy to use, understand and
communicate across thousands of Google Analytics users.” ~ Katarzyna
Malik, Nestlé Google Analytics Specialist
Happy Analyzing!
Posted by Matthew Anderson, Google Analytics Team
Steps to enable Bot Filtering:
Go Google Analytics home page and click on the Admin tab.Click on View settings
select Bot Filtering to get rid of known bots and spiders option.
This will remove the spam hits from their analytics for only upcoming analytics data. So this solution has two cons!!
Cons:
Historical data will not be affected by this option, i.e. spam hits
which were made in the past will remain in your data, Google will
only filter your future hits.
Google promises to remove hits from known bots, which means that the
time from the new bot appearance to the moment when it will be
included in the Google filter list can be indefinitely long. I use
this solution for the last week though and didn't find any new bots
breaking through the filter
Ref:
SO POST
techcrunch
G+
Blog
Android google analytics shows visits form Russia without even installing app on any device
i am trying to create an android app and just added analytics to it a few days back then i didnot use the app at all , strangely it shows some visits from russia all from same region and same service provider is it spam or any thing else
service providers are
Service Provider Sessions % Sessions
1.
cjsc er-telecom company samara 28 70.00%
2.
cjsc er-telecom holding samara branch 7 17.50%
Referral spam is a common thing where people generate fake traffic to your Google Analytics property with the referrer set to their site. For a website, you can deal with it by using the Referral Exclusion List (note: this will not apply retroactively), but for an app you'll need to use a filter.
To add to my previous reply; The device that, according to my analytics, connected via that service was running iOS.
And they were all referrals from social-buttons.com. I only found out about this site moments ago via a google search, never seen it in my life.
I'm led to believe something isn't right, it's very out of the ordinary for me to get more than 6 page visits a day, all of them being non-returning visitors. They don't navigate between pages nor do they stay for any more than 10 seconds.
I dunno if this has helped, but it'll give you a little bit of insight into it.