Geotargeting settings control the geotargeting plugin options.

Set the global defaults for the geotargeting module to use, and if the delivery options should be shown in the UI, even if geotargeting data is not available.

To modify the geotargeting settings, as an administrator user, go to Configuration > Global Settings > Geotargeting Settings.

There are just two geotargeting options in Revive Adserver.

Geotargeting Settings

The "Geotargeting Module Type" option allows the module to be used for geotargeting to be set at a global level. The options are:

• "None" - when selected, geotargeting will be globally disabled for Revive Adserver; or
• "MaxMind GeoIP2" - when selected, Revive Adserver will use MaxMind GeoIP2 geotargeting.

When the MaxMind GeoIP2 module has been selected, then by default, the Revive Adserver user interface will only show the delivery options for geotargeting when the MaxMind geotargeting data is found to be available to the Revive Adserver system when accessing the user interface. Normally, this will not be an issue. However, under certain circumstances (such as running the Revive Adserver user interface on separate servers/domains from the Revive Adserver delivery engine), the MaxMind geotargeting data may not be found when accessing the user interface.

When this is intentionally the case, the "Show geotargeting delivery rules even if GeoIP data unavailable" option may be selected, to ensure that the geotargeting delivery options are shown in the user interface, even when Revive Adserver does not find the geotargeting data is present.

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.