joined:May 1, 2018
I am getting strange results with adsense since April 26, 2018.
I have three responsive ad units on a responsive page. One ad above the fold and two below the fold.
"Ad requests" have dropped drastically (more than 70%) for the two ad units below the fold. The first ad unit is unaffected.
Since ad impressions are dependent on "Ad requests", they have also dropped by more than 70%.
To analyse the issue, I opened the page in Google Chrome browser and in Dev Tools clicked on the Network tab and then typed "ads?" in "Filter" input field.
After refreshing page, I found that GET ad requests for these units is now only made when the ad placement is visible on screen after scrolling down to the bottom of the page (on any platform, desktop or mobile).
This has led to lower ad impressions and lower CPM earnings for these ad units. All in all I am expecting around $40-50 lost revenue per month because of this behavior.
This happens on all browsers: Chrome, Firefox etc.
Checked numerous other websites, GET ad requests is only made when ad placements comes in view when there is more than one ad on a page. Ad request for first ad is always made even if you haven't scrolled into its placement (may because usually the first ad is always in the top viewport of the page).
Old Clarification on ad request behavior: [productforums.google.com
The above url mentions that if you have three ad units, three ad requests will be made as soon as page loads even if the ad placement is not scrolled into.
Prior to this issue, all three ad units had a "individual ad unit impressions to page views ratio" of 0.90 to 0.95.
After this issue, first above the fold ad have same ratio of 0.90 to 0.95.
However, both below the fold ads now have a "individual ad unit impressions to page views ratio" of 0.30 to 0.35.
In simple words, before this issue, the three ad unit impressions were 90%, 90%, 90% (as compared with page views).
Now after the issue, the three ad unit impressions are 90%, 30%, 30% (as compared with page views).
Now my questions are:
- Is this a new behavior?
- Or it was always like this and Google forced it on my website after finding some discrepancies?
Anyone else facing similar issues? Please, test it out on your own website.