Journey Optimizer with Adobe Campaign v8 blueprint

Demonstrates how Adobe Journey Optimizer can be used with Adobe Campaign to natively send messages by utilizing the real-time messaging server in Campaign.


Reference architecture Journey Optimizer blueprint {modal="regular"}

Using both Journey Optimizer and Campaign to send messages independently of each other is possible but has some technical considerations that need to be thought through. If you wish to pursue this route please work with your Pre-Sales Enterprise Architect to ensure that you have an understanding of what will be required to support the implementation.


Review the following prerequisites for each application.

Adobe Experience Platform

  • Schemas and datasets must be configured in the system before you can configure Journey Optimizer data sources
  • For Experience Event class-based schemas add 'Orchestration eventID field group when you want to have an event triggered that is not a rule-based event
  • For Individual Profile class-based schemas add the ‘Profile test details’ field group to be able to load test profiles for use with Journey Optimizer
  • Journey Optimizer and Campaign are provisioned in the same IMS Org

Campaign v8

  • Execution instance of the real-time messaging service (i.e Message Center) must be hosted by Adobe Managed Cloud Services
  • All message authoring is done within the Campaign instance itself


Implementation steps

Follow the implementations for each application described below.

Adobe Experience Platform


  1. Configure individual profile, experience event, and multi-entity schemas in Experience Platform, based on customer-supplied data.
  2. (Optional) Create Experience Event class-based schemas for Adobe Campaign broadLog, trackingLog and non-deliverable addresses tables.
  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.


  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 Journey usage.


  1. Ingest data into Experience Platform using streaming APIs & source connectors.

Journey Optimizer

  1. Configure your Experience Platform datasource and determine what fields should be cached as part of the profileStreaming data used to initiate a customer journey must be configured within Journey Optimizer first to get an orchestration ID. This orchestration ID is then supplied to the developer to use with ingestion.
  2. Configure external data sources.
  3. Configure custom actions for Campaign instance.

Campaign v8

  • Messaging templates need to be configured with appropriate personalization context.
  • For Campaign standard: Export workflows need to configured to export the transactional messaging logs back to the Experience Platform. The recommendation is to run at most every four hours.
  • For Campaign v8.4 it is possible to leverage Adobe Campaign Managed Services Source Connector in Experience Platform to sync delivery and tracking events from Campaign into Experience Platform. Refer to the Source Connector documentation for details.

Mobile push configuration (optional)

  1. Implement Experience Platform Mobile SDK to collect push tokens and login information to tie back to known customer profiles.

  2. Leverage Adobe Tags and create a mobile property with the following extension:

    • Adobe Journey Optimizer | Adobe Campaign Classic | Adobe Campaign Standard
    • Adobe Experience Platform Edge Network
    • Identity for Edge Network
    • Mobile Core
  3. Ensure you have a dedicated datastream for mobile app deployments vs. web deployments.

  4. For more information follow the Adobe Journey Optimizer Mobile Guide.

    note important
    Mobile tokens may need to be collected in both Journey Optimizer and Campaign if there is desire send real-time communications via Journey Optimizer and batch push notifications via Campaign. Campaign v8 requires the exclusive use of the Campaign SDK for capturing push tokens.