Erik Geurts
-
Posts
752 -
Joined
Posts posted by Erik Geurts
-
-
-
That .off bit was not part of your previous post. The links should not have those in them. It makes me suspect your server was compromised (which is a nice way of saying: it was hacked).
-
That link has nothing to do with me.
If you want to evaluate Revive Adserver, you can download it free of charge from https://www.revive-adserver.com/download/ and then you can follow the installation instructions from https://www.revive-adserver.com/support/installation/
-
What do you mean by "demo of your work"?
-
-
-
Why are you concerned that your comment would be blocked? I see no reason for that at all.
-
It is not necessary to manually and/or automatically clear those cached files. If you want to do it anyway, it won't hurt from a functional perspective. Revive Adserver will just rebuild any cached files it needs, and that might slow down the application while it is doing the rebuilding.
-
Many of my customers are, but I think you will understand if I say that that would be confidential information.
-
One zone that has only a single banner from an override campaign linked to it will display with an 'error' or rather warning symbol. The reason is that we consider that scenario to be a potential problem, or at least something to look at closely. That's because most of the times, override campaigns come with some sort of delivery limitation or frequency cap, and thus the zone as a whole has a very high likelihood of displaying blanks. In order to avoid blanks, one should make sure to have at least one banner from a remnant campaign linked to each zone, and the banner should be without any delivery limitations or frequency capping.
-
That icon indicates there is a problem. If no banners are listed under probabilities, then there is a problem. Most likely there is a mismatch between the dimensions of the zone and the dimensions of the banner(s) you think you've linked to it.
By the way, what is that word "diffusion" in the subject of the thread? It's not a Revive Adserver term. What do you mean exactly?
-
Override did exist at the time, it just had a different name.
1 hour ago, checkad said:i have 100.000 pages viewed per day.
If i set up 1 zone (identical on all pages) with only one banner to display, this zone should be able to display 100.000 banners (no limitation, no capping), right ?Correct. If there are no external blocking factors like ad blockers.
1 hour ago, checkad said:i've tried to set that campaign as overide without more success (no other overide campaign than this one).
If you have just a single override campaign linked to the zone, with no delivery limitations, it will (should) work identically to a remnant campaign.
To investigate properly, check the "Probabilities" tab of each of the zones involved. There you will see the probability of each banner in each zone being delivered as it was calculated during the last time the maintenance process ran.
-
I've reviewed both your message multiple times, but it is still unclear what you're trying to achieve or what you think is wrong.
Are you certain you understand the 3 different campaign types correctly? See also: https://documentation.revive-adserver.com/display/DOCS/Creating+a+Campaign#CreatingaCampaign-Basicinformation
-
Revive Adserver is primarily a publisher ad server, although it can be used (and is being used successfully) as ad network or advertiser/agency ad server.
However, it is not the "self service" system you are looking for.
-
I would first investigate if you've perhaps got overly strict security settings on your server. Also, it could be caused by an ad blocker in your browser.
-
No, this is not normal. The lg.php program logs impressions, so it should be part of an iframe invocation code as well. Or have you perhaps disabled impression logging?
-
Can you send me a PM with your phone number and e-mail address?
-
Arjen, I noticed you are from The Netherlands, so am I. If you want to discuss if Revive Adserver meets your requirements directly with one of the people managing the open source project, we could consider having a conversation.
-
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...
-
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.
-
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.
-
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.
-
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.
-
Revive Adserver does not do any sort of filtering. I have no idea what that text about DFP means, so I do not think I'll be able to help you.
Asynchronous JS Tag not working on v4.0.0
in Managing Revive Adserver
Posted
If there is a 500 error, then the cause can be found in your web server's error log. I suggest you try that first.
Just curious: did the async tags work before you upgraded to v4.0? You write about 2.3, but I assume you mean 3.2?