Pixels and tracking
Your store sends visitor activity and orders to the ad platforms and analytics tools you connect to it. You manage all of them from one place in the dashboard, with no code to edit.
Available tools
- In the sidebar, open Pixels.
- The Pixels & Analytics page shows one card per tool:
- Facebook Pixel — see Connect Facebook Pixel and Meta Conversions API.
- TikTok Pixel — see Connect TikTok Pixel.
- Snapchat Pixel — see Connect Snapchat Pixel.
- Google Analytics — see Connect Google Analytics.
- Google Tag Manager — see Connect Google Tag Manager.
- Click Open App on the card you want to set up.
A card shows an Active badge once an ID is saved for it, and Inactive when none is.
Tools by plan
| Tool | Plans that include it |
|---|---|
| Facebook Pixel (browser) | Every plan, including PAYG |
| Google Analytics | Every plan, including PAYG |
| TikTok Pixel (browser and server) | Starter and above |
| Snapchat Pixel (browser and server) | Growth, Pro and Enterprise |
| Google Tag Manager | Growth, Pro and Enterprise |
| Meta Conversions API (server-side tracking for Facebook) | Growth, Pro and Enterprise |
If your plan does not include a tool, its card shows a Locked badge and the message Not included in current plan, and its Upgrade Plan button takes you to the plans page.
Events your store sends
| Event | When it is sent |
|---|---|
| Page view (PageView) | When any storefront page opens |
| Product view (ViewContent) | When a product page opens |
| Add to cart (AddToCart) | When a product is added to the cart |
| Start checkout (InitiateCheckout) | When the customer starts typing their name or phone number in the order form on a product page |
| Purchase (Purchase) | When the customer submits their order |
Zimam translates each event into the name each platform uses. For example, a purchase reaches TikTok as CompletePayment, Snapchat as PURCHASE, and Google Analytics as purchase.
Browser tracking and server tracking
- Browser: the pixel runs in the visitor's browser. Ad blockers or privacy settings can stop it.
- Server: Zimam's server sends the same event straight to the platform, so it arrives even when the browser pixel is blocked. This works for Facebook (Conversions API), TikTok (Events API) and Snapchat (Conversions API) once you add an access token, and for Google Analytics once you add a Measurement Protocol API secret.
The server sends product view, add to cart, start checkout and purchase. Page views are sent from the browser only. To Google Analytics, the server sends only the purchase.
How an event is counted once
Every event gets one ID, created before it is sent to any platform, and the browser copy and the server copy carry that same ID. When a platform receives both copies with the same ID, it counts them as one event.
For a purchase, the ID is the order's own ID. Each order therefore counts as one purchase, even when it arrives from both the browser and the server.
Landing pages
The same pixels run on your landing pages. On a landing page you can choose which of your store's Facebook, TikTok and Snapchat pixels run on that page. Google Analytics and Google Tag Manager always run on every page.
Who can save
If your team role does not allow changing store settings, you can see these settings but the save button stays disabled.