Linking Loops 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 Loops connector syncs campaigns, campaign groups, mailing lists, 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.
Enter your Loops API key to sync your campaigns, transactional emails, mailing lists and other account data.
You can generate an API key in your Loops account under Settings > API.
Note: the Loops API has no bulk contact export, so contacts can't be synced. Some tables (campaigns, themes, components) require the Content API to be enabled for your Loops team.
You'll be asked for:
- 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.
All Loops tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
campaigns | A marketing campaign, including its status, schedule, audience, and group. | Full refresh | — | — |
campaign_groups | A campaign group used to organize related marketing campaigns. | Full refresh | — | — |
mailing_lists | A mailing list contacts can subscribe to. | Full refresh | — | — |
audience_segments | An audience segment with filter rules, used for campaign targeting. | Full refresh | — | — |
workflows | An automation workflow in the Loops account. | Full refresh | — | — |
transactional_emails | A transactional email, including its group and current draft and published messages. | Full refresh | — | — |
transactional_groups | A transactional group used to organize related transactional emails. | Full refresh | — | — |
contact_properties | A contact property (default or custom) defined in the Loops account. | Full refresh | — | — |
themes | An email theme with style attributes for authored email messages. | Full refresh | — | — |
components | A reusable email component available for use in LMX templates and authored email messages. | Full refresh | — | — |
campaign_metrics | All-time email engagement counters for a sent campaign. Opens and clicks count sends, not events. | Full refresh | — | — |
transactional_email_metrics | All-time delivery counters for a transactional email, totalled across every published version. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the 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.