fix(clevertap): correct real-time delivery claim and attribution data location - #153
Open
samiksha-shreya wants to merge 3 commits into
Open
fix(clevertap): correct real-time delivery claim and attribution data location#153samiksha-shreya wants to merge 3 commits into
samiksha-shreya wants to merge 3 commits into
Conversation
… location (LIN-1972)
The doc overstated real-time delivery ("every time a user is attributed... we
send an install event") - the real-time firer is currently disabled, so Sync
is the reliable delivery path today, not an instant automatic one. Also fixed
"Viewing Attribution Data": attribution events land under Analytics > Events >
UTM Visited, not a per-user "install events" section - verified live against
a real CleverTap project while fixing the underlying integration bugs (see
hazelnut PR #632).
…t optional Found while investigating a real customer with an active, high-volume project (thousands of installs/month) and CleverTap correctly configured, but zero CleverTap data ever sent — because their app never calls signup() with clevertapId. There's no error or partial delivery in this case, so it's easy to miss. Added an explicit warning under the setup step.
Walks through the exact CleverTap dashboard flow (Snapshot, Events, UTM Visited breakdown, Session/Geography/Technographics/People tabs) with screenshots so customers can find their attribution data without guessing. Account info blurred in every screenshot. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UnC9k2PDE24bCHzvfFPYpd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
What was wrong: The CleverTap setup guide said data gets sent to CleverTap instantly, every time a user is attributed. That's not quite accurate right now — real-time delivery is currently switched off on our backend, so the reliable way to get data into CleverTap today is the Sync button, not something automatic. The guide also pointed people to the wrong place in the CleverTap dashboard to actually view this data. And separately, the guide didn't make clear that one setup step (passing the CleverTap ID when a user signs up) is required — skip it, and literally nothing reaches CleverTap, with no error shown anywhere to tell you something's missing.
What we fixed:
Summary
The CleverTap integration doc overstated real-time delivery and pointed at the wrong place to view attribution data. Both were caught and verified while fixing the underlying bugs in hazelnut (PR #632).
Changes
signup()is required, not optional — skipping it means zero data reaches CleverTap, silently.