Integrations / Marketing Automation
CleverTap
Server-side event delivery to CleverTap via the Upload Events API (POST /1/upload). Events are keyed on the user's identity (email by default), wrapped in the d[] array as type:event records with evtName + evtData, and matched to CleverTap profiles for engagement and segmentation.
Datafly Signal delivers first-party events to CleverTap server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload CleverTap expects.
Why route CleverTap through Datafly Signal
Profiles update from the server, not the browser
Events reach CleverTap even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the CleverTap rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
CleverTap is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartadd_to_wishlistbegin_checkoutloginpagepurchasesearchsign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the CleverTap documentation.
Frequently asked questions
Does Datafly Signal integrate with CleverTap?
Yes. Datafly Signal delivers first-party events to CleverTap server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload CleverTap expects. The integration is included in every deployment at no additional cost.
How is server-side CleverTap tracking different from the CleverTap tag?
The CleverTap tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to CleverTap from your server, so delivery does not depend on browser conditions.
Which events can Signal send to CleverTap?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, begin_checkout, login, page, purchase, search, sign_up, and more. Any event in your schema can be mapped to CleverTap through pipeline configuration without a code change.
Do I need to keep the CleverTap tag on my site?
No. Signal delivers to CleverTap from the server, so no client-side CleverTap script is required on your site.
Other marketing automation integrations
Ready to move CleverTap server-side?
See how Datafly Signal delivers first-party events to CleverTap from infrastructure you control, with hashed identity and consent enforcement built in.