ÃÛ¶¹ÊÓƵ

DocumentationTutorialsBlueprints

Real-Time Customer Data Platform with Campaign integration pattern

Last update: Mon Mar 25 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Developer
  • User

Showcases how the ÃÛ¶¹ÊÓƵ Experience Platform and its Real-Time Customer Profile and centralized segmentation tool can be utilized with ÃÛ¶¹ÊÓƵ Campaign to deliver personalized conversations.

Applications

  • ÃÛ¶¹ÊÓƵ Experience Platform Real-Time Customer Data Platform
  • ÃÛ¶¹ÊÓƵ Campaign v7 or Campaign Standard

Architecture

Reference architecture for the Batch Messaging and ÃÛ¶¹ÊÓƵ Experience Platform integration pattern {modal="regular"}

Prerequisites

  • Experience Platform and Campaign are recommended to be provisioned in the same IMS Org and be utilizing ÃÛ¶¹ÊÓƵ Admin Console for user access. This also ensures that customers can utilize the solution switcher from within the marketing UI

Guardrails

The following sections describe the guardrails for this integration.

ÃÛ¶¹ÊÓƵ Campaign

  • Only supports ÃÛ¶¹ÊÓƵ Campaign single organizational unit deployments
  • ÃÛ¶¹ÊÓƵ Campaign is source of truth for all active profiles meaning profiles must exist in ÃÛ¶¹ÊÓƵ Campaign and new profiles should not be created based on Experience Platform segments.
  • Campaign export workflows to run at most every 4hrs
  • XDM schema and datasets for ÃÛ¶¹ÊÓƵ Campaign broadLog, trackingLogs and non-deliverable addresses are not out of the box and must be designed and built

Real-Time Customer Data Platform segment sharing

Implementation steps

The following sections describe implementations steps for each application.

ÃÛ¶¹ÊÓƵ Experience Platform

Schema/datasets

  1. Configure individual profile, experience event, and multi-entity schemas in Experience Platform, based on customer-supplied data.
  2. Create ÃÛ¶¹ÊÓƵ Campaign schemas for broadLog, trackingLog, non-deliverable addresses, and profile preferences (optional).
  3. Create datasets in Experience Platform for data to be ingested.
  4. Add data usage labels in Experience Platform to the dataset for governance.
  5. 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 ÃÛ¶¹ÊÓƵ Campaign usage.

Sources/destinations

  1. Experience Platform and Campaign Standard Sources and Desintations
  2. Experience Platform and Campaign v7 Sources and Desintations
  3. Ingest data into Experience Platform using streaming APIs & source connectors.
  4. Configure Azure blob storage destination for use with ÃÛ¶¹ÊÓƵ Campaign.

ÃÛ¶¹ÊÓƵ Campaign

  1. Configure schemas for profile, lookup data, and relevant delivery personalization data.
IMPORTANT
It’s critical to understand at this point what the data model is within Experience Platform for profile and event data so you know what data will be required in ÃÛ¶¹ÊÓƵ Campaign.

Import workflows

  1. Load and ingest simplified profile data onto ÃÛ¶¹ÊÓƵ Campaign sFTP.
  2. Load and ingest orchestration and messaging personalization data onto ÃÛ¶¹ÊÓƵ Campaign sFTP.
  3. Ingest Experience Platform segments from Azure blob via workflows.

Export workflows

  1. Send ÃÛ¶¹ÊÓƵ Campaign logs back to Experience Platform via workflows every four hours (broadLog, trackingLog, non-deliverable addresses).
  2. Send profile preferences back to Experience Platform via consulting-built workflows every four hours (optional).

Mobile push configuration

  • Two supported approaches for integrating with mobile devices for push notifications:

    • Experience Platform Mobile SDK
    • Campaign Mobile SDK

  • Experience Platform Mobile SDK route:

    • Leverage ÃÛ¶¹ÊÓƵ Tags and the Campaign Classic extension for setting up your integration with the Experience Platform Mobile SDK
    • Need a working knowledge of ÃÛ¶¹ÊÓƵ Tags and data collection
    • Need mobile development experience with push notifications in both Android and iOS to deploy the SDK, integrate with FCM (Android) and APNS (iOS) to get push token, configure your app to receive push notifications and handle push interactions

  • Campaign Mobile SDK

    • See the
IMPORTANT
If you deploy the Campaign SDK and are working with other Experience Cloud applications they will require the use of the Experience Platform Mobile SDK for data collection. This will create duplicate client side calls on the device.
recommendation-more-help
045b7d44-713c-4708-a7a6-5dea7cc2546b