Skip to content
Online store

Ad pixels & conversion tracking

Snapchat, TikTok, Meta and Google — events from the browser and the server, with the visitor’s consent

Anyone advertising on Snapchat, TikTok, Instagram and Google needs to know which ad brought an order. You connect those platforms’ pixels and analytics tools to your store and they receive the standard commerce events: product view, add to cart, checkout started, purchase. If you add a platform’s server-side key, the server also sends the purchase with the same order id so it is not counted twice — and only with the visitor’s consent.

On every plan

What this covers

  • Six tools for the store: Google Analytics 4, Google Tag Manager, Meta Pixel, TikTok Pixel, Snap Pixel and Microsoft Clarity
  • The standard commerce events go to every enabled tool: view item, add to cart, begin checkout, purchase — and search and add payment info on the Meta, TikTok and Snap pixels
  • Server-side conversion APIs: Meta Conversions API, TikTok Events API, Snap Conversions API and Google Data Manager API, each with an optional encrypted key
  • The purchase is sent with the same order id from browser and server, so the platform de-duplicates it and your purchase count is not inflated
  • Customer data (e-mail, phone, names) is sent hashed, and only for a visitor who pressed Accept
  • An optional visitor-consent banner, and a browser sending Global Privacy Control or Do Not Track is treated as not having consented, whatever the store chose
  • Google Analytics 4 runs in consent mode v2: every storage type is denied until the visitor accepts
  • Snap’s script is not even downloaded before Accept, and Clarity records nothing until Accept, with checkout, order and booking pages masked
  • An outbox with bounded retries: if a key is refused, sending stops and the owner is told once, so your events are not lost silently
  • Optional extra server-side funnel events for Meta, TikTok and Snap, switched on per platform
  • A booking’s manage page loads no tag from any vendor, because its address is itself a credential

Where this stops

  • The ad tools work on the online store. The server keys are optional: a store that does not enter them runs on the browser pixel alone.
  • Google Tag Manager on its own has no server feed, because it has no measurement id of its own.

We write this here because finding it out during implementation is far worse than reading it now.

Related features

All features
  • On every plan

    Online store

    An online store for every branch — 22 themes, selling from the till’s own catalogue and stock

    17 capabilitiesSee the detail

  • Plan: Professional

    Store insights & abandoned carts

    See what visitors look at, what they left in the cart, then message the ones worth reaching

    12 capabilitiesSee the detail

  • Browse on every plan

    Integrations marketplace

    45 integrations in one place — each with its own connection form, a guide in your language and a live test

    12 capabilitiesSee the detail

See it on your shop

Thirty minutes on your products, your tax setup and your hardware — not a slide deck.