400 Bad Request with Google AdSense

Question

I am running a website that uses AJAX requests and history.pushState for navigation.

The requested content code contains Google's asynchronus AdSense code:

<ins class="adsbygoogle"
     style="display:inline-block;width:468px;height:60px"
     data-ad-client="ca-pub-xxxxx"
     data-ad-slot="xxxxxx"></ins>
<script>
(adsbygoogle = window.adsbygoogle || []).push({});
</script>

The head tag contains the adsbygoogle.js:

<script async src="//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js"></script>

This setup is working for one dynamically loaded pageview. After that, ads don't show up anymore. The error console shows:

400 (Bad Request) in expansion_embed.js:188

The expansion_embed.js requests the ad from http://googleads.g.doubleclick.net/pagead/ads. The requestet url contains lots of parameters.

Now, every time the ad does show up, the prev_fmts parameter has a value of 468x60. If the ad fails to load, this parameter's value is 486x60%2C468x60.

What is causing this parameter to change? Is it possible that this change is causing the 400 Bad Request errors?

expansion_embed.js is a minified script that is hosted by google. It's a bit tricky to find the relevant code. — user276289, Oct 02 '13 at 14:33
is it possible that your selector `adsbygoogle` is selecting more than 1 element? — David Nguyen, Oct 02 '13 at 17:10
same problem here, all ads loading but one, i have no clue why btw same adv size — ROLO, Dec 26 '13 at 18:46
I had a ton of these errors from Google AdSense after making lots of changes to my site. I cleared my cache in Chrome and all went away. — Jonathan Tonge, Nov 01 '18 at 23:25

score 63 · Answer 1 · answered Jul 13 '16 at 12:26

63

You just need to wait, when you first implement Adsense it will give this error. It took until next morning for Adsense to start displaying ads. I implemented their Responsive ad type.

answered Jul 13 '16 at 12:26

Robert Sinclair

4,550
2
44
46

2

Took about an hour for me. Weird that there's a delay! – Andy Ray Jul 27 '16 at 20:23
8

what's weird is 400 instead of anything else and no warning in the AdSense dashboard. – AndreiMotinga Aug 13 '16 at 21:52
2

@AndreiMotinga yep, that's how they roll – Robert Sinclair Mar 22 '17 at 03:13
1

yeah it tooks 1 hour – abhaygarg12493 Apr 12 '17 at 05:23
2

Now it took me about only 15 minutes which is far better than an hour or more, but still so lame... – err Oct 11 '17 at 13:04
Can anyone help me out with this issue? I am running angular 7 SSR with ng2-AdSense. Been getting 400 errors for about a week now. Did anyone install with angular SSR? – chris_r Sep 03 '19 at 18:50

score 4 · Answer 2 · edited Jan 30 '18 at 23:53

4

I was also getting same error when I added adsense code first time in my website. In my case, it started working simply after reloading page.

edited Jan 30 '18 at 23:53

A-Sharabiani

17,750
17
113
128

answered Jun 24 '15 at 19:49

Balram Singh

1,576
19
30

2

In my case, it started working after reloading around 5 times – Pathros Mar 23 '16 at 20:19

score 3 · Answer 3 · answered Apr 29 '14 at 11:40

I had the same problem, and after some research, I've seen it's a problem of incompatibility between Google Adsens and AJAX sites.

See Google's announcement and these two threads in Google's forums.

I've tried to artifically mangle the prev_fmts parameter, but I couldn't find my way through the obfuscated JS. Anyway, I guess that doing this would go against Google Adsense TOS.

score -1 · Answer 4 · answered Aug 19 '17 at 08:40

-1

Adblock was blocking the ads. I Enabled the site to solved it.

answered Aug 19 '17 at 08:40

Eyal

4,653
9
40
56

1

AdBlock really block the ads but with different error code. The error 400 is different and still occurs with disabled AdBlock. I had to wait ~15 minutes, and the problem was gone. – err Oct 11 '17 at 13:03
This fix my problem. Thanks – Dessauges Antoine May 11 '18 at 13:26
1

Nope. Adblock blocks using net::ERR_BLOCKED_BY_CLIENT, or anything else, but it cannot use 400. – Ath.Bar. Aug 20 '21 at 14:47

400 Bad Request with Google AdSense

4 Answers4

Linked