3rd-party Messaging blueprint

Last update: 2023-05-30
  • Created for:
  • Developer
    User

Demonstrates how Adobe Journey Optimizer can be utilized with 3rd party messaging systems to orchestrate and send personalized communications.


Architecture

Reference architecture Journey Optimizer blueprint

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

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
  • 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

3rd-party messaging system

  • Need to understand what load the system can support for transactional API calls
    • Number of calls allowed per second
    • Number of connections
  • Need to understand what authentication is required to make API calls
    • Auth type:  token | password | OAuth2 are supported via Journey Optimizer
    • Auth cache duration:  how long is the token valid?
  • If batch ingestion is only supported then needs to be streamed to a cloud storage engine like Amazon Kinesis or Azure Event Grid 1st
    • Data can be batched of these cloud storage engines and funneled into the 3rd-party
    • Any middleware required would be the responsibility of the customer or 3rd-party to provide

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 datasets in Experience Platform for data to be ingested.
  3. Add data usage labels in Experience Platform to the dataset for governance.
  4. 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 3rd party application

Mobile push configuration (optional as 3rd party may collect tokens)

  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 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

Previous page
Next page

On this page