Geolocation Decision Criteria
A Web Realtime decision’s Geolocation decision criteria allow you, through their use within a smart asset, to present content accordant with a visitor’s current geographical location.
The following decision criteria types are available at a geolocation decision:
![](../__attachments/3904938585/att_13_for_3864789100.png?inst-v=c3007bf4-8f91-43d3-9633-90859273c945)
Note that geolocation decision criteria make use of either a Bing Maps, Azure or Google Maps Services API , all calls to which are recorded in the RPI Realtime logs (any provider-specific exceptions are provided at specific criteria’s documentation). Note that the provider is responsible for determining a visitor’s location, in accordance with their own criteria.
The appsettings setting GeoCoordsCacheTimespanMinutes
is used to control the length of time for which geolocation coordinates will be cached before another call to the API is made.
Several of the above are documented separately in more detail.