Known Customer Activation Blueprint

Use offline attributes and events such as offline orders, transactions, CRM, or loyalty data, along with online behavior for online targeting and personalization.

Expanded identifiers with built in governance controls provide more opportunities to communicate with known customers. Activate audiences to known profile-based destinations such as email providers, social networks, and advertising destinations.

Additional detail is provided in the Audience and Profile Activation with Experience Cloud Applications Blueprint specific to integrations between Experience Platform and Experience Cloud Applications.

Use Cases

  • Audience targeting for known audiences on social and advertising destinations.
  • Online personalization with online and offline attributes.
  • Activate audiences to known channels, such as email and SMS.

Applications

  • Real-time Customer Data Platform
  • Audience Manager People Based destinations can also be leveraged for people based activation to Facebook, LinkedIn, and Google Customer Match.

Architecture

Known Customer Activation via Real-time Customer Data Platform

Reference architecture for the Known Customer Activation Blueprint

Known Customer Activation via Audience Manager People Based Destinations

Reference architecture for the Known Customer Activation Blueprint

Guardrails

Refer to the guardrails as outlined on the Audience and Profile Activation Overview page.

Implementation Steps for Real-time Customer Data Platform

  1. Create schemas for data to be ingested.
  2. Create datasets for data to be ingested.
  3. Configure the correct identities and identity namespaces on the schema to be sure that ingested data can stitch into a unified profile.
  4. Enable the schemas and datasets for profile.
  5. Ingest data into Experience Platform.
  6. Provision Real-time Customer Data Platform segment sharing between Experience Platform and Audience Manager for audiences defined in Experience Platform to be shared to Audience Manager.
  7. Create segments in Experience Platform. The system automatically determines whether the segment is evaluated as batch or streaming.
  8. Configure destinations for sharing of profile attributes and audience memberships to desired destinations.

Implementation Considerations

  • Sharing profile data to destinations requires that you include the specific identity value used by the destination in the destination payload. Any identity that is necessary for a target destination must be ingested into Platform and configured as an identity for the Real-time Customer Profile.

  • See the Audience and Profile Activation with Experience Cloud Applications Blueprint for additional details on sharing audiences from Real-time Customer Data Platform to Audience Manager, Analytics, Target, Campaign and Journey Optimizer.

Implementation Steps for Audience Manager People Based Destinations

  • For details on implementing Audience Manager see the following documentation.

  • For details on implementing People Based Destinations in Audience Manager see the following documentation.

On this page