MoEngage Source

Ingest your event data from MoEngage into RudderStack.

  •   3 minute read  

MoEngage is an intelligent customer engagement platform. It lets you personalize every customer interaction and drive better engagement, retention, loyalty and lifetime value.

This guide will help you set up MoEngage as a source in RudderStack. By leveraging MoEngage Streams, you can automatically forward your users’ engagement and activity events to RudderStack.

Getting started

Follow these steps to set up your MoEngage source in the RudderStack dashboard:

  1. Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select MoEngage.
  2. Assign a name to your source and click Continue.
  3. Your MoEngage source is now configured. Note the Webhook URL in the Settings tab.
MoEngage source webhook URL
  1. Log in to your MoEngage dashboard. Then, go to App Marketplace, search for RudderStack, and click Add Integration.
  2. In the Integrate tab, add a name for your connection, enter the webhook URL obtained in Step 3 and select the events you want to forward to RudderStack.
MoEngage App Marketplace
  1. Click Connect to save your details.

Supported events

RudderStack ingests the following MoEngage events as track events, without any transformation:

success
RudderStack also supports ingesting custom events defined in the MoEngage dashboard.

Supported properties

RudderStack automatically ingests the following properties present in the above events:

NameDescription
App VersionThe mobile application version on which the event is tracked. This property is tracked with all events.
SDK VersionThe version of the MoEngage SDK on which the event is tracked. This property is tracked with all events.
PlatformThe OS on which the event is tracked, for example, Android, iOS, or Web. This property is tracked with all events.
Campaign IdThe campaign ID associated with the event.
Campaign NameRepresents the name of the campaign of which the message was a part.
Campaign TypeRepresents the type of the campaign of which the message was a part.
Readable Campaign IdRepresents the ID of the the campaign of which the message was a part.
Parent Campaign idRepresents the campaign ID of parent periodic campaign; the child instances of which are re-run on a recurring basis. Tracked when a periodic campaign is run.
Parent Flow IdRepresents the Flow ID of the parent journey campaign. Tracked when the journey campaign is run.
Parent Flow NameRepresents the flow name of the parent journey campaign. Tracked when the journey campaign is run.
Locale IdRepresents the ID of message locale. Tracked when the campaign is sent using Localization.
Locale NameRepresents the name of the message locale. Tracked when the campaign is sent using Localization.
Variation IdRepresents the ID of a message variation. Tracked when a campaign is sent using A/B Testing.
URLTracked when display filter is selected in the in-app campaign.
timestampThe user’s time while performing the event in ISO 8601 timestamp format.
First SessionGenerated for all the events tracked with the MoEngage web SDK. The value is True only for the first user session.
Logged In StatusGenerated for all the events tracked with the MoEngage web SDK. The value is True only if the user has logged in on the device.
Exit ReasonTracked when a user exits the flow. This is tracked as an attribute of the User Exited Flow event.
info
Refer to MoEngage’s Derived Events & Attributes to know which attributes you can forward to RudderStack.

Questions? Contact us by email or on Slack