Linking Partnerize as a source
This source is currently in alpha. The interface and available tables may change.
The Partnerize connector syncs your partnership and affiliate marketing data – campaigns, conversions, clicks, and reference catalogs – into PostHog, so you can join partner-driven revenue with your product analytics.
Prerequisites
You need a Partnerize partner (publisher) account with API access. The API credentials are available to account users under Account settings in the Partnerize platform.
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.
The connector needs three values:
- User application key and User API key: both are shown under Account settings in the Partnerize platform. They are used together as the username and password for the API.
- Publisher ID: the ID of the partner account whose campaigns, conversions, and clicks you want to sync.
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 conversions and clicks tables support incremental syncs using Partnerize's report date filters.
For conversions, choosing last_modified as the incremental field also picks up status changes (for example pending to approved) on previously synced conversions, so it is the recommended cursor.
Configuration
| Option | Type | Required |
|---|---|---|
User application key | text | Yes |
User API key | password | Yes |
Publisher ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
campaigns | Campaigns the partner is approved to promote, with tracking, commission, and invoicing settings. | Full refresh | — | — |
conversions | Conversions (sales, leads) attributed to the partner, with commission values, statuses, per-item breakdowns, and the originating click. | Incremental, Full refresh | conversion_time, last_modified | — |
clicks | Clicks recorded on the partner's tracking links, with device, traffic source, and referer detail. | Incremental, Full refresh | set_time | — |
countries | Reference list of countries with ISO codes, currency, and geographic metadata. | Full refresh | — | — |
currencies | Reference list of currencies supported by Partnerize. | Full refresh | — | — |
devices | Reference list of device types clicks and conversions are attributed to. | Full refresh | — | — |
timezones | Reference list of timezones available for campaign reporting. | Full refresh | — | — |
traffic_sources | Reference list of traffic sources clicks and conversions are attributed to. | Full refresh | — | — |
user_contexts | Reference list of user contexts (environments such as web or in-app) for attribution. | Full refresh | — | — |
conversion_types | Reference list of conversion types (e.g. sale, lead) used by campaigns. | Full refresh | — | — |
conversion_metrics | Reference list of conversion metrics used to classify conversions. | Full refresh | — | — |
partnership_models | Reference list of partnership models (e.g. affiliate, influencer) for attribution. | Full refresh | — | — |
Troubleshooting
If the source fails to connect, check that the user application key and user API key are copied exactly from Account settings, and that the publisher ID belongs to an account your user can access.
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.