Developer docs
An overview for developers and technical partners: how the pixel, the store integrations, and the server-side push fit together. Full endpoint reference is in progress.
Trakt has three jobs: capture the ad click first-party, receive the order server-side, and report the conversion back to the ad platforms. Each part is designed so that a hostile browser or a broken theme cannot silently take tracking down.
A lightweight first-party script served from your own domain. It records the click id (gclid, gbraid, fbclid, msclkid, ttclid) on landing and mirrors visitor and session ids into first-party cookies.
A WooCommerce plugin or a Shopify app sends the order to Trakt server-side, carrying the identifiers the pixel stamped, so the sale can be matched to the session that earned it.
Trakt reports the recovered conversion to Google (offline conversion import) and Meta (Conversions API) from the backend, with the click id attached.
Every push can run in shadow: the exact payload is built and logged without being sent, so you can reconcile before anything is written to an ad account.
Ingestion
The store integrations post orders to Trakt over HTTPS with an HMAC signature over the raw request body, so the payload cannot be tampered with in transit and Trakt can verify it came from your store. Order data flows server to server; it never depends on the shopper completing a client-side callback.
For technical partners
Trakt is built by a Shopify development partner, so the integration surface is designed to be understood, not just installed. If you are an agency or platform that wants to integrate Trakt for your clients, or you want early access to the endpoint reference, get in touch and we will bring you in.
The endpoint documentation is in progress. Start a workspace to see the integration in your own account, or reach out for early access.