[Troubleshooting] QA a campaign with a geolocation targeting

Geolocation is one of the multiple criteria available on the platform to target a campaign. This service is made available through an external provider. If you need documentation on how to set this up, please refer to userGeolocation criterion.

How does Geolocation work?

To determine the Country/State/City of the visitor, we use their IP address. This IP address is stored in the visitor’s Session Storage, in a variable called ABTastyGeoloc. This variable is only visible if a campaign, currently live, uses one of the following targeting:

• Geolocation

• IP

• Weather

Good to Know 💡 AB Tasty does not collect the IP address of the visitor.

How to QA a campaign using a targeting by Geolocation?

If you are using a VPN, turn it ON and select the targeted country or city. Don’t forget to edit your IP Address in the QA Mode, it’s possible that your VPN IP Address is different!

To edit your geolocation manually, you must edit the ABTastyGeoloc variable in your SessionStorage:

To retrieve the targeted values (‘code_country’, ‘code_least_specific_subdivision’...) and add them to ABTastyGeoloc, you can consult ABTasty.results and unfold the available variables until you find the information that interests you. To find out more about how ABTasty.results works, see this article.