ioZen captures utm_id from landing URLs and shares an event ID between the browser pixel and server-side conversion calls, so ad platforms deduplicate correctly.
Two fixes to attribution accuracy.
ioZen now captures the utm_id campaign ID from landing URLs. Ad platforms substitute a numeric ID there (TikTok’s campaign ID, Meta’s campaign ID), and it’s the stable key to track by, since utm_campaign carries a name that changes whenever someone renames the campaign. It shows up on the submission attribution panel and as a CSV export column.
Browser event IDs and the pixel cookies are now stored on the submission when the form completes, so the server-side conversion call shares an event ID with the browser pixel event. Ad platforms use that shared ID to deduplicate the pair instead of counting one conversion twice. Pixel events also now fire only after the submission is durably saved, so a failed save can no longer report a conversion with no matching record behind it.
Available on Pro, Business, and Enterprise plans.
ioZen now captures the utm_id campaign ID from landing URLs. Ad platforms substitute a numeric ID there (TikTok's __CAMPAIGN_ID__, Meta's campaign.id), and it is the only stable campaign key since utm_campaign carries a name that changes on rename. It appears on the submission attribution panel and as a CSV export column. Browser event IDs and the _fbp/_ttp pixel cookies are now stored on the submission when the form completes, so the server-side Conversions/Events API call shares an event_id with the browser Pixel event and the platform deduplicates the pair instead of counting the conversion twice. Pixel conversion events also fire only after the submission is durably saved, so a failed save can no longer report a conversion with no matching record.
