...
| Note |
|---|
The "Show geotargeting delivery rules even if GeoIP data unavailable" must only be used by advanced users who are intentionally configuring a system where geotargeting data is not available in the user interface, but will be available in the delivery system. For normal users, this option should not be set, otherwise, it is highly likely that geotargeting delivery options will be set on banners, but these will not work, as neither the user interface or the delivery system will have geotargeting information available. |
Managing MaxMind GeoIP2 Files
The geotargeting plugin that ships with Revive Adserver v5.0.x and higher will automatically download and use the required datafile(s) from the MaxMind webserver at the time of installation, or when upgrading an existing installation that used an older version of the software. Specifically, it will download the compressed file "GeoLite2-City.tar.gz" and extract the file "GeoLite2-City.mmdb" contained in it. It will also store an md5 checksum of the mmdb file, so that it can check for future updates of it.
The geotargeting plugin also checks every night during the midnight maintenance run if a newer version of the MaxMind data file is available from MaxMind's webserver. If so, it will download that automatically and use it to update the file it stored before, and also a new md5 checksum.
The geotargeting plugin adds a section to the configuration file with an entry where a system administrator can specify another location for the datafile(s), in case there is an alternative process already being used to retrieve and update said files. By default, the section looks like this:
[rvMaxMindGeoIP2]mmdb_paths=
Here is an example of how it could be altered to reference a file somewhere else on the server:
[rvMaxMindGeoIP2]
mmdb_paths="/{path}/GeoLite2-City.mmdb"
With this in place, the Revive Adserver software will no longer attempt to update the file at regular intervals, as it is assumed that the file is being updated by some other process.