Linking DingConnect as a source
This source is currently in alpha. The interface and available tables may change.
The DingConnect connector syncs your DingConnect data into the PostHog Data warehouse, so you can analyze your top-up transactions and account balances alongside your product data.
Prerequisites
You need a DingConnect account with API access so you can generate an API key.
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 DingConnect, you'll need:
- API key – generate one under the Developer tab of your DingConnect account settings.
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 DingConnect tables are full refresh only, since the API exposes no incremental sync filter.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Countries | A country that DingConnect operates in. | Full refresh | — | — |
Currencies | A currency that DingConnect supports. | Full refresh | — | — |
Providers | A mobile operator or biller whose products can be sold through DingConnect. | Full refresh | — | — |
Products | A sellable product (e.g. a top-up amount) offered by a provider. | Full refresh | — | — |
Promotions | A time-bound promotion applied to a provider's products. | Full refresh | — | — |
Balance | Current account balance per currency. Full refresh only | Full refresh | — | — |
TransferRecords | Transfer history is only retained upstream for ~2 months. Full refresh only | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your DingConnect API key is invalid or has been revoked. Generate a new key under the Developer tab of your account settings, then reconnect.
- If you get a permission error, your API key does not have access to this data. Check the key's permissions in your DingConnect account settings, 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.