Batch Messaging and Adobe Experience Platform Blueprint

Execute scheduled and batch messaging campaigns using Adobe Experience Platform as a central hub for customer profiles and segmentation.

Use Cases

  • Scheduled email campaigns
  • Onboarding and re-marketing campaigns


  • Adobe Experience Platform
  • Adobe Campaign Classic or Standard

Integration Patterns

  • Adobe Experience Platform → Adobe Campaign Classic
  • Adobe Experience Platform → Adobe Campaign Standard


Reference architecture for the Batch Messaging and Adobe Experience Platform Blueprint


  • Supports Adobe Campaign single organizational unit deployments only
  • 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.
  • Segment membership realization from Experience Platform is latent for both batch (1 per day) and streaming (~5 minutes)

Real-time Customer Data Platform segment sharing to Adobe Campaign:

  • Recommendation of 20-segment limit
  • Activation is limited to every 24 hours
  • Only union schema attributes available for activation (no support for array/maps/experience events).
  • Recommendation of 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 or full segment exports are supported
  • File encryption is not supported
  • Adobe Campaign export workflows to run at most every 4 hrs
  • See profile and data ingestion guardrails for Experience Platform

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.

Mobile app deployment

  1. Implement Adobe Campaign SDK for Adobe Campaign Classic or Experience Platform SDK for Adobe Campaign Standard. If Experience Platform Launch is present, the recommendation is to use Adobe Campaign Classic or Adobe Campaign Standard extension with Experience Platform SDK.

Adobe Campaign

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

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).

On this page