- Adobe Target Guide Home
- Target release notes
- Introduction
- Introduction to Target
- Access Target from the Adobe Experience Cloud
- Target key concepts
- Understand the Target UI
- Adobe Target welcome kit
- Adobe Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Adobe Target at a glance
- Chapter 3: Develop your testing an personalization ideas
- Chapter 4: Tips for using Target
- Chapter 5: Inspiration for testing and personalization activities
- Chapter 6: Easily avoidable pitfalls
- Chapter 7: Create and run your first Target activity
- Chapter 8: Communicate your activity results
- Chapter 9: Next steps and resources
- Glossary
- How Adobe Target works
- Training and certification
- Training videos for Adobe Target Standard and Premium
- Target optimization and personalization FAQ
- Administer Target
- Implement Target
- Implement Target overview
- Before you implement
- Client-side web: implement Target
- Overview: implement Target for client-side web
- How at.js works
- How to deploy at.js
- 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 frequently asked questions
- at.js version details
- Upgrading from at.js 1.x to at.js 2.x
- at.js cookies
- mbox.js implementation
- mbox.js implementation overview
- Migrate from mbox.js to at.js
- What mbox.js does
- Configure mbox.js
- Download mbox.js
- Target page methods by mbox.js library version
- Create an Order Confirmation mbox - mbox.js
- mbox.js Frequently Asked Questions
- mbox.js functions
- mbox.js cookies
- mbox.js version details
- Understand the Global mbox
- Target for mobile apps
- Target for mobile apps overview
- How Target works in mobile apps
- Enable Target in the SDK
- iOS - create a Target location and success metric
- iOS - send custom user data
- Send activity information to Adobe Analytics
- Target mobile preview
- Prefetch offer content
- Target for mobile apps FAQ
- Use Location Service
- Server Side: implement Target
- Hybrid implementation
- Email: implement Target
- Integrate Adobe Target with the Experience Cloud
- Adobe Analytics as the reporting source for Adobe Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- Use an Analytics tracking server
- A4T reporting
- Troubleshooting the Analytics and Target integration (A4T)
- A4T Frequently Asked Questions
- Initial provisioning - A4T FAQ
- Activity settings - A4T FAQ
- View reports - A4T FAQ
- Redirect offers - A4T FAQ
- Lift and confidence - A4T FAQ
- Metric definitions - A4T FAQ
- Inflated visit and visitor counts - A4T FAQ
- Classifications - A4T FAQ
- Share metrics, audiences, and reports - A4T FAQ
- Legacy SiteCatalyst to Test&Target Integration - A4T FAQ
- Expected data variances between Target and Analytics when using and not using A4T
- Experience Cloud Audiences
- Integrate Target with Adobe Audience Manager
- Integrate Target with Adobe Campaign
- Experience Cloud Device Co-op
- Adobe Analytics as the reporting source for Adobe Target (A4T)
- Activities
- Activities overview
- Target activity types
- A/B Test
- Auto-Allocate
- Auto-Target
- Automated Personalization
- Automated Personalization overview
- Random Forest Algorithm
- Create an Automated Personalization activity
- Upload data for the Target personalization algorithms
- Data collection for Target’s personalization algorithms
- Estimate the Traffic Required for Success
- Preview Experiences for an Automated Personalization Test
- Target Automated Personalization offers
- Manage exclusions
- Select the control for your Automated Personalization or Auto-Target activity
- Automated Personalization FAQ
- Preview Automated Personalization activities with experience preview URLs
- Troubleshoot Automated Personalization
- Experience Targeting
- Multivariate Test
- Recommendations activity
- Edit an activity or save as draft
- Priority
- Activity settings
- Success metrics
- Activity Change Log
- Troubleshoot activities
- Activity QA
- Audiences
- Experiences and offers
- Experiences and offers overview
- Visual Experience Composer (VEC)
- Visual Experience Composer overview
- Visual Experience Composer Options
- Include the Same Experience on Similar Pages
- Multipage Activity
- Activity Collisions
- Modifications
- Element Selectors Used in the Visual Experience Composer
- Mobile Viewports for Responsive Experiences
- Visual Experience Composer Best Practices and Limitations
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Visual Experience Composer overview
- Troubleshooting the Visual Experience Composer and Enhanced Experience Composer
- Troubleshooting the Visual Experience Composer
- Troubleshooting the Enhanced Experience Composer
- Enabling Mixed Content in Your Browser
- Page Modification Scenarios
- Visual Experience Composer helper extension
- Redirect to a URL
- Creating Carousels that Work in the Visual Experience Composer
- Form-Based Experience Composer
- Single Page App (SPA) Visual Experience Composer
- Offers
- Reports
- Reports overview
- Report settings
- Auto-Target Summary report
- Automated Personalization Summary reports
- Personalization Insights report
- Offer reporting groups in Automated Personalization
- Experience Performance report (MVT)
- Location Contribution report (MVT)
- Analytics for Target (A4T) reporting
- Conversion rate
- Downloading data in a CSV file
- Reporting FAQ
- Recommendations
- Recommendations overview
- Introduction to Recommendations
- Plan and implement Recommendations
- Entities
- Criteria
- Design
- Activity
- Recommendations as an offer
- Frequently asked questions
- Recommendations Classic documentation
- Troubleshoot Target
- Target APIs
- Resources and Contact Information
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 around the globe. 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 in How Adobe Target works.
You can allowlist Target edge nodes, if desired.
The following list includes the current hosts:
-
CLIENTCODE.tt.omtrdc.net(where CLIENTCODE is your Target client ID)
-
mboxedge17.tt.omtrdc.net -
mboxedge21.tt.omtrdc.net -
mboxedge22.tt.omtrdc.net -
mboxedge26.tt.omtrdc.net -
mboxedge28.tt.omtrdc.net -
mboxedge29.tt.omtrdc.net -
mboxedge30.tt.omtrdc.net -
mboxedge31.tt.omtrdc.net -
mboxedge32.tt.omtrdc.net -
mboxedge34.tt.omtrdc.net -
mboxedge35.tt.omtrdc.net -
mboxedge36.tt.omtrdc.net -
mboxedge37.tt.omtrdc.net -
mboxedge38.tt.omtrdc.net