Most. Help

Concept

Standard events: Meta's fixed vocabulary for conversion actions

Standard events are Meta's predefined event names - Purchase, Lead, InitiateCheckout and others - that its optimisation and reporting understand out of the box.

Standard events

Standard events are Meta's fixed vocabulary of event names — Purchase, Lead, InitiateCheckout, AddToCart, ViewContent, CompleteRegistration and others. They are the names Meta's delivery optimisation, reporting columns and audience rules understand without extra configuration.

Why the naming matters

Campaigns optimise toward specific standard events — "optimise for Purchase" is only meaningful if your Purchase events actually arrive under that name. Non-standard names still appear in Events Manager, but they cannot power optimisation goals or fill standard reporting columns, and mixing two names for one business action splits the signal.

Standard events across pixel and CAPI

The pixel and the Conversions API share the event vocabulary: a Lead sent by the pixel and a Lead sent from the server use the same name, which is also a requirement for deduplication — Meta only collapses a browser/server pair when both the event name and the event ID match.

Sources

Sources

Related concepts

Concept

Server-side tracking: delivering conversions from your infrastructure

Server-side tracking sends conversion events from your server (or tracker) directly to ad platforms, instead of relying on browser tags and cookies.

Concept

Offline conversion: the conversion no browser pixel ever sees

An offline conversion happens outside the tracked web or app session - an in-store purchase, a CRM deal, a phone order. Platforms accept them through server channels, with longer delivery windows than web events.

Concept

Match rate: how many of your events a platform can tie to a real user

Match rate is the share of sent events that TikTok (or Meta) successfully matched to a real user profile - the quality metric of server-side delivery.

Concept

Match key: the identifiers that tie a server event to a real user

A match key is an identifier in an event payload - click ID, hashed email or phone, IP with user agent, mobile ad ID - that lets the ad platform tie the event to a real profile. Snapchat rejects events without one.

Concept

Events API: TikTok's server-side interface for conversion events

The Events API is TikTok's interface for sending conversion events from your server, complementing the TikTok Pixel where browser tracking is lost.

Concept

Event Quality Score: how platforms grade the completeness of your events

An event quality score is the platform's grade of how complete an event payload is: Meta's Event Match Quality runs 0-10, Pinterest targets a "Good" EQS, Reddit and Snapchat surface warnings in their test views.