Skip to contentSkip to navigationSkip to topbar
Twilio Segment Docs
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

MoEngage (Actions) Destination

Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Moengage (Actions) in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.
(information)

Info

This page is about the Actions-framework MoEngage Segment destination. There's also a page about the non-Actions MoEngage Destination. Both of these destinations receives data from Segment.

This destination is maintained by MoEngage. For any issues with the destination, contact the MoEngage Support team.

Benefits of MoEngage (Actions) vs MoEngage Classic

benefits-of-moengage-actions-vs-moengage-classic page anchor

MoEngage (Actions) provides the following benefits over the MoEngage Classic destination:

  • Data Consistency. Data consistency between device-mode and cloud-mode. Earlier, data sent from device and cloud-mode would sometimes be mismatched with duplicated properties - this has now been fixed.
  • Better Mapping. Using MoEngage Actions, you can now map incompatible properties with MoEngage-compatible properties. This significantly reduces your development bandwidth.
  • Region Support. Support across all data clusters. Moengage provides an option to choose your Data Region where your app is present.
  • Better Configuration. There are additional configurations for the JavaScript integration like custom Service Worker.

Getting started

getting-started page anchor

  1. From the Segment web app, click Catalog, then click Destinations.

  2. Search for MoEngage (Actions) and select it.

  3. Click Configure MoEngage.

  4. Select an existing Source to connect to MoEngage (Actions).

  5. Finish the setup.

  6. Configure the settings. See the table below for more information.

    Field NameDescription
    NameThe name of the Moengage destination such as MoEngage prod, MoEngage test.
    App IdNavigate to Settings > API > General on your MoEngage dashboard to access the App ID.
    App KeyNavigate to Settings > API > General on your MoEngage dashboard to access the App Key.
    Endpoint RegionThis is your MoEngage data center. Read more(link takes you to an external page).

  7. Enable the toggle option to Enable the destination and click Save changes.

Default Mapping

default-mapping page anchor
(warning)

Do not change the preset values

Moengage provides preset values to all mappings and hence no changes are required in the Identify User Actions, and Track Event Actions.

Destination Settings

destination-settings page anchor
Property nameTypeRequiredDescription
Api Idstring
required

Your Moengage API Id

Api Keypassword
required

Your Moengage API Key

Endpoint Regionselect
required

The region to send your data.

Available Actions

available-actions page anchor

Build your own Mappings. Combine supported triggers with the following Moengage-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track Event

track-event page anchor

Send an event to Moengage.

Track Event is a Cloud action. The default Trigger is type = "track"

Property nameTypeRequiredDescription
Event typeSTRING
required

The type of the event being performed.

Event NameSTRING
required

The name of the event being performed.

User IDSTRING

Optional

The unique identifier of the user.

Anonymous IDSTRING

Optional

The unique identifier of the anonymous user.

OS NameSTRING

Optional

The name of the mobile operating system or browser that the user is using.

APP VersionSTRING

Optional

The version of the mobile operating system or browser the user is using.

Library VersionSTRING

Optional

The version of the mobile operating system or browser the user is using.

TimestampDATETIME

Optional

The timestamp of the event. If time is not sent with the event, it will be set to the time our servers receive it.

Event PropertiesOBJECT

Optional

An object of key-value pairs that represent event properties to be sent along with the event.

Update Existing Users OnlyBOOLEAN

Optional

If set to true, events from the Segment will only trigger updates for users who already exist in Moengage.

Identify User

identify-user page anchor

Set the user ID for a particular device ID or update user properties.

Identify User is a Cloud action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
Event typeSTRING
required

The type of the event being performed.

User IDSTRING

Optional

The unique user identifier set by you

Update existing users onlyBOOLEAN

Optional

Setting this to true will not create new users in MoEngage. Only existing users will be updated

Anonymous IDSTRING

Optional

The generated anonymous ID for the user

OS NameSTRING

Optional

The name of the mobile operating system or browser that the user is using.

APP VersionSTRING

Optional

The version of the mobile operating system or browser the user is using.

Library VersionSTRING

Optional

The version of the mobile operating system or browser the user is using.

TimestampDATETIME

Optional

The timestamp of the event. If time is not sent with the event, it will be set to the time our servers receive it.

User PropertiesOBJECT

Optional

Properties to set on the user profile

Testing the integration

testing-the-integration page anchor
  1. Navigate to Connections > Destinations> MoEngage.
  2. Go to the Event tester tab.
  3. Test your track and identify methods.
Event Tester.

If successful, the data starts flowing into your MoEngage account in 3-5 minutes. You can log in to your MoEngage dashboard and go to Test & Debug > Recent events to verify.