Known Customer Personalization with Target
Use cases
- Online personalization with known customer data
- Landing page optimization
- Personalization based on prior product/content views, product/content affinity, environmental attributes, and demographics in addition to offline data such as transactions, loyalty and CRM data, and modeled insights
- Share and target audiences defined in Real-time Customer Data Platform on websites and mobile apps using Adobe Target
Applications
- Real-time Customer Data Platform
- Adobe Target
Reference documentation
Integration patterns
Integration Pattern
Capability
Pre-Requisites
Real-time segment evaluation on the Edge shared from Real-time Customer Data Platform to Target
- Evaluate audiences in real-time for same or next page personalization on the Edge.
- Any segments evaluated in streaming or batch fashion will also be projected to the Edge Network to be included in edge segment evaluation and personalization.
- Any segments evaluated in streaming or batch fashion will also be projected to the Edge Network to be included in edge segment evaluation and personalization.
- Web/Mobile SDK must be implemented or the Edge Network Server API.
- Datastream must be configured in Experience Edge with the Target and Experience Platform extension enabled.
- Target destination must be configured in Real-time Customer Data Platform Destinations.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
- Datastream must be configured in Experience Edge with the Target and Experience Platform extension enabled.
- Target destination must be configured in Real-time Customer Data Platform Destinations.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
Streaming and batch audience sharing from Real-time Customer Data Platform to Target via the Edge approach
- Share streaming and batch audiences from Real-time Customer Data Platform to Target through the Edge Network.
- Audiences evaluated in real-time require the Web SDK and Edge Network implementation.
- Audiences evaluated in real-time require the Web SDK and Edge Network implementation.
- Web/Mobile SDK or Edge API implementation of Target is not required for sharing streaming and batch RTCDP audiences to Target but is required to enable real-time edge segment evaluation.
- If using AT.js, only profile integration against the ECID identity namespace is supported.
- For custom identity namespace lookups on the Edge, the Web SDK/Edge API deployment is required, and each identity must be set as an identity in the identity map.
- Target destination must be configured in Real-time Customer Data Platform Destinations, only the default production sandbox in RTCDP is supported.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
- If using AT.js, only profile integration against the ECID identity namespace is supported.
- For custom identity namespace lookups on the Edge, the Web SDK/Edge API deployment is required, and each identity must be set as an identity in the identity map.
- Target destination must be configured in Real-time Customer Data Platform Destinations, only the default production sandbox in RTCDP is supported.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
Streaming and batch audience sharing from Real-time Customer Data Platform to Target and Audience Manager via the Audience Sharing Service Approach
- This integration pattern can be leveraged when additional enrichment from 3rd party data and audiences in Audience Manager is desired.
- Web/Mobile SDK is not required for sharing streaming and batch audiences to Target but is required to enable real-time edge segment evaluation.
- If using AT.js, only profile integration against the ECID identity namespace is supported.
- For custom identity namespace lookups on the Edge, the Web SDK/Edge API deployment is required, and each identity must be set as an identity in the identity map.
- Audience projection via audience sharing service must be provisioned.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
- Only audiences from the default production sandbox support the audience sharing core service.
- If using AT.js, only profile integration against the ECID identity namespace is supported.
- For custom identity namespace lookups on the Edge, the Web SDK/Edge API deployment is required, and each identity must be set as an identity in the identity map.
- Audience projection via audience sharing service must be provisioned.
- Integration with Target requires the same IMS Org as the Experience Platform instance.
- Only audiences from the default production sandbox support the audience sharing core service.
Implementation patterns
Known Customer Personalization is supported via several implementation approaches.
Implementation pattern 1 - Edge Network with Web/Mobile SDK or Edge Network API (Recommended Approach)
- Using the Edge Network with the Web/Mobile SDK. Real-time edge segmentation requires the Web/Mobile SDK or Edge API implementation approach.
- Refer to the Experience Platform Web and Mobile SDK Blueprint for the SDK based implementation.
- For use in the Mobile SDK the Adobe Journey Optimizer - Decisioning extension must be installed.
- Refer to the Edge Network Server API for an API based implementation of Adobe Target with Edge Profile.
Implementation pattern 2 - Application specific SDKs
Using traditional application-specific SDKs (for example, AT.js and AppMeasurement.js). Real-time Edge segment evaluation is not supported using this implementation approach. However streaming and batch audience sharing from Experience Platform hub are supported using this implemenation approach.
Refer to the Adobe Target Connector Documentation
Refer to the Experience Platform Web SDK Blueprint
Implementation considerations
- Any primary identity can be leveraged when utilizing implementation pattern 1 outlined above with the Edge Network and Web SDK.
- First login personalization with known customer data that was prior ingested into RTCDP requires that the personalization request has a primary identity which matches the known customer identity graph in the Real-time Customer Data Platform. If the primary ID is set to ECID or an identity that has not yet been stitched with the known customer profile, then it will take several minutes for the identity stitch to be realized on the edge and for edge personalization to include prior ingested known customer data.
- Edge profiles currently have a 14 day TTL. Hence if a user has not logged in or been active for 14 days on the edge, the profile on the edge may be expired, and thus the edge must fetch the profile from the hub to have the historic profile view to power personalization which includes prior ingested profile attributes and segments, this will result in personalization with the historic view of profiles happening on subsequent page views vs. the first login.
Related documentation
SDK documentation
Segmentation documentation
Tutorials
recommendation-more-help
blueprints-learn-help-blueprints