Linking Tremendous as a source
This source is currently in alpha. The interface and available tables may change.
The Tremendous connector syncs your rewards and payouts data, such as orders, rewards, invoices, and campaigns, into the PostHog Data warehouse, so you can analyze your incentive programs alongside your product data.
Prerequisites
You need a Tremendous account with access to create an API key. Tremendous has separate sandbox and production environments with separate API keys, and production API access must be approved by Tremendous first.
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 Tremendous, you'll need:
- Environment – whether to sync from your Production or Sandbox Tremendous environment. Make sure the API key you provide matches the selected environment.
- API key – create an API key under Team settings → Developers in Tremendous.
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 orders table supports incremental syncs on the created_at field. All other tables are full refresh only, as the Tremendous API doesn't expose a server-side timestamp filter for them.
Configuration
| Option | Type | Required |
|---|---|---|
Environment | select | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
orders | An order wraps around the fulfilment of one or more rewards. | Incremental, Full refresh | created_at | — |
rewards | A single reward, sent to a recipient. A reward is always part of an order. | Full refresh | — | — |
invoices | Invoices are instruments to fund your Tremendous account's balance. Once paid, the respective funds are added to the account balance. | Full refresh | — | — |
members | Users that can access and manage the organization through the Tremendous dashboard. | Full refresh | — | — |
campaigns | Campaigns define the look and feel of how rewards are sent out and the products recipients can choose from. | Full refresh | — | — |
products | A product represents one way to pay out a reward to its recipient, e.g. a specific gift card, charity donation, or prepaid card. | Full refresh | — | — |
funding_sources | Payment methods used to fund rewards in the organization's account. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid, revoked, or for the wrong environment. Sandbox and production keys are not interchangeable — generate a key for the selected environment under Team settings → Developers, then reconnect.
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.