​

Introduction

The MoEngage and OpenAI Ads Conversions integration establishes a secure, server-to-server (S2S) connection. By bypassing browser-side obstacles such as cookie restrictions, Intelligent Tracking Prevention (ITP), and ad blockers, it captures conversions that client-side tracking often misses. MoEngage provides a single omnichannel connector for OpenAI, available through the OpenAI Ads Conversions app in the MoEngage App Marketplace. It sends conversion events captured across all your environments, including your website, mobile app, and physical store, directly into your OpenAI Ads Manager.

​

Use Cases

Integrating OpenAI Ads Conversions with MoEngage allows you to sync event data to support the following use cases:

• Signal resilience: Recover “lost” conversions typically blocked by browser privacy settings and ad blockers.
• Real-time attribution: Send server-side signals directly to OpenAI to improve click-through and view-through attribution accuracy.
• Return on Ad Spend (ROAS) optimization: Send real-time conversion data to OpenAI to improve ad delivery, audience matching, and Cost Per Acquisition (CPA).
• Multi-source tracking: Capture purchases, subscriptions, sign-ups, appointments, and custom events from any channel, and attribute them to your ad clicks.
• Conversion reporting: Report conversion volume and value in OpenAI Ads Manager to measure return on investment.

​

Integration

​

Step 1: Generate Credentials in OpenAI Ads Manager

To establish the connection, retrieve your Pixel ID and generate an API key in OpenAI Ads Manager.

​

Step 1.1: Retrieve Your Pixel ID

To retrieve your Pixel ID, perform the following steps:

1. Log in to your OpenAI Ads Manager account.
2. On the left navigation menu, navigate to Settings > General > Manage conversion keys.
3. In the top right corner, click Create, and then select Data Source.
4. In the Data Source Name box, enter a name for the data source.
5. In the Type list, select Web.
6. Click Create.

OpenAI then displays your Pixel ID. Click Copy, and paste the value in a safe place for use in the Step 2: Connect OpenAI Ads Conversions in the App Marketplace section.

​

Step 1.2: Generate a Conversions API Key

To generate a Conversions API key, perform the following steps:

1. In OpenAI Ads Manager, navigate to Settings > General > Manage conversion keys.
2. In the top right corner, click Conversion keys.
3. Click Create new key.
4. In the Name box, enter a name for the key.
5. Click Create.

Copy the access token that OpenAI displays.

​

Step 1.3: Create Conversion Events in OpenAI Ads Manager

OpenAI Ads requires you to create each conversion event in Ads Manager before the events MoEngage sends start to populate them. Events can flow correctly from MoEngage, but if the matching conversion event does not exist in OpenAI Ads Manager, it does not appear in your reporting. For each event you want to track, perform the following steps:

1. Log in to your OpenAI Ads Manager account.
2. On the left navigation menu, navigate to Settings > General > Manage conversion keys.
3. Click the Conversion Events tab.
4. In the top right corner, click Create, and then select Conversion Event.
5. In the Base Event list, select the event you want to track.
6. Enter a name for the conversion event.
7. Under Data source, select the data source you created in the Step 1.1: Retrieve Your Pixel ID section.
8. Click Create.

Repeat these steps for every event you want to track. For the events OpenAI supports, refer to Supported Events in the OpenAI documentation.

​

Step 2: Connect OpenAI Ads Conversions in the App Marketplace

To connect OpenAI Ads Conversions in the App Marketplace, perform the following steps:

1. On the left navigation menu in the MoEngage UI, click App Marketplace.
2. In the search box, enter OpenAI Ads Conversions.
3. Under Search results, click the OpenAI Ads Conversions tile.
4. Click the Integrate tab.
5. Click + Add integration.
6. Enter the following details:

   Field	Required	Description
   Connection name	Yes	A unique internal name for the connection (for example, OpenAI Ads - Production).
   API Key	Yes	The Bearer token from your OpenAI Ads Manager, generated in the Step 1.2: Generate a Conversions API Key section. This authorizes API calls.
   Pixel ID	Yes	The Pixel ID from your OpenAI Ads Manager, retrieved in the Step 1.1: Retrieve Your Pixel ID section. This directs conversion signals to the correct dataset.

7. Click Test to validate and save the connection.

The Integrate tab lists each connection you create, with its status, integration type, and who last updated it. Use the Status toggle to turn a connection off without deleting it.

​

Step 3: Create an OpenAI Ads Conversions Campaign

To create an OpenAI Ads Conversions campaign, perform the following steps:

1. On the left navigation menu in the MoEngage UI, click + Create New, and then click Campaign.
2. Under Connected Apps, click See all.
3. In the Connected Apps dialog box, search for OpenAI Ads, and then click the OpenAI Ads Conversions tile.
4. Click the delivery type you need: One Time, Periodic, or Event Triggered.
5. In Step 1 (Target users), select your audience.
6. In Step 2 (Content), under Select connector, select Track OpenAI Ad Conversions in the Connector list, and then select your connection in the Connections list.
7. Under Conversion Goals, enter the following:

   Field	Required	Description
   Event Type	Yes	The conversion event to track, from OpenAI’s standard taxonomy. Default is Order Created.
   Custom Event Name	Conditional	Required only when Event Type is Custom. Enter 1–64 characters, using lowercase letters, numbers, underscores, and dashes.
   Action Source	Yes	The channel where the conversion originated, such as Web, Mobile App, Offline, Physical Store, Phone Call, or Email. Default is Web.
   Event ID	Yes	Unique transaction, order, or event ID used for deduplication. Ensures only the first signal with this ID is recorded.
   Currency	Conditional	The ISO 4217 currency code for the conversion value. Required when you fill Conversion Value. Default is USD.
   Conversion Value	No	The monetary value of the conversion, as an integer in the currency’s minor units.

   The Action Source drives omnichannel tracking, letting you attribute conversions to app interactions, web visits, or physical storefront purchases. Type @ in any text box to personalize its value with a user or event attribute.
8. Under Attribution, enter the following:

   Field	Required	Description
   Source URL	Conditional	The URL where the conversion occurred (for example, https://shop.example.com/checkout/confirmation). Required when Action Source is Web.
   IP Address	No	IPv4 or IPv6 address, used to improve user matching. Sent raw rather than hashed.
   Browser Details	No	The browser’s User-Agent string, which helps with cross-device attribution.

   Include the Source URL wherever possible, because it improves click-through attribution accuracy for web conversions.
   
9. Under Advanced Matching, enter the following. These identifiers help OpenAI link conversions to specific users, and MoEngage normalizes and SHA-256 hashes personally identifiable information (PII) before transmission.

   Field	Required	Description
   External ID	No	Your internal customer or user ID (for example, customer_12345). Protected with SHA-256 hashing.
   Country	No	Two-letter ISO 3166-1 country code (for example, US). Sent as-is.
   City	No	City name, lowercased automatically. Maximum 128 characters.
   Zip Code	No	Postal or ZIP code. Sent as-is. Maximum 32 characters.

   MoEngage sends the email address on its own, so map at least one of these identifiers for users who have no email address on file. A conversion with no match signal at all cannot be attributed to your ads.
   The user’s email address is picked up automatically from the standard attribute, so it does not appear as a field. MoEngage strips aliases and periods, lowercases the string, and applies SHA-256 hashing before sending it.
   
10. Under Event Data, in the Conversion Event Data block, enter a key in the Key box and its value in the adjacent box. Click + New KV Pair to add each further pair.

    Key	Applies To	Description
    amount	All events	The monetary value of the item, as an integer in the currency’s minor units following ISO 4217. For example, 4200 for $42.00 USD.
    currency	All events with amount	The ISO 4217 currency code for the item, such as USD or EUR. Required whenever amount is present.
    plan_id	Subscriptions, Custom	Your internal subscription or plan identifier (for example, plan_starter).
    item_id	Purchase, Subscriptions, Custom	Internal product or item identifier (for example, sku_12345).
    item_name	Purchase, Subscriptions, Custom	Product name (for example, Premium Subscription).
    item_quantity	Purchase, Subscriptions, Custom	Number of items, as an integer.
    content_type	Optional for all	Item category or type (for example, product).
    group_id	Optional for all	Product group or bundle identifier (for example, bundle_summer_2024).
    variant_dict.size	Optional for all	Product variant size (for example, large).
    variant_dict.color	Optional for all	Product variant color (for example, blue).

    The amount and currency keys set the value of the individual items. The Currency and Conversion Value fields under Conversion Goals set the value of the conversion event itself, so the two are separate.
11. Under Test Campaign, select an identifier type, enter a test user’s value, and then click Test.
12. Click Next, configure Step 3 (Schedule and Goals), and then publish the campaign.

Test campaigns ignore frequency capping. Test your connector configuration before you publish to production.

​

Custom Events

To track a conversion outside OpenAI’s standard taxonomy, perform the following steps:

1. Under Conversion Goals, select Custom in the Event Type list.
2. In the Custom Event Name box, enter a name of 1–64 characters, using lowercase letters, numbers, underscores, and dashes. Spaces are not supported.
3. Under Event Data, map the keys that apply to the event.

Valid custom event names include video_completed, ebook_downloaded, and webinar_registered.

​

Supported Conversion Events

MoEngage supports direct mapping to OpenAI’s standard event taxonomy. Select the event you want to track in the Event Type list. For the full list of supported events and the data each one accepts, refer to Supported Events in the OpenAI documentation.

​

Usage Constraints

• Monetary value format: Send the conversion value as an integer in the currency’s minor units. For example, $42.00 USD is 4200, €29.99 EUR is 2999, £1.50 GBP is 150, and ¥100 JPY is 10000, because JPY has no decimal sub-units. Set the Currency field whenever you send a conversion value.
• Deduplication hygiene: Map a unique Event ID, such as a transaction or order ID. OpenAI records only the first occurrence of an Event ID and ignores duplicates, which prevents over-reporting.
• User matching and privacy: Pass raw values directly to the connector, because MoEngage normalizes and SHA-256 hashes personally identifiable information (PII) natively.
• Timestamp accuracy: Event timestamps must fall within the last 7 days and cannot be more than 10 minutes in the future. MoEngage fills in the current timestamp when you omit it.
• Rate limits and batch processing: The OpenAI Conversions API accepts batches of up to 1,000 events per request. If one event in a batch fails schema validation, the entire batch fails, so verify data integrity across all events.

​

FAQs