TikTok Events API, server-side

Your conversions (purchases, leads, sign-ups, custom events), not every page view. For each one:

• the value, the currency and an event identifier;
• the TikTok click ID (ttclid), in full. TikTok states that it can be up to 1,000 characters long and must not be cut. Oriva reads it from the landing URL, or from the TikTok pixel cookie if the URL no longer carries it;
• the TikTok pixel cookie (_ttp), the IP address and the browser;
• email, phone and customer ID, in TikTok's own format (the phone keeps its “+”, unlike Meta), irreversibly hashed before they are stored.

A standard event is recognized directly by TikTok. TikTok uses a custom event only for reporting and audiences, never to optimize a campaign: avoid TikTok's reserved event names and keep the name short.

Yes. TikTok deduplicates an event received from the browser and from the server when it carries the same name and the same event identifier. Give the same order reference to your pixel and to Oriva.

TikTok ties a conversion to the day the ad was seen, Oriva to the day of the sale. On a given day the two figures can therefore differ without any send missing. Oriva's dashboard puts the two figures side by side and explains the gap.

With the test event code of your pixel (TikTok Events Manager, Test Events tab). The “Test this destination” button sends a test call and shows you TikTok's answer, without creating a fake sale. Without a test code, Oriva refuses to send the test, so it never touches your real data.

Same rule as for Meta: without the visitor's agreement for advertising, nothing goes to TikTok.

• your TikTok pixel code;
• an Events API access token, generated in the pixel's settings (copy it and keep it safe);
• optional: a test event code.