3rd-party Messaging blueprint
Demonstrates how Adobe Journey Optimizer can be utilized with 3rd party messaging systems to orchestrate and send personalized communications.
Architecture
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
3rd-party Messaging Application
- Must support REST API calls for sending transactional payloads
Guardrails
Journey Optimizer Guardrails Product Link
Guardrails and End to End Latency Guidance
Implementation steps
Adobe Experience Platform
Schema/datasets
- Configure individual profile, experience event, and multi-entity schemas in Experience Platform, based on customer-supplied data.
- Create datasets in Experience Platform for data to be ingested.
- Add data usage labels in Experience Platform to the dataset for governance.
- Create policies that enforce governance on destinations.
Profile/identity
- Create any customer-specific namespaces.
- Add identities to schemas.
- Enable the schemas and datasets for Profile.
- Set up merge policies for differing views of Real-time Customer Profile (optional).
- Create segments for Journey usage.
Sources/destinations
- Ingest data into Experience Platform using streaming APIs & source connectors.
Journey Optimizer
- 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 3rd party application
Mobile push configuration (optional as 3rd party may collect tokens)
-
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
-
For more information follow the Adobe Journey Optimizer Mobile Guide
Related documentation
recommendation-more-help
045b7d44-713c-4708-a7a6-5dea7cc2546b