Skip to main content
(Use this example if your integration involves syncing large amounts of data between MoEngage and a data warehouse or platform like Snowflake.)

[Partner Name] & MoEngage Integration

Author : [Your Company Name]
Date of Last Update : [Date]
(Provide a brief, 2-3 sentence introduction to your company and what you do. Then, explain the core value proposition of the integration with MoEngage. What key problem does it solve for our mutual customers?) For example: Partner Name : [Partner Name] Partner Category : Data warehouses

Overview 🚀

(Explain the integration’s core value from a data perspective. Describe how it solves key business problems, like breaking down data silos or enriching user profiles, and mention if the data flow is one-way or bi-directional.) The MoEngage and [Partner Name] integration empowers you to leverage high-quality, real-time customer data to build unified user profiles and drive hyper-personalized engagement. By seamlessly forwarding [Type of Data, for example, user profiles, computed attributes, and events] from [Partner Name] to MoEngage, you can unlock powerful marketing use cases, enhance segmentation, and ensure data consistency across your stack—all without significant engineering effort. This integration also allows for a bi-directional flow, enabling you to export rich engagement data from MoEngage back into [Partner Name] for deeper business intelligence and analysis.

Use Cases 🎯

(List the 2-3 primary things users can achieve with this integration. Be specific and action-oriented.)
  • Enrich User Profiles with Warehouse Data : Sync computed attributes like Customer Lifetime Value (CLV), churn prediction scores, or product-affinity models from [Partner Name] to MoEngage to create highly targeted segments and personalize campaigns.
  • Trigger Journeys from Warehouse Events : Send key events (e.g., subscription renewals, offline purchases, support ticket escalations) from [Partner Name] to MoEngage to trigger real-time, contextual user journeys across any channel.
  • Analyze Campaign Data in Your BI Tools : Export MoEngage campaign interaction data (sends, opens, clicks, conversions) back to [Partner Name] to join with your internal datasets for 360-degree attribution and ROI analysis.

Prerequisites ✅

(List everything a user must have in place before they can begin the setup. Be explicit with account types or plan levels if required.)
  • An active MoEngage account.
  • An active [Partner Name] account on the [for example, Pro, Enterprise] plan.
  • Admin access to both platforms.
  • Your [for example, API Key, Account ID, etc.] from the [Partner Name] dashboard.
  • (For data warehouse integrations, add specific credential and permission steps below as needed.)
  • Create a dedicated service account or database user in your data warehouse (e.g., Snowflake, Redshift, BigQuery) for MoEngage.
  • Assign necessary permissions/roles to the service account/user. This should include READ access to the specific schemas and tables MoEngage will import from, and WRITE access to the schema where MoEngage will export data.
  • Generate and securely store credentials , such as an access token, or a service account key file (e.g., a JSON file for BigQuery), which will be required to configure the connection in MoEngage.

Integration Setup 🛠️

(This is the most critical section. Provide a clear, step-by-step guide for the setup. Detail the configuration needed in your platform (like creating service accounts, granting permissions, and finding credentials) and the steps in MoEngage. Use screenshots and links to your detailed docs wherever necessary.)

Step 1: Grant MoEngage Access in [Partner Name]

Before MoEngage can import or export data, you need to create a dedicated user/role and grant the necessary permissions within your platform.
  • Create a Service User/Role for MoEngage (Provide instructions on how to create a new user or role specifically for the MoEngage integration. For example: “Log into your [Partner Name] dashboard, navigate to Admin > Users, and click ‘Create New User’.”)
  • Grant Required Permissions (Provide the exact SQL commands or UI-based steps to grant permissions. Be specific about READ access for imports and WRITE access for exports.
  • Locate Your Connection Credentials_ (Show users where to find all the necessary credentials required for the setup in MoEngage. Use screenshots.)_

Step 2: Configuration in [External Platform, for example, Snowflake]

  1. Explain the initial setup steps required on the external platform. This often involves setting up a specific app, view, or share.
  2. Link to your own detailed documentation for this process, if required.

Step 3: Configuration in MoEngage

  1. Explain the steps the user needs to take within MoEngage to complete the connection.
  2. Explain the steps the user needs to take to set up their data imports and exports.
  3. Be detailed and use screenshots wherever required.

Troubleshooting & FAQs❓

(List 2-3 common issues users might face and their solutions). For example:

Issues

Example Issue: Incremental syncs are not pulling new or updated records.
  • Check “Last Updated” Column: For periodic syncs, MoEngage often relies on a timestamp column (e.g., updated_at) to identify new or modified records. Confirm that this column’s value is being correctly updated in your source table every time a record changes. If the timestamp doesn’t change, MoEngage won’t detect the update.
  • Verify Timezone Consistency: Ensure the TIMESTAMP column used for incremental syncs is stored in UTC. MoEngage interprets all timestamps as UTC. If your source data is in a local timezone, recently updated records might be missed if the time difference causes them to fall outside the sync window.
  • Confirm Sync Configuration in MoEngage: Double-check your import job settings in MoEngage. Make sure you have selected “Periodic Sync” and have correctly identified the column that tracks the last updated timestamp for your records.

FAQs

[Specify the behavior]. For example: “To import JSON data successfully as an Object data type in MoEngage, the source column in [Partner Name] must be of type JSON or VARIANT. STRUCT columns are automatically mapped to Object fields in MoEngage.
[Specify the behavior]. For example: “MoEngage interprets all TIMESTAMP data as UTC. It is strongly recommended to store all timestamp information in your warehouse in UTC to ensure accurate, time-based segmentation and campaign triggering.
[Specify the behavior]. For example: “Directly writing custom SQL queries with JOINs is not supported. The best practice is to create a dedicated VIEW in [Partner Name] that contains all the fields from all the tables you wish to import into MoEngage. You can then select this view as your data source.
[Specify the behavior]. For example: “Yes, you can select both tables and views from [Partner Name] as a data source for your imports.
[Specify the behavior]. For example: “If you add a new column to your source table/view, you will need to manually edit the import job in MoEngage to map the new field. If a column is removed, it may cause the sync to fail. You should update the import job to remove the missing field.
[Specify the behavior]. For example: “Yes. To perform a historical import, you can set up a one-time sync job. This will pull all rows from your specified table or view. For ongoing syncs, the integration will only pull new or updated rows based on a timestamp column.
For issues related to data configuration or sync failures from [Partner Name], contact their support team at [Partner Support Email/Link]. For issues related to data processing or campaign setup within MoEngage, contact your Customer Success Manager.

Support 🤝

  • For issues related to [Partner Name] , contact our support team at [Partner Support Email or Link to Support Portal].
  • For issues related to the MoEngage platform, contact the MoEngage Support team.