Adobe Journey Optimizer is a purpose built system for marketing teams to react in real-time to customer behaviors and meet them where they are at. Data management capabilities have been moved to the Adobe Experience Platform allowing marketing teams to focus on what they do best: which is creating world class customer journey’s and personalized conversations. This blueprint outlines the technical capabilities of the application and provides a deep dive into the various architectural components that make up Adobe Journey Optimizer.
Use cases
Triggered messages
Welcome and registration confirmations
Shopping cart and application form abandons
Location triggered messages
In-stadium experiences
Travel and hospitality pre-arrival and stay experiences
Demonstrates how Adobe Journey Optimizer can be utilized with 3rd party messaging systems to orchestrate and send personalized communications
Deliver 1:1 in the moment personalized communications to customers as they interact with your brand or company
Considerations:
3rd party system has to support bearer tokens for authentication
No support for static IPs due to multi-tenant architecture
Be aware of architectural constraints on 3rd party system when it comes to API calls per second. May be a need for the customer to buy additional volume from the 3rd party vendor to support volume coming from Journey Optimizer
Does not support Decision Management in messages or payloads
Shows how you can use Adobe Journey Optimizer to orchestrate 1:1 experiences utilizing the Real-Time Customer Profile and leverage the native Adobe Campaign transactional messaging system to send the message
Leverage the Real-Time Customer Profile and power of Journey Optimizer to orchestrate in the moment experiences while utilizing the native real-time messaging capabilities of Adobe Campaign to do the last mile communication
Considerations:
Campaign application must be on either v7 build >21.1 or v8
Messaging throughput
Campaign v7 - up to 50k per hour
Campaign v8 - up to 1M per hour
Campaign Standard - up to 50k per hour
No throttling is performed so use cases need technical vetting by an Enterprise Architect
No support for utilizing Decision Management in message sent by Campaign
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
Email
Must have a subdomain ready to be used for message sending
Subdomain can either be fully delegated to Adobe (recommended) or CNAMEs can be used to point to Adobe-specific DNS servers (custom)
Google TXT record is needed for each subdomain to ensure good deliverability
Mobile Push
Customer must have a mobile developer available to build the app
Please be aware of these not listed in the link above:
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
Natively supports Decision Management in messages only (no custom actions)
Message types supported:
Email
Push (FCM / APNS)
Custom Actions (via Rest API)
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 via user/pass or authorization token
No ability to package and move individual components of Adobe Experience Platform or Journey Optimizer between various sandboxes. Must re-implement in new environments
Configure your Experience Platform data source 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.
Mobile push configuration
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:
Adobe Journey Optimizer
Adobe Experience Platform Edge Network
Identity for Edge Network
Mobile Core
Ensure you have a dedicated datastream for mobile app deployments vs. web deployments
