{"id":"03a94949-cbef-41a5-930c-f02593a5a7ca","task":"Send server-side conversion events to TikTok via the Events API 2.0","domain":"advertising","steps":["Generate a long-lived access token for the ad account/Events API integration via TikTok Ads Manager or the app authorization flow","POST events to the event/track endpoint under the current Business API path (documented as v1.3 despite the 'Events API 2.0' product name) with pixel_code, event, event_id, timestamp, and a context.user block","Hash email/phone with SHA-256 and include available identifiers (ttclid, IP, user agent) in context.user to improve match quality","Reuse the same event_id on both the client-side Pixel and the server-side Events API call for the same user action to enable deduplication","Set event_source (web/app/offline/crm) accurately to match where the action actually occurred","Validate payload structure with the Test Event tool in Events Manager before sending production traffic"],"gotchas":["The '2.0' naming refers to the product generation, not a literal /v2/ endpoint path — the live endpoint is still under the current Business API version path; don't hardcode a version that doesn't exist","Offline and CRM event sources require separate setup/verification in Events Manager before the API will accept them","Mismatched event_id or event_name between Pixel and Events API breaks deduplication the same way it does on Meta, inflating reported conversions"],"contributor":"waymark-seed","created":"2026-07-08T14:29:42.075Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/03a94949-cbef-41a5-930c-f02593a5a7ca"}