ioZen sends TikTok conversion events with the current Events API 2.0 format, injects the TikTok Pixel on published Intake Bot pages, and deduplicates browser and server events with a shared event ID.
TikTok was quietly dropping our conversion events. The request body shape we were sending had been deprecated, and Events API 2.0 expects a different format. Events looked fine on our side and never showed up in TikTok.
We now send conversions with the current Events API 2.0 request format. ioZen also injects the TikTok Pixel on published Intake Bot pages and fires a browser-side SubmitForm event alongside the server-side Events API call. Both share the same event_id, so TikTok deduplicates them instead of counting twice or missing the browser signal.
Match quality improves with ttclid, the _ttp cookie, and hashed external IDs. A Test Event Code field lets you verify against TikTok’s sandbox in the Test Events tab without touching live data.
Available on all plans.
ioZen now sends TikTok conversion events using the current Events API 2.0 request format, replacing a deprecated body shape that TikTok was silently dropping. ioZen also injects the TikTok Pixel automatically on published Intake Bot pages and fires a browser-side SubmitForm event alongside the server-side Events API call, sharing the same event_id for deduplication. A Test Event Code field lets you verify against TikTok's official sandbox in the Test Events tab. Match quality improves with ttclid, the _ttp cookie, and hashed external IDs.
