Send a server-side conversion event via Snapchat Conversions API V3
domain: marketingapi.snapchat.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain your Snap Pixel ID and a long-lived access token from Snapchat Business Manager under Events Manager.
Construct a POST request to https://tr.snapchat.com/v3/{PIXEL_ID}/events, replacing {PIXEL_ID} with your actual pixel identifier.
Build the request body as a JSON object with a top-level 'data' array; each element in the array represents one event object containing event_type, event_time, and user_data fields.
Populate user_data with hashed identifiers (SHA-256 lowercase) such as email, phone, or mobile ad ID to maximize match rates.
Set the Authorization header to 'Bearer <your_access_token>' and Content-Type to 'application/json', then send the request.
Inspect the response for a 'status' field; a value of 'SUCCESS' confirms the events were accepted. Log any per-event errors returned in the response body.
Known gotchas
The V2 endpoint at tr.snapchat.com/v2/conversion is deprecated — always use the V3 path /v3/{PIXEL_ID}/events and the V3 payload shape (data array), not the old single-event envelope.
event_time must be a Unix timestamp in seconds; events older than 28 days or in the future by more than a few minutes will be rejected.
Hash all PII fields with SHA-256 (lowercase hex) before sending; sending unhashed values violates Snapchat policy and will cause match failures.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?