Linking impact.com Partner 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.
This source is currently in alpha. The interface and available tables may change.
The impact.com Partner connector syncs the data your partner (publisher) account sees on impact.com: the brand programs you've joined, the conversions credited to you, and the invoices for your earnings. If your account is a brand (advertiser) account, use the impact.com source instead.
Prerequisites
You need an impact.com partner account with API access. The connector authenticates with an API access token, which any account user can create from their profile settings.
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.
When linking impact.com Partner, you'll need:
- Account SID and Auth token from an impact.com API access token.
To get these:
- Log in to impact.com.
- Go to your user profile, then Settings → Technical → API.
- Create an access token with read-only scopes.
- Copy the token's Account SID and Auth Token into PostHog.
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.
The Actions table supports incremental sync on EventDate, and Invoices on CreatedDate. On the first sync, Actions backfills up to 3 years of history in 44-day chunks, which is a limit of the impact.com API.
Configuration
| Option | Type | Required |
|---|---|---|
Account SID | text | Yes |
Auth token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Campaigns | The brand programs (campaigns) you've joined on Impact.com. Full refresh only. | Full refresh | — | — |
Actions | Conversion and commission records credited to you, fetched in 44-day windows (an Impact.com API limit). Only syncs the last 3 years on initial sync. | Incremental, Full refresh | EventDate | — |
Invoices | Invoices issued to you for your earnings. | Incremental, Full refresh | CreatedDate | — |
Troubleshooting
- Invalid credentials when connecting: check that the Account SID and Auth Token belong to a partner (publisher) account. Brand and agency accounts use different APIs, so a brand token won't validate here. For brand accounts, use the impact.com source.
- Missing older actions: the impact.com API only returns actions from the last 3 years, so the initial backfill stops there.
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.