- 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
Configure data collection
Follow the steps in the Data Collection diagram to ensure that all necessary tasks needed for data collection are executed in the correct sequence.
Click the images in this topic to expand to full screen.
The data layer is ready during page load or the data layer change after page load.
If you have already mapped data during the initialize SDK phase, you must execute the steps in this diagram if:
- Your data layer is augmented in any way on the same page and you want to send that additional data to Target
- You want to send product-catalog data to Target Recommendations
Collect data diagram
The step numbers in the following illustration correspond to the sections below.
Click the following links to navigate to the desired sections:
2.1: Configure data mapping
This step helps ensure that all the data that must be sent to Adobe Target is set.
See details
Prerequisites
- Data layer should be ready with all the data that must be sent to Target.
Readings
Actions
Use the targetPageParams() function to set all the required data that must be sent to Target.
Return to the diagram at the top of this page.
2.2: Link to entity attributes
Link to entity attributes to update the product catalog for Target Recommendations.
See details
Readings
Considerations
- An alternate way to pass entity attributes is to update the product catalog in the Target UI to use Recommendations product feeds.
- Passing entity attributes is applicable only on pages where product-catalog data is available in the data layer.
- Passing the
entity.event.detailsOnly=trueparameter in any call takes priority.
Return to the diagram at the top of this page.
2.3 Fire the Adobe Target Track API
This step helps ensure that all the data that must be sent to Target is sent.
See details
Prerequisites
- All data mapping must have been done using the targetPageParams function.
Readings
Actions
Use adobe.target.trackEvent() method to send all data that must be sent to Target.
Return to the diagram at the top of this page.
Proceed to Step 3: Render experiences
