NitroX

Connect NitroX to MoEngage to export user profiles and website events in real time for personalized campaigns and behavioral segmentation.

NitroX is a commerce platform designed to capture and structure identified user data and behavioral events. When you connect NitroX to MoEngage, you can automatically export user profiles and supported website events to create personalized marketing campaigns and behavioral segments.

MoEngage X NitroX

This integration enables a real-time outbound data flow from NitroX to MoEngage. When you connect NitroX to MoEngage, you can use behavioral data triggers to orchestrate targeted retention, recovery, and engagement campaigns.

The NitroX integration is built and maintained by Nitro. For customization requests or issues specific to the NitroX connector’s behavior, reach out directly to Nitro Support.

Use cases

When you connect NitroX to MoEngage, you can synchronize audience data to support the following use cases:

• Abandoned cart recovery: You can use tracked nitro_addtocart and nitro_checkout events to automatically trigger MoEngage email or push sequences for users who do not complete their purchases.
• Post-purchase engagement: You can use event payloads such as nitro_orders/paid or nitro_orders/fulfilled to automate order confirmation messages and trigger cross-sell campaigns.
• Targeted product recommendations: You can use the nitro_product_view and nitro_category_view data to segment users based on their browsing behavior and send relevant product offers.
• Automated audience segmentation: You can use the created_by user attribute with a value of Nitro to identify users generated by NitroX in MoEngage for exclusive promotional targeting.

Key Features and Functionality

The NitroX integration delivers the following core capabilities within MoEngage:

• Real-time event synchronization: You can synchronize website events, including product views, cart additions, and checkout progressions, in real time.
• User profile exports: You can export identified user profiles and track Nitro-specific user properties to create precise audience segments.
• Order lifecycle tracking: You can automate the synchronization of order lifecycles to capture orders when they are created, updated, paid, and fulfilled.

Supported Events

The tables below outline the real-time behavioral events synchronized from NitroX:

All behavioral events exported from NitroX to MoEngage use the following prefix: nitro_ (for example, nitro_view or nitro_addtocart).

Event name	Description
page_view	A user views a webpage.
product_view	A user views a product detail page.
addtocart	A user adds an item to the shopping cart.
removefromcart	A user removes an item from the shopping cart or empties the cart.
checkout	A user starts the checkout process.
orders/create	A user creates an order.
orders/paid	A user completes the payment for an order.
orders/updated	The status or details of an existing order change.
orders/fulfilled	An order is shipped or delivered.
is_consented	A user gives explicit consent for marketing communications.
otp_verified	A user successfully verifies a one-time password (OTP).

Integration

Prerequisites

Before you set up this integration, make sure you have the following credentials from your MoEngage account:

• Workspace ID (earlier App ID): The unique identifier for your MoEngage workspace.
• API Key: The key used to authenticate API requests.

Step 1: Find Your Credentials in MoEngage

To find your credentials, perform the following steps:

1. On the MoEngage UI, navigate to Settings > Account > APIs.

2. Copy the ID under Workspace ID (earlier app id).

3. In the API keys section, copy the API key on the Data tile.

   

Step 2: Configure the Connection in NitroX

To configure the connection in NitroX, perform the following steps:

1. Sign in to your NitroX account.

2. On the sidebar menu in NitroX, click the Integrations menu item.

   

3. In the Integration list, scroll down to the Connect with Moengage section, and then turn the toggle on to expand the integration fields.

4. In the Region list, select the data center region that matches your MoEngage account (for example, DC-04).

5. In the Primary Identifier list, select the primary identifier (either Phone number or Email) based on your MoEngage user configuration.

6. In the Workspace ID / App ID and Api Key boxes, type or paste the credentials you obtained in Step 1.

7. Click Save.

   

Step 3: Verify Data Tracking in MoEngage

To verify that your user profiles and behavioral data are syncing correctly, perform the following steps:

To verify a specific user:

1. In the left navigation bar of your MoEngage account, click the target-like icon to open the Segment menu, and then click Search Users.

2. In the Search Users box, type the user ID, email address, mobile number, name, or MoEngage ID.

   

To view all synchronized users from NitroX:

1. On the Segment menu, click Create segment.

2. Select Filter users by.

3. Under the query builder tabs, click User property.

4. In the first drop-down list, select the created_by attribute. In the evaluation operator list, select is. In the type list, select Constant value.

5. In the final select option list, search for or select Nitro (case-sensitive).

6. Click Show count.

   

The query evaluates and returns the total number of synced profiles under the Query results panel.

Troubleshooting

Use the troubleshooting table below to resolve common integration issues:

Issue	Possible Cause	Solution
Data does not sync to MoEngage.	Region mismatch.	Verify that the region you select in the NitroX integration setup form matches the data center region for your MoEngage account.
User profiles do not update.	Primary identifier mismatch.	Make sure that the primary identifier you select in NitroX matches the Customer ID type in your MoEngage settings.
Authentication fails.	Invalid API credentials.	In MoEngage, click Settings, click APIs, and verify that you copied the Workspace ID and the API Key into NitroX without any blank spaces.
Events do not appear in segmentation.	Incorrect event search terms.	Make sure that you search for user behavior events by using the prefix such as nitro_view or nitro_addtocart.
Nitro-specific segment returns 0 users.	Incorrect attribute targeting.	Make sure that you query the user property by using the exact created_by attribute with a case-sensitive value of Nitro.