Custom conversions and custom metrics

Custom conversions and custom metrics solve different problems. A custom conversion defines a specific action you want to count and optimize toward. A custom metric is a calculation you build in reporting from numbers Meta already provides. The first changes what gets counted. The second changes how you read the counts.

What a custom conversion is

A custom conversion is a rule layered on top of your pixel or Conversions API data. You choose a source event, such as page view or purchase, and add conditions. A common rule is a URL contains condition, for example counting a page view only when the URL includes “thank-you-demo”. Other rules can use event parameters, such as a purchase value above a set amount.

Meta’s current guidance lists the supported rule types and limits, including how many custom conversions an account can hold, so check it before you plan a setup.

When to use a custom conversion

• Separate similar actions. A site has one thank-you page template for two products. A rule on the URL splits them so you can track each.
• Track a valuable subset. Count only purchases above a certain value, or only a certain product category.
• Use a signal without changing site code. If a standard event already fires, a rule can narrow it without a developer.
• Report on a step in a flow where no standard event exists.

If you can fire a standard event with the right parameters, that is usually cleaner, since standard events work across more of Meta’s tools. Review conversions explained for how the event types relate.

Limits to know

A custom conversion can only count what the underlying event already captured. It cannot recover an event that never fired. It also depends on the event data arriving reliably, so a setup that loses events through browser restrictions will lose them here too. Server events sent through the Conversions API help with that, as covered in the Meta pixel and Conversions API guide.

Rules that depend on URLs break when the site changes its URL structure. After a redesign, retest each rule.

What a custom metric is

Ads Manager lets you build a custom metric from existing columns with a formula. For example, you can divide purchases by link clicks to see a click-to-purchase rate, or calculate profit by subtracting a cost figure from purchase value. Metrics are saved as columns you can reuse in a reporting view.

When to use a custom metric

• Measure something specific to your business, such as contribution after product cost.
• Standardize a ratio your team discusses often.
• Compare ads on a figure that Meta does not report by default.

A custom metric is only as good as its inputs. If the underlying purchase count is affected by attribution windows, your calculated figure inherits the same limits. The attribution models guide covers those choices.

A practical sequence

1. List the actions that matter to the business.
2. Check which are covered by standard events.
3. Create custom conversions only for the gaps.
4. Test each rule by completing the action yourself and confirming it appears in Events Manager.
5. Build custom metrics once the counts are trustworthy.

How YieldBI helps

YieldBI supports conversion tracking and attribution, including pixel and Conversions API setups and offline conversions, so the events behind your rules and metrics are captured more completely. Its incremental attribution models and effective windows add a view of how much of the reported result came from the ads.