Linking CleverTap as a source
Contents
Alpha: This source is in alpha. The connector works, but hasn't been tested against a live CleverTap account. Expect rough edges.
The CleverTap connector syncs one configured event and the profiles of users who performed that event into the PostHog data warehouse. This is useful for retention analysis, campaign attribution, and combining CleverTap engagement data with your product analytics.
Prerequisites
- A CleverTap account with API access enabled.
- Your Account ID – find it in the CleverTap dashboard under Settings > Account.
- Your Passcode – find it in the CleverTap dashboard under Settings > Passcode.
- The name of the event you want to sync.
- Knowledge of which region your CleverTap account is in.
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.
You'll be asked for:
Account ID – your CleverTap account identifier.
Passcode – your CleverTap API passcode.
Region – the region your CleverTap account is hosted in:
- Europe (
eu1) – default - United States (
us1) - India (
in1) - Singapore (
sg1) - Indonesia (
aps3) - United Arab Emirates (
mec1)
- Europe (
Event name – the CleverTap event to export (for example,
App Launched).Start date – the earliest date to export, in
YYYY-MM-DDformat. The export runs from this date through yesterday (UTC).
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.
Both CleverTap tables use full refresh. Each sync replaces the contents of the table.
Available tables
| Table | Description | Sync method |
|---|---|---|
events | Occurrences of the configured CleverTap event within the export date range | Full refresh |
profiles | Profiles of users who performed the configured event within the export date range | Full refresh |
Events columns
| Column | Description |
|---|---|
event_name | The event name selected for this connection |
ts | Event time in account time, stored as a YYYYMMDDHHMMSS integer |
event_date | The event date in account time, derived from ts for partitioning |
profile | User identifiers, platform, and profile properties for this event |
events | Event summaries returned by CleverTap for this user |
event_props | Properties associated with this event occurrence |
session_props | Session metadata and campaign attribution properties |
Profiles columns
| Column | Description |
|---|---|
identity | The custom user identifier, when the account has assigned one |
email | The user email address, when available |
name | The user name, when available |
profileData | Custom profile properties and channel subscription preferences |
platformInfo | Device and platform metadata, including platform object IDs |
events | Lifetime event counts and the first and last occurrence times for each event |
Sync limitations
The connector exports a single event at a time. To sync multiple events, create a separate source for each one.
Profiles include only users who performed the configured event within the date range.
CleverTap excludes the following notification lifecycle events from event exports:
- Notification Sent
- Notification Bounce
- Notification Control Group
- Notification Rendered
- Notification System Control Group
Event timestamps use account time, not UTC.
Troubleshooting
Invalid credentials – check that your Account ID and Passcode are correct and haven't been rotated.
Permission errors – check that your CleverTap account has API access enabled and that you selected the correct region.
Export errors – check the event name, date range, and API access. CleverTap rejects exports for unsupported notification events.
Cursor errors – if an export cursor expires or becomes invalid, reset the table sync to start a new export.
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.
Configuration
Supported tables
The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.