Send audiences to MoEngage Cohorts

MoEngage is a cross-channel customer engagement platform built for marketers and product owners who value agility over complexity. Use real-time insights and personalized cross-channel communications and adapt to evolving customer expectations.

Note

This destination uses the MoEngage Cohort Sync API . Each segment it creates is a custom segment in MoEngage.

Beta

The MoEngage Cohorts connector is in beta. Contact your Amperity representative to learn more.

Caution

MoEngage archives a segment after 60 days without an update, and an archived segment that was created by Cohort Sync cannot be restored. A run in which nobody joined or left the audience sends nothing to MoEngage. An audience that does not change for 60 days therefore loses its segment in MoEngage.

To start again, change the list name to a name that has not been used in the workspace. The next run creates a new segment and sends the whole audience to it.

Important

MoEngage assigns every segment that Cohort Sync creates to the Default Team. When your workspace uses Teams, people on other teams might not see the segment.

The steps required to configure campaigns to send audiences to MoEngage.

Note

Ask your DataGrid Operator or your Amperity representative for help configuring MoEngage as a destination to which you can send campaigns for customer activation.

Caution

This destination is available for sending campaign audiences to MoEngage after it is configured by a Datagrid Operator or your Amperity representative.

If this destination cannot be selected from the campaigns editor or activations canvas ask your Datagrid Operator or Amperity representative to configure a destination for sending campaign audiences to MoEngage.

Build a segment

Use the Segment Editor to build any audience using a series of drop-downs and picklists.

As you define the attribute profile for an audience be sure to refresh segment insights to view audience size and to see the value it brings to your business.

When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.

About segments that use the sub-audience editor

You can use any attribute that is in your customer 360 database to define your audience.

When sending the list of customers who belong to this audience to MoEngage as part of a campaign you must choose specific attributes to send.

MoEngage supports the following attributes: audiences.

Important

Validate the audience with MoEngage by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by MoEngage. Send the sample audience to MoEngage and verify the sample audience is correct in MoEngage. Make adjustments if necessary. Only send full audiences after validation is complete.

Add to a campaign

Use the campaign editor to configure Amperity to send data to MoEngage. Add a segment, define exclusions and sub-audiences, and then define each audience sent to MoEngage.

	Open the Campaign Editor. This is available from the Campaigns page. Click the Create campaign button in the top right corner of the page.
	Assign MoEngage as a destination for at least one treatment group. Note You may need to edit the attributes for the sub-audience to ensure Amperity is sending the right data to MoEngage.
	Click Edit attributes to review the attributes that Amperity sends to MoEngage. customer IDs Amperity pre-selects the list of attributes sent to MoEngage. The Edit attributes page for MoEngage is similar to: Note The Merged Customers table is the default table for sending data to MoEngage, even though segments are often built against the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table.

Configure default attributes

Each unique destination configured to send treatment group audiences to MoEngage has a set of default attributes.

Configure default attributes by clicking the Default attributes link next to the Create campaign button on the Campaigns page.

The source table defaults to the Merged Customers table for most attributes. This is configurable.

MoEngage requires the customer_id field, and Amperity sends only that field.

Source attribute	Required?	Destination attribute
customer_id	Yes	The MoEngage customer ID for the customer. MoEngage adds the customer to the segment only when it already has a user with this customer ID. Map the field that holds the ID your app or website uses for each user in MoEngage. This is not necessarily the Amperity ID.

Each campaign send removes the customers who left the audience since the last send, and then adds the customers who joined.

The customer ID is the unique ID that MoEngage identifies a user by. It is usually the ID that your app or website passes to the MoEngage SDK when a user logs in, which is not necessarily the Amperity ID. Confirm which field in Amperity holds the same value before you send, and alias that field as customer_id in the query, for example SELECT loyalty_id AS customer_id.

Amperity sends each customer ID as text, after removing leading and trailing whitespace, and MoEngage matches it exactly. When the field holds a floating-point number, such as a DOUBLE, or a DECIMAL with digits after the decimal point, convert it in the query, for example CAST(CAST(loyalty_id AS BIGINT) AS VARCHAR) AS customer_id. Otherwise the ID 12345 is sent as 12345.0 or 12345.00 and does not match the user in MoEngage.

Return one row for each customer ID. Amperity does not send these rows:

• A row whose customer ID is null or empty. Amperity skips the row without an error, and counts it with the rows sent from cache.

• A row whose customer ID repeats another row’s customer ID. Amperity keeps one of the rows and skips the others without an error. Which row it keeps is not determined.

• A row whose customer ID MoEngage does not accept. This is a customer ID that contains only whitespace, is one character long, or is a placeholder value such as unknown, guest, null, none, n/a, 0, or -1. These values are compared without regard to case. MoEngage lists the values it does not accept in its Data API overview . Amperity reports the row as failed instead of sending it.