- All three platforms want the same pattern: keep the browser tag, add server events, and send the order number as the shared ID so each platform can deduplicate the two copies. All three state a 48-hour window.
- Credentials differ: TikTok pixel code plus Events Manager token, Snapchat Pixel ID plus Ads Manager token, Pinterest ad account ID (not tag ID) plus conversion token.
- Click IDs are not interchangeable:
ttclid(TikTok),ScCidsent assc_click_id(Snapchat),epikor the_epikcookie sent asclick_id(Pinterest). Save them on the landing page; they are gone by checkout otherwise. - A paid order is
Purchase,PURCHASEorcheckout, and TikTok hashes phones with the leading+while Snapchat and Pinterest want digits only. - Each platform has a test tool. Pinterest can return HTTP 200 with failed events, so read the body. Unconfirmed items (event age limits on TikTok and Pinterest, Snapchat’s 7 versus 37 days) are marked.
A WooCommerce store that advertises on TikTok, Snapchat or Pinterest usually starts with each platform’s pixel. The pixel sees only what the browser lets it see: ad blockers and a customer who closes the tab before the thank-you page loads cut into the count. All three platforms offer a server-to-server Conversions API (called Events API at TikTok) for exactly this gap.
The three APIs differ in the details that break integrations: where the token comes from, how a phone number is hashed, what the purchase event is called. This guide walks through each in the order you will meet them on a WooCommerce store. It builds on the cross-platform rules in our dedup and limits reference and does not repeat those tables. For Meta, which has its own long guide, see Meta Conversions API for WordPress.
Sources are official documentation read in October 2026. Where a page did not state a value, this article says “not confirmed”.
Pixel or tag versus server API: why run both
None of the three platforms asks you to choose. TikTok’s setup guide recommends sending both the Pixel and the Events API. Pinterest’s API reference says that when you submit data through both the tag and the API, Pinterest removes duplicates. Snap documents how Pixel and API events are paired for deduplication (below).
The price is deduplication: without a shared ID, a purchase seen by the browser and the server is two purchases. See Meta Conversions API deduplication for the idea and client-side vs server-side tracking for why the server copy exists.
Setup comparison
TikTok: pixel code and access token
Create a pixel in TikTok Ads Manager under Tools, Events, Connect data source, Web. Manual setup offers Pixel only, Events API only, or both. TikTok recommends both.
The access token comes from Events Manager: open the pixel, go to Settings and click Generate Access Token. You must be an Admin or Operator on the ad account. A token generated there only works for pixels in the same ad account; a developer app with the “Measurement, Report Conversion Event” permission is the route for one token across several accounts (TikTok, Events API authentication).
Requests go to POST https://business-api.tiktok.com/open_api/v1.3/event/track/ with an Access-Token header. The pixel code is sent in the body as event_source_id, with event_source set to web (TikTok, setup guide for web). Tutorials using the older /pixel/track/ endpoints are out of date: TikTok announced their sunset for the second half of 2024 (Events API 2.0 overview).
Snapchat: Pixel ID and a long-lived token
Snap sends web events to https://tr.snapchat.com/v3/{PIXEL_ID}/events with the token as an access_token parameter. Snap recommends a static long-lived token created in Ads Manager on the Business Details page. You must be an Organization Admin. These tokens do not expire, and they only work for pixels and apps owned by the organization that created them (Snap, Getting started).
Pinterest: ad account ID and a conversion token
In Ads Manager choose Ad Account Overview, Conversions, Conversions API, Set up API, then Conversion access token and Generate new token. The token is displayed together with your ad account ID (Pinterest, track conversions in the API). Events go to POST https://api.pinterest.com/v5/ad_accounts/{ad_account_id}/events with Authorization: Bearer <token>. The token’s user must own the ad account or hold a role such as Admin, Analyst, Audience or Campaign (Pinterest v5 OpenAPI description).
The Pinterest tag has its own tag ID, but the events endpoint in the OpenAPI description takes only the ad account ID in its path.
Capture the click ID on the landing page
A click ID is a pointer to one ad click in the platform’s own log. It arrives once, in the landing-page URL, and by the time the order is paid the customer may have visited ten pages. If your site does not store it, the server event goes out without it and matching falls back on email, IP and user agent.
-
TikTok
ttclid. TikTok describes three ways to keep it: leave the parameter in the URL and send the full URL inpage.url(TikTok’s backend parses it); read the first-party cookie the TikTok Pixel writes, which is also namedttclid; or parse and store it yourself. If you store it yourself, TikTok suggests a 28-day or longer lifetime, refreshed when a newer one appears; its valid period equals your click-through window in Attribution Manager (TikTok, Send ttclid). -
Snapchat
ScCid. Snap appends&ScCid=to the ad’s landing URL. Either pass the value assc_click_idor pass the full URL inevent_source_urland Snap extracts it. Snap also suggestssc_cookie1(the_scidfirst-party cookie) for Snap Pixel users, orexternal_idotherwise. None of these are hashed (Snap, Using the API; Snap, Parameters). -
Pinterest
epik. The value lives in the_epikcookie or in the&epik=URL parameter and goes intouser_data.click_id. Pinterest advises preferring the cookie, because it works when the URL parameter is missing or has been stripped, and says to send it at least on checkout events.
On a WooCommerce site, the usual place to keep the value is the visitor’s session or a first-party cookie set on the first page view, then copy into the order meta when the order is created. That way a payment confirmation arriving minutes later, from a webhook with no browser attached, still has it. Full-page caching is the trap: capture must run in the browser or on an uncached request. For the same pattern with Google’s IDs, see GCLID, GBRAID and WBRAID explained, and for LinkedIn’s, LinkedIn Conversions API for WordPress.
WooCommerce events to platform events
Purchase matters most; add to cart and checkout start help with audiences and drop-off. Where each moment fires in WooCommerce: woocommerce_add_to_cart runs when an item is added (WC_Cart), woocommerce_before_checkout_form runs before the checkout form is shown and woocommerce_thankyou on the order received page (both listed in the WooCommerce hook reference), and woocommerce_payment_complete runs when an order is paid (WC_Order). The thank-you hook can fire again on a page reload, so rely on the order number as the dedup ID. More on purchases in WooCommerce server-side tracking.
Pinterest is the odd one out: its guide names checkout as the event for a completed transaction. Its list also has view_content; the table uses page_visit for a product view as an editorial choice, so match whatever your Pinterest tag sends. TikTok’s standard events are listed in its supported events page.
Purchase value needs care on all three. TikTok says value is the total of the order and price the price of one item. Snap requires currency and value on PURCHASE events. Pinterest takes value as a string and recommends the pre-tax, pre-shipping final value; if you leave the currency out, Pinterest defaults to the advertiser’s account currency.
One order, three requests
The order number becomes event_id everywhere; the requests differ in names, units and hashing.
Hashing: three platforms, three rule sets
All three use SHA-256 for personal data, and all three want you to normalize first and hash second. Hashing an un-normalized email gives a valid-looking hash that matches nobody.
-
TikTok. Email, phone and
external_idmust be SHA-256 hashed. Trim and lowercase email first. Phones go to E.164 (+12133734253), keeping the+, before hashing.ip,user_agent,ttclidandttpare not hashed. -
Snapchat. Hash with lowercase hex SHA-256, and normalize before. Phone numbers include the country code but exclude the
+, spaces and other non-numeric characters, and a leading zero on the number itself is removed. IP address, user agent andsc_click_idare not hashed (Snap, Best practices). -
Pinterest.
emis an array of SHA-256 hashes of lowercased emails. Phone numbers are digits only, with country code and no symbols, spaces or leading zeros. IP address, user agent andclick_idare sent as they are.
The phone difference is real: the same number normalized for TikTok and for Snapchat produces two different hashes, so do not share one hashing helper across platforms without a flag. Check a hash in a terminal with printf '%s' 'alice@example.com' | shasum -a 256.
Minimum user data: Snap needs em, ph, or the IP and user-agent pair; Pinterest needs em, hashed_maids, or that pair. TikTok requires a user object and page.url and recommends email, phone, IP and user agent together.
Deduplication: what each platform actually keys on
TikTok deduplicates on three fields together: event_source_id, event and event_id. If several events share them, TikTok keeps the first and discards later ones received within 48 hours of it. If a later copy arrives within 5 minutes of the first, TikTok tries to merge its data into the first event: if the first lacked user.email and the second has it, the email is added. So the 5 minutes is a merge window inside the 48-hour drop window, not a delay before deduplication starts. Order numbers and transaction IDs are TikTok’s suggested event_id values. In the browser, the ID goes in the third argument: ttq.track('AddToCart', {...}, { event_id: 'abcde12345' }) (TikTok, Event deduplication).
TikTok also has a fallback: with no API event_id but a user.ttp value, it drops an API event that follows a matching browser event within 5 minutes. For a WooCommerce purchase use event_id; the server event may arrive long after the browser’s.
Snapchat pairs the Pixel’s client_dedup_id with the API’s event_id (48 hours) and, for PURCHASE only, the Pixel’s transaction_id with the API’s order_id (up to 30 days). The cross-channel pair takes precedence, the order pair is the fallback. Event names must match, and Snap warns against placeholders such as null or an unrendered template tag. The ID must be unique to a single conversion, “not per session, per visit, or per user” (Snap, Deduplication).
Pinterest asks for the same event_id and event_name in every source. It retains the first captured event and removes duplicates within 48 hours. Two orders need two different IDs. Offline events cannot be deduplicated.
For events without an order number, create a UUID once and pass it to both the browser call and the server queue. Never generate it separately on each side, or at page-build time on a cached page.
Test tools and what good looks like
TikTok. In Events Manager open the pixel, go to the Test Events tab and copy the code from Step 2 of “Test Server Events”. Add it to the request as test_event_code, send a request, then look for the event in the Event Activity section. TikTok says to remove the field before switching to production (TikTok, verify Events API setup). A good response is HTTP 200 with "code": 0. On a batch, errors name the zero-based index of the invalid event, such as data.2.event_id.
Snapchat. Send the same body to /v3/{asset_id}/events/validate. It checks construction without sending production events. /events/validate/logs returns test events from the past 24 hours and /events/validate/stats a count for the last hour. Failures carry a status of INVALID and HTTP 400 for reasons Snap lists: missing price or currency on a purchase, invalid hashed IP, timestamp out of range, unhashed personal data, insufficient personal data (Snap, Verify setup).
Pinterest. Add ?test=true to the events URL. Test data goes to a sandbox and is not used for reporting or optimization, and only the first 20 events of a test batch are processed. Verify in Ads Manager under Campaign manager, Conversions, Test events. Remove the parameter for production. The response contains num_events_received, num_events_processed and a status per event. Pinterest’s own example shows one event failing inside an otherwise normal response, so check the per-event status, not just the HTTP code.
Limits and common errors
- Batch and rate. TikTok: up to 1,000 events per request (more and the whole request is rejected) and 1,000 queries per second per ad account; TikTok recommends sending events one at a time, as they happen. Snap: up to 2,000 events per batch. Snap’s own Getting started page states both a standard limit of 10 requests per second and a recommendation of up to 1,000 QPS, so which applies is unclear; design your queue for the lower number and ask Snap if you need more. Pinterest: up to 1,000 events per request and 5,000 calls per minute per ad account, with real-time sending, or at most one hour of lag, recommended.
-
Event age. Snap’s Parameters page says
event_timecannot be more than 7 days in the past; its Introduction says a maximum of 37 days back. That conflict is on Snap’s side. TikTok’s and Pinterest’s maximum age is not confirmed on any page we could read. A delivery queue that retries for days should check an old event with the test tool. - TikTok code 40002 (invalid payload) lists as causes invalid JSON, a missing field or wrong type, an unhashed value in a field that needs SHA-256, and more than 1,000 events. 40100 means the rate limit was hit. 40104 means an empty access token, and 40001 a permission problem (TikTok, responses and errors).
- Units. TikTok and Pinterest take Unix seconds. Do not send milliseconds.
- Duplicates counted twice. Nearly always an ID mismatch: different casing, a prefix on one side only, a different event name, or an ID generated twice.
Where Traculo fits
Traculo’s WordPress plugin forwards events from Traculo’s servers to TikTok, Snapchat and Pinterest, along with Google Analytics 4, Meta, Google Ads, LinkedIn and Plausible, using a domain API key, so you do not run your own queue or endpoints. The delivery log shows each event with the response from each integration and a success or error status, and it exports to CSV or JSON (up to 5,000 events per export). That log is where the errors above show up: a 40002 from TikTok, an INVALID from Snap, a failed event inside a Pinterest 200. It does not replace the platforms’ own test tools. See the beginner’s guide to server-side tracking for the bigger picture.
Frequently asked questions
Do I still need the TikTok Pixel, Snap Pixel or Pinterest tag if I send server events?
Yes. TikTok recommends running both, and Snap and Pinterest document how Pixel and API events are deduplicated, so both is a supported setup. If the browser tag is blocked, the server event still arrives. Deduplication on a shared ID prevents double counting.
What should I use as the event_id for a WooCommerce purchase?
The order number. All three platforms accept order numbers or transaction IDs, and it stays the same on retries or when the thank-you page reloads. For events with no natural ID, create a UUID once and pass the same value to the browser call and the server request.
Why does Pinterest show a successful request but no conversion?
Pinterest can return HTTP 200 with failed events in the response body, for example for an invalid event_name. Read num_events_processed and each event’s status. Also check that ?test=true is not still on the URL, because test events are not used for reporting.
Is the same SHA-256 hash valid on all three platforms?
For emails, yes if you trim and lowercase first. For phone numbers, no: TikTok wants the E.164 form with the +, while Snap and Pinterest want digits only. Test each platform with its own tool.
How old can a TikTok or Pinterest event be?
Not confirmed on any page we could read. Pinterest recommends real time or at most an hour of lag. Test an old timestamp before relying on a retry queue.
Related reading
- Meta Conversions API for WordPress: the complete guide (cluster hub)
- Dedup rules and limits on every ad platform
- Meta Conversions API deduplication: event_id explained
- LinkedIn Conversions API for WordPress
- GCLID, GBRAID and WBRAID explained
- WooCommerce server-side tracking: purchases, refunds, subscriptions
- Client-side vs server-side tracking in WordPress
- Why is your WordPress analytics data missing?
If you would rather not maintain three sets of hashing rules and request queues, Traculo forwards your WordPress events to TikTok, Snapchat and Pinterest and logs every response. See Traculo integrations and the server-side event tracking page.