2. Also, you posted at 6 AM on 8/26. I have seen Analytics not have
the previous day's data fully updated for a day or two. Have you
checked it since then? Has the Analytics data changed since your post?
I suspect the date difference will play a large role (since evenings
are usually busy app times and the evening of 8/24 for Analytics is
included in the "day" of 8/25 for AdMob.
-Jim
--
Thanks,
SPA Support
AdMob is a recent acquisition of Google. It is a fact that AdMob and
Google have not yet completing system integration. Even so,to my
knowledge, they do not have a method of reconciliation (a direct
module or tracking mechanism) for either AdMob or the old Google
Adsense. I'm not sure it would work, though - too many moving parts.
After accounting for the timezone issue, you still have other issues
like:
What if there is an error running the javascript for Google Analytics
(GA) on the webpage - like an out of memory error? What if you don't
send the GA data packet (URL request) before the person leaves the
page (i.e. the ad caused them to click, but the very title of the
webpage is not what they expected, so they back out)? What if GA
receives the "hit" but the URL has an error? Or a GA server processing
error occurs? GA does not pay you, so errors are less important... in
fact, you might pay them for the service, in which case you expect it
to be accurate. But, 400 events is a very low number when they are
processing billions of bits of data. A undetected problem could easily
arise. Have you been able to validate the GA data gathering process
using another test scenario? In other words, you are questioning
whether they "system" works, but are you sure that your testing
methodology and implementation works?
Our Android apps use GA and we track over two million pageviews and
events daily. Only about 60% of our "visits" have "events" - but they
should all have events. So, we are getting a pageview, but no GA
events on pages where GA events are coded? Strange... maybe that's
similar to your problem. Anyway, we also get app errors stating that
Google pageviews/events are not sent due to processing errors. We have
not yet been able to determine the extent to which it happens, but it
appears to be significant. In other words, the device does not
transmit GA data even though it is supposed to.
The biggest problem with that level of tracking, though, would be that
you, as an advertiser, would probably get hammered by us publishers if
you had a bad ad. That is, if you wanted to "experiment" with an ad
and it turned out to be a dud, we would tear you apart. We would
notice that it's bad and cut you from our apps but we wouldn't know
if/when you changed it (not until we allow it again - but why would we
do that? if your ad was bad, would we really want to just randomly let
it back on our apps?). It would be like having a store that only sells
the "best selling products" - a store like that would have no
inventory most of the time, but when it did, it would make money!
Why would we want to run low-paying, unappealing ads? The level of pay
is not subject to opinion, but ads have a very subjective "appeal"
aspect. Ad departments/companies spend a lot of time and energy
"experimenting" with ads to get the best ones. Do you really want
large companies with deep pockets pushing out the small guy because
they can afford to with better paying, professionally developed ads?
I'm sure publishers would get more creative and figure out a system
that might not be as bad as what I'm saying, but it would still cost a
lot more for advertising creativity. It would certainly be a lot more
expensive for an advertiser to try out an ad if the information were
that transparent and low-cost. This cost differential would impact
small advertisers the most.
Regardless of my opinion - maybe that is the best way to do this, and
the tools simply aren't there yet.
-Jim
--
Thanks,
SPA Support
As for Google "acknowledging" a discrepancy - they would first need it
measured, which requires the integration that you are looking for.
Without that, the discrepancy could be elsewhere in the system (in
your code or mine, for example, as third parties). The biggest one,
for example, is how "dispatch" is handled in GA. That's where we have
experienced a lot of unexpected results. The dispatch doesn't trigger
as we expect, so the pageview is not counted (not sending the data
packet).
Good luck - hope you can nail this down...
-Jim
--
Thanks,
SPA Support
Furthermore, if that were a known mechanism for monitoring this type
of activity, spoofing referral data is easy and GA would suddenly have
even less reliable data. (I don't know why an advertiser would want to
make it look like more clicks occurred than actually did, but I could
see a competitor having a field day with that one; it would suck dry
advertiser budgets with virtually no results, making them look like
they can't deliver or, as you are worried about, they are "stealing"
revenue.) Stripping it is more common, and I would suspect that AdMob
strips it for security reasons, such as the above (more likely,
though, spoofing URL referrals could invalidate AdMob tracking
mechanisms based on invalid/excessive requests that could occur
through error, spyware or web bots). If they don't strip it, then what
purpose does it serve them? Does the client need to know the referral
source? Perhaps in some cases...
Integration is the only way to know that valid clicks result in
corresponding pageviews. Perhaps they could encode referrer data to
support this use, but that takes time.
-Jim
On Thu, Sep 1, 2011 at 1:20 PM, alex_slobodnik <alex.sl...@gmail.com> wrote:
> Just to make sure I understand, why would Google need integration to
> check for discrepancy? GA encodes referrer data, right? So Google
> knows which GA pageviews came through AdMob. Total number of such
> pageviews should be roughly equal to total number of AdMob clicks (no
> x3 times difference). How difficult is it to run map-reduce
> computation to check this is true for some subset of domains?
>
>
>
> of GA hits through AdMob for fairly large subset of domains and then
> compare that number with the corresponding AdMob numbers.
--
Thanks,
SPA Support
So, determining a request source (e.g. an AdMob click vs. an embedded
web link vs. a bookmark vs. an app embedded link, etc.) even from a
single client is not reliable based on referrer, IP address data does
not help because the server does not get the true client IP and the
exposed IP changes rapidly. So, trying to collect and decipher the
data for small groups of clients/domains would be difficult at best,
and then to use that data to test the validity of other data sets
(e.g. AdMob clicks) for large groups becomes even less reliable.
You've got some good thoughts on how to test this stuff. I know we
would all like some third-party verification that the "system" works
and is valid. Keep digging and maybe we'll figure something out...
Also, any progress on your original concern? It seemed like a pretty
good test if the webpage was specifically for the AdMob ads and the GA
implementation could be relied on.
-Jim
--
Thanks,
SPA Support
The fundamental issue is that even a GA solution would still leave
some people skeptical, regardless of the implementation hurdles. The
only ways to feel completely confident in AdMob are self verification
and/or third-party verification.
Additionally, excessive transparency leaves AdMob vulnerable to
competitors and overreaction (both advertisers and publishers seem
quick to move when errors occur). The industry is so new that there
are not established benchmarks or clear expectations.
We will all keep searching for a while, I'm sure...
-Jim
--
Thanks,
SPA Support