Source connector

CleverTap connector

CleverTap integration for databases, warehouses and BI tools

Mobile analytics and lifecycle engagement. Datrise captures CleverTap entities such as users, events, campaigns, segments, journeys and push deliveries, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The CleverTap Data Export API (Get Events / Get User Profiles) authenticates with API key, incremental runs key on from / to (YYYYMMDD date range on the event date), and CleverTap caps calls at No per-minute, per-hour or per-day limit is published; concurrency is capped at 3 concurrent requests for most APIs and 15 for the upload APIs, over which the API returns HTTP 429.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `clevertap_users`) with a schema derived from the CleverTap API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the CleverTap pipeline page, and join the waitlist to get the CleverTap connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What CleverTap data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
users	clevertap_users	Upsert by primary key, incremental on updated-at
events	clevertap_events	Append-only, incremental by timestamp
campaigns	clevertap_campaigns	Upsert by primary key, incremental on updated-at
segments	clevertap_segments	Upsert by primary key, incremental on updated-at
journeys	clevertap_journeys	Upsert by primary key, incremental on updated-at
push deliveries	clevertap_push_deliveries	Append-only, incremental by timestamp

CleverTap API: setup facts for the connector

Verified against the vendor documentation on 2026-09-03. Unknown values are left blank rather than guessed.

API	CleverTap Data Export API (Get Events / Get User Profiles)
Authentication	API key — Account-level credentials sent as the `X-CleverTap-Account-Id` and `X-CleverTap-Passcode` headers; there is no OAuth flow for the export APIs.
Pagination	cursor — Two-step export: POST the filter to obtain an opaque cursor, then GET batches with `batch_size` (default 500, maximum 5000) until `next_cursor` is absent from the response.
Rate limit	No per-minute, per-hour or per-day limit is published; concurrency is capped at 3 concurrent requests for most APIs and 15 for the upload APIs, over which the API returns HTTP 429
Incremental cursor	from / to (YYYYMMDD date range on the event date) — Only a whole-day `from`/`to` range is available, and the Get User Profiles API exposes no updated-at filter at all, so profile syncs are full refreshes.
Webhooks	Yes — CleverTap Webhooks (per-campaign HTTP POST, 5 s timeout, 2 retries)
Bulk export	Yes — Cursor-based Get Events / Get User Profiles export, plus scheduled S3 and GCP exports
Deletes detectable	No

Official API reference

What bites when replicating CleverTap

An export cursor expires 4 hours after creation or after 1 hour of inactivity, whichever comes first; an expired cursor returns HTTP 400 with status `CURSOR_INVALIDATED` and the export has to restart from step 1.
Each cursor is single-threaded — reusing one from two workers causes an unrecoverable out-of-order failure, so a large export cannot be parallelised across pages.
Event timestamps (`ts`) are 14-digit `yyyyMMddHHmmSS` integers in the account's configured timezone, not UTC, so a naive UTC parse shifts every row.
Notification events (Sent, Bounce, Control Group, Rendered, System Control Group) are excluded from the Get Events API and only reachable via the S3/GCP export.

Compare this against every other documented API

Popular destinations for CleverTap

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

CleverTap connector FAQ

What CleverTap data does the connector extract?: 6 objects: users, events, campaigns, segments, journeys and push deliveries. Each lands in its own table with types preserved; history-style objects (2: events and push deliveries) load as append-only streams.
Is the CleverTap integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load CleverTap data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each CleverTap → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your CleverTap pipeline with guided onboarding

Join the waitlist to get priority access for CleverTap integrations with guided setup, schema-aware mapping, and production-grade incremental sync.