Real-Time CDP with Adobe Campaign Integration Pattern

Showcases how the Adobe Experience Platform and its Real-Time Customer Profile and centralized segmentation tool can be utilized with Adobe Campaign to deliver personalized conversations.


Applications

  • Adobe Experience Platform Real-Time CDP
  • Adobe Campaign v7 or Campaign Standard

Architecture

Reference architecture for the Batch Messaging and Adobe Experience Platform Integration Pattern

Prerequisites

  • Experience Platform and Campaign are recommended to be provisioned in the same IMS Org and be utilizing Adobe Admin Console for user access. This also ensures that customers can utilize the solution switcher from within the marketing UI

Guardrails

Adobe Campaign

  • Only supports Adobe Campaign single organizational unit deployments
  • Adobe Campaign is source of truth for all active profiles meaning profiles must exist in Adobe Campaign and new profiles should not be created based on Experience Platform segments.
  • Campaign export workflows to run at most every 4hrs
  • XDM schema and datasets for Adobe Campaign broadLog, trackingLogs and non-deliverable addresses are not out of the box and must be designed and built

Experience Platform CDP segment sharing

  • Recommendation of 20 segment limit
  • Activation is limited to every 24hrs
  • Only union schema attributes available for activation (no support for array/maps/experience events)
  • Recommendation on no more than 20 attributes per segment
  • One file per segment of all profiles with “realized” segment membership OR if segment membership is added as an attribute in the file both “realized” and “exited” profiles
  • Incremental and full segment exports are supported
  • File encryption is not supported

Implementation Steps

Adobe Experience Platform

Schema / Datasets

  1. Configure individual profile, experience event, and multi-entity schemas in Experience Platform, based on customer-supplied data.
  2. Create Adobe Campaign schemas for broadLog, trackingLog, non-deliverable addresses, and profile preferences (optional).
  3. Create datasets in Experience Platform for data to be ingested.
  4. Add data usage labels in Experience Platform to the dataset for governance.
  5. Create policies that enforce governance on destinations.

Profile / Identity

  1. Create any customer-specific namespaces.
  2. Add identities to schemas.
  3. Enable the schemas and datasets for Profile.
  4. Set up merge policies for differing views of Real-time Customer Profile (optional).
  5. Create segments for Adobe Campaign usage.

Sources / Destinations

  1. Ingest data into Experience Platform using streaming APIs & source connectors.
  2. Configure Azure blob storage destination for use with Adobe Campaign.

Adobe Campaign

  1. Configure schemas for profile, lookup data, and relevant delivery personalization data.
IMPORTANT

It’s critical to understand at this point what the data model is within Experience Platform for profile and event data so you know what data will be required in Adobe Campaign.

Import workflows

  1. Load and ingest simplified profile data onto Adobe Campaign sFTP.
  2. Load and ingest orchestration and messaging personalization data onto Adobe Campaign sFTP.
  3. Ingest Experience Platform segments from Azure blob via workflows.

Export workflows

  1. Send Adobe Campaign logs back to Experience Platform via workflows every four hours (broadLog, trackingLog, non-deliverable addresses).
  2. Send profile preferences back to Experience Platform via consulting-built workflows every four hours (optional).

Mobile Push Configuration

  • Two supported approaches for integrating with mobile devices for push notifications:

    • Experience Platform Mobile SDK
    • Campaign Mobile SDK
  • Experience Platform Mobile SDK route:

    • Leverage Adobe Tags and the Campaign Classic extension for setting up your integration with the Experience Platform Mobile SDK
    • Need a working knowledge of Adobe Tags and data collection
    • Need mobile development experience with push notifications in both Android and iOS to deploy the SDK, integrate with FCM (Android) and APNS (iOS) to get push token, configure your app to receive push notifications and handle push interactions
  • Campaign Mobile SDK

    • Please follow the [Campaign SDK documentation](Campaign Mobile SDK
      Please follow the deployment documentation outlined here)
    IMPORTANT

    If you deploy the Campaign SDK and are working with other Experience Cloud applications they will require the use of the Experience Platform Mobile SDK for data collection. This will create duplicate client side calls on the device.

On this page