Journey Optimizer with Adobe Campaign v7 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.


Architecture

Reference architecture Journey Optimizer blueprint
IMPORTANT

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.


Prerequisites

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 v7

  • 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

Guardrails

Journey Optimizer Guardrails Product Link

Additional Journey Optimizer guardrails

  • Capping is available via API today to ensure that the destination system is not saturated to the point of failure. This means that messages that exceed the cap will be dropped completely and never sent. Throttling is not supported.
    • Max connections - maximum number of http/s connections a destination can handle
    • Max call count - maximum number of calls to be made in the periodInMs paramater
    • periodInMs - time in milliseconds
  • Segment membership initiated journeys can operate in two modes:
    • Batch segments (refreshed every 24hrs)
    • Streaming segments (<5mins qualification)
  • Batch segments – need to ensure you understand the daily volume of qualified users and ensure the destination system can handle the burst throughput per journey and across all journeys
  • Streaming segments – need to ensure the initial burst of profile qualifications can be handled along with the daily streaming qualifying volume per journey and across all journeys
  • Decision Management in not supported
  • Business events are not supported
  • Outbound integrations to 3rd-party systems
    • No support for a single Static IPs as our infrastructure is multi-tenant (must allow list all datacenter IPs)
    • Only POST and PUT methods are supported for custom actions
    • Authentication support: token | password | OAuth2
  • No ability to package and move individual components of Adobe Experience Platform or Journey Optimizer between various sandboxes. Must re-implement in new environments

Campaign (v7)

  • Execution instance of Message Center must be hosted by Adobe Managed Cloud Services
  • Needs to be on either v7 build >21.1
  • Messaging throughput
    • AC (v7) 50k per hour
  • AC (v7) only supports event initiated journey’s
    • No segment or segment membership initiated Journey’s
    • Read Audience and Business event based journey’s are not supported due to volume it can send to the execution instances
  • AC (v7) does not support Decision Management in messages
  • No throttling of outbound API calls made to Campaign

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 Experience Event class-based schemas for Adobe Campaign broadLog, trackingLog and non-deliverable addresses tables (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 Journey usage.

Sources/destinations

  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 v7

  • Messaging templates need to be configured with appropriate personalization context
  • For Campaign v7 - Export workflows need to configured to export the transactional messaging logs back to the Experience Platform. The recommendation is to run at most every 4hrs.

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

    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.


On this page