Cadillac ad I can't get rid of on android phone

[gasman]

Any update on this? I am still unable to use this website on mobile without the ad popping into the middle of the screen.

[agulati]

You can scroll down to the bottom of the webpage. You will see it saying CP Style 2. Switch it to CP Style 2a and the ads should not appear.

[Slacker]

I like that style 2a works but it seems that tweets don’t load.

Not sure if this merits its own thread but more of an FYI.

[psyang]

Originally Posted by Slacker

I like that style 2a works but it seems that tweets don’t load.

Not sure if this merits its own thread but more of an FYI.

As I mentioned above, style 2A "works" because it actually fails to load the proper Javascript to even run ads. It's likely this affects the Javascript to view tweets too.

[redflamesfan08]

Related to this I guess. Is there a revenue difference for CP between a mobile browser (no Adblock) and Tapatalk?
Asking as I cannot stand using Chrome/safari and all the zooming that’s required.... but I’d like to allow for max ad revenue for the site.

[photon]

That I have no idea about, I can't imagine they'd be insanely different. I use Tapatalk personally, I'd say use whichever one feels better to use for you.

[Roof-Daddy]

2a works but tweets don't load so im constantly switching back and forth from style 2 to 2a so i can see an embedded tweet with a butload of thanks.

[KootenayFlamesFan]

Is 2 working now? It seems to be working for me right now.

[photon]

If Google fixes their ads then yeah it should be fine to switch back.

[steveo]

I still get the ads in the middle - but just using desktop browsing in chrome to get rid of it.

[Vansmack]

Originally Posted by steveo

I still get the ads in the middle - but just using desktop browsing in chrome to get rid of it.

Ditto and this works better than switching to 2a for me as tweets will imbed.

[ricosuave]

so, how does this get fixed? i know of some users who are not tech savvy at all and simply cant navigate due to this.

[photon]

It gets fixed by Google, Bingo's contacted them about it.

[photon]

I've changed it to CP Style 2 TmpFix which should have the side ad fix plus also still allow embedded tweets.

[Fuzz]

Are you sure this is Google's problem? I searched for "breakglass_mode" and didn't get any other results. Usually when no one else is having the problem, it's your problem, not someone elses. Unless that isn't what is causing the actual issue. Just wondering if waiting around for Google to fix it is the best strategy...it could be a long wait.


Have you tried removing the ad frame completely?

[photon]

You mean the iframe? The iframe isn't in our html code.

The code that we put in is only this:

var googletag = googletag || {};
googletag.cmd = googletag.cmd || [];
(function() {
var gads = document.createElement('script');
gads.async = true;
gads.type = 'text/javascript';
var useSSL = 'https:' == document.location.protocol;
gads.src = (useSSL ? 'https:' : 'http:') +
'//www.googletagservices.com/tag/js/gpt.js';
var node = document.getElementsByTagName('script')[0];
node.parentNode.insertBefore(gads, node);
})();
</script>

<script type='text/javascript'>
googletag.cmd.push(function() {
googletag.defineSlot('/12345/LeaderboardROS', [[728, 90], [970, 90]], 'div-gpt-ad-12345').addService(googletag.pubads());
googletag.defineSlot('/12345/ROSScraper', [[120, 600]], 'div-gpt-ad-12345').addService(googletag.pubads());
googletag.pubads().enableSingleRequest();
googletag.pubads().collapseEmptyDivs();
googletag.enableServices();
});
</script>

and

<div id='div-gpt-ad-12345'>
<script type='text/javascript'>
googletag.cmd.push(function() { googletag.display('div-gpt-ad-12345'); });
</script>
</div>

Then their Javascript replaces the div with whatever.

I get what you're saying about others not having a problem, but we've been running Google ads for years and years without an issue, then it started up, and we haven't changed anything, whereas Google changes their code all the time. Plus this isn't on all browsers.

This same thing happened with one specific ad previously and Bingo just blocked that one ad and it was fine again for everyone.

I mean it could be a weird interaction between their Javascript and our specific site's HTML, but the site's HTML isn't something I can do a lot of changing to.

EDIT: I wonder if there's an option I can set that would effect things.. those googletag.pubads() calls look like they have various configurations. https://developers.google.com/doubleclick-gpt/reference

[psyang]

Originally Posted by Fuzz

Are you sure this is Google's problem? I searched for "breakglass_mode" and didn't get any other results. Usually when no one else is having the problem, it's your problem, not someone elses. Unless that isn't what is causing the actual issue. Just wondering if waiting around for Google to fix it is the best strategy...it could be a long wait.


Have you tried removing the ad frame completely?

Thanks for bumping this. It made me take another look around. The "bad" ads are the ones that are being served inside a safeframe.

Safe frames appear to be inline iframes that expand to display the entire page when clicked. It is "safe" because it doesn't actually redirect the page to another site, but just expands its iframe, and displays the expanded ad there. It acts like a sandbox.

So it looks like, for whatever reason, the ad thinks it has been clicked, and so expands to cover the entire page. The ad itself is only sized for the sidebar, so it appears in the middle of the expanded area. That might be what "breakglass=2" represents - a value of 2 may mean the ad should "break the glass" of the container div and expand.

This is all just hypothetical guesses - I've never worked with any ad server.

Anyways, doing a search on safeframe, I did see this post:

5. Forgetting to uncheck ‘Serve into SafeFrame’.
In the ‘Creatives’ settings page, DFP automatically checks “serve in SafeFrame”. Uncheck that! The SafeFrame delivers the ad in an iFrame that is insulated from rest of page.

In some respects ‘Serve into SafeFrame’ is a good thing because it means the ad cannot affect page elements outside of the iFrame. The problem? Many ads may not work because they need to expand out of the size of the original container. Additionally, there may be discrepancies in reporting due to the unpredictable behavior of the ad call-to-page routing in the SafeFrame process.

I don't know if this applies to CP or not, but if there is a checkbox where you can disable "serve into SafeFrame", that might be worth trying.

[Fuzz]

Photon, in that link there is an option called "boolean forceSafeFrame" perhaps you cloud set that to falsemight help, though it says it won't do anything if not specified at page level. But I wonder if it might override a hidden call from Google if you add it.

[Fuzz]

There is also this:


https://developers.google.com/double...afeFrameConfig

[psyang]

Originally Posted by Fuzz

There is also this:


https://developers.google.com/double...afeFrameConfig

Nice find. The "allowOverlayExpansion: false" property definitely looks promising. Change this line:

googletag.defineSlot('/12345/ROSScraper', [[120, 600]], 'div-gpt-ad-12345').addService(googletag.pubads());

to

googletag.defineSlot('/12345/ROSScraper', [[120, 600]], 'div-gpt-ad-12345').setSafeFrameConfig({allowOverlayExpansion:false}).addService(googletag.pubads());

and see what happens. If you want, you can set up a new style with this change and I can do some testing on it.