netvillage Posted June 19, 2017 Report Posted June 19, 2017 So I notice is all my Async JS tags the value in data-revive-id="" never seems to change, even for different websites, advertisers, whatever. Is that normal? The ZoneID changes, but never the ID Quote
Matteo Beccati Posted June 22, 2017 Report Posted June 22, 2017 Hi @netvillage, yes, it is normal. It is a generated value that should be unique for each Revive Adserver instance. andrewatfornax 1 Quote
netvillage Posted June 22, 2017 Author Report Posted June 22, 2017 Yeah, after looking into the source that seemed to be the case. thanks! andrewatfornax 1 Quote
Adi Posted November 15, 2018 Report Posted November 15, 2018 Hallo, @Matteo Beccati ! I've installed the fresh webserver and Revive Adserver. But the invocation code has the new data-revive-id: <ins data-revive-zoneid="1" data-revive-id="0221d5147ec0b9b881fa2c3cfd4a172c"></ins> <script async src="//ads.abagain.net/www/delivery/asyncjs.php"></script> The websites I am working with have the old one like: <ins data-revive-zoneid="1" data-revive-id="3737cf5d3d340e4fadc9904da5d61dde"></ins> <script async src="//ads.abagain.net/delivery/asyncjs.php"></script> How (if should) and were is it possible to change this parameter? Quote
andrewatfornax Posted November 17, 2018 Report Posted November 17, 2018 No need to change it - the value is unique per installation. As you have created a fresh install, the ID should be different. Quote
Adi Posted November 17, 2018 Report Posted November 17, 2018 Thank you @andrewatfornax for your answer. I do understand that it was an idea - to change this parameter for each installation. Now I need to reconfigure the server in order to make it the same - otherwise I need to send new codes to all zones to al the websites I work with. The question is: "How can I change this ID to the previous one?" Thank you! Quote
andrewatfornax Posted November 24, 2018 Report Posted November 24, 2018 Ah, I see - I think it's stored in one of the core database tables? Quote
Adi Posted November 24, 2018 Report Posted November 24, 2018 (edited) @andrewatfornax Thank you for your interest. No. We simply opened another AWS instance, the previous was deleted. And built everything from zero. Edited November 24, 2018 by Adi Quote
Matteo Beccati Posted November 26, 2018 Report Posted November 26, 2018 data-revive-id is a hash calculated using the delivery and deliverySSL config values. @Adi The old one had "www" in the path while the new one doesn't, that's why you're getting a different id. andrewatfornax 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.