ÃÛ¶¹ÊÓƵ

DocumentationTutorialsBlueprints

Web/Mobile Personalization with known customer data blueprint

Last update: Fri Jun 14 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer
  • User

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 ÃÛ¶¹ÊÓƵ Target.

Applications

  • Real-time Customer Data Platform
  • ÃÛ¶¹ÊÓƵ Target
  • ÃÛ¶¹ÊÓƵ Audience Manager (optional): Adds third-party audience data
  • ÃÛ¶¹ÊÓƵ Analytics or Customer Journey Analytics(optional): Adds the ability to build segments based on historical customer and behavioral data with fine grained segmentation

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.
  • In addition, 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.
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.
  • Web/Mobile SDK or Edge API implementation of Target is not required for sharing of streaming and batch RTCDP audiences to Target though it is required to enable real-time edge segment evaluation outlined above.
  • 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 of streaming and batch audiences to Target though it 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.

Real-time, streaming, and batch audience sharing to ÃÛ¶¹ÊÓƵ Target

Architecture

Reference architecture for the Online/Offline Web Personalization Blueprint {modal="regular"}

Sequence Detail

Reference architecture for the Online/Offline Web Personalization Blueprint {modal="regular"}

Overview Architecture

Reference architecture for the Online/Offline Web Personalization Blueprint {modal="regular"}

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)

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 ÃÛ¶¹ÊÓƵ Target Connector Documentation
Refer to the application specific SDK Blueprint

Implementation considerations

Identity pre-requisites

  • Any primary identity can be leveraged when utilizing implementation pattern 1 outlined above with the Edge Network and Web SDK. First login personalization requires the personalization request set primary identity match the primary identity of the profile from Real-time Customer Data Platform.

SDK documentation

Segmentation documentation

Tutorials

recommendation-more-help
045b7d44-713c-4708-a7a6-5dea7cc2546b