Issues with asyncronous JS tag

[Michael Oeser]

When I use the default asyncronous JS tag on my clients site no banner shows up. When I switch to the regular JS tag the banner show as expected. Any idea why that is?

[Erik Geurts]

The first thing I would try is to make a very simple test page, with minimal or no HTML but just the async tag, and to upload it to your client's actual site/server. Then you can test if the tag will work on its own. It might be that something in the site is interfering with the tag.

[Michael Oeser]

Thanks Erik.

To cut it short: Is there any reason why I should NOT use the regular JS tag which is working just fine

[Erik Geurts]

The main advantage of the async tag is that it is asynchronous. If the ad server is slow to respond, or not responding at all, using the async tag means that the webpage will appear regardless. That's why we developed the async tag. If you're comfortable about using a traditional javascript tag, by all means do so.

I am surprised, however, that the async tag isn't working, I don't see any reason why it doesn't, we've been using it for a very long time now on billions of ad impressions with great results.

[Michael Oeser]

It´ strange in fact and I will investigate it but for the moment I´ fine with the traditional JS tag.

Thanks

[Michael Oeser]

I have added a plain HTML page with the async code.

http://www.automotiveit.eu/adserver-test.html

Can you see why it´ not working?

The related zone ID 6 has a running campaign which works on the mainpage with the traditional JS tag.

[Erik Geurts]

Yes, I can see that when I call your zone 6 with a traditional invocation code, I get a regular ad, but like you I do not see the async tag returning anything.

Did you generate this async tag fresh just now? Could you please make sure that it is the exact code that Revive Adserver generates?

I'm asking because this part:

data-revive-id="aa2d475d0af67de0182d07e1fd6902f1"

Is supposed to be a hash value of your ad delivery URL. If this hash and the URL http://adserver.automotiveit.eu/www/delivery/ do not match, the tag won't work.

[Michael Oeser]

I regenerated the async and the traditional tags once again and added them to the testpage. Same result. how can I figure out if the hash matches my URL?

By the way: I took the same file and added it to my own site just to check and it shows nothing except the comments: https://der-prinz.de/adserver-test.html

Edited December 8, 2016 by Michael Oeser

[Erik Geurts]

When I view that page on your own site, I see an ad for both tags:

But when I view it on the first site (http://www.automotiveit.eu/adserver-test.html) I only get an ad for the javascript tag (nr 2).

When you generate a zone's async invocation code inside your Revive Adserver UI, it will automatically calculate the correct has value.

[Michael Oeser]

You are right. I can see them also on my site (had to deactivate my ad-blocker ;-))

Well then it seems as if something on my clients site blocks the async tag from displaying. Since we don´ seem to find a simple solution we will live with the traditional tag.

[Erik Geurts]

41 minutes ago, Michael Oeser said:

had to deactivate my ad-blocker ;-)

I still don't understand why anyone working in online advertising would even have an ad blocker...

[Michael Oeser]

Because I don´ really work that much in online-advertising and I don´ like to get bombarded by ads ;-)