Use audiences in Adobe Target to target users based on their geographical location.
Geo location parameters let you target activities and experiences based on your visitors’ geography. You can include or exclude visitors based on their country, state/province, city, zip/postal code, latitude, longitude, DMA, or mobile carrier. This data is sent with each Target request and is based on the visitor’s IP address. Select these parameters just like any targeting values.
In the Target interface, click Audiences > Create Audience.
Name the audience and add an optional description.
Drag and drop Geo into the audience builder pane.
Click Select, then select one of the following options:
A visitor’s geo information is determined from the originating IP address of a Target location request (mbox request). The IP-to-geo resolution is done for the first call of a new session. This means, if the IP address of a visitor changes mid session of a visit, the geo information is still based on the IP address of the first call.
For Mobile Carrier, Target uses the IP address registration data (who owns the block of IP addresses) to determine the appropriate mobile carrier using Mobile Country Codes (MCC) and Mobile Network Codes MNC).
Specify an operator and the appropriate value.
(Optional) Set up additional rules for the audience.
Click Done.
The following illustration shows an audience that targets users accessing the activity from a latitude greater than 44° and a longitude less than 22°.
The accuracy of geo targeting depends on several factors. WiFi connections are more accurate than cellular networks. When a visitor is using a cellular data connection, the accuracy of the geo-lookup can be affected by location, the provider’s data relationship with DeviceAtlas, and other factors. Cell tower-based network connections might be less accurate than wired or WiFi connections. Also, a visitor’s IP address might be mapped to the visitor’s ISP location, which might not be the same as the visitor’s actual location. Some mobile geo-location issues can be solved using the Geolocation API.
The following table shows the accuracy of IP-based geographical information from DigitalEnvoy for wired or WiFi Internet connections. DigitalEnvoy provides the most accurate data in the industry. Global accuracy is more than 99.9 percent at the country level and is up to 97 percent accurate at a city level. Accuracy information does not apply to cell tower-based networks.
Country | State | City | Region |
---|---|---|---|
US | 99.99% | 96% | 94% |
Canada | 99.99% | 96% | 94% |
Europe | 99.99% | ||
UK | 99.99% | 87% | |
Germany | 99.99% | 95% | 93% |
Scandinavia | 99% | Low 90s | Mid 80s |
Spain | 99.99% | Around 90% | Mid to high 90s |
Asia | 99% | Mid 90s | Low 90s |
Japan | 99.99% | Mid 90s | Low 90s |
Australia | 99.99% | 94% | 91% |
You can use geo information for profile scripts.
For example, use:
profile.geolocation.country
profile.geolocation.state
profile.geolocation.city
profile.geolocation.zip
profile.geolocation.dma
profile.geolocation.domainName
profile.geolocation.ispName
profile.geolocation.connectionSpeed
profile.geolocation.mobileCarrier
So, you can write a target expression called “From North America” with the following code:
return profile.geolocation.country == 'united states' || profile.geolocation.country == 'canada' || profile.geolocation.country == 'mexico';
You can use profile.geolocation
values directly as tokens in offers, plugins, and so forth.
For example, use:
${profile.geolocation.country}
${profile.geolocation.state}
${profile.geolocation.city}
${profile.geolocation.zip}
${profile.geolocation.dma}
${profile.geolocation.domainName}
${profile.geolocation.ispName}
${profile.geolocation.connectionSpeed}
${profile.geolocation.mobileCarrier}
${profile.geolocation.latitude}
${profile.geolocation.longitude}
The following questions are frequently asked about geo-targeting:
Most mobile device users access content via WiFi, which means Target’s IP-based geo targeting is as accurate as on a desktop. Cell tower-based connections might be less accurate because the visitor’s IP address is based on the tower where the signal is being picked up. Some mobile geo-location issues can be solved using the Geolocation API.
Due to the way AOL proxies its traffic, Target can only target them at a country level. For example, a campaign targeted to France successfully targets AOL users in France. But a campaign targeted to Paris does not successfully target AOL users in Paris. If your intent is to specifically target AOL users, you can set the region field to “aol.” In fact, you can target US AOL users by specifying two targeting conditions: country exactly matches “united states” and region exactly matches “aol.”
at.js 1.x: You can override your IP address with an IP address from a different location and use the mboxOverride.browserIp url
parameter. For example, if your company is in the UK, but your global campaign targets visitors in Auckland, New Zealand, use this style of URL assuming that 60.234.0.39
is an IP address in Auckland:
https://www.mycompany.com?mboxOverride.browserIp=60.234.0.39
Clear your cookies before doing testing the activity.
mboxOverride.browserIp
is supported in at.js 1.x only. This functionality is not supported in at.js 2.x.
at.js 2.x: To override your IP address with at.js 2.x, install a browser extension/plugin (such as X-Forwarded-For Header for Chrome or Firefox). This extension lets you pass the x-forwarded-for header in your page requests.
Puerto Rico, Hong Kong, and other territories are treated as separate “Country” values.
No, Target uses geo data during the session only, then the data is discarded.
This video includes information about using audience categories.