- Adobe Target Developer Guide
- Getting started
- Before you implement
- Privacy and security
- Privacy overview
- Privacy and data protection regulations
- Target cookies
- Delete the Target cookie
- The impact of third-party cookie deprecation on Target (at.js)
- Google Chrome SameSite cookie policies
- Apple Intelligent Tracking Prevention (ITP) 2.x
- Content Security Policy (CSP) directives
- Allowlist Target edge nodes
- Methods to get data into Target
- Target security overview
- Supported browsers
- TLS (Transport Layer Security) encryption changes
- CNAME and Adobe Target
- Client-side implementation
- Overview: implement Target for client-side web
- Adobe Experience Platform Web SDK implementation overview
- at.js implementation
- at.js overview
- How at.js works
- How to deploy at.js
- On-device decisioning
- at.js functions
- at.js functions overview
- adobe.target.getOffer()
- adobe.target.getOffers() - at.js 2.x
- adobe.target.applyOffer()
- adobe.target.applyOffers() - at.js 2.x
- adobe.target.triggerView() - at.js 2.x
- adobe.target.trackEvent()
- mboxCreate() - at.js 1.x
- targetGlobalSettings()
- mboxDefine() and mboxUpdate() - at.js 1.x
- targetPageParams()
- targetPageParamsAll()
- registerExtension() - at.js 1.x
- sendNotifications() - at.js 2.1
- at.js custom events
- Debug at.js using the Adobe Experience Cloud Debugger
- Use cloud-based instances with Target
- at.js FAQs
- at.js version details
- Upgrading from at.js 1.x to at.js 2.x
- at.js cookies
- User-agent and client hints
- Understand the Global mbox
- Server Side implementation
- Server Side: implement Target overview
- Getting started with Target SDKs
- Sample apps
- Transition from Target legacy APIs to Adobe I/O
- Core principles
- Integration
- On-Device Decisioning
- Node.js SDK Reference
- Java SDK Reference
- .NET SDK Reference
- Python SDK Reference
- Hybrid implementation
- Recommendations implementation
- Mobile app implementation
- Email implementation
- API guides
- Implementation patterns
Allowlist Target edge nodes
Information and an up-to-date list of hosts to help you allowlist Adobe Target edges.
An edge is a geographically distributed serving architecture that ensures optimum response times for end-users requesting content, regardless of where they are located. Each edge node has all the information required to respond to the user’s content request and to track analytics data on that request. User requests are routed to the nearest edge node. For more information, see The edge network.
You can allowlist Target edge nodes, if desired.
In addition to allowlisting the Network Address Translation (NAT) IP addresses of Target edges and Target edge IP addresses discussed in the article, you should also allowlist all Adobe Analytics IP address blocks.
For more information, see All Adobe Analytics IP address blocks in the Adobe Analytics tech notes documentation.
Adobe Target infrastructure is being updated and customers who want to allowlist addresses must use both sets of IPs. Failing to do so will impact customers using server-side or hybrid implementations where Target API calls for fetching experiences are originated from within a network behind a firewall that is configured to use an allowlist.
All Edge4x addresses listed in both tables below are scheduled to be updated on August 9, 2023.
Network Address Translation (NAT) IP addresses of Target edges
List of egress IP addresses of Target edges. Allowlist these IPs if you plan to have Target reach out to your services.
| Edge Location | Egress IP Addresses |
|---|---|
| Edge41 (Mumbai) | 3.6.2.221 13.235.112.4 52.66.66.192 |
| Edge42 (Tokyo) | 52.69.55.232 43.206.61.43 13.113.73.214 |
| Edge44 (East Coast US) | 54.164.192.223 52.86.86.203 54.88.167.98 |
| Edge45 (West Coast US) | 52.40.124.129 54.148.219.69 54.189.208.212 |
| Edge46 (Sydney) | 54.253.144.4 54.66.198.142 13.211.218.51 |
| Edge47 (Ireland) | 52.208.136.136 54.170.28.19 99.80.111.82 |
| Edge48 (Singapore) | 3.1.141.36 18.143.112.116 52.76.61.44 |
Target edge IP addresses
List of IP addresses of Target edges. Allowlist these IPs if you want to make API calls to Target edges.
This list will change often, as the load balancers scale up and down based on traffic profiles.
| Edge Location | Domain | IP Addresses |
|---|---|---|
CLIENTCODE.tt.omtrdc.net(where CLIENTCODE is your Target client ID) |
||
| Edge41 (Mumbai) | mboxedge41.tt.omtrdc.net |
3.6.2.221 52.66.66.192 13.235.112.4 |
| Edge42 (Tokyo) | mboxedge42.tt.omtrdc.net |
43.206.61.43 13.113.73.214 52.69.55.232 |
| Edge44 (East Coast US) | mboxedge44.tt.omtrdc.net |
54.88.167.98 54.164.192.223 52.86.86.203 |
| Edge45 (West Coast US) | mboxedge45.tt.omtrdc.net |
52.40.124.129 54.148.219.69 54.189.208.212 |
| Edge46 (Sydney) | mboxedge46.tt.omtrdc.net |
54.66.198.142 54.253.144.4 13.211.218.51 |
| Edge47 (Ireland) | mboxedge47.tt.omtrdc.net |
54.170.28.19 52.208.136.136 99.80.111.82 |
| Edge48 (Singapore) | mboxedge48.tt.omtrdc.net |
52.76.61.44 3.1.141.36 18.143.112.116 |
As the load balancers detect changes in the traffic profile, it will scale up or down. The time required for Elastic Load Balancing to scale can range from 1 to 7 minutes, depending on the changes detected. When the load balancers scale, they update the DNS record with the new list of IP addresses. To ensure you are taking advantage of the increased capacity, Elastic Load Balancing uses a TTL setting on the DNS record of 60 seconds.
