Standard Events

Standard events are the named, predefined actions that Meta already understands, so when your site reports one, Meta knows exactly what it means without you having to explain it.

Think about what happens when someone moves through your site. They look at a product, they add it to the cart, they start checkout, and some of them buy. Each of those moments has a name that Meta already recognizes: ViewContent, AddToCart, InitiateCheckout, Purchase, and for lead businesses, Lead and CompleteRegistration. You fire the matching event at the moment the person does the thing, and because the name is one Meta knows, it can both optimize toward that action and report on it cleanly. This is what separates them from custom events, which are the ones you invent yourself when the action you care about has no standard name Meta provides.

The reason this matters is that standard events are the shared language between your website and Meta. When you tell an ad set to optimize for purchases, it is the Purchase standard event that Meta counts and chases across every auction. So if that event is not firing, or it is firing on the wrong page, your whole Sales objective is quietly working from bad information, and no amount of budget or creative fixes a foundation that is reporting the wrong thing.

Here is the part people skip: sending a standard event is not the same as sending it correctly. A Purchase that fires on every page load, or an AddToCart that never fires at all, poisons everything downstream, because Meta optimizes toward what it is told happened, not what actually happened. The real work is making sure each event fires on the right action, once, with the right details attached, not just confirming the events technically exist.

Standard events only help you when they fire on the real action, at the right moment, exactly once.