Meta Custom Conversions: When to Use Them and How to Set Them Up

Meta gives you multiple ways to define what counts as a conversion for your business. Standard events are the most powerful option, but they require code changes on your website. Custom conversions offer a code-free alternative — you define a conversion rule in Events Manager, and Meta tracks it using your existing pixel data.

But custom conversions are not just a workaround for non-technical users. They have specific strengths and important limitations that make them the right choice in some situations and the wrong choice in others. This guide explains exactly when to use custom conversions, how to set them up step by step, and the mistakes that will limit your account.

What Are Meta Custom Conversions?

Custom conversions are rules you create in Meta Events Manager that define a conversion goal based on either a URL visit or a pixel event. When someone on your website meets the rule — for example, they visit a specific URL or trigger a specific event — Meta records it as a custom conversion.

The key distinction: you are not adding new code to your website. You are creating a rule that interprets your existing pixel data in a new way.

Custom conversions sit alongside standard events and custom events in the Meta tracking ecosystem:

Type	Defined In	Requires Code?	Use as Campaign Goal?	Limit
Standard Events	Website code / GTM	Yes	Yes — directly	No limit
Custom Events	Website code / GTM	Yes	Only via Custom Conversion	No limit
Custom Conversions	Events Manager	No	Yes — directly	100 per account

When to Use Custom Conversions

Custom conversions are the right tool in these specific situations:

1. You cannot modify your website code

If you are running ads to a landing page on a platform that does not support custom code — certain website builders, third-party landing page tools, or client sites where you do not have code access — a URL-based custom conversion lets you track visitors to a specific thank-you page without touching a single line of code.

2. You want to segment a standard event

Suppose you sell both products and services on the same website, and your Purchase event fires for both. You can create two custom conversions — one that filters Purchase events to only those from your product category, and one from your services category. This lets you run separate campaigns optimised toward each revenue stream.

3. You want to turn a custom event into a campaign goal

Custom events (events with names you invented) cannot be used directly as campaign optimisation goals. But if you wrap a custom event in a custom conversion rule, it becomes usable as a campaign goal. This is the standard workaround for non-standard tracking actions.

4. You need quick testing without a developer

Custom conversions can be created and modified in minutes with no code deployment. For rapid A/B testing of different conversion definitions, or for testing a new conversion goal before investing in a proper pixel implementation, custom conversions are significantly faster to set up.

Two Types of Custom Conversions

URL-Based Custom Conversions

URL-based custom conversions fire when the Meta Pixel records a PageView on a URL that matches your rule. You can match on:

URL equals — exact URL match (e.g., https://yoursite.com/thank-you)
URL contains — fires on any URL containing a string (e.g., “thank-you” or “order-confirmed”)
URL does not contain — exclusion rule

URL-based conversions are the simplest to set up and require only that your pixel base code is installed on the target page. They work well for thank-you pages, order confirmation pages, and any post-conversion page with a unique URL.

Limitation: if your thank-you page URL does not change between users (for example, it is always exactly /thank-you/ regardless of which product was purchased), you cannot pass dynamic values like order amount. URL-based conversions report a fixed value you set at creation time, or no value at all.

Event-Based Custom Conversions

Event-based custom conversions fire when a specific pixel event is recorded, with optional filters applied. For example:

Purchase event where the value is greater than £100
Lead event where the content_name parameter equals “consultation-request”
ViewContent event where the content_ids array contains a specific product ID

Event-based custom conversions can inherit the value from the underlying event (so your Purchase custom conversion reports real revenue), making them significantly more useful than URL-based conversions for ecommerce reporting and ROAS optimisation.

How to Create a Custom Conversion: Step by Step

Go to Meta Events Manager at business.facebook.com
Select your pixel in the left sidebar
Click Custom Conversions in the top navigation
Click Create Custom Conversion
Choose your rule type: Website Event (event-based) or Website URL (URL-based)
For URL-based: enter your URL rule and select the match type (equals, contains, etc.)
For event-based: select the pixel event from the dropdown, then add optional parameter filters
Set the conversion category (Purchase, Lead, Other, etc.) — this affects how Meta reports and optimises
Set the value: either a fixed amount or “Use the value sent by the pixel” (recommended for event-based)
Give the custom conversion a clear name (e.g., “High-Value Purchase £100+”) and click Create

After creating the custom conversion, verify it is receiving data by going to Events Manager and checking whether recent pixel activity is triggering the rule. If you created a URL-based conversion, visit the target URL in a new tab and check whether it appears in the custom conversion’s activity.

Using Custom Conversions in Campaigns

Once created, a custom conversion appears as a selectable conversion goal when you set up a conversion campaign in Ads Manager. At the ad set level, under the Conversion section, click the conversion dropdown and you will see your custom conversions listed alongside standard events.

The campaign optimisation rules are the same as for standard events: Meta needs a minimum of around 50 conversion events per week per ad set to exit the learning phase. If your custom conversion fires infrequently, consider using a higher-funnel event as your optimisation goal and tracking the custom conversion as a secondary event.

For ROAS-based bidding (Target ROAS or Highest Value), your custom conversion must pass a monetary value. If you set up a fixed value at creation time, all conversions will be reported at that value — which is fine for tracking purposes but inadequate for value-based bidding. Use event-based custom conversions with “Use the value sent by the pixel” for accurate ROAS reporting.

The 100-Conversion Limit Per Account

Meta allows up to 100 active custom conversions per ad account. This sounds like a lot, but accounts that have been running for several years can accumulate unused custom conversions that eat into the limit. Old custom conversions do not automatically deactivate even if the underlying page or event no longer exists.

Best practice for managing the limit:

Audit your custom conversions quarterly — delete any that have received zero events in the last 90 days
Name custom conversions clearly with dates or campaign names so you know when they were created
Avoid creating one-off custom conversions for short campaigns; use a standard event instead and apply audience or campaign filters in reporting

Custom Conversions vs Standard Events: Which Should You Use?

The short answer: always prefer a properly implemented standard event over a custom conversion when you have developer access or a compatible platform. Standard events are more flexible, have no account-level limit, and integrate more deeply with Meta’s optimisation algorithm.

Use custom conversions when:

You cannot add code to the page (URL-based, no-code solution)
You need to segment an existing standard event by parameter value
You need to wrap a custom event to use it as a campaign goal
You are testing a new conversion goal before committing to a full implementation

Do not use custom conversions as a permanent replacement for a proper standard event implementation. Custom conversions built on URL matches are fragile — a URL structure change on your site will silently break the conversion tracking without any error notification.

Common Custom Conversion Mistakes

URL-based conversion on a non-unique URL — if your checkout page is always /checkout/ regardless of user or order, every visitor to that page gets counted as a conversion
Forgetting to set a value — custom conversions with no value cannot be used for value-based bidding or ROAS tracking
Duplicating standard events — creating a custom conversion that exactly mirrors an existing standard event is redundant; use the standard event directly in your campaign
Not checking the conversion category — setting the wrong category (e.g., categorising a Lead as “Other”) means Meta will not apply the right optimisation logic
Building up too many old conversions — dead custom conversions from old campaigns clutter your account and eventually push you toward the limit

Run a tracking audit on your custom conversions regularly. In Events Manager, go to Custom Conversions and sort by “Last received” to quickly identify which conversions have stopped firing. Delete anything that has not received an event in 90 days unless it is still needed for an active campaign.

For a complete picture of how Meta tracks your conversions — standard events, custom conversions, and the Conversions API working together — the 5-minute Facebook pixel audit covers the verification steps you should run after any configuration change.

📋 Not sure where to start? Use our Free Tracking Audit Checklist to find out where your setup is losing data.

Book a free tracking audit → We’ll review your setup and tell you exactly what to fix.

Not sure where your tracking is losing you money?