Activation with Online & Offline Data Blueprint

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

Activate audiences to known profile-based destinations such as email providers, social networks, and advertising destinations.

The Activation with online and offline data blueprint aligns closely with the Audience and Profile Activation with Experience Cloud Applications Blueprint. 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.


  • Adobe Experience Platform
  • Real-time Customer Data Platform


Activation with Online & Offline data with destinations

Reference architecture for the Online/Offline Audience Activation Blueprint


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

Implementation Steps

  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.

  • For activation scenarios where audiences are shared from Experience Platform to Audience Manager the following identities are shared automatically: IDFA, GAID, AdCloud, Google, ECID, EMAIL_LC_SHA256. Currently, customer namespaces are not shared. The audiences from Experience Platform can be shared through Audience Manager destinations when the required destination identities are included in the Real-time Customer Profile, or where identities in the Real-time Customer Profile can be related to the required destination identities that are linked in Audience Manager.

On this page