Real-time, streaming, and batch audience sharing to Adobe Target
Architecture
Sequence Detail
Overview Architecture
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 application specific 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
Personalization at Scale Insights, Intelligence and Impact
Adobe Customer Success Webinars
Tuesday, Apr 1, 3:00 PM UTC
Adobe Target innovations, including Gen AI, and best practices on AI-powered personalization and experimentation at scale.
RegisterThe True Cost of a Failed Implementation
A failed implementation isn’t just an inconvenience — it costs real revenue. Poor execution and misaligned tools disrupt pipelines,...
Wed, Mar 19, 2:00 PM PDT (9:00 PM UTC)
Put the Customer at the Center and Build Relationships That Last a Lifetime
First impressions last a lifetime. Great first impressions feel personal, connected, and relevant right from the start. From the first...
Wed, Mar 19, 2:30 PM PDT (9:30 PM UTC)
Connect with Experience League at Summit!
Get front-row access to top sessions, hands-on activities, and networking—wherever you are!
Learn more