andrewatfornax

Hi @alicia33, Probably the easiest thing to do would be to put the invocation tags somewhere, and test out if the impressions and clicks are being tracked. If it's not working, then you can go from there and work through some of our troubleshooting guides!

Hi @midler, Unfortunately, I don't have an Android phone, but even if I did, without some more information, I wouldn't be able to confirm if it's a bug or not, as you don't actually provide links to somewhere where we could test the issue to see if it happens for us. Do you still have the issue? If so, maybe setting up a test scenario that can be used to evaluate what's going on would be a good starting point. Thanks!

Sounds like this is fixed - the issue was a need to change the language, rather than the timezone...

https://documentation.revive-adserver.com/display/DOCS/Only+One+Active+Banner+in+Email-Newsletter+Zones ?

https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering

Country geo-targeting will work out of the box, as we include the free county data file in the Revive Adserver release. In what way is the targeting "not working"?

The issue is that the user you are using to connect to the database with does not have all of the required permissions to create the database and tables... See your database documentation for details on how to do that!

Hi @Keval SMS, Could I please recommend that you contact the authors of the 3rd party plugin directly about this issue? Thanks!

I think the short answer is that I am not aware of any option to change this. Can you please raise a GitHub case (with PR if you are so inclined)?

So, just to clarify, though - if you put the legacy city geo targeting data file in place, Revive Adserver provides an option to allow targeting by city, which isn't available if the data file isn't present?

Yes, that is indeed the case - if you use a *x* zone, then any banner of any size will be able to be displayed. Unfortunately, that's just the way it is - if you want to be able to fall back from a zone of one size to another size, well, the assumption is that any size is okay... The only way around this would be to use *x* zones, but separate out your banners by sizes into different campaigns, or use other Delivery Rule options to control where banners are displayed. There are some API options that can be used to obtain information about what zones have banners linked or not, but this is for management, rather than delivery. In the delivery service, no, there is no current option to "ping" the zone to find out if it would deliver a banner or not.

I don't think there's any upper limit to the weight, other than what the database field will support - unless the UI prevents certain values?

Ah, I think maybe you don't need the PDO version of the MySQL library; instead, you can use the mysqli version, which Revive should support natively.

What does your phpinfo(); page look like?

Hi @dalouke, Capping depends on the ability to set a cookie in the user's browser, so, the very first impression they see is not a capped banner, if there is no cookie already set from Revive Adserver. This is to ensure that we don't deliver a capped banner over and over and over again to someone who won't accept the cookie.

https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering

Update your PHP installation to have the MySQL extension!

https://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded and https://documentation.revive-adserver.com/display/DOCS/Plugins+Missing+or+Disabled ?

https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken ?

No, best option is the use of Delivery Rule Sets for consistent application.

Yes, this can be done - in the UI, there are options for different URLs for the admin UI, delivery, etc etc. If you set these up, and configure your web server serve the host names used appropriately (e.g. the UI root path needs to be www/admin) then this can be done.

This sounds like you are either not correctly specifying the location of your old installation during the upgrade, or, if you are, the webserver does not have permission to access the old installation directory and files. (During the upgrade, access to the old installation is needed to bring across various files/settings.)

Duplicate post of https://forum.revive-adserver.com/topic/5384-upgrading-from-414-to-421/

I would recommend starting a new thread, with some details of your error, what you were doing at the time you got the error, etc.

In what way is is "not working"?