Meta Ads

Custom Conversion

Also called URL-based conversion

A Meta event you define from URL rules or event parameters, without adding new code to the site.

Quick facts: Custom Conversion

Category
Meta Ads
Also called
URL-based conversion
Level
Beginner
Affects
Bidding, reporting accuracy, audience building
Where to see it
Meta Events Manager (Custom Conversions), Meta Pixel Helper
In this article4
  1. How a custom conversion works
  2. Why custom conversions matter
  3. Where custom conversions go wrong
  4. What to do about it

How a custom conversion works

Meta’s pixel sends a general page view from every page it is installed on. Named outcomes — a purchase, a lead, a booking — normally need extra code placed on the site. A custom conversion avoids that. You give Meta a rule instead: a web address containing a particular string, or an existing event carrying a particular parameter, and Meta counts a conversion every time traffic matches the rule.

The most common rule is a web address match. If a completed enquiry always lands on a confirmation page with its own address, that page can be turned into a conversion inside Events Manager without a developer touching the theme. Rules can also narrow an event that already exists, so one purchase event becomes several conversions split by product category or by order size.

Why custom conversions matter

They put measurement within reach of the person running the ads. On smaller sites in Nepal the marketer is rarely the person allowed to edit the code, and a rule built in the interface is often the difference between having something to optimise towards and having nothing. Meta’s delivery system can only learn from outcomes it receives, so a defined conversion is the input that bidding works from.

They also keep your core measurement tidy. The main standard events stay intact for value-based bidding, while custom conversions sit alongside them for narrower reporting questions.

Where custom conversions go wrong

The rule itself is the weak point. A rule matching any address that contains “thank-you” will also catch a page you publish months later with a similar address. Worse, a checkout or form that shows its confirmation message without changing the address will never match at all — nothing in the address changes, so nothing fires. Single-page checkouts fail this way constantly.

Double counting is the second trap. A custom conversion built on top of a purchase event does not replace that event; both are recorded, and any report that adds the two together overstates results badly.

Third, address rules are fragile. Change the confirmation page during a redesign or a migration and the conversion quietly stops recording, usually with no warning anywhere.

What to do about it

Name each custom conversion so a stranger could tell what it counts, and write the rule down somewhere outside Meta. Complete a real enquiry or order yourself, watch the event arrive, then check received volume again the following day before you trust it for bidding. When the outcome genuinely drives revenue, send it properly through the pixel and Conversions API together rather than leaning on an address rule alone.

Review the list every few months. Ad accounts collect custom conversions the way a drawer collects keys: most no longer open anything, and the clutter makes the useful ones harder to find.

Do and do not

Do

  • Name each conversion so a stranger knows what it counts
  • Test the rule with a real completed enquiry or order
  • Record every rule outside Meta before a site redesign

Do not

  • Add a custom conversion to its underlying event in reports
  • Rely on a URL rule when the address never changes
  • Leave unused conversions cluttering the account for years

Questions people ask about this

Do I need a developer to create a custom conversion?

Usually not. If the pixel is already installed and the completed action lands on its own web address, you can define the rule inside Events Manager yourself. A developer is only needed when the confirmation has no distinct address, or when you want to send order value and product details, since those must come from the site's code.

What is the difference between a custom conversion and a standard event?

A standard event is a named signal the site itself sends, such as Purchase or Lead, and it can carry value, currency and product details. A custom conversion is a rule you build on top of traffic that is already arriving. Standard events are richer and more reliable; custom conversions are quicker to set up and need no code.

Why has my custom conversion stopped recording?

The commonest cause is a changed web address. Redesigns, page rebuilds and site migrations often move or rename the confirmation page, and the rule no longer matches anything. Check the rule against the address a real completion lands on today. The other cause is the pixel being removed or blocked on that page entirely.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.