Changing profile.geolocation.state for testing purposes | Community
Skip to main content
tonyl62487480
July 24, 2019
Solved

Changing profile.geolocation.state for testing purposes

  • July 24, 2019
  • 2 replies
  • 2882 views

Is it possible to add a URL parameter to set a geolocation state for testing purposes which overrides the stored geolocation.state that has been set in the user profile?

We currently have an A/B test that should deliver bespoke content depending on which state has been identified in the user profile but we are unable to test any variations apart from the content for our current state/location.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer17

What version of mbox are you using?  If you using mbox.js you can override your IP address with an IP address from a different location and use the mboxOverride.browserIP url parameter.  So if your company is in the UK, but your global campaign targets visitors in Aukland, New Zealand, use this style of URL assuming that 60.234.0.36 is an IP address in Auckland: to over http://www.mycompany.com?boxOverride.browserIp=60.234.0.36

If you are using at.js, you can use the QA link to view the experience.

2 replies

Jennifer17Accepted solution
Level 2
July 24, 2019

What version of mbox are you using?  If you using mbox.js you can override your IP address with an IP address from a different location and use the mboxOverride.browserIP url parameter.  So if your company is in the UK, but your global campaign targets visitors in Aukland, New Zealand, use this style of URL assuming that 60.234.0.36 is an IP address in Auckland: to over http://www.mycompany.com?boxOverride.browserIp=60.234.0.36

If you are using at.js, you can use the QA link to view the experience.

Adobe Employee
July 29, 2019

Our documentation has many other details around Geolocation:

Geo

The above comment from Jennifer has a slight typo.  The correct parameter is "?mboxOverride.browserIp=".  Jennifer should have included the "m" at the start of the parameter.