Tracking pixel
A tracking pixel is a small code placed on your store pages that tells the ad platform what visitors do: opened a page, started an order form, completed an order. These signals build retargeting lists, train the algorithm on who buys, and tie each order to the ad it came from.
Also calledPixelConversion pixelTracking codeEvent tracking
The formula
Tracking accuracy = (Orders recorded in platform ÷ Orders in your store dashboard) × 100
- Orders recorded in platform: count of "purchase" events the pixel captured in the period.
- Orders in your store dashboard: actual count of incoming orders in the same period.
- Result is a percentage: the closer to 100%, the more accurate your measurement.
Worked example
How to spot a pixel giving you incomplete data
- 1Your store dashboard shows 74 orders for the week.
- 2The ad platform logged 60 "purchase" events in the same period.
- 3Tracking accuracy = (60 ÷ 74) × 100 ≈ 81%, so 14 orders were missed.
- 4After fixing event firing on the thank-you page: 72 of 74, roughly 97%.
Takeaway: The platform's algorithm learns only from what reaches it; losing 19% of orders means improvements built on incomplete data and decisions to pause winning campaigns.
What it means in practice
In COD a "purchase" event logs when the form is submitted—before confirmation call and before delivery. So the platform's purchase count always leads actual collected orders, and the gap is your confirmation and delivery rates.
Test the pixel before any big launch. Open a product page, submit a test order, and confirm all three events arrived: page visit, form start, order complete. Event-debug tools in the platforms show them live and catch missing or duplicate events.
A duplicate event is as deceptive as a missing one. Installing the pixel twice on the same page doubles the recorded orders, so returns look excellent and you scale a losing campaign. Compare platform numbers to your store dashboard weekly instead of trusting one side.
Common mistakes
- Installing the pixel without setting up events: lists build incomplete and the algorithm doesn't learn from buyers.
- Installing the pixel twice on the same page, doubling recorded orders and making returns look better than they are.
- Changing your store template or thank-you page without re-testing events—tracking stops silently for weeks.
- Judging campaigns by platform numbers alone without comparing to your order log, when the gap might be dozens of orders.
Questions and answers
What's the difference between the pixel and my store's order dashboard?
Your store dashboard records orders as they happened. The pixel records what it captured and attributes it to an ad. A gap is normal, but a large one means a broken event. Compare the two numbers weekly and trust your store dashboard for money.
Does the pixel work with Shopify, YouCan, and Lightfunnels?
Yes, all three support ad platform pixels and event setup. The critical step after installation is the same everywhere: submit a test order and verify page-visit, form-start, and order-complete events arrived.
Does the pixel track orders from direct messages?
No. An order from a private message or call never passes your page, so the pixel can't catch it. Log those orders and their source manually, or your campaigns look weaker than they are and you might pause an ad that actually sells.
Why do platform numbers change after a day or two?
Because attribution updates retroactively: late events arrive and the platform re-ties some orders to ads the customer saw earlier. So don't make pause decisions on hours-old numbers—wait for the time window to stabilize.