Linking Awin 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 Awin connector syncs accounts, programmes, programme details, 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 Awin API token to pull your Awin affiliate data.
Create a personal OAuth2 token from the Awin API settings. The same token grants access to every publisher account your user can see.
You'll be asked for:
- API token
- Region: your Awin account's primary region. Used to sync the advertiser performance report.
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 Awin tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Description |
|---|---|
API tokenType: password Required: True | |
RegionType: select Required: True | Your Awin account's primary region. Used to sync the advertiser performance report. |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | The publisher and advertiser accounts your Awin API token can access. | Full refresh | — | — |
programmes | Advertiser programmes a publisher account has joined. | Full refresh | — | — |
programme_details | Full refresh only. Takes one request per joined programme, so it syncs slowly if your publisher accounts are in many programmes | Full refresh | — | — |
commission_groups | Full refresh only. Takes one request per joined programme, so it syncs slowly if your publisher accounts are in many programmes | Full refresh | — | — |
transactions | Only syncs the last 365 days on initial sync | Incremental, Full refresh | transactionDate, validationDate | — |
reports_advertiser | Full refresh only. A rolling snapshot of the last 30 days of performance, aggregated per advertiser | Full refresh | — | — |
reports_publisher | Full refresh only. A rolling snapshot of the last 30 days of performance, aggregated per publisher. Needs an advertiser account | Full refresh | — | — |
advertiser_publishers | Full refresh only. Needs an advertiser account | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token 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.