Without tracking, ad platforms only know who clicked. With tracking, they know who bought, booked or enquired, and they can find more people like them. Browser restrictions, ad blockers and privacy settings mean the Pixel alone now misses some actions, which is why the Conversions API was introduced. The Academy's glossary explains the pixel and Conversions API.
Pixel versus Conversions API
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | Visitor's browser | Your server or platform integration |
| Setup | Code snippet or partner integration | Server setup, partner integration or gateway |
| Affected by browser limits | Yes | Less so |
| Data | Page views, clicks, events in the browser | Events sent directly, including offline or CRM events |
| Best use | Together with the Conversions API | Together with the Pixel |
Standard events
Events describe what people do. Common standard events include:
- PageView: a page loaded.
- ViewContent: a product or key page viewed.
- AddToCart: an item added to a basket.
- InitiateCheckout: checkout started.
- Purchase: an order completed, with value.
- Lead: an enquiry or form submitted.
- CompleteRegistration: a sign-up completed.
Choose events that match your business and set the most important as your optimisation goal.
Setting up the Pixel
- Create a dataset (Pixel) in Meta Events Manager.
- Add the code to your website, or connect through your website platform's integration.
- Set up standard events for key actions.
- Test with Meta's test events tool.
Many website builders and ecommerce platforms offer simple integrations that handle both Pixel and Conversions API.
Setting up the Conversions API
Options include partner integrations in ecommerce and website platforms, Meta's Conversions API Gateway or a custom server setup. Small businesses usually choose a partner integration because it needs no coding and stays updated automatically.
Deduplication
When both Pixel and Conversions API send the same event, Meta needs to recognise it as one action, not two. Matching event names and event IDs from both sources allows deduplication. Partner integrations usually handle this automatically; check in Events Manager that events are not double counted.
Event match quality
Meta scores how well it can match events to people, based on information such as hashed email or phone number sent with events. Higher match quality improves optimisation and reporting. Only send customer information you are allowed to share, hashed as required.
Consent and privacy
In the UK, placing tracking cookies and similar technologies for advertising generally needs consent under PECR, and personal data must be handled lawfully under UK GDPR. Your cookie banner should allow people to refuse advertising tracking, and tracking should respect their choice. The Academy's guide to cookie consent for ad pixels explains the rules, and the glossary covers PECR.
Checking tracking works
Use Events Manager to see events arriving, the test events tool to check new setups and browser extensions such as Meta Pixel Helper to inspect the Pixel. Make a test purchase or enquiry and confirm it appears once, with the right value.
Tracking on other platforms
TikTok, LinkedIn, Pinterest and Snapchat offer similar tools: a browser pixel or Insight Tag and a server-side events API. The principles are the same: track key events, combine browser and server data, and respect consent.
Why tracking quality matters for results
Platforms optimise towards the events they receive. If purchases are missing or doubled, the system learns the wrong lessons. Instagram's documented organic signals are watch time and completion, likes, shares (sends per reach), saves, relationship history✓, but for ads the key signal is conversion data: better data means better delivery.
Offline and CRM events
Businesses that close sales by phone or in person can send offline events, such as a booked appointment or a signed contract, back to Meta through the Conversions API. This shows which ads lead to real revenue, not just form fills, and helps the platform find higher-quality leads. Many CRM systems offer integrations for this.
A worked example
An online homeware shop relies on the Pixel alone and sees fewer purchases reported in Meta than in its shop dashboard. It enables its ecommerce platform's Conversions API integration, confirms deduplication in Events Manager and improves match quality by sending hashed emails for customers who consented. Reported purchases align more closely with real sales, and cost per purchase falls as the system learns from fuller data.
Choosing the right optimisation event
Optimise for the event closest to real business value that still happens often enough for the platform to learn. A shop with plenty of daily sales should optimise for Purchase. A business with few sales might start with AddToCart or InitiateCheckout, then switch to Purchase as volume grows. Lead businesses can optimise for Lead and send qualified lead events from their CRM later, so the system learns which leads become customers.
Keeping tracking healthy
Website redesigns, new checkout systems and plugin updates often break tracking without anyone noticing. Add a tracking check to every website change, review Events Manager weekly for sudden drops or spikes and set up alerts where available. A few minutes of checking prevents weeks of campaigns optimising on broken data.
Common mistakes
- Relying on the Pixel alone.
- Double counting events without deduplication.
- Tracking without proper consent.
- Optimising for an event that rarely fires.
- Never testing after website changes.
Learning tracking
The Academy's paid social module in the third level covers pixels, the Conversions API and audiences, and the analytics module on attribution and ROI covers measuring results. The free assessment shows where you would start.
