Meta Pixel · Facebook Pixel
Events fire. Audiences grow. Ads get smarter.
Meta Pixel is the JavaScript snippet every Meta advertiser needs on their site. It fires events as users browse — PageView, ViewContent, AddToCart, Purchase — and reports back to Meta. Those events build retargeting audiences, train ad-delivery algorithms, and measure conversions. Without the Pixel, your Meta ads are targeting in the dark.
Pixel event stream · fbq.fire()
Live · simulated user journey
fbq('track', 'PageView');
event #1
{
"event_name": "PageView",
"event_time": 1745148320,
"source_url": "/shop",
"user_agent": "Mozilla/5.0...",
"fbp": "fb.1.1745..1234",
}
Recent events
PageView
ViewContent
AddToCart
InitiateCheckout
Purchase
Custom audiences · Business Manager
Updating live
All Visitors
Triggers: PageView
+1
25,420
+0 this session
Product Viewers
Triggers: ViewContent
18,340
+0 this session
Cart Abandoners
Triggers: AddToCart, InitiateCheckout
3,418
+0 this session
Recent Purchasers
Triggers: Purchase
1,847
+0 this session
Lookalikes available:
4 seed audiences → 12 LAL targets
The events that matter
17 standard events, 6 you'll actually need.
PageView
Fires on every page. Base signal. Installed automatically when Pixel loads. The baseline of all audiences.
ViewContent
User viewed a specific product/content. Pass content_ids + value + currency. Enables product-level retargeting.
AddToCart
User added item to cart. High-intent signal. Primary abandonment-recovery audience trigger.
InitiateCheckout
User started checkout flow. Closest to conversion. Retarget aggressively — 10-20% recover with well-timed ads.
Purchase
Transaction completed. Pass value + currency + order_id. Trains conversion optimisation. The north-star event.
Lead / CompleteRegistration
Non-ecomm conversions: form-fill, sign-up, booking. For lead-gen sites, this is your Purchase equivalent.
Why Pixel alone isn't enough
Pair the Pixel with the Conversions API (CAPI).
iOS 14+, Safari ITP, and EU privacy laws block ~30-50% of browser-side Pixel fires. CAPI is the server-side counterpart — it sends the same events directly from your server to Meta. Together they close the gap.
Pixel only (browser-side)
- • Blocked by ad blockers (~25% of EU users)
- • iOS 14+ Safari: 7-day attribution window only
- • Privacy extensions strip Pixel fires
- • Cookies gone within browser session
- • Meta receives 50-70% of actual events
Pixel + CAPI (server-side backup)
- • Server-side events can't be ad-blocked
- • Fires even when browser Pixel fails
- • Hashed PII (email, phone) enables attribution
- • Event deduplication via event_id
- • Meta receives 95-100% of actual events
Event Match Quality (EMQ) score: Meta grades your CAPI implementation 0-10. Below 6 = ads underperform; 8+ = strong attribution. We set up CAPI with proper PII hashing, event_id deduplication, and server-side event builders to score consistently 8-9.
Proper Pixel setup
What "installing the Pixel" actually means in 2026.
Most SMBs "have Pixel installed" but it's misfiring 40% of events. Proper setup is 8 specific things — miss any and ad performance suffers.
01
Base Pixel code on every page
Added to site `<head>` (or via GTM). Loads `fbq` library. PageView fires automatically. Foundational — skip and nothing else works.
02
Standard events mapped to site actions
ViewContent on product pages, AddToCart on cart button, Purchase on thank-you page. Pass real `value` and `currency` — don't leave them blank.
03
Event deduplication via event_id
Same event_id on browser Pixel and CAPI fire. Meta dedupes server-side. Without this, events double-count and attribution is inflated (makes ads look falsely good).
04
Advanced Matching (hashed PII)
Pass hashed email, phone, name when user logs in / checks out. Sharply improves attribution match rate. Must hash SHA256 client-side before sending.
05
CAPI server-side integration
Shopify: native CAPI (free). WooCommerce: PixelYourSite or custom via webhook → Meta CAPI endpoint. Custom: Node/PHP script fires parallel to browser Pixel.
06
Conversions API Gateway (self-hosted)
For high-volume or privacy-first setups: deploy Meta's CAPI Gateway on your own server. Events flow browser → your server → Meta. Full data sovereignty.
07
Test via Events Manager Test Events
Test tool lets you fire events from staging and verify Meta receives them with correct parameters + EMQ score. Never launch without full test pass.
08
Monitor EMQ + event diagnostics
Weekly check in Business Manager → Events Manager. Look for: missing parameters, low match rate, deduplication gaps, events firing without value. Fix as you find them.
Pixel pitfalls
Mistakes that quietly break your Meta ads.
Missing value + currency on Purchase
Purchase fires but without `value: 89.00, currency: EUR`. Meta can't optimise ROAS. Ad delivery goes to lowest-LTV users. Massive performance hit.
Events firing on wrong pages
Purchase firing on /cart (not /thank-you). Inflates conversion count 10×. Ad algorithm trained on false data. Takes weeks to recover once fixed.
Duplicate Pixels on same site
Old Pixel still in theme header; new Pixel added via GTM. Events fire twice. Attribution doubled. Reports lie. Audit + consolidate — one Pixel per site.
CAPI without deduplication
Pixel + CAPI both fire without matching event_id. Meta counts as 2 separate events. Conversions look inflated until Meta catches on + throttles delivery.
Running ads without Purchase events
Can't optimise for conversions if Meta doesn't know what a conversion looks like. Budget burns on lookalike-of-nobody audiences. Fix Pixel first, then turn on spend.
GDPR consent mode incomplete
Firing Pixel without consent violates GDPR. €20m+ fines per Data Protection Commission decisions. Set up Google Consent Mode v2 or equivalent; fire Pixel only after opt-in.
Frequently asked
Meta Pixel questions.
Yes — full Pixel + CAPI setup: €1,200-3,500 flat depending on platform. Includes base install, standard-events mapping, Advanced Matching, CAPI integration, event deduplication, EMQ optimisation, GDPR consent config. Plus documentation so your team understands what's firing and why.
Let's get your Pixel firing properly.
45-minute Pixel audit. Share your Business Manager; we walk through your Events Manager, test each event, check EMQ score, identify CAPI gaps. You'll leave with a clear fix list + rough cost to implement — whether that's with us or your own team.