Why is my Meta Ads custom conversion not tracking?

Quick answer: prove the base event before debugging the custom conversion

A Meta Ads custom conversion usually shows no activity for one of three reasons: the underlying event never arrives, the event arrives but does not satisfy the custom conversion rule, or the conversion works but the report or campaign is looking at a different event, data source, date range, or attribution scope. Treat those as separate layers.

Run one controlled test and preserve its timestamp, page URL, event name, parameters, browser or server source, and test order ID or lead ID. First confirm the base event appears in Events Manager. Then test whether the same payload meets every custom conversion condition. Only after both are true should you investigate attribution and Ads Manager reporting.

• User symptom: a custom conversion is inactive, reports zero, or is absent from expected campaign results while related activity exists.
• Control level: event source, custom rule, URL or parameter values, report columns, attribution, and ad set optimization event.
• Time grain: one timestamped test followed by a mature reporting cohort rather than today's partial totals.
• Likely mechanism: failed collection, a rule mismatch, the wrong conversion selected, or an attributed-result gap.
• Decision produced: repair event collection, correct the rule, align reporting, or change campaign setup without disturbing a healthy layer.

Keep custom-conversion failure separate from nearby tracking problems

This diagnosis starts at the rule layer. It differs from a Pixel not firing, where the browser event is never collected; low Event Match Quality, where received events lack strong customer information; Events Manager not matching Ads Manager, where received events are not all attributed to ads; and a campaign optimizing for the wrong event, where delivery uses a valid but commercially weak signal.

The boundary matters because reinstalling the Pixel cannot fix a URL rule that excludes the confirmation page, and editing a custom rule cannot recover an event that was never sent. Locate the first failed boundary before changing code or campaign delivery.

• No base event in Events Manager: debug Pixel, Conversions API, consent, tag firing, or the source integration.
• Base event exists but the custom conversion does not: debug the custom conversion definition and payload values.
• Custom conversion records activity but Ads Manager shows no attributed results: debug reporting scope, attribution, identity, and campaign selection.
• Ads Manager reports the conversion but lead or sales quality is weak: move to funnel, CRM, or optimization-event diagnosis.

Capture one known test from action to received event

Use a clean browser session and complete the exact action the custom conversion should represent. Note the account time zone, test time, destination URL after redirects, consent choice, browser, device, and any transaction or lead identifier. If both browser and server events are sent, preserve the event ID used for deduplication.

In Events Manager, verify the correct data source received the expected base event. Inspect the final URL and every parameter used by the custom conversion rather than relying on the event name alone. Case, spacing, path variants, query strings, numeric-versus-string types, and missing values can make a rule fail while the event itself looks healthy.

• Confirm the test reached the intended thank-you, confirmation, or completion state.
• Record the exact standard or custom event name, including capitalization.
• Inspect the final browser URL after redirects and normalization.
• Compare every required parameter key, value, and data type with the rule.
• Check browser and server copies for consistent event IDs and payload meaning.

Audit the custom conversion rule literally

Open the custom conversion and translate its definition into a plain-language test: which data source, which base event, which URL condition, which parameter conditions, and which value or category should qualify? Evaluate every condition against the captured payload. Do not infer that a contains rule, exact match, or parameter comparison behaves the way a similarly named analytics filter behaves.

Look for environment drift. A rule created against an old domain, legacy checkout path, renamed event, retired product ID, or staging URL can silently stop matching after a site release. If multiple domains, regional stores, form providers, or checkout hosts are involved, test each path separately before broadening the rule.

• Verify the custom conversion points to the Pixel or dataset that receives the live event.
• Compare exact-match and contains conditions with the real final URL.
• Check whether required parameters are absent from browser or server payloads.
• Review recent site, tag-manager, checkout, form, domain, and event-name changes.
• Create a narrowly controlled test definition before replacing a production rule.

Separate event receipt from Ads Manager attribution

A custom conversion can register activity without producing an Ads Manager result for every occurrence. Ads Manager reports the subset credited to eligible ad interactions under the selected conversion event, attribution setting, account time zone, date range, campaign scope, and filters. Organic tests and actions without an eligible matched interaction can prove collection without proving paid attribution.

Build a saved report with the custom conversion added explicitly as a column. Hold account, campaigns, dates, time zone, attribution setting, filters, and breakdowns constant. Compare a mature date range first, because recent conversions can still be processing and daily rows can obscure a stable full-period total.

• Events Manager activity answers whether Meta received and classified an event.
• Ads Manager results answer whether an eligible event was attributed within the selected report scope.
• Use the exact custom conversion column rather than a blended Results column.
• Remove unsupported breakdowns while establishing the headline total.
• Do not treat an organic browser test as proof that paid attribution should appear.

Verify the campaign is using the conversion you diagnosed

At ad set level, confirm the conversion location, data source, performance goal, and selected conversion event. Similar names can hide different custom conversions, especially when teams duplicate campaigns across accounts or recreate rules after site changes. Use stable IDs where the interface or export exposes them, not names alone.

Do not switch a live ad set merely to make a diagnostic label disappear. Changing the optimization event can disrupt delivery and learning. First establish that the existing event is invalid or misaligned with the business outcome, then plan the change with a documented baseline and enough time to judge downstream quality.

• Match the ad account, data source, domain, and custom conversion to the live destination.
• Confirm the ad set selects the intended event rather than a similarly named legacy copy.
• Check duplicated campaigns for inherited data sources or optimization events.
• Compare the selected event with the actual business outcome the campaign should optimize toward.
• Record the change time so reporting and delivery shifts are not confused with tracking repairs.

Fix the first failed layer and retest end to end

If the base event is missing, repair tag firing, consent sequencing, browser or server payloads, redirects, or integration delivery. If the event arrives but the rule fails, correct the data source, event, URL, or parameter conditions. If classification works but Ads Manager is blank, align the custom column, campaign scope, dates, time zone, attribution setting, and selected event before escalating.

Retest with a new traceable action after the fix and keep the pre-fix evidence. Do not repeatedly edit several tracking and campaign variables at once. A clean before-and-after record should show the source action, event sent, event received, custom rule matched, result attributed where eligible, and downstream lead or order reconciled.

• Collection fix: make the intended base event arrive once with the required fields.
• Rule fix: make the captured payload satisfy a documented definition.
• Reporting fix: use the exact event and a like-for-like Ads Manager view.
• Campaign fix: select a verified conversion that represents the desired outcome.
• Validation rule: confirm source records and qualified outcomes, not only a green platform status.

How an AdSpecIt-style audit helps diagnose custom conversions

An AdSpecIt-style audit can establish the account-level context around a missing custom conversion: campaign objectives, conversion locations, selected events, data sources, recent edits, attribution settings, reported results, and downstream performance. That narrows the investigation before a developer changes a healthy Pixel or a media buyer resets a working campaign.

The useful output is a prioritized evidence trail: verify the source action, prove base-event receipt, test the custom rule, align the Ads Manager report, confirm campaign selection, and reconcile the result with real leads or orders. Related AdSpecIt guides on Pixel firing, Event Match Quality, Events Manager versus Ads Manager, and wrong optimization events cover the adjacent layers when the first failure sits outside the custom-conversion rule.