Equivalent method for mboxOverride.browserIp in AT.js...

[HariharanSubra1]

Hi All,
I am using mboxOverride.browserIp for validating the geo location activity. Currently we are planing to upgrade the at.js version. In the new version 'mboxOverride.browserIp' is not supporting. Can any one help me on this?

Thanks,
Hariharan S

[nnakirikanti]

As this feature is decommission by Adobe with at.js 2.x, other alternatives  i suggest to use VPN or DNS Proxy

Free VPN for certain Geo locations

1. ZenMate Free VPN 
2. Windscribe
3. Hola Free VPN (Beware some companies blocks this).

DNS Proxy

1. Unlocator (free trail and paid version but works like champ https://unlocator.com/)

Let us know if anything works for you.

[nnakirikanti]

I use VPN as an alternative, Adobe Target decommissioned this feature from at.js 2.x.

Free VPN for certain Geo-locations 

1. Windscribe ( Usage upto 2GB Free)
2. ZenMate VPN (free for certain locations)
3. hola (Beware some companies block this)

[HariharanSubra1]

Thank you for the response. But In my company laptop I cannot use VPN and I cannot suggest other team member to use the VPN to validate the GEO targeted campaign. Now a days I am finding some IP and sharing the mboxOverride.browserIp Parameters to validate.

[nnakirikanti]

These are browser level VPN proxies, if you can install chrome addon's that will suffice for testing

[HariharanSubra1]

Thank you for the suggestion. Using VPN add on I cannot able to validate DMA specific / Zip code specific Geo located campaign. Its hard to find the VPN location for that.

[Ryan_Roberts_ · Accepted solution]

Hi @HariharanSubra1, 

One option that has worked for me is using the X-Forwarded-For header to spoof different geo's IP addresses to QA your Target activities using geo targeting. You can find extensions for Firefox or Chrome to allow you to easily apply this header to your page requests. Here's one I've tried: https://addons.mozilla.org/en-US/firefox/addon/x-forwarded-for-injector/

Also, if you want to manually fire a request to Target via the Delivery API (same API used by at.js 2.x) you can just add the x-forwarded-for header in a curl like this:

curl 'http://rr.tt.omtrdc.net/rest/v1/delivery?client=YOURCLIENTCODE&sessionId=68fcd64a1f7844aa970001&version=2.2.0' -H 'User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0' -H 'Accept: */*' -H 'Content-Type: text/plain' -H 'X-Forwarded-For: 192.223.241.21' --data '{"context":{"channel":"web","address":{"url":"http://sb.com/plain_site/page_three.html"}},"execute":{"pageLoad":{}}}'

Change the client, x-forwarded-for, session ID, and url and you can check your own test.

Hope that helps.

-Ryan

[nnakirikanti]

Good one, i was not sure of this before.

[karand53490614]

@HariharanSubra1 mboxOverride.browserIp for validating the geo location activity does not work with at.js 2.x, if you want to test this for a geo, you could use a VPN which points to that particular location and test this.

Regards,

Karan