Repository navigation
fix(tiktok): send the Events API 2.0 body - #769
Open
laurentdav wants to merge 1 commit into
Open
laurentdav wants to merge 1 commit into
laurentdav wants to merge 1 commit into
Conversation
The destination posted the Events API 1.0 body (pixel_code, context) to the 2.0 endpoint /open_api/v1.3/event/track/: TikTok recorded nothing. Now event_source/event_source_id, user/page per event, event_time in seconds, phone_number sent as phone, identity fields normalised before hashing. Fixes elbwalker#768 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 41 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
This branch has not been deployed
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
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.
Fixes #768.
What
/open_api/v1.3/event/track/endpoint expects: top-levelevent_source: "web",event_source_id(pixel code),partner_name?,test_event_code?,data[]; each item hasevent,event_time(seconds),event_id,user,page,properties(no morepixel_code,context, ISOtimestamp).user.ip/user.user_agent.phone_numberis still accepted as a mapping key and sent asphone;phoneworks too.+) and external_id (trimmed) are normalised before SHA-256; an existing SHA-256 hex digest is kept.ttp,ttclid,localestay in clear as before.website/docs/destinations/server/tiktok.mdxfollow. Changeset: patch.Why
With the 1.0 body on the 2.0 endpoint no server event reached TikTok in our production flow. We have been running a patched copy with this body since.
Verify
npm run verify:touched -- server-destination-tiktok: typecheck, lint, 32 tests and step examples pass.🤖 Generated with Claude Code