Custom Conversion
A custom conversion is a tracking event you define yourself, usually by setting rules on a URL or a standard event, so an ad platform can count a specific action that matters to your business.
Key takeaways
- A custom conversion is a rule stored in the ad account, not extra code on the site.
- Rules can match URL fragments, event parameters or a reported value above a threshold.
- Parameter-based rules survive redesigns; URL-based rules break silently when routing changes.
- Narrow rules report cleanly but may deliver too few weekly conversions to optimise against.
- Ad accounts limit how many custom conversions exist, and archived ones still consume the allowance.
In depth
A custom conversion is a saved filter that lives in the ad account, not a new tag on your site. You pick a source, either all traffic or one existing event, then add rules: the URL contains a string, an event parameter equals a value, the reported value exceeds a threshold. You assign a category so the platform knows what kind of outcome it represents. From then on the platform evaluates every incoming event against the rule and counts the ones that match.
Precision of the rule decides its usefulness. URL rules are quick to build and fragile, because a routing change, an added query parameter or a single-page application that never changes the address will break them silently. Parameter rules survive redesigns but only work if the parameter is actually sent. Narrowing also costs volume: a rule that isolates your best leads may produce too few weekly conversions for the delivery system to optimise against, even though it reports beautifully.
The practical pattern is to define one custom conversion per outcome you would defend in a budget review, and to base it on a parameter rather than a page address wherever possible. In a scorecard funnel, matching on the tier value sent with the completion event is far more durable than matching on a results URL, and it keeps working when the result page is rebuilt. Assign a monetary value so the platform can weigh conversions instead of merely counting them.
A custom conversion can only see what was already sent. If the completion event carries no tier parameter, no rule can recover it, and the answer is a code change rather than a cleverer filter. Ad accounts also cap how many you can create, and archived ones often keep occupying that allowance. Because each definition lives inside one platform, the same outcome measured in two ad accounts needs two rules, and they will drift apart unless someone maintains both.
Example in practice
How to measure it
Judge the definition first. Compare the count the custom conversion reports against the number of matching records in your own database for the same window; a substantial excess means the rule is catching traffic it should not. Then check the weekly volume against what the delivery system needs to learn, because a rule that reports fewer than a handful of conversions each week will not move optimisation regardless of how precise it is.
After that, judge the outcome. Cost per custom conversion is only meaningful next to what happens downstream, so pair it with the share of those conversions that sales accepts. If a rule tightens and cost per conversion rises while accepted-lead volume holds steady, the rule improved the signal. If both fall together, the rule is filtering out real prospects rather than noise.
Common mistakes
Building the rule on a URL that is not unique is the classic error. A condition matching a path that also appears in a blog article or a help page counts unrelated visits as conversions, and because the number goes up, nobody investigates. Test any URL rule against your full site map before saving it, and prefer an exact match on a dedicated confirmation path over a contains rule that quietly widens as the site grows.
The second is creating a separate custom conversion for every campaign or audience. The allowance fills, the ranked event slots are consumed, and reporting becomes a list of near-identical rows that nobody can compare. Define conversions by business outcome and use campaign structure or breakdowns to slice them. Leaving the value field empty is a smaller but common omission, since the platform then treats a marginal lead and a large opportunity as equal.
Frequently asked questions
How is a custom conversion different from a standard event?
A standard event is a predefined action like "Lead" or "Purchase" that the platform offers out of the box. A custom conversion adds your own rules on top, such as a specific URL or value threshold, so you can measure a more precise action.
Do custom conversions help ad optimization?
Yes. When you optimize delivery toward a custom conversion, the platform learns to find people likely to complete that exact action. This usually produces higher-quality leads than optimizing for a broad event.
What is the difference between a custom conversion and a custom event?
A custom event is something your site sends, defined in code and named by you. A custom conversion is a rule the ad platform applies to events it already receives, defined in the account interface with no deployment. Use a custom event when the platform needs information it does not have; use a custom conversion when the information is already arriving and only needs filtering.
Are custom conversions retroactive?
Often partly. Several platforms apply a new rule to recent history, so numbers appear for the past few weeks immediately, but the lookback is limited and it does not extend to optimisation, which only learns from conversions recorded after the rule existed. Treat any backfilled figures as a reporting convenience rather than proof the rule will perform.
How many custom conversions can I create?
Each ad account has a fixed allowance, and it is smaller than most teams expect. Archiving a conversion usually does not free the slot, so plan the set before creating them. If you are close to the ceiling, consolidate near-duplicate rules into one conversion and separate the cases with campaign structure or reporting breakdowns instead.
Should I optimise campaigns toward a custom conversion?
Only if it produces enough weekly volume for the delivery system to learn. A narrow, high-quality conversion is excellent for reporting but can starve optimisation, leaving campaigns permanently in a learning state. A common compromise is to optimise toward a broader event while reporting on the narrow custom conversion, then tighten once volume supports it.
Can I build a custom conversion on a value threshold?
Yes, provided your events actually send a value. Rules can require the reported value to exceed an amount, which is how teams separate small purchases from large ones or low scores from qualifying ones. If no value is sent, the rule matches nothing, and the fix is to include the value in the event rather than to change the rule.
Why does my custom conversion report zero?
Usually the rule never matches. Check that the source event is genuinely being received, that the parameter name is spelled exactly as sent including case, and that a URL condition matches the address the browser really shows after redirects. Consent blocking can also stop the underlying events entirely, in which case no rule built on them will ever count.