- 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
- Target welcome kit overview
- Chapter 1: Introduction
- Chapter 2: Target at a glance
- Chapter 3: Develop your testing and 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 Target works
- Training and certification
- Training videos for 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
- Adobe Experience Platform Web SDK implementation
- at.js implementation
- On-device decisioning
- 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 (legacy)
- 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 Target with the Experience Cloud
- Adobe Analytics as the reporting source for Target (A4T)
- A4T overview
- Before you implement
- Analytics for Target implementation
- User permission requirements
- Create an activity that uses Analytics as the reporting source
- A4T support for Auto-Allocate and Auto-Target activities
- 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 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 the Target 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
Implement Target using Adobe Platform Launch
Adobe Experience Platform Launch is the next-generation tag management platform from Adobe and is the preferred method to implement Adobe Target. Platform Launch gives customers a simple way to deploy and manage the analytics, marketing, and advertising tags necessary to power relevant customer experiences.
Implement Target using Platform Launch
The following table lists the various sources where you can get more information about Platform Launch:
| Resource | Details |
|---|---|
| Implementing Target using the Adobe Target Extension Tutorial | This tutorial provides step-by-step instructions to implement Target in a website with Platform Launch. Topics include adding the at.js JavaScript library, firing the global mbox, adding parameters, and integrating with other solutions. This article is part of a larger tutorial that shows you how to implement Platform Launch, and other Adobe Experience Cloud solutions. |
| Adobe Platform Launch Documentation | Information about deploying and managing the analytics, marketing, and advertising tags necessary to power relevant customer experiences. |
| Adobe Target Extension Documentation | Information about implementing Target using Platform Launch. |
Advantages of implementing at.js using the Target Platform Launch extension
The following advantages apply only if you use Platform Launch to implement at.js. For this reason, Adobe strongly suggests that you use Platform Launch rather than a manual implementation of at.js.
- Solves Adobe Analytics and Target race condition: Because the Analytics call could be fired before the Target call, the Target call is not stitched to the Analytics call. This sequencing can lead to incorrect data. Starting with 0.6.0, the Platform Launch extension ensures that the Analytics beacon call waits until the Target call completes, successfully or not. Using Platform Launch solves the data inconsistency customers can experience when implementing manually.
- Prevents incorrect redirect offer handling: If you have Target and Analytics on the page, and there is a redirect offer executed by Target, you can experience a situation in which the Analytics tracker fires a request when it shouldn’t (because the user is being redirected to a different URL). If you implement Target and Analytics via Platform Launch, you’ll not experience this issue. Using Platform Launch, Target instructs Analytics to abort the Analytics beacon request.
Resources on adobe.com
Resources
Adobe Account
Change region
Copyright © 2021 Adobe. All Rights Reserved.
