In this guide
- Ad tracking links an ad click to a sale. It uses UTMs, click IDs, pixels, server events and, later, offline conversions.
- Each layer covers a gap in the one before. None is complete alone.
- Start with consistent UTMs, click IDs and server-side purchases.
Ad tracking sounds like one thing and is really a stack. Each layer answers a different question, and each fails in a different way. This page explains the layers in order, what they do and where they leak, and gives a small starter set-up. For deeper pages follow the links. For the whole system see attribution tracking and conversion tracking FAQ.
Layer 1: UTMs
UTMs are parameters you add to ad links: source, medium, campaign, content and term. They tell your own analytics where a visit came from. They are free and universal, and they only work if you use one naming scheme and the parameters survive redirects. See avoiding UTM removal.
Brands that grow on cleaner data
Stores and agencies use Open Tracked to see which ads earn the sale.
Layer 2: click IDs
Platforms add their own IDs to ad links, such as gclid for Google Ads and fbclid for Meta. They let the platform link a later conversion to the exact click. They must be captured on arrival and kept. Safari may remove some. See Safari removes click IDs.
Layer 3: pixels and tags
Pixels in the browser report page views and conversions to the platforms. They are easy to set up and miss events when blockers and browser limits intervene. See how to add the Meta pixel with GTM.
Ask Ari instead of digging through reports
Ari reads your tracking and ad data and answers in plain words.
Layer 4: server-side events
Your server sends conversions directly to the platforms, with customer data for matching. It recovers what the browser lost. See Conversions APIs explained.
Layer 5: offline conversions
Later stages, such as a qualified lead or a closed deal, are sent back so the platform learns what a good customer looks like. See offline conversions.
What each layer sees
| Layer | Sees | Misses |
|---|---|---|
| UTMs | Your own source and campaign | The exact click; they can be stripped |
| Click IDs | The exact click | Lost in Safari and redirects |
| Pixels | Browser events | Blocked requests |
| Server events | Orders and leads with customer data | Needs consent and good data |
| Offline conversions | What happens after the lead | Needs the identifiers saved at the form |
A starter set-up
One UTM scheme
Write it down and use it for every link.
Capture click IDs
Into a first-party cookie, then onto the order or lead.
Pixels for key events
Page view, add to cart, purchase, lead.
Server-side purchase and lead
With a shared event ID and hashed customer data.
A weekly check
Platform numbers against store orders.
With Open Tracked, steps 2 and 4 are covered by the server container and power-ups such as Click ID Restorer and Cookie Keeper, on every plan, and the analytics shows spend and orders together.
A realistic example
A small store runs Meta ads and sees 140 purchases in Meta against 210 orders in its shop. It reviews the layers. UTMs are inconsistent, with "Facebook", "facebook" and "fb" all in use, so its analytics scatters the traffic. Click IDs are lost for iPhone visitors. The pixel misses blocked visitors, and there are no server events. The team fixes the UTM scheme in an afternoon, adds a server container with purchase events and hashed e-mail, and restores click IDs for Safari. A month later Meta shows about 185 purchases against the shop's 215, and the analytics report finally groups traffic sensibly. None of the fixes was advanced. Each addressed one layer that had been leaking.
Raw events in. Clean events out.
Open Tracked collects each event on your own domain, removes the noise and sends what is left to Meta, Google Ads, TikTok.
Frequently asked questions
What is ad tracking?
Linking ads to the actions people take afterwards, with UTMs, click IDs, pixels, server events and offline conversions.
Which layer matters most?
Server-side purchase events with good matching data, supported by UTMs and click IDs.
Why do I need UTMs if I have click IDs?
UTMs feed your own analytics, and click IDs feed the platform.
Is the pixel enough?
Rarely. It misses events lost in the browser.
How do I check my tracking?
Compare platform numbers with your store each week.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Integrations · 6 min read
