Tracking Pixels and Conversions API
Set up pixels to track conversions and optimize your ad campaigns.
What it does
Tracking pixels send your Horsee store's events (page view, product view, cart, checkout and purchase) to Meta, Google, TikTok and Taboola, so those platforms can measure conversions and optimize your ads. Meta, Google Analytics 4, Google Ads and TikTok also receive the events from the server (server-side), which reduces the data lost to ad blockers and browser cookie restrictions.
Supported platforms
- Meta Ads (Facebook/Instagram): browser pixel + Conversions API (CAPI) on the server.
- Google Analytics 4: browser tag + Measurement Protocol on the server.
- Google Ads: conversion tag, with one conversion label per event.
- TikTok Ads: pixel + TikTok Events API on the server.
- Taboola: conversion pixel in the browser (Taboola has no server-side sending).
Step by step
- In the store menu, open Marketing > Tracking.
- Click New Pixel, pick the platform and click Connect.
- Fill in the platform fields:
- Meta: Pixel ID and Access Token (CAPI). The Test Event Code is optional.
- GA4: Measurement ID (format G-XXXXXXXXXX) and API Secret, which you create in GA4 under Admin > Data Streams > Measurement Protocol API secrets.
- Google Ads: the account ID (AW-…) and the conversion labels for each event.
- TikTok: Pixel ID and Access Token (Events API).
- Taboola: Account ID and, if you have one, the Pixel ID.
- Choose the sending channels: Server-Side (CAPI), Client-Side (Browser), or both.
- Save and use Test to check the pixel. Changes apply right away on the published store, with no need to republish.
Events tracked automatically
These events fire with no extra setup:
- PageView: a visit to any page
- ViewContent: a product view
- AddToCart: an add to cart
- InitiateCheckout: the start of checkout
- AddPaymentInfo: payment details entered
- Purchase: a completed purchase (with value and items)
- Lead: a sign-up or lead capture
The Event History tab lists the events that were sent.
Pixel Diagnostics
The Pixel Diagnostics screen shows how your sends are doing over the last 24 hours, 7 days or 30 days: total events, failure rate, events skipped because of consent, duplicates, Purchase match quality (EMQ: how many purchases arrived with email, phone, _fbp and _fbc) and the most frequent errors. It is the best place to confirm that Purchase is firing. The screen doesn't have a menu shortcut yet: open the address /inside/stores/<store-id>/pixel-diagnostics in the dashboard.
Common errors
- Access Token is required when server-side sending is on: paste the platform's token or turn off Server-Side.
- Turn on at least one sending channel: turn on Server-Side, Client-Side, or both.
- Google Ads without a conversion label: the pixel loads, but Google Ads records no conversions. Add a label for every event you want to measure.
- Failure rate above 5% in Diagnostics: read the platform's message under Top errors. An expired token, or one without permission, is fixed by creating a new token and updating the pixel.
To check in the browser, use the Meta Pixel Helper and Google Tag Assistant extensions (Chrome).
Was this article helpful?
Your feedback helps us improve our guides