Skip to main content
The MoEngage Audience destination sends audience data out of Zeotap CDP to MoEngage, where the matched users become a segment you can target in MoEngage campaigns. For the opposite direction — streaming MoEngage engagement events into Zeotap CDP — see MoEngage Source. For the MoEngage destination that is linked from a Journeys workflow instead of from an audience, see MoEngage.

​
What this is

MoEngage’s Cohort Sync API supports direct server-to-server sync of cohort and audience data into MoEngage. This destination uses that API so you can:
  • Create custom segments (audiences) in MoEngage for campaigns.
  • Add users to those segments in real time.
  • Keep the segments updated, so campaign targeting stays fresh.
Two limits apply to this integration:
  • No new users are created. The sync only matches users who already exist in MoEngage, using their uid. Audience members with no matching MoEngage user are not added.
  • User dissociation is not supported as of now. Removing a user from the Zeotap CDP audience does not remove them from the MoEngage segment.

​
Supported identifiers

The destination maps one identifier: User ID. On the mapping screen you pick the Zeotap CDP catalogue attribute that carries the user’s MoEngage uid and map it to the User ID destination field, which is a required string.

​
Prerequisites

Before you create the destination, gather the following:
  • MoEngage account — an active MoEngage account.
  • API keys — your Workspace ID (formerly DATA API ID) and a Data API Key. Both are generated from the MoEngage dashboard under Settings → Account → APIs → Data API Settings.
  • Data centre number — the 0X in your account’s MoEngage API endpoint https://api-0X.moengage.com, replaced with your own data centre number (for example 01, 02 or 03).

​
How the credentials are used

MoEngage’s API uses HTTP Basic authentication, with your Workspace ID as the username and your Data API Key as the password. You supply both values once when you create the destination; you do not construct the API request yourself.

​
Create the MoEngage destination

1
Log in to the Zeotap CDP App and go to the Destinations application under Integrate.
2
Click + Create Destination.
The Destinations listing in the Zeotap CDP App, with the + Create Destination button highlighted in the top right above the table of existing destinations.
3
Under the All Destinations section, search for MoEngage.
The All Destinations catalogue with the Search for a Destination box highlighted above a grid of destination tiles.
The All Destinations search box filtered to MoEngage, returning the single MoEngage tile described as tracking users in MoEngage using the User API.
4
Click MoEngage. The left of the screen describes the destination; the right lists the fields the integration needs. Provide them as follows:a. Enter a name for the destination.b. Enter the API Key, Workspace ID and Data Center (01, 02, 03 and so on) for your MoEngage instance. See Prerequisites for where these values come from in MoEngage.
The Destination Details tab of a saved MoEngage destination, showing the Destination Name field, API Key and Workspace ID fields each with a reveal control, and a Data Center field containing a two-digit number.
c. Review all the values you entered and click Next to proceed.
5
On the screen that appears, choose the appropriate action and mapping. Under Choose your Action, choose Sync User/Send Events as the action.Under Map the Fields, map the catalogue attribute holding the user’s MoEngage uid to the User ID destination field.
The action and mapping screen, with a Choose your Action selector at the top and a Map the Fields row underneath pairing a Choose Catalogue Attribute dropdown with the required User ID destination field of type String. The action shown selected is Add Audience to segment.
6
Click Create Destination. The destination is then listed in the Audiences application and can be linked to any audience.
1
In the Audiences application, find the audience you want to send, click its Audience Activation icon and choose Link to Destination.
The Audiences listing page with audience names obscured, showing the ID, status and last-updated columns and the per-row action icons, including the Audience Activation icon.
2
In the Select Destination panel, search for the MoEngage destination you created and drag it onto the canvas.
The audience activation canvas with an empty drag-and-drop area on the left and the Select Destination panel on the right, its search box highlighted above a scrollable list of destination cards.
3
On the Destination Details tab, the Workspace ID, API Key and Data Center fields are populated automatically from the values you entered when you created the destination.
4
Click Save Destination. The MoEngage destination is attached to the audience.
The attached MoEngage destination card on the audience canvas, showing the MoEngage logo, the destination name, a destination ID with a copy control, and the configured action Add Audience to segment.
For the end-to-end linking workflow, including scheduling and the other options on the Destination Settings window, see Activate your batch audiences.
Note:The terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an Audience or a segment could be a specific group of customers who are over 18 years of age and who have performed an addToCart event within the last 30 days.

​
Verify the destination is set up correctly

After you save the destination, confirm the following:
  • The MoEngage destination appears in the Audiences application and is selectable when you link an audience.
  • Once linked, the MoEngage card is shown attached to the audience, carrying the destination name and the action you configured.
  • The Workspace ID, API Key and Data Center shown on the Destination Details tab of the linked destination match the MoEngage instance you intended to send to.
Bear in mind when you compare counts that the sync matches only users who already exist in MoEngage, so audience members without a matching MoEngage user will not appear in the MoEngage segment.

​
Troubleshoot the MoEngage sync

For delivery problems that are not specific to MoEngage, see Why deliveries fail.

​
Next steps

Last modified on September 24, 2026