Introduction

The integration enables streaming MoEngage campaign events and user actions to Adobe Experience Platform HTTP APIs via MoEngage Streams, creating unified customer profiles in Adobe Experience Platform (AEP). 

Key Features/Functionality

With this integration, you can:

• Send MoEngage campaign events (email opens, push notifications, SMS delivery) in real-time.
• Send user action events (app events, custom events, behavioral data) from MoEngage to AEP.
• Build unified customer profiles combining MoEngage engagement data with CRM, web analytics, and offline data.

Architecture and Adobe Audience Manager Integration

Use Cases

• Unified Customer View: Combine MoEngage campaign engagement (email opens, push clicks) with web behavior from Adobe Analytics and offline purchases from CRM to create complete customer profiles.
• Advanced Segmentation: Build segments like "Users who opened promotional email in last 7 days but haven't purchased" using both MoEngage engagement data and e-commerce transaction data.
• Cross-Channel Journey Orchestration: Trigger Adobe Journey Optimizer campaigns based on MoEngage campaign non-engagement (e.g., didn't open email → send SMS via different channel).
• Campaign Performance Analytics: Query historical MoEngage campaign events in Data Lake to analyze performance trends, A/B test results, and cohort behavior over time.
• Identity Graph Enrichment: Stitch MoEngage user IDs with Adobe ECID, CRM IDs, and email addresses to resolve identities across all customer touchpoints.

Step 1: Identify Your Identity Namespaces

Before you configure the integration, identify the identity namespaces to use for stitching MoEngage data with your existing customer profiles in AEP.

Step1.1: Review Existing Identity Namespaces

To review existing identity namespaces, perform the following steps:

1. Log in to Adobe Experience Platform.
2. Navigate to Identities → Browse.
3. Review your existing identity namespaces.
4. Identify the namespace(s) to use as primary and secondary identities.

Identity Namespace Requirements

Identity Type	Requirement	Examples	Notes
Primary Identity	Required	CRM ID, Loyalty ID, Email	Must exist in your AEP namespace. Share the identity symbol (e.g., lumaCrmId ) with MoEngage.
Secondary Identities	Optional but recommended	Email, Phone, Adobe ECID	Use standard Adobe namespaces (Email, Phone, ECID) when possible.
MoEngage User ID	Recommended	MoEngage User ID	If you want to track MoEngage's internal user ID, create a custom namespace with the symbol moengageUserId.

Step 1.2: Create a MoEngage User ID Namespace (Optional but Recommended)

If you want to include the internal MoEngage user ID as an identity in AEP, perform the following steps:

1. Click Create identity namespace.
2. Configure the following settings:
   • Display name: MoEngage User ID
   • Identity symbol: moengageUserId
   • Type: Cross-device ID
3. Click Create.

Step 2: Create an XDM Schema

The XDM schema defines the structure of MoEngage event data in AEP. You can use the recommended schema structure or customize it based on your requirements.

Use the Recommended Schema Structure (Out-of-the-Box)

MoEngage provides a sample schema structure that works out-of-the-box with MoEngage Streams. If you replicate this structure, the integration will work with minimal configuration.

Sample Schema Structure

Create an XDM ExperienceEvent schema with the following field structure:

Field Path	Type
_id	String
timestamp	DateTime
eventType	String
eventMergeId	String
producedBy	String
identityMap	Map
_{tenant}.source	String
_{tenant}.eventName	String
_{tenant}.eventCode	String
_{tenant}.appName	String
_{tenant}.campaignId	String
_{tenant}.campaignName	String
_{tenant}.campaignType	String
_{tenant}.campaignChannel	String
_{tenant}.eventAttributesJson	Map
_{tenant}.userAttributesJson	Map
_{tenant}.deviceAttributesJson	Map

Note: _{tenant} represents your organization's tenant namespace (for example, _yourorgname).

Step 2.2: Create the Schema in AEP

To create the schema in AEP, perform the following steps:

1. Navigate to Schemas → Browse.
2. Click Create schema → XDM ExperienceEvent.
3. In the Name box, type MoEngage Events.
4. Ensure the following standard field groups are present:
   • XDM ExperienceEvent
   • IdentityMap
5. Create a custom field group named MoEngage Event Details.
6. Add the fields listed in the table above under your tenant namespace.
7. To enable the schema for profiles, turn the Profile toggle on.
8. Click Save.

Step 2.3: Customize the Schema Structure

If you want to customize the schema fields (different field names, additional fields, different structure), perform the following steps:

1. Create your custom XDM ExperienceEvent schema with your desired field structure.
2. Ensure that you include the following required fields.
   • _id (required for deduplication)
   • timestamp (required)
   • identityMap (required for identity resolution)
   • eventType (recommended)
3. Add custom fields for MoEngage data under your tenant namespace.
4. To enable the schema for profiles, turn the Profile toggle on.

warning

Important: Custom Schema Requirements If you customize the schema structure, you will need to create your own field mapping configuration to match your custom field names. Follow the manual mapping steps in Step 5, Option B to test locally before requesting MoEngage support to generate the mapping CSV file.

Step 2.4: Download Schema JSON

After you create and save the schema, download the schema JSON for reference:

1. Open your schema in the Schema Editor.
2. Click the More (three dots) menu in the upper-right corner.
3. Select Copy schema structure or Download JSON.
4. Save this file. You might need it when you coordinate with MoEngage support.

Step 2.5: Note Your Schema Details

After creating the schema, note down the following details:

• Schema ID: You can find it in the schema details (for example, https://ns.adobe.com/{TENANT}/schemas/{SCHEMA_ID})
• Tenant ID: Your organization's tenant namespace (for example, _yourorgname).

Step 3: Create a Dataset

Datasets store data that conforms to your XDM schema. To create a dataset, perform the following steps:

1. Navigate to Datasets → Browse.
2. Click Create dataset from schema.
3. Select the MoEngage Events schema that you created.
4. Configure the dataset  with the following information:
   • Name: MoEngage Event Data
   • Description: Campaign events and user actions from the MoEngage Streams API.
5. Click Finish.
6. Open the new dataset and turn the Profile toggle on to enable it for the Real-Time Customer Profile.

Save the Dataset ID: This is required for the HTTP API configuration (locate  in the dataset details, for example, 690da33230e4cd0adff86e57).

Step 4: Configure the HTTP API Streaming Source

The HTTP API source provides a streaming endpoint to send data to AEP.

Step 4.1: Choose an Authentication Method

Before you create the HTTP API source connection, choose one of the following authentication methods:

1. No Authentication
2. OAuth 2.0 Authentication

Step 4.1: Create the HTTP API Source Connection

To create the HTTP API source connection, perform the following steps:

1. Navigate to Sources → Catalog.
2. In the Streaming category, find HTTP API.
3. Click Add data.
4. Configure the account details:
   • Account name: MoEngage Streams Connection.
   • Description: HTTP API endpoint for streaming MoEngage events.
   • Authentication: Choose the method you had selected earlier.
5. Click Connect to source.

Step 4.2: Set Up OAuth 2.0 Credentials (If Selected)

If you selected Authenticated in the previous step, you must set up OAuth 2.0 credentials through Adobe Developer Console and perform the following steps:

Step 4.3: Create the Service Account Integration

To create the service account integration, perform the following steps:

1. Navigate to Adobe Developer Console.
2. Select your organization or create a new project.
3. Click Add to Project → API.
4. Select Adobe Experience Platform from the API list.
5. Choose OAuth Server-to-Server credential type.
6. Configure the required product profiles and permissions.
7. Click Save configured API.

Copy OAuth Credentials

After creating the integration, copy the following credentials from the Adobe Developer Console:

Step 4.4: Configure Dataflow

To configure the dataflow, perform the following steps:

1. In the dataflow configuration enter the following details:
   • Dataflow name: MoEngage Event Stream.
   • Description: Streams MoEngage campaign and user events to AEP.
     Note: Do NOT select XDM compatible.
2. Select dataset: MoEngage Event Data
3. Click Next to proceed to mapping.

Step 5: Configure Field Mapping

After you create the HTTP API source, AEP displays a mapping interface where you can map MoEngage fields to your XDM schema. Before proceeding with field mapping, you have to either share your schema structure with MoEngage or generate a test payload yourself.

Step 5.1: Prepare a Schema Sample

Generate a sample payload based on your schema structure to validate the mapping configuration:

1. Using the schema JSON you downloaded in Step 2, generate a sample event payload that includes:
   • All required XDM fields (_id, timestamp, identityMap)
   • Your custom tenant fields for MoEngage data
   • Identity mappings for your configured namespaces
2. Share with MoEngage: Send this sample payload along with your schema JSON to MoEngage support. They will generate the appropriate mapping CSV file for your schema structure.

Complete Dataflow Setup

After configuring the dataflow, you'll receive a streaming endpoint URL that looks like:

https://dcs.adobedc.net/collection/{UNIQUE_COLLECTION_ID}

Step 6: Test with Postman

Before enabling MoEngage Streams, test the streaming endpoint with sample data to ensure proper schema validation and data ingestion.

Step 6.1: Prepare the Test Payload

Create a test payload in the MoEngage Streams format:

{
  "app_name": "Your App Name",
  "source": "MOENGAGE",
  "moe_request_id": "test_request_001",
  "id": "test_event_001",
  "time": 1731421200,
  "event_uuid": "unique_event_id_001",
  "event_source": "MOENGAGE",
  "event_name": "Email Sent",
  "event_code": "MOE_EMAIL_SENT",
  "event_type": "CAMPAIGN_EVENT",
  "identities": {
    "externalId": "customer_123",
    "moengageUserId": "moe_user_456",
    "email": "test@example.com",
    "phone": "+1234567890"
  },
  "event_attributes": {
    "campaign_id": "camp_001",
    "campaign_name": "Welcome Campaign",
    "campaign_type": "Event Trigger",
    "campaign_channel": "Email"
  },
  "user_attributes": {
    "subscription_tier": "premium",
    "preferred_language": "en"
  },
  "device_attributes": {
    "platform": "iOS",
    "os_version": "16.2"
  }
}

Step 6.2: Send a Test Request in Postman

To send a test request in postman, perform the following steps:

1. Open Postman and create a new POST request.
2. In the URL box, enter: {YOUR_STREAMING_ENDPOINT}?syncValidation=true.
3. Add the following header Content-Type: application/json.
4. Paste the test payload in the Body (RAW JSON).
5. Update the identities section with your actual identity values.
6. Click Send.

Expected Response

Successful ingestion returns:

{
  "inletId": "{INLET_ID}",
  "xactionId": "{TRANSACTION_ID}",
  "receivedTimeMs": 1731421250000,
  "synchronousValidation": {
    "status": "pass"
  }
}

Step 6.3: Verify Data in AEP

1. Navigate to Datasets → MoEngage Event Data.
2. Click Preview dataset.
3. Verify that the test event appears with the correct field values.
4. Check Profiles → Browse to verify profile creation or update.

Step 7: Share Details with MoEngage for Streams Setup

After you have successfully tested the integration, provide the following details to MoEngage to enable Streams for your workspace.

Information to Share with MoEngage

OAuth 2.0 Credentials Details (If Using OAuth)

If you configured OAuth 2.0 authentication in Step 4, provide the following credentials to MoEngage:

Submit Integration Request

Contact your MoEngage Customer Success Manager and share all the details mentioned above. MoEngage performs the following:

1. Review your configuration and test payload.
2. Generate or validate the mapping CSV file for your schema (if not provided).
3. Configure Streams to send data in the correct format.
4. Set up identity mappings based on your namespace configuration.
5. Enable Streams for your workspace.
6. Notify you once the integration is live.