This page is part of the Customer.io documentation. For the complete documentation index, see llms.txt.

10

MoEngage Destination

About this integration

MoEngage is an AI-driven platform that helps you personalize customer interactions, enhance engagement, increase retention, and boost lifetime value. This integration seamlessly sends user data and user journey information from our sources direclty to MoEngage, to target your audience and manage campaigns.

Use cases

• Sync customer profiles to MoEngage so you can use MoEngage’s segmentation and campaign tools with up-to-date customer data. When someone signs up or updates their profile, their user record in MoEngage updates automatically.
• Track customer behavior in MoEngage by sending events like purchases, page views, or feature usage. MoEngage uses these events to power push notifications, in-app messages, and other engagement campaigns.
• Unify your engagement data across Customer.io and MoEngage. If you use MoEngage for mobile engagement (push, in-app) and Customer.io for other channels, this integration keeps both systems working with the same customer data.
• Trigger MoEngage campaigns based on events from your data pipeline. For example, trigger a push notification campaign in MoEngage when a user completes a purchase or abandons a cart.

Getting started

MoEngage operates in multiple regions. Select the region matching your MoEngage account—using the wrong region causes authentication failures.

1. Go to Data & Integrations > Integrations and select the MoEngage entry in the Directory tab.

2. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.

3. Configure your integration.

   1. Api Id: Your Moengage API Id

   2. Api Key: Your Moengage API Key

   3. Region: The region to send your data.

4. Click Enable Destination.

Actions

When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.

Identify user

The Identify User action creates or updates a user profile in MoEngage. It maps to identify calls by default. Use it to sync customer attributes like name, email, phone number, and custom traits to MoEngage.

MoEngage uses these profiles for segmentation, campaign targeting, and personalization. Include a consistent identifier (like userId) so MoEngage can match incoming data to existing user profiles.

Track event

The Track Event action sends an event to MoEngage. It maps to track calls by default. These events appear in the user’s activity timeline in MoEngage and can trigger campaigns, flows, and segments. For example, if you send a track call with the event name Purchase Completed, you can configure a MoEngage campaign that sends a follow-up push notification to that user.

Things to know

• Select the correct data center region. MoEngage operates in multiple regions (US, EU, India, Singapore). API calls fail with authentication errors if you select the wrong region.
• User identity is key. MoEngage needs a consistent user identifier to match incoming data to user profiles. Make sure your identify and track calls include a userId that MoEngage can use to look up or create the user.
• Events power MoEngage’s engagement tools. Events you send via the Track Event action drive segmentation, campaign triggers, analytics, and Smart Triggers across MoEngage. The more behavioral data you send, the more you can do in MoEngage.
• MoEngage enforces its own rate limits. High-volume event streams may hit MoEngage’s API throttles. If you send large volumes of events, check your MoEngage plan’s API limits.