> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Dub as a source - Docs

Copy page

# Linking Dub as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Dub connector syncs your link attribution data from [Dub](https://dub.co) into PostHog: short links, click, lead, and sale events, customers, tags, domains, folders, and your partner program's partners, commissions, and payouts. This lets you join link and affiliate performance with the rest of your product analytics.

## Prerequisites

You need a Dub workspace and a workspace API key. Some tables need more than the free plan:

-   The `click_events`, `lead_events`, and `sale_events` tables require a Dub [Business plan](https://dub.co/pricing) or higher.
-   The `payouts` table requires a Business partner program plan or higher.
-   The `partners` and `commissions` tables require a [Dub Partners](https://dub.co/partners) program.

Tables your plan can't access show a permission note in the schema picker, so you can leave them unselected.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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 Dub, you'll need:

-   **Workspace API key**: create one in your [Dub workspace](https://app.dub.co) under **Settings** > **API Keys**. The key starts with `dub_` and is scoped to a single workspace.

## 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_at` timestamp). 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

The event tables (`click_events`, `lead_events`, `sale_events`) support incremental syncs on the event timestamp, which we recommend since events are append-only. All other tables sync as full refresh: the Dub API has no updated-since filter for them, and entities like commissions change status after creation, so a full reload keeps them accurate.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| Workspace API key | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| links | A short link in the workspace, with its destination, targeting rules, and lifetime analytics counters. | Full refresh | — | — |
| click_events | A click on one of the workspace's short links, with device, location, and referrer detail. Requires a Dub Business plan or higher. | Incremental, Full refresh | timestamp | — |
| lead_events | A lead conversion event attributed to a short link click. Requires a Dub Business plan or higher. | Incremental, Full refresh | timestamp | — |
| sale_events | A sale conversion event attributed to a short link click, with the sale amount and payment processor. Requires a Dub Business plan or higher. | Incremental, Full refresh | timestamp | — |
| customers | A customer tracked for conversion attribution in the workspace, with lifetime sales totals. | Full refresh | — | — |
| tags | A tag used to organize short links in the workspace. | Full refresh | — | — |
| domains | A custom domain configured for short links in the workspace. | Full refresh | — | — |
| folders | A folder used to group and access-control short links in the workspace. | Full refresh | — | — |
| partners | A partner enrolled in the workspace's partner program, with lifetime performance totals. | Full refresh | — | — |
| commissions | A commission earned by a partner for a click, lead, sale, or custom event in the partner program. | Full refresh | — | — |
| payouts | A payout of accrued commissions to a partner. Requires a Dub Business plan or higher. | Full refresh | — | — |

## Troubleshooting

If a sync fails with a permission error, check your Dub plan: event and payout tables need a Business plan or higher, and partner tables need a partner program. Disable syncing for tables your plan doesn't include.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.

### Was this page useful?

HelpfulCould be better