Explaining a gap between platform leads and genuine enquiries

Platform leads and genuine enquiries can differ because the reports count different actions, users, requests, dates or channels. Write down each definition, match records where possible, then reconcile received submissions to distinct genuine enquiries. Do not call the whole gap “spam” without evidence.

Identify the figures being compared

For the platform figure, record the product, report, column, conversion action or event, date range, time zone and counting setting. For the business figure, record the intake routes, receipt-date range, exclusions and counting unit.

A Google Ads conversion total and a month's CRM enquiries may differ even when tracking works. Google Ads can report an imported Analytics conversion against the ad-click date, while Analytics reports it against the event date.

Google Ads offers “One” and “Every” conversion counting. Its “Conversions” and “All conversions” columns can include different action sets.

In GA4's Lead acquisition report, “New leads” counts unique users with a generate_lead event, not distinct requests. That recommended event is not sent automatically.

Reconcile without forcing totals to match

First, compare the platform figure with received requests that can reliably be linked to its configured action. List matched records, events with no confirmed received request and received requests with no expected event.

Explain differences in date, scope and counting convention separately. A user-level GA4 metric cannot be turned into a request count by simple subtraction.

Then reconcile the business's own intake records: distinct successful submissions, confirmed test or spam exclusions, repeated submissions linked to the same need, and distinct genuine enquiries. Keep uncertain classifications visible. Use non-overlapping rules so one submission is not removed twice.

A button click or confirmation-page view may be configured as a conversion without proving that a request reached the team. A phone or email enquiry may reach the business without a website event. These are possible explanations to test against the actual configuration, not assumed faults.

Investigate unmatched records

Sample platform events and seek corresponding received requests. Sample received enquiries and seek the expected events. Check successful delivery, repeated firing, other intake routes and the date convention. For Google Ads, check the conversion action, primary or secondary setting, counting method and column used.

For GA4, establish whether the comparison uses event counts or the Lead acquisition report's unique-user metrics. If a dimension shows “(not set)”, Google says it lacks a value; the reason depends on the dimension and report. Keep an unknown source unknown while investigating it.

Key Metrics to Track When Reconciling Lead Gaps

Explain the remaining gap

State confirmed differences, the size of any still-unmatched group and the next check. For example: “The ad report uses configured conversions by click date; the enquiry report uses distinct requests by receipt date. Some events have not yet been matched to intake records.”

Use genuine enquiries for decisions about requests actually received, and platform figures for questions that fit their configured definitions. If a tracking or handoff fault is confirmed, assign its repair and check later requests under the corrected setup.