How TikTok tracking works in Releva
The TikTok integration is a server-side event feed. Once you connect a TikTok For Business account under Settings › TikTok and choose an ad account and a pixel, Releva sends standard TikTok events (ViewContent, AddToCart, Purchase and others) to that pixel through TikTok’s Events API, from Releva’s servers. It does not create ads, audiences or pixels, and it has no public API: you connect and configure it only in the admin. Your website’s TikTok pixel keeps working as before; Releva adds the events it sees on its side, such as orders that arrive through a platform webhook.
This page explains the pieces and what Releva sends. To set it up, follow Connect TikTok to Releva and Send your store’s events to TikTok.
The pieces
Section titled “The pieces”| Setting | Where | What it does |
|---|---|---|
| Connection | Settings › TikTok, Connect TikTok to Releva | A TikTok For Business login. Releva stores an access token plus the TikTok user’s display name and e-mail (shown as Name and Email). Everything below needs it. |
| Ad account | Settings › TikTok | The TikTok advertiser account whose pixels you can pick. Releva lists the ad accounts the connected user can see. |
| Pixel | Settings › TikTok | The pixel that receives every event. Releva stores the pixel code and sends it to TikTok as the event source. Without a pixel nothing is sent. |
| Backend Tracking | Settings › TikTok, OFF / ON | The master switch. OFF stops all sending and keeps your event list. |
| Tracked events | Settings › TikTok | Which of the eight standard events Releva sends. Editable only while Backend Tracking is ON. |
Any user with access to the shop in the Releva admin can open the page and change these settings.
Events Releva sends
Section titled “Events Releva sends”Releva maps the activity it tracks for your shop to eight TikTok standard events:
| TikTok event | Sent when Releva records | Carries |
|---|---|---|
ViewContent |
a product view | the product (content_id, name, first category, price, brand), value, currency |
AddToCart |
products added to the cart | the added products as contents, value (price × quantity), currency, num_items |
InitiateCheckout |
a started checkout, reported by your platform integration (for example the Shopify connector) | the cart products, value, currency |
Purchase |
a completed order | the ordered products, value, currency, order_id |
AddToWishlist |
products added to the wishlist | the products, value, currency |
Search |
an on-site search | search_string |
CompleteRegistration |
a new registration | user data only; registrations older than 7 days are not sent |
Subscribe |
a newsletter subscribe captured by Releva (the subscribe endpoint) | user data only |
Where these actions come from (the JS SDK, a platform connector or the events API) is explained in How events get into Releva.
Two things are never sent to TikTok:
- Page views. Your TikTok pixel already sends them from the browser; a server-side copy would double-count with no way to deduplicate.
- Add payment info. TikTok’s Events API has no standard event for it.
Custom events your integration sends to Releva (event names of the form custom/<name>) are forwarded to TikTok under <name>, with their products, order id and custom properties. They are not in the Tracked events picker and are not filtered by it: whenever Backend Tracking is ON, every custom event goes through.
What decides whether an event is sent
Section titled “What decides whether an event is sent”Releva checks, in this order:
- The shop has a TikTok connection with a Pixel. Otherwise nothing is sent and nothing is queued.
- Backend Tracking is ON.
- The event is in Tracked events, or it is a custom event.
The event list has three states:
| Stored value | Meaning | When you see it |
|---|---|---|
| Not set | Send all eight events | A fresh connection. The picker shows all eight events selected. |
| A list | Send only these | The first time you switch Backend Tracking to ON, Releva fills in all eight explicitly; you then remove what you do not want. |
| An empty list | Send none of the eight (custom events still go) | You cleared the picker with the × at its right. |
Switching Backend Tracking to OFF does not clear the list. Switch it back ON and the same events are sent again. Releva rejects any name that is not one of the eight; the picker only offers those eight.
One consequence worth knowing: a started checkout only ever reaches TikTok as InitiateCheckout. Remove it from the list and TikTok gets nothing for that action.
What every event carries
Section titled “What every event carries”Besides the event-specific properties above, every event sent to TikTok has:
event_time: when the action happened, in Unix seconds.user.emailanduser.phone, hashed with SHA-256. The e-mail is trimmed and lower-cased first; the phone keeps only digits and a leading+.user.external_id: the Releva user id, hashed with SHA-256.user.ipanduser.user_agentof the visitor, when Releva has them.user.ttp: the visitor’s TikTok browser id (see below), when Releva has it.page.url: the page the action happened on, when known.event_id: only when your integration passed aneventIdwith the event. Releva never generates one.
Events are queued and sent to TikTok in batches of up to 1000. A batch TikTok rejects is retried. Releva attaches no test event code, so what you see in TikTok Events Manager is live data.
Avoid duplicates
Section titled “Avoid duplicates”If your website’s pixel and Releva both send the same event for the same action, TikTok counts it twice unless both carry the same event ID. The settings page warns about this:
Events can be duplicated. Events will be duplicated in your TikTok Pixel if they are sent both from your website and from Releva’s servers, unless both carry the same event ID. Enable only events that your website does not already send.
Two ways to avoid it:
- Keep the lists disjoint. Under Tracked events, keep only the events your website does not already send through the pixel. Typical choice: keep
Purchasewhen orders reach Releva through a platform webhook, removeViewContentandSearchwhen the pixel already sends them. - Share an event ID. A developer sends the same id to the TikTok pixel in the browser and as
eventIdon the event sent to Releva. TikTok then deduplicates the two. This needs work in your integration; Releva cannot do it for you.
The _ttp browser id
Section titled “The _ttp browser id”TikTok’s pixel sets a cookie named _ttp in the visitor’s browser. The Releva JS SDK reads it on every push and sends it along as ttp; nothing has to be configured. Releva remembers it per visitor for 365 days and attaches it as user.ttp to every event it sends to TikTok, including server-side events such as a purchase reported by a platform webhook, so TikTok can match them to the browser session.
Releva only stores the id when the shop has a TikTok connection with a pixel. Releva never sets the cookie itself: the TikTok pixel must be on your website. The mobile SDKs have no TikTok support.
Disconnecting
Section titled “Disconnecting”Disconnect TikTok from Releva removes the connection and all its settings (ad account, pixel, event list) from Releva at once, without a confirmation step. Sending stops. It does not revoke Releva’s access inside TikTok For Business; do that in TikTok if you want. Connecting again starts from an empty configuration.