What is Meta Pixel Events?
Also known as: Facebook Pixel Events, Meta standard events
What are Meta Pixel events?
Meta Pixel events are the named signals a pixel sends to Meta when something happens on your site. PageView fires on every load. Purchase fires on the order-confirmation page. Each event carries a payload of parameters that Meta uses for attribution, audience building, and ad delivery optimization.
Per Meta's Standard Events documentation, an event has three parts.
- Event name. A pre-defined string like
Purchaseor a custom string likeDemoBooked. - Parameters. Structured data:
value,currency,content_ids,content_type,num_items. - User data. Hashed identifiers: email, phone, external_id, IP, user agent. These drive Event Match Quality.
The pixel sends. Meta receives. The event becomes a row in your ad account, a member in a retargeting audience, and a conversion signal that trains the delivery algorithm.
Standard events vs custom events
Every Meta Pixel event is either a standard event or a custom event.
| Type | Defined by | Reports | Works with Advantage+ | Use when |
|---|---|---|---|---|
| Standard event | Meta | Pre-built columns in Ads Manager | Yes | An event in Meta's list fits your action |
| Custom event | You | Build manually with trackCustom | Limited | No standard event matches |
Standard events get first-class treatment. They populate the Conversions column. They feed Advantage+ Shopping campaigns directly. They unlock pre-built optimization goals.
Custom events still work for retargeting and audience building. They just take more setup to read in reports.
The rule: pick the closest standard event first. Add a custom event only when no standard event fits.
Full list of Meta standard events
Meta supports 17 standard events. Below are the nine that drive almost every performance campaign, plus the parameters Meta expects.
| Event | Fires when | Required parameters | Optional parameters |
|---|---|---|---|
PageView | Any page loads | none | none |
ViewContent | Product or content page loads | content_ids, content_type | value, currency |
Search | User runs an on-site search | search_string | content_ids, content_category |
AddToCart | Item added to cart | content_ids, content_type, value, currency | num_items |
AddToWishlist | Item saved for later | content_ids | value, currency |
InitiateCheckout | Checkout flow starts | value, currency | content_ids, num_items |
AddPaymentInfo | Payment method entered | value, currency | content_ids |
CompleteRegistration | Account or trial signup | value, currency | status, registration_method |
Lead | Form submit, demo request | value, currency | content_name, content_category |
Purchase | Order confirmed | value, currency | content_ids, content_type, num_items |
Eight more standard events round out the list. Subscribe, StartTrial, Schedule, Contact, Donate, FindLocation, CustomizeProduct, SubmitApplication. Each takes the same parameter shape.
The non-negotiable rule. Always send value and currency on revenue events. Without them, ROAS reports break and the algorithm cannot optimize for value.
How to fire Meta Pixel events
Three implementation paths. Pick one and stay consistent.
Native fbq code
Drop the base pixel in <head>. Then call fbq('track', 'EventName', { ... }) on the page or button click.
<script>
fbq('track', 'Purchase', {
value: 89.00,
currency: 'USD',
content_ids: ['SKU-1234'],
content_type: 'product',
num_items: 1
});
</script>Fast. Reliable. Hard to maintain across many pages without a dev team.
Google Tag Manager
Wrap the pixel in a custom HTML tag. Trigger it on a GTM event like purchase. Pull parameters from the dataLayer.
fbq('track', 'Purchase', {
value: {{DLV - ecommerce.purchase.value}},
currency: {{DLV - ecommerce.purchase.currency}}
});Works for marketers without dev access. The trade-off. GTM-based pixels load slightly later and can miss events on fast-bounce visits.
Platform integrations
Shopify, WooCommerce, BigCommerce, and Webflow all ship native Meta Pixel apps. Connect the ad account, paste the Pixel ID, the platform fires the right events automatically.
The platform integration is fastest to ship. The native fbq path gives the most control. GTM sits in between.
Event Match Quality and what affects it
Event Match Quality (EMQ) is a 0 to 10 score Meta assigns to every event. It measures how confidently Meta can match the event to a real Facebook or Instagram user.
Per Meta's Event Match Quality documentation, an EMQ above 7.0 is the working threshold for healthy attribution. Below 5.0, conversions drop out of reports and CPA targets drift.
What raises EMQ.
- Hashed user identifiers. Email, phone, first name, last name, date of birth, city, state, country. SHA-256 hashed. Sent on every event.
external_id. Your internal user ID. The single highest-impact parameter for EMQ.- Browser data.
fbpcookie,fbcclick ID, IP address, user agent. Auto-captured by the browser pixel. Must be passed manually on the Conversions API side. - Deduplication setup. Same
event_idon browser pixel and CAPI. Without it, Meta cannot recognize the pair as one conversion.
What kills EMQ. Sending only value and currency. Forgetting to hash. Inconsistent email casing between browser and server. Skipping external_id. Each gap drops the score by 0.5 to 1.5 points.
Common implementation mistakes
Most underperforming Meta accounts fail at the pixel layer, not at the creative layer.
The five mistakes that ruin event data.
- Firing Purchase on the cart page. The event must fire on the order-confirmation page only. Cart-page Purchase events inflate reported revenue and train the algorithm on garbage.
- Double-firing. A pixel installed via GTM and the site theme will fire every event twice. Check the network tab on a test purchase. Two
POSTrequests tofacebook.com/trmeans deduplicate. - Missing currency on revenue events. A
Purchasewithvalue: 89but nocurrencyassumes USD. International accounts lose 20 to 40 percent of attributed revenue this way. - No event_id for CAPI deduplication. Browser pixel fires
Purchase. Server firesPurchase. Without a sharedevent_id, Meta counts one sale as two. CPA reports lie. - Mismatched parameters between browser and server. The browser sends
content_ids: ['1234']. The server sendscontent_ids: [1234]. Meta treats them as different events. Deduplication breaks silently.
A 30-minute pixel audit using the Meta Pixel Helper browser extension catches all five.
Real-world example: a well-instrumented funnel
A direct-to-consumer coffee subscription brand instruments every step of its funnel.
| Page | Event | Parameters | EMQ tactic |
|---|---|---|---|
| Home | PageView | none | fbp cookie auto |
| Roast catalog | ViewContent | content_ids, content_type=product, value, currency | external_id from logged-in users |
| Quiz start | Custom QuizStart + Lead | content_name=roast_quiz | hashed email if collected |
| Cart | AddToCart | content_ids[], value, currency, num_items | external_id |
| Checkout | InitiateCheckout | value, currency | hashed email + phone |
| Order success | Purchase | value, currency, content_ids[], content_type=product | external_id + email + phone, CAPI mirror |
Browser pixel handles the visible events. The backend mirrors Purchase, Lead, and InitiateCheckout to the Conversions API with a shared event_id. Hashed email, phone, and external_id ride on every server event.
After 30 days, EMQ on Purchase averages 8.4. Reported conversions match Shopify revenue within 4 percent. Cost per acquisition on the Advantage+ Shopping campaign drops 31 percent versus the previous quarter, when only browser events fired.
The creative did not change. The pixel events did.
Related terms
Frequently asked questions
What is the difference between a Meta Pixel and a Meta Pixel event?
The pixel is the script. The event is the message it sends. One pixel installed on your site fires many events. PageView fires on every page. Purchase fires only on the order-confirmation page. Same pixel, different events, different optimization signals.
How many Meta Pixel standard events are there?
Meta documents 17 standard events. The nine most-used in performance ads are PageView, ViewContent, AddToCart, AddToWishlist, InitiateCheckout, AddPaymentInfo, Purchase, Lead, and CompleteRegistration. The rest cover sub-cases like Search, Subscribe, StartTrial, Donate, Schedule, and Contact.
Should you use standard events or custom events?
Standard events first. They get pre-built reports, work with Advantage+ campaigns, and feed Meta's algorithm cleanly. Use custom events only when no standard event fits. A B2B SaaS firing 'Demo Booked' as a custom event is fine, but tag it with a standard Lead event too so it counts in Ads Manager.
What is Event Match Quality (EMQ)?
EMQ is Meta's 0 to 10 score for how well an event matches a real user. It rises when you send identifying parameters (email, phone, external_id, IP, user agent) hashed and consistent across browser and server. Per Meta's EMQ docs, accounts above 7.0 typically see meaningfully better attribution and lower CPA.
Do Meta Pixel events still work without cookies?
Browser-fired events lose accuracy without third-party cookies. The fix is the Conversions API. Send the same event from your server with a shared event_id and hashed user data. Meta deduplicates the pair and recovers attribution that the browser-side pixel alone would miss.