Technical Advisory: Upcoming Change to the Launch Egress IP Addresses

[#1]

What is Changing?

Adobe Experience Platform Launch is updating our underlying infrastructure and deployment pipelines.  This requires us to use new egress IPs.

The new egress IP addresses are:

• 184.72.239.68
• 23.20.85.113
• 54.226.193.184

Impact

If you are adding Launch egress IPs to an allow list for any reason, you'll need to update your allow list.

The most common reason for adding Launch IP addresses to an allow list is when you're using an SFTP host to receive your Launch library builds.

If you are not able to quickly update your allow list, and you need to do a deploy in between now and then, one potential workaround is to switch to an Archive build on the Managed by Adobe host, then download that .zip file.

When Will This Happen?

This change will go into effect on Tuesday, October 27th.

[#2]

Great article thebenrobb! Got a slightly more basic question: 

When implementing new third-party tracking extensions in Adobe Launch, e.g., Facebook Pixel, is there a way to anonymize the IP address so Facebook does not receive the user’s IP?

Thanks!

[#3]

@dwights96500116, the tag manager itself does not have any capabilities around anonymizing IP addresses.  If you send data to Adobe's new Edge Network (with the Web and Mobile SDKs), that has a capability to blank out IP Addresses before forwarding the events on to 3rd-party destinations.