Triggered Messaging and Adobe Experience Platform Blueprint

Execute triggered messages and experiences using Adobe Experience Platform as a central hub of streaming data, customer profiles, and segmentation.

Use Cases

• Triggered messages
• Registration confirmations
• Shopping cart and application form abandons
• Location triggered messages

Architecture

Integration Patterns

• Adobe Experience Platform -> Journey Orchestration

Prerequisites

• Adobe Experience Platform
• Journey Orchestration

Guardrails

Journey Orchestration

• See link for more details on limitations
• Capping is available through API setup to ensure that the destination system is not saturated to the point of failure. Capping means that messages that exceed the cap are dropped completely and never sent. Throttling is still 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 parameter
  • periodInMs: Time in milliseconds
• Segment membership initiated journeys can operate in two modes:
  • batch segments (refreshed every 24 hours)
  • Streaming segments (<5-minute qualification)
• Batch segments: Ensure you understand the daily volume of qualified users and ensure that the destination system can handle the burst throughput per journey and across all journeys
• Streaming segments: Ensure that the initial burst of profile qualifications can be handled along with the daily streaming qualifying volume per journey and across all journeys
• Final destination must support REST API & JSON payload
• Does not support Offer Decisioning currently
• See profile and data ingestion guardrails for Experience Platform

Adobe Campaign Standard

• Can only support 14 tps (50k per hour) in throughput
• Segment-membership-initiated journeys are not supported
• Reaction events to transactional message open/clicks are supported within Journey Orchestration.
• Transactional messaging logs are not natively synced to Experience Platform currently, requiring a manual configuration. It is recommended to export logs at most every four hours.

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 Adobe Campaign schemas for the following: broadLog, trackingLog, non-deliverable addresses, and profile preferences (optional).
3. Add data usage labels to the dataset for governance.
4. Create policies to enforce governance on destinations.

Profile/Identity

1. Create any customer-specific namespaces.
2. Add identities to schemas.
3. Enable schemas and datasets for profile.
4. Set up merge rules for differing views of Real-time Customer Profile (optional).
5. Create segments for Adobe Campaign usage.

Sources/Destinations

1. Ingest data into Experience Platform using streaming APIs & source connectors.
2. Configure Azure blob storage destination for use with Adobe Campaign.

Mobile app deployment

1. Implement Adobe Campaign SDK for Adobe Campaign Classic or Experience Platform SDK for Adobe Campaign Standard. If Experience Platform Launch is present, the recommendation is to use Adobe Campaign Classic or Adobe Campaign Standard extension with Experience Platform SDK.

Journey Orchestration

1. Streaming data used to initiate a customer journey must be configured within Journey Orchestration 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.

Adobe Campaign Standard

1. Configure messaging templates with appropriate personalization settings.
2. Configure export workflows export transactional messaging logs. Recommendation is to run at most every four hours.

Related Documentation

• Adobe Experience Platform documentation
• Journey Orchestration documentation
• Adobe Campaign Classic documentation
• Adobe Campaign Standard documentation
• Experience Platform Launch documentation
• Experience Platform Mobile SDK documentation