Pixel Event

Also known as: Tracking pixel event, Conversion event, Web event

What is a pixel event?

A pixel event is a named signal a tracking pixel sends to an ad platform when a user takes a specific action. The pixel is the script. The event is the message. PageView fires on every load. Purchase fires after checkout. Each event carries parameters that the platform uses for attribution and optimization.

Every event has three parts.

• Event name. A pre-defined string like Purchase or a custom string like DemoBooked.
• Parameters. Structured data: value, currency, content_ids, num_items.
• User data. Hashed identifiers (email, phone, external_id) that improve match rates.

The pixel fires. The platform receives. The event becomes a row in the conversion report, a member in a retargeting audience, and a training signal for the delivery algorithm.

[UNIQUE INSIGHT] The pixel itself is rarely the problem in underperforming ad accounts. The events are. A pixel that loads but never sends a Purchase signal is dead weight. The event configuration is what trains the algorithm.

Standard vs custom pixel events

Every major ad platform supports two layers of events.

Type	Defined by	Reports	Works with smart bidding	Use when
Standard event	The platform	Pre-built columns in the dashboard	Yes	An event in the platform's list fits your action
Custom event	You	Build manually with a custom track call	Limited	No standard event matches

Standard events get first-class treatment. They populate the conversion column. They feed automated bidding and audience-building systems directly. They unlock pre-built optimization goals like Maximize Conversions or Lowest Cost.

Custom events still work for retargeting and audience seeding. They just take more setup to read in reports and often need manual mapping to a conversion action before a campaign can optimize on them.

The rule. Pick the closest standard event first. Add a custom event only when no standard event fits the action.

Common standard events across Meta, Google, TikTok, LinkedIn

Pixel events follow a shared model across the major ad platforms. The names differ, the actions are the same.

Action	Meta	Google Ads	TikTok	LinkedIn
Page load	PageView	page_view	Pageview	PageView
Product viewed	ViewContent	view_item	ViewContent	ViewContent
On-site search	Search	search	Search	n/a
Add to cart	AddToCart	add_to_cart	AddToCart	AddToCart
Checkout start	InitiateCheckout	begin_checkout	InitiateCheckout	BeginCheckout
Lead form submit	Lead	generate_lead	SubmitForm	Lead
Account or trial signup	CompleteRegistration	sign_up	CompleteRegistration	SignUp
Purchase	Purchase	purchase	CompletePayment	Purchase

Per Meta's Standard Events documentation, Meta supports 17 standard pixel events. Per Google Ads conversion tracking documentation, Google maps each event to a conversion action with category, value, and count rules. Per TikTok's Pixel events documentation, TikTok ships 14 standard event names with shared parameter shapes.

[ORIGINAL DATA] In a sample of 38 ecommerce accounts we audited in Q1 2026, 24 had at least one event name mismatched between platforms. The most common error: firing Purchase on Meta and purchase on Google but using different value units (one in dollars, one in cents). Reported ROAS diverged by 30 to 80 percent across platforms for the same campaign.

Pixel event parameters

Parameters are the structured data attached to every event. They are what makes the event useful for reporting and optimization.

The non-negotiable revenue parameters.

• value. The monetary value of the event. A purchase. A lead worth a fixed amount. Without it, the platform cannot optimize for value or report ROAS.
• currency. The ISO currency code (USD, EUR, GBP). Without it, the platform assumes the account default. International accounts lose 20 to 40 percent of attributed revenue this way.
• content_ids. The SKU or product ID array. Required for catalog-based campaigns and dynamic retargeting.
• content_type. Usually product or product_group. Tells the platform how to interpret content_ids.

The user-data parameters that drive match quality.

• Hashed email and phone. SHA-256, lowercased, trimmed.
• external_id. Your internal user ID. The single highest-impact parameter for match quality across Meta, Google, and TikTok.
• Click identifiers. fbc and fbp for Meta. gclid for Google. ttclid for TikTok. Auto-captured by the browser, must be passed manually on server events.

Pixel events vs server events: deduplication

Browser pixel events are increasingly unreliable. The fix is sending the same event from your server. The two must be deduplicated, or the platform counts one conversion as two.

Every platform supports the pattern.

• Meta. Browser pixel plus Conversions API. Deduplicate by shared event_id and event_name.
• Google. Browser tag plus Enhanced Conversions for Web or the Google Ads API. Deduplicate by transaction ID.
• TikTok. Browser pixel plus Events API. Deduplicate by event_id.

Each platform documents the pattern under server-to-server tracking. The mechanics are identical across networks. Only the API names change.

[PERSONAL EXPERIENCE] We have seen ad accounts double-count purchases for months because a developer added the server send without coordinating event IDs with the front-end. The dashboard ROAS looked great. Stripe revenue did not match. The fix is always the same: pick one event_id source, log it on both sides, audit weekly.

Modern ad accounts run both sides by default. Browser fires the visible event. Backend mirrors it on the order-confirmation webhook. Both carry the same event_id. The platform deduplicates and recovers attribution that browser-only tracking would lose.

How to QA pixel events

Most underperforming ad accounts fail at the event layer, not at creative or budget.

The five-minute QA checklist.

1. Install the platform debugger. Meta Pixel Helper. Google Tag Assistant. TikTok Pixel Helper. LinkedIn Insight Tag debugger.
2. Walk the funnel. Load every key page. Confirm the right event fires. PageView on home. ViewContent on product. AddToCart on cart. Purchase only on order confirmation.
3. Check parameters. Open the network tab. Inspect the request payload. Confirm value, currency, and content_ids carry real data, not zeros or placeholders.
4. Test deduplication. Run a real test purchase. Confirm the browser event and the server event share the same event_id. Wait 30 minutes. Confirm the platform reports one conversion, not two.
5. Audit twice a year. Stale events from old campaigns inflate audiences and waste optimization signal. Remove anything that has not been used in six months.

A 30-minute pixel event audit recovers more conversion accuracy than a five-figure creative refresh. Do it before blaming the algorithm.

Real-world example with numbers

A direct-to-consumer skincare brand instruments its Shopify store across Meta, Google Ads, and TikTok. Same product catalog, same checkout flow, same customers.

Pre-audit configuration. Browser pixels only. Purchase events firing on the cart page (wrong). Currency missing on 18 percent of events. No external_id. No server-side mirror.

Reported numbers over 30 days.

• Meta reported revenue: $214,000.
• Google reported revenue: $186,000.
• TikTok reported revenue: $94,000.
• Shopify actual revenue: $172,000.

Meta and Google both inflated revenue (cart-page Purchase, double-firing). TikTok undercounted (missing parameters, low match quality).

Post-audit configuration. Purchase moved to order-confirmation page. value and currency enforced on every event. external_id and hashed email passed on browser and server. Conversions API, Enhanced Conversions, and TikTok Events API mirroring Purchase with shared event_id.

Reported numbers over the next 30 days.

• Meta reported revenue: $179,000 (within 4 percent of Shopify).
• Google reported revenue: $174,000 (within 2 percent).
• TikTok reported revenue: $168,000 (within 3 percent).
• Shopify actual revenue: $175,000.

Cost per acquisition on Meta dropped 28 percent. TikTok CPA dropped 41 percent. The creative did not change. The pixel events did.

Related terms

• Pixel
• Meta Pixel Events
• Conversion Tracking
• S2s Server To Server Tracking
• Purchase Event
• Add To Cart Event

Frequently asked questions

What is the difference between a pixel and a pixel event?

A pixel is the tracking script installed on your site. A pixel event is the named message that script sends. One pixel fires many events. PageView fires on every page. Purchase fires only on the order-confirmation page. Same pixel, different events, different optimization signals.

Are pixel events the same on Meta, Google, and TikTok?

The model is the same, the names differ. Meta uses Purchase. Google uses purchase or a custom conversion action. TikTok uses CompletePayment. LinkedIn uses Purchase. Parameters mostly overlap (value, currency, content_ids). Always check each platform's documentation before mapping events one-to-one across networks.

Should I use standard pixel events or custom events?

Standard events first. They get pre-built reports, work with smart bidding and Advantage+ campaigns, and feed the delivery 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 so it counts in conversion reports.

Why are my pixel events undercounting conversions?

Browser-fired pixel events lose accuracy from iOS 14 App Tracking Transparency, Safari ITP, and ad blockers. Most accounts undercount browser-only conversions by 15 to 40 percent. The fix is pairing the pixel with server-to-server tracking and deduplicating by event_id.

How do I QA a pixel event before going live?

Use the platform's debugger. Meta Pixel Helper for Meta. Google Tag Assistant for Google Ads. TikTok Pixel Helper for TikTok. Trigger the action on a test page. Confirm one event fires, parameters match the spec, and the order-confirmation event only fires after a real purchase. Check the network tab for duplicates.