Documentation

Everything you need to go from zero to verified server-side events. Setup takes about 15 minutes and requires no theme edits and no developer.

Quickstart

  1. Create a Shopify custom app. In your Shopify admin, go to Settings → Apps and sales channels → Develop apps and create an app for TrackedSale. Under API credentials, grant the Admin API scopes for orders and script tags, install the app, and copy the Client ID and Client secret.
  2. Connect the store. In TrackedSale, add your store with its myshopify.com domain and paste the Client ID and secret. We validate the credentials before anything is saved, pull your shop's real timezone and currency, register the orders/create webhook and inject the storefront snippet automatically. If a credential is wrong, nothing is created.
  3. Add your destinations. For each platform, paste the IDs and API tokens from that platform's own dashboard: Meta (Pixel ID + Conversions API token), TikTok (Pixel code + Events API token), Google (tag ID), Klaviyo (public API key) and Pinterest. Each pixel can be toggled on and off independently.
  4. Verify. Place a test order or use Meta's Test Events code (supported natively) and watch the event arrive in your platform's event manager within seconds. The store page shows per-destination delivery status.

How tracking works

TrackedSale runs two capture paths that reinforce each other:

  • Browser context. A lightweight script captures on-site events (page views, add to cart, checkout) along with click IDs (fbc/fbp, ttclid, gclid, epik) and consent state, and sends them to our edge servers.
  • Webhook truth. Purchases come from Shopify's orders/create webhook — signed by Shopify, verified on our servers. Order values are what Shopify says they are, not what a browser script managed to observe before being blocked.

Browser and server events share one event_id, so platforms that receive both automatically discard the duplicate — you get the richer match data without double counting.

What each platform receives

  • Meta CAPI: SHA-256 hashed email, phone, name and address; fbp/fbc click IDs; order value and items; event_id for deduplication.
  • TikTok Events API: hashed email and phone, ttclid, order value, event_id.
  • Google: tag-based conversions with enhanced match fields and verified order values.
  • Klaviyo: full order details and profile matching for flows and segments (Klaviyo receives plain-text profile data, as its API requires).
  • Pinterest: hashed email, epik click ID, event_id.

Every event carries the shopper's consent state. Where consent is denied, marketing destinations are gated and Google receives the corresponding Consent Mode signals. TrackedSale never force-grants consent on a shopper's behalf.

Next steps

Questions we hear often are answered in the FAQ. Ready to see your own numbers? Start your free trial — no card required.