MoEngage (Actions)

MoEngage (Actions) Destination provides significant improvements over the Classic Destination:

Benefits of MoEngage (Actions) vs. MoEngage Classic

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

• Data consistency: We have improved data consistency between Device Mode and Cloud Mode. Previously, data sent through these modes would sometimes be mismatched or contain duplicated properties; this issue is now resolved.
• Mapping support: Using MoEngage Actions, you can now map properties that are previously incompatible with MoEngage-compatible properties. This significantly reduces your development bandwidth.
• Enhanced configuration: Additional configurations are now available for the JavaScript integration, including the option for a custom Service Worker.

Step 2: Set up MoEngage (Actions) Destination

To set up the MoEngage (Actions) Destination, perform the following steps:

1. On the Setup page, enter a Destination name. 
   Note: Select your preferred setup method. Optional: If you previously integrated with MoEngage, you can copy the settings from a previous destination.
2. Click Save. 
   

3. On the Settings tab, enter your MoEngage App details. 

   Entity	Description
   Name	This is the name of the MoEngage destination, such as MoEngage prod, MoEngage test, and so on.
   App ID	Copy and paste the Workspace ID. The Workspace ID of your MoEngage account is available at Settings -> Account -> APIs -> Workspace ID. The Data API ID and the Workspace ID of your MoEngage account are the same.
   App Key	Copy and paste the App Key. The Data API key of your MoEngage account is available at Settings -> Account -> APIs -> API keys > Data API settings.
   Endpoint region	This is your MoEngage data center. For more information, refer here.

4.  Turn the Enable Destination toggle on and then click Save Changes.
   

Enable Mappings - Track and Identify

The MoEngage (Actions) Destination now supports Data Mapping. This allows you to control how Segment sends the event data it receives from your sources to MoEngage. Each Action within this destination lists its required and optional event data. You can also choose which event types, event names, or event property values trigger an Action.

These triggers and mappings enable you to send different versions of an Action, depending on the context from which it is triggered. For more information, refer to Classic Destinations and Destination Actions. To use mappings, click the Mappings tab > + New Mapping. The MoEngage (Actions) provides two Actions: Track Event and Identify User.

Add Identify User mapping

1. Click the Mappings tab and then click + New Mapping.
2. In the Add mapping section, under ACTIONS, select Identify User. 
   
3. Define the event triggers based on your requirements, or retain the default condition provided by MoEngage.
4. Click Test Event. The segment attempts to fetch a recent event that matches your trigger conditions.
5. In the Define mappings step, MoEngage provides preset values for all mappings.
6. Scroll to the end of the page to optionally test your connection.
   
7. After the configuration, click Save. Ensure these values remain unchanged.

Portfolio Support

If Portfolio is enabled in your MoEngage workspace, you can route events to specific projects by providing the project name in your Segment payload according to the following requirements:

• Map the Project Name attribute in Segment to your MoEngage project name
• Ensure the value for this field exactly matches the project names configured in your MoEngage Portfolio.
  

Event Route to Projects

For Portfolio-enabled workspaces, MoEngage uses attribute-based routing. This allows you to send events from Segment to specific projects. To route events, you must map the project identifier from your Segment properties to the dedicated MoEngage attribute: Project Name (moe_project_name).

Event Ingestion Rules

The following behavior describes how MoEngage handles event ingestion based on the Project Name mapping:

• Attribute mapping: Map your source property (for example, brand_name or app_id in Segment) to the MoEngage attribute Project Name. When this mapping is present, MoEngage identifies the target project based on the attribute value.
• Exact name matching: The value passed in the source column must exactly match the Project Name configured in your MoEngage portfolio settings.
• Fallback behavior (mismatched or blank): If the Project Name field is left blank, the mapping is missing, or the value does not exactly match a configured project, the event is ingested at the global portfolio level.

For more information, refer to Portfolio and Portfolio: Data Ingestion and Management

Update Existing Users Only 

When making an Identity call, you can create new users in MoEngage. If you select the Update existing users only option and the forwarded user is not already present in MoEngage, a new user will not be created; only the properties of existing users will be updated. If the setting to create new users is set to Yes, only the properties of existing users will be updated. (The value true is implied by Yes.) 

Add Track Event Action

To add the Track Event action, perform the following steps:

1. Click the Mappings tab and then click + New Mapping.
2. In the Add mapping section, under ACTIONS, select Track Event.
   
3. Define the event triggers based on your requirements, or retain the default condition provided by MoEngage.
4. Click Test Event. The segment attempts to fetch a recent event that matches your trigger conditions.
5. In the Define mappings step, MoEngage provides preset values for all mappings.
6. Scroll to the end of the page to optionally test your connection.
   

7. After the configuration, click Save.
   Note: Ensure these values remain unchanged.

   info	Information After the Identify User and Track Event mappings, the Enabled toggle is turned on. If not, enable them by turning the toggle in the Status column.

Migration from the Classic MoEngage Destination