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.
By the end of this lesson you'll know
- What standard events are and the key ones to use
- Why parameters like value and currency matter
- How custom conversions let you track pages with no code
- What event match quality is and why to care
Standard 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 |
Parameters 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.
Custom 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.
Custom 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.
Event 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.
Key takeaways
- 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.