CleverTap + Bruin
Ingest CleverTap data into your warehouse with incremental loading, quality checks, and full lineage. Defined in YAML, version-controlled in Git.
For business teams
What you get
Analysis beyond built-in reports
Join CleverTap behavioral data with revenue, support, and CRM data. Answer questions CleverTap alone can't.
Trusted behavioral data
Quality checks catch tracking gaps, duplicate events, and missing timestamps before they corrupt your models.
Self-serve for analysts
CleverTap data lands in your warehouse where analysts already work. No more exporting, no more waiting.
Real user journeys
Combine CleverTap events with purchase and support data to see the full customer journey, not just the product funnel.
For data & engineering teams
How it works
Event schema validation
Check for null event IDs, missing timestamps, and duplicate events on every sync. Catch tracking issues at ingestion.
YAML-defined, Git-versioned
Your CleverTap pipeline is a YAML file. Review in PRs, deploy with CI/CD, roll back with git revert.
SQL + Python transforms
Transform raw CleverTap events into funnels, cohorts, and user journeys with SQL or Python — in the same pipeline.
Dependency-aware scheduling
Bruin resolves pipeline dependencies automatically. Transforms only run after CleverTap data has landed.
Before you start
Step 1
Add your CleverTap connection
Connect using CleverTap account credentials and region. Add this to your Bruin environment file — credentials are stored securely and referenced by name in your pipeline YAML.
Parameters
account_idCleverTap account ID from dashboard settingspasscodeCleverTap account passcode for API authenticationregionCleverTap data center region (us1, eu1, in1, sg1)
connections:
clevertap:
type: clevertap
uri: "clevertap://?account_id=<your-account-id>&passcode=<your-passcode>®ion=<region>"Step 2
Create your pipeline
Define a YAML asset that tells Bruin what to pull from CleverTap and where to land it. This file lives in your Git repo — reviewable, version-controlled, and deployable with CI/CD.
Available tables
name: raw.clevertap_events
type: ingestr
parameters:
source_connection: clevertap
source_table: 'events'
destination: bigqueryStep 3
Add quality checks
Add column-level and custom SQL checks to your CleverTap data. If a check fails, the pipeline stops — bad data never reaches downstream models or dashboards.
columns:
- name: event_id
checks:
- name: not_null
- name: unique
- name: event_timestamp
checks:
- name: not_null
custom_checks:
- name: data is fresh
query: |
SELECT MAX(event_timestamp) >
TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 24 HOUR)
FROM raw.clevertap_eventsStep 4
Run it
One command. Bruin connects to CleverTap, pulls data incrementally, runs your quality checks, and lands clean data in your warehouse. If a check fails, the pipeline stops — bad data never reaches downstream.
--start-date$ bruin run .Running pipeline...
clevertap_events
✓ Fetched 2,847 new records
✓ Quality: campaign_id not_null PASSED
✓ Quality: spend not_null PASSED
✓ Quality: no negative ad spend PASSED
✓ Loaded into bigquery
Completed in 12sOther Analytics integrations
Ready to connect CleverTap?
Start for free, or book a demo to see how Bruin handles ingestion, quality, lineage, and scheduling for your entire data stack.