Standard Events vs Custom Conversions
A pixel that only fires “PageView” tells Meta almost nothing useful. The real power comes from tracking meaningful actions — a lead, a purchase, a booking. This lesson makes sense of how that works.
Standard events like Purchase and Lead are recognised and optimised automatically, while custom conversions let you track pages such as a thank-you URL with no code. Always send parameters like value and currency so Meta can optimise for revenue.
01Standard events
Standard events are Meta's predefined actions that its system recognises and optimises for automatically. The ones a small business uses most:
| Event | Fires when someone… |
|---|---|
| ViewContent | Views a key page (a product, a service) |
| Lead | Submits an enquiry or form |
| CompleteRegistration | Signs up or registers |
| Contact | Calls, chats or contacts you |
| AddToCart | Adds a product to cart |
| InitiateCheckout | Starts checkout |
| Purchase | Completes a purchase |
02Parameters make events useful
An event on its own is a bare fact. Parameters add the detail that unlocks real optimization:
- Purchase needs value and currency — without them you can't optimise for ROAS or see revenue.
- ViewContent and AddToCart benefit from content_ids and content_type.
A Purchase event without a value tells Meta “someone bought” but not “this sale was worth ₹4,000.” Send the value and currency, and Meta can chase high-value buyers, not just any buyer.
03Custom conversions (the no-code hero)
Don't want to touch events at all? Custom conversions let you define a conversion using a simple rule in Events Manager — usually a URL. For example: “anyone who lands on /thank-you counts as a Lead.” No developer, no code. For a lot of service businesses, a thank-you-page rule is the fastest way to start tracking leads.
04Custom events (use sparingly)
If you invent your own event name (say brochure_download) that's a custom event. It works, but Meta understands it less well than a standard event, so it optimises more weakly. Rule of thumb: use a standard event whenever one fits, and only go custom when nothing standard matches.
05Event match quality
Meta needs to connect each event to a real person to optimise well. Event Match Quality improves when you also send hashed first-party details — email, phone, name — known as Advanced Matching. Higher match quality means better optimization from the same number of events.
Meta now offers AI enrichment, which can automatically attach extra page, product and business details to your events. It rolls out with a review window before it activates — a helpful boost, but still no substitute for sending clean value and currency on purchases.
Naming everything as custom events (“my_purchase”, “cart_add”) when standard events exist. You lose Meta's built-in understanding and weaken optimization for no reason.
- Standard events (Purchase, Lead, ViewContent…) are recognised and optimised automatically.
- Always send parameters — especially value and currency on purchases.
- Custom conversions track thank-you pages with no code.
- Boost event match quality with Advanced Matching; prefer standard events over custom.
Frequently asked questions
What are standard events in Meta ads?
Predefined actions Meta recognises automatically, such as ViewContent, AddToCart, Lead and Purchase. Meta can optimise for them natively, so use them wherever one fits.
What is a custom conversion?
A rule you build in Events Manager, usually based on a URL, that counts as a conversion with no code, for example anyone who reaches your thank-you page becoming a Lead.
Why send value and currency with a Purchase event?
Without them Meta knows a sale happened but not its worth, so it cannot optimise for ROAS. Sending value lets Meta chase high-value buyers, not just any buyer.
Return to the Meta Ads course hub for the full curriculum.