CleverTap

Datafly Signal delivers events to CleverTap server-to-server using the Upload Events API (POST /1/upload). Events are keyed on each user’s identity, matched to their CleverTap profile, and made available for segmentation, journeys, and omnichannel campaigns — without a client-side tag.

Why route CleverTap through Datafly Signal

• Profiles are updated 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.

Prerequisites

Before configuring CleverTap in Signal you need a CleverTap account and its server-side API credentials.

Configure in Signal

Configuration Fields

Management UI Setup

1. Go to Integrations > Add Integration > CleverTap.
2. Choose the Default preset.
3. Enter your account_id, passcode, and region.
4. Select consent categories (typically marketing).
5. Click Save.

API Endpoint

POST https://{region}.api.clevertap.com/1/upload

Required headers:

X-CleverTap-Account-Id: {account_id}
X-CleverTap-Passcode: {passcode}
Content-Type: application/json; charset=utf-8

Events are sent as a JSON object with a d array. Up to 1,000 records may be sent per request, and CleverTap allows up to 15 concurrent requests per account. Signal batches and rate-limits automatically.

Identity Signals

identity is the Signal user ID, else the trimmed, lower-cased email (plain text: it is the profile’s identity in CleverTap). Events from visitors with neither are not sent.

Event Mapping

Each event is one record in d[]: type: "event", identity, ts (epoch seconds), evtName and scalar evtData.

Product events take their fields from the first Signal item (Product ID, Product Name, Category, Brand, Price, Quantity); Charged carries all items in Items, the only nested value CleverTap accepts. Currency is upper-case. Profile updates from identify are not sent yet (#1499).

Testing Your Integration

1. Trigger an event on your site (e.g. complete a test order).
2. In the CleverTap dashboard, open the user’s profile (search by the identity you sent) and confirm the event appears under Events.
3. Inspect the raw response in Signal’s event debugger — a clean delivery returns HTTP 200 with:

{ "status": "success", "processed": 1, "unprocessed": [] }

Troubleshooting