Meta gives advertisers two ways to define what counts as a conversion: standard events (ViewContent, AddToCart, Purchase) with their built-in semantic meaning, and custom conversions that filter standard events or website URL visits into more granular conversion definitions. Choosing the wrong approach for your business can cause Meta’s algorithm to optimize toward the wrong goal, deplete budget on unqualified conversions, or limit your ability to use advanced optimization features. This guide explains when each approach is correct and the configuration details that determine which performs better.

What Standard Events Give You

Standard events have predefined semantic meaning in Meta’s system. When you fire a Purchase event with a value parameter, Meta’s algorithm knows this represents a completed transaction and uses this signal in its purchase-intent modeling for all advertisers — your Purchase events contribute to the cross-advertiser signal pool that Meta uses to identify users likely to purchase. This pooled signal is one of the most powerful targeting inputs available.

Standard events also enable automatic advanced matching, value-based lookalike audiences, and direct use in Meta’s Advantage+ shopping campaigns without additional configuration. The Purchase standard event is natively supported in all campaign objective types that involve conversion optimization.

What Custom Conversions Give You

Custom conversions let you define a conversion as a filtered subset of standard events or a URL match. For example, a custom conversion defined as “Purchase event WHERE currency = GBP AND value > 100” lets Meta optimize specifically for high-value orders rather than all purchases. A custom conversion defined as “URL contains /thank-you” works even without any pixel events, using only URL-based tracking.

Custom conversions are the right choice when: your standard Purchase event includes both high-value and low-value orders that have meaningfully different ROAS, you want to optimize for a specific product category’s purchases, you need to track a conversion on a page where you cannot deploy pixel code but can match the URL, or you are tracking an event type that does not have a corresponding standard event.

The Optimization Volume Requirement

Meta’s algorithm requires at least 50 optimization events per ad set per week to exit the learning phase. This minimum applies whether you use standard events or custom conversions. If your custom conversion is too narrowly defined — “Purchase WHERE product_category = premium AND value > 500” — you may never reach 50 events per week per ad set, keeping your campaigns permanently in the learning phase and preventing the algorithm from optimizing effectively.

The solution for low-volume conversions: use value optimization with the Purchase standard event rather than a custom conversion that restricts to high-value orders. Set a minimum ROAS target in your campaign instead of filtering at the event definition level. Meta’s value-based optimization (available when you pass dynamic purchase values) achieves high-value order focus without reducing the event volume that the algorithm needs to learn.

Custom Conversions for Lead Generation

For lead generation businesses, custom conversions based on the Lead standard event with quality filters are often the right approach. Fire a Lead event for all form submissions, but fire a custom event (lead_qualified) only for leads that meet your qualification criteria — specific job titles, company sizes, or industries selected in the form. Optimize campaigns toward lead_qualified instead of all Lead events to improve lead quality without sacrificing the signal volume from the broader Lead event.

This requires passing the qualifying information from the form to the data layer at submission time and using a GTM condition or custom event to fire the qualified lead event only when the criteria are met. Monitor the ratio of Lead events to lead_qualified events monthly — if the ratio changes significantly, a form field change or lead qualification criteria update may be needed.