User Location Data
How does it work?
Available if you use Akamai's EdgeScape service, this criterion lets you use Akamai's Content Targeting (EdgeScape) data to match based on the user location, country, or continent. Client browser's approximate geographic location is determined by looking up the IP address in a database.
Not all the EdgeScape data are available for matches. For information on EdgeScape, see the EdgeScape User Guide, available from a link on the Documentation pages.
Operators
Value | The Rule is True When... |
---|---|
is one of | any of the user locations you specified in the text field is present in the request. |
is not one of | any of the user locations you specified in the text field is not present in the request. |
Fields
In the Content Target field, select the geographic scope. Narrow down the criterion by selecting continents, countries or region codes from the drop-down list.
Additional Options
-
IPs to consider: Specify which IP addresses determine the user's location. You can select the following options:
-
Connecting IP only: Allows the connecting client's IP address.
-
X-Forwarded-For IPs only: Allows IP addresses specified in the X-Forwarded-For header, succeeding if any of them match.
-
Both connecting IP and X-Forwarded-For IPs: Allows for both.
-
X-Forwarded-For IPs to consider: If you allow X-Forwarded-For IPs, and there are multiple IPs, select whether to consider all IPs or only the first. If a request is made through multiple proxies, the first IP should be the original client.
Updated over 3 years ago