Connect tracking pixels and analytics tools
Send checkout and purchase events to Meta, Google Analytics 4, Google Tag Manager, TikTok, X and LinkedIn, record sessions with Microsoft Clarity or Hotjar, and choose which checkouts use which integration.
A tracking integration tells an outside platform what happens on your checkout: someone opened it, chose an offer, paid. Ad platforms use that to measure and optimize campaigns; analytics tools use it for reports and recordings. When you finish, at least one platform will be connected, set as the default for your checkouts and tested. You never paste a script: Zanfia only asks for the platform's ID and, where it exists, a token.
The platforms
All of them are cards under Integrations → Analytics (/integrations/analytics).
| Platform | What it does | What you enter |
|---|---|---|
| Meta Conversion API | Sends purchase and checkout events to Meta (Facebook and Instagram ads) with your own pixel | Pixel ID and Access token (starts with EAA) |
| Google Analytics 4 | Measures visits, checkout steps and purchases in your GA4 property | Connect with Google, or Measurement ID (G-…) and an optional API secret |
| Google Tag Manager | Loads your container on checkout and thank-you pages so you manage extra tags yourself | Container ID (GTM-…) |
| TikTok | Sends checkout and purchase events to your TikTok pixel | Pixel ID, optional Events API token |
| X | Sends checkout and purchase events to your X pixel | Pixel ID, optional token and event tags |
| Sends checkout and purchase events to your LinkedIn Insight Tag | Partner ID, optional token and conversion-rule URNs | |
| Microsoft Clarity | Session recordings and heatmaps of your checkout pages | Project ID |
| Hotjar | Session recordings and heatmaps of your checkout pages | Site ID |
Coming soon
The Meta Ads card (connecting a Meta account to pull ads performance and set up pixels automatically) shows Coming soon. To track Meta conversions today, use Meta Conversion API with your own pixel and token.
Connect a platform
Open the card
Go to Integrations → Analytics and click Connect on the platform's card. The window Connect [platform] opens.
Enter the ID and the token
Type a Name of the integration (only you see it; it tells accounts apart) and the ID from the table above. Where do I find this? under a field unfolds step-by-step instructions and a button that opens the platform. Paste only the ID: a whole installation snippet is refused with a validation message. For Google Analytics 4 you can skip the typing: Connect Google account, pick the GA4 property and its web data stream, and Zanfia creates the secret for you.
Choose the events
On the Events step choose what Zanfia sends: Purchase, Checkout started, Add to cart and Trial started. If you are not sure, leave the suggested selection as it is. Tag Manager, Clarity and Hotjar have no events to choose, so their window has a single step.
Set it as the default and save
Leave Set as default for new orders on so your checkouts send events to this integration automatically, then save. You see Integration saved. The card now shows Connected, the number of accounts and a line Default · [name].
Good to know
Platforms with an optional token work in two modes. Without the token the card says Browser events only: events are sent from the customer's browser and can be lost to ad blockers. With the token it says Browser + server events: purchases are also reported from Zanfia's servers.
Choose which checkouts use it
Each checkout sends its events to one integration per platform.
Open the checkout's Tracking tab
Open a checkout, switch the view at the top to Analytics (/checkouts/<id>/analytics) and
open the Tracking tab.
Keep the defaults or customize
Use workspace defaults makes the checkout follow the defaults you set under Integrations → Analytics. If no default exists, the tab warns that the checkout tracks nothing. Custom for this checkout lists every platform on the left with its status (Assigned or Not assigned); pick the integration for each platform you want and save.
Test it
Test integrations opens the checkout in test mode: events go to the platforms' test tools and are tagged TEST in the events log, so no production data is recorded. Meta and TikTok need a test event code from their Events Manager; Google Analytics 4 needs none, its events appear in DebugView.
Cookie consent and recordings
Browser-side tags respect your cookie banner (Your privacy matters, with Accept all and Reject all). A visitor who rejects cookies is not tracked by pixels, and Clarity and Hotjar stay off completely; they run only after the visitor accepts analytics cookies. In the recordings, what visitors type into form fields is masked.
Check that events arrive
| Where | What you see |
|---|---|
| The card's Manage window | Status of each account over the last 7 days: Active, Issues, Failing or No events yet, with counts of delivered, failed, sent from browser and blocked by cookie consent |
| Analytics → Traffic & conversions → Events | Every event with its status and integration, for the whole workspace |
| A checkout's Analytics → Events tab | The same log for one checkout |
No events yet is not an error: the first events appear when a customer visits a checkout or places an order. A card marked Needs attention has an integration that was disabled or is failing; open Manage to read why. The usual cause is an access token that expired or was revoked: edit the integration, paste a fresh token and save to switch it back on.
Change or remove an integration
Manage lists the accounts of a platform. You can edit one (a saved token is kept when you leave the field blank), set or remove the default, add another account, or remove one. Removing asks for confirmation: "Remove this integration? Checkouts that use it will stop sending events to this platform."
Was this article helpful?