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.
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.
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
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
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
Execution instance of Message Center must be hosted by Adobe Managed Cloud Services
AC (v8) up to 1M per hour based on package
AC (v8) does not support Decision Management in messages
No throttling of outbound API calls made to Campaign
With 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 additional details. Link
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
Configure external data sources
Configure custom actions for Campaign instance
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 4hrs.
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 additional details. Link
Mobile push configuration (optional)
Implement Experience Platform Mobile SDK to collect push tokens and login information to tie back to known customer profiles
Leverage Adobe Tags and create a mobile property with the following extension:
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.