Platform
A first-party pixel that runs on your own domain, captures the ad click the moment a visitor lands, and ties it to a session that survives ad blockers, Safari, and the end of third-party cookies.
The Google and Meta pixels are third-party scripts, and browsers are steadily shutting them down. Ad blockers drop them, Safari caps their cookies at seven days, and third-party cookies are ending outright. The result is that a third or more of your conversions never make it back to the platform that earned them.
How it works
The Trakt pixel is served from your own site, so browsers treat it as first-party and leave it alone. It records the click id (gclid, gbraid, fbclid, msclkid, ttclid) the instant a visitor arrives and stamps it onto a visitor and session that persist, then mirrors those ids into first-party cookies so the eventual order can be matched back to the exact click.
gclid and gbraid from Google, fbclid from Meta, msclkid from Microsoft, ttclid from TikTok, all recorded first-party the moment the visitor lands.
Because it is first-party, the pixel is not blocked or truncated the way the platform pixels are. The session lives long enough to connect to the purchase.
When the order arrives from Shopify or WooCommerce, Trakt matches it to the browsing session the pixel recorded, then pushes the conversion back with the click id attached.
A single async script that does not slow your store. No tag manager gymnastics, no per-page setup, no changes to how your ads are built.
What it feeds
The pixel is the first link in the chain. Once the click is captured first-party, Trakt can join it to the order, report the recovered conversion to Google and Meta server-side, keep first and last touch apart, and reverse refunds against the right campaign. None of that is possible if the click is lost at the door.
Install the app or plugin, run it in shadow mode, and see how many clicks your third-party pixels were dropping.