frEEk

You can see the behaviour on bigclassaction.com. I just confirmed yesterday that it is still happening. It does _not_ happen on a page that doesn't have any ads like https://www.bigclassaction.com/evaluation.php FF only. Exact same pages in Chrome don't display this effect.

This is a significant issue given FF has a significant browser share. We will have to lose the async tags if this can't be solved, which is a damn shame cause they sure help pagespeed times.

Done.

Serving Adsense ad units via Revive, using the async tags, results in Analytics (assuming the Adsense account is linked to Analytics of course) not seeing the impressions or clicks generated by those ads. Simply switching back to the old JS tags started the data flowing.

Same behaviour confirmed here. Only happens in FF, and does not happen with non-async JS tags. Current install (3.2.1). It doesn't seem to stack in the history, oddly. ie. start on homepage, see 1 or 2 (can't tell what causes the random choice of how many) extra history entries. Navigate to a new page, new page has 1 or 2 extra entries but the previous page now just shows the one entry. My guess is this is a bug in FF, but maybe something that can be worked around easily? Can view the issue on bigclassaction com and am happy to make tweaks on the site to help debug.

Aha, that was exactly it, thank you! The one tweak I made in all the re-saving was making the third party ad code https. An excellent feature, but that one requires documentation. Ideally I'd put a warning right on the page when you save your ad code, if you detect insecure code.

Well, I have no idea how it fixed, but after multiple delivery_cache* resets and running through all the campaign & banner settings screens checking all settings against zones that appeared to be working, it started working. Nothing was changed. Can only guess some new setting since the upgrade from 3.0.0 was reset by saving a page of settings somewhere.

Another installation suffering this problem here. Using the JS invocation code. Code runs on page and requests add from http://domain.com/revive/www/delivery/ajs.php?zoneid=2&charset=UTF-8&cb=123123123&charset=UTF-8&loc=http%3A//otherdomain.com/path/page.php works just fine. Make the URL https and it claims it can't find an ad to serve. The OX_random string is set just fine, and with 3.1 the beacon is served, but no ad. Oddly though, if I change the zoneid to another valid zone, it DOES seem to serve under SSL just fine. Is there a setting regarding https delivery I'm not seeing?