Forum Moderators: martinibuster

Message Too Old, No Replies

Monitoring invalid clicks

Adsense vs DFP reports

         

Benco

3:29 am on Jul 11, 2012 (gmt 0)

10+ Year Member



A few months ago my finalized earnings started to differ significantly from estimated earnings,
with differences of more than 10 percent. Since the problem did not go away during the next months
and actually started growing, I got worried about getting my account banned for invalid activity.

I was suspecting that some of the changes I had made were causing the problem, but
rolling back all of the changes was not possible. And the problem is simply that in order to
see the effect of a change you need to wait for a full month until earnings are finalized.

Luckily, after some research I found a method that can help in this situation:

The basic idea is to serve Adsense through DFP and monitor any invalid activity by looking
at the reporting differences between Adsense and DFP.

When you serve Adsense through DFP you still get the usual reports from your Adsense account,
and additionally you can generate Adsense reports in DFP. The easiest measure to look at is
click count. For some reports in DFP you need to use the small "edit report" link at the
top to make the Adsense click count show up. Note that Adsense reports in Google Analytics
will stop working when you use DFP.

Reports from your Adsense account are not filtered (invalid clicks contribute to estimated earnings).
By contrast, DFP reports are filtered and do not include invalid clicks:
[support.google.com...]

It makes sense that DFP filters clicks directly, since it can be used as an ad server for
campaigns with all sorts of durations, and therefore click counts need to be accurate on
a daily basis. It would make no sense for DFP to correct its reports at the end of the month.

In my case under normal conditions (without difference between estimated and finalized earnings)
the click count in the DFP report was about 20 percent smaller than in the Adsense report.
However during months with invalid activity (large difference between estimated and finalized earnings)
the DFP click count was about 30-50 percent smaller than in the Adsense report.

The advantage is that you can monitor the difference between DFP and Adsense click counts
on a daily basis, without having to wait for the end of the month. I have noted a delay of about
one day, i.e. if you change something today the data for tomorrow does not reflect the change yet,
but after two days you should see the effect. If your DFP account uses a different
time zone than the Adsense account you might need to average over a couple of days as well.

With some additional effort you can also monitor different sections of your site independently.
I was using URL channels in my Adsense reports, and have set up different ad units in DFP for
the corresponding sections of the site. That way you can compare click counts of an URL channel
with the click count of the corresponding ad unit in DFP and analyze each section of your site
independently.

By using this method I was able to isolate my problem, since only one
section was affected by invalid activity. The section included a piece of dynamic content I had
added months before, and maybe the javascript code was somehow interfering with Adsense. After
removing the dynamic content I could see the click count differences going back to normal within
a few days, and at the end of the month the finalized earnings were back in line with estimated earnings.

I just wanted to share this method since it was quite helpful in my case, and since it can be used
to detect invalid activity and keep your account in good standing with Google. For example
if you buy traffic from a new source or make changes to your site, you can verify that everything
is still okay by comparing the click counts in DFP and Adsense.

levo

4:27 am on Jul 11, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Very interesting, could you give us more details on the javascript code? I've always thought that invalid clicks are result of rough bots etc.

Benco

2:03 pm on Jul 11, 2012 (gmt 0)

10+ Year Member



It was a widget that updated itself when a user clicked on it, by fetching some new data through an Ajax call to the server.

pixar24

8:35 am on Jul 23, 2012 (gmt 0)

10+ Year Member



Thank you for sharing this information.
I suffer from an invalid click count (that has risen to around 20%) in my Adsense account, for about 8 months now.
Following your advice, I compared my numbers in Adsense and DFP for each ad location, and found out quickly that one of my top ad locations is showing an invalid click count between 15% and 39%.
All other ads are showing no significant invalid click count.
The ad is a 728x90 image (no text) ad, in a prime location at the top of the pages.
This is a great discovery on its own, at least I pinpointed the problem ad now.
I have removed all dynamic content that I could think of, that could cause a conflict with Adsense. Let's see what happens in the coming days. Will keep you posted.

Benco

7:07 pm on Aug 1, 2012 (gmt 0)

10+ Year Member



Hi Pixar,

have you had any luck with removing all dynamic content?

If not maybe you could play around with the ad location, for example moving the ad below the fold. I suspect that Google's spam filter can be triggered by certain user behaviour, for example if a user lands on a page and then directly clicks on an ad (without navigating around your site before), such clicks might be considered to be invalid. If that is true then placing ads aggressively on landing pages might be problematic.

Benco

11:18 pm on Aug 1, 2012 (gmt 0)

10+ Year Member



It seems Google has removed the resource I was linking to in my original post. At the moment you can still view it in the cache:
[cc.bingj.com...]
It is just an official statement from Google explaining that DFP reports filter out spam, while Adsense reports do not.

pixar24

8:14 am on Aug 11, 2012 (gmt 0)

10+ Year Member



Hi Benco,

I removed the 3 dynamic scripts on my pages (with the ad location that is causing the invalid click problem) and the invalid click problem was gone. That was good news.
However, I'm trying to figure out which of the 3 scripts is causing the trouble, but can't find it.
Tested with removing them one by one, but no good result.
I keep trying to find out where the error is, but it takes time, because after each step you have to wait 3-4 days to see the test results.