Linking MoEngage as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
This source is currently in alpha. The interface and available tables may change.
The MoEngage connector syncs campaigns, campaign report, daily campaign report, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Sync your MoEngage campaigns and their performance reports.
Find your Workspace ID and the Campaign report API key in your MoEngage dashboard under Settings > Account > APIs. Pick the data center your dashboard URL shows (for example, dashboard-01.moengage.com is DC-01).
The daily_campaign_report table backfills the last 90 days by default. Set a daily report start date to backfill further. The campaign_report table always covers the last 30 days.
You'll be asked for:
- Data center: choose between DC-01 (US), DC-02 (EU), DC-03 (India), DC-04 (US), DC-05 (Singapore), DC-06 (Indonesia) and DC-101.
- Workspace ID
- Campaign report API key
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Some MoEngage tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Data center | select | Yes |
Workspace ID | text | Yes |
Campaign report API key | password | Yes |
Daily report start date (optional) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
campaigns | Campaigns in the MoEngage workspace, across channels, with their status, delivery type, and configuration details. | Full refresh | — | — |
campaign_report | Per-campaign performance stats aggregated over the trailing 30 days, broken down by platform, locale, and variation. The whole table refreshes on every sync. | Full refresh | — | — |
daily_campaign_report | Per-campaign performance stats for a single day, broken down by platform, locale, and variation. One row per campaign, day, platform, locale, and variation. | Incremental, Full refresh | date | — |
Troubleshooting
- If the connection fails with an authorization error, the campaign report API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.