Why Google Ads and GA4 Report Different Conversions

Start with the event definition

Check whether both platforms count the same action. One report may include a form start, call tap or imported event while another counts only a successful form. Compare event names, trigger rules, count settings, primary and secondary goals, and whether a CRM or phone provider adds another conversion.

Write down the expected action in plain language: ‘the form provider accepted a request and created one record.’ If the actual tag fires earlier or twice, fix that mismatch before discussing attribution models. Report a diagnostic click separately from a lead.

Compare attribution settings and reporting scope

Attribution models assign credit to touchpoints along a path. Google Analytics describes attribution as the method that distributes credit across interactions, and its reporting model can differ from how Google Ads reports ad interactions. A person may see several channels before requesting service, and the systems can assign fractional or channel-specific credit differently.

Check the comparison date range, lookback window, channel scope and conversion timestamp. A booked appointment might happen days after an ad click. One report may use the interaction date and another the event date. Do not compare different periods or scopes and treat the gap as a tracking error without checking the definitions.

Check account linking and identifiers

Verify that Google Ads and Analytics are linked to the intended property and that auto-tagging and click identifiers are handled as expected. Review redirects, consent behavior and cross-domain steps. A visitor who rejects analytics measurement may not appear in GA4 the same way as in an ad platform’s own report.

Google’s documentation describes auto-tagging and the GCLID for identifying ad clicks. A parameter can be dropped by a redirect or third-party form. Test the route and confirm the landing page, consent choice and CRM record before assuming the connection is complete.

Look for duplication and missing events

Check whether the form provider sends a success message and the website sends another, whether a thank-you page reload repeats the event or whether an ad platform imports the same GA4 key event and also fires a native tag. Use the system’s deduplication method if available and keep one source of truth for the operational lead count.

Missing counts can also come from blocked scripts, consent settings, a form redirect, phone calls that are not tracked or reporting thresholds. A discrepancy does not automatically mean one platform is wrong. Trace a controlled test through tag preview, analytics and the CRM, then classify the gap.

Build a comparison table, not a combined total

Show each system’s number beside its definition: Google Ads attributed primary conversions, GA4 `generate_lead` events, and unique CRM inquiry records. Include the date range, attribution model, consent caveat and duplication rule. Do not add the three totals and call them unique leads.

If one system is intended as the operational source of truth, say so. GA4 helps compare channel behavior; Google Ads supports ad optimization under its conversion settings; the CRM records what the office worked. Each answers a different question, and all can be useful without matching exactly.

A troubleshooting sequence

• Confirm both reports use the same date range and event definition.
• Check primary/secondary status and custom campaign goals.
• Verify account linking, auto-tagging, consent and redirects.
• Inspect tag preview and a controlled form success/failure test.
• Compare duplicate events and unique CRM records.
• Record known limitations and do not force the totals to match.

Avoid a false fix

Do not fire a lead event on every button click to close a reporting gap. Do not switch attribution settings solely until numbers align. Do not remove consent choices or send extra identifiers without an approved basis. A clean explanation of a difference is better than a misleading total.

If the difference affects advertising decisions, ask the analytics or form provider to confirm how the event is emitted. Parallax’s existing successful GHL form event should remain the lead signal; article views, form starts and clicks remain separate.

What to tell the owner

Explain which platform counts the action, which system stores the customer request, how each assigns credit and which gaps remain. State whether a unique CRM lead was verified. If it was not, say ‘reported event’ rather than ‘lead’ until the underlying record is confirmed.

A report can guide budget decisions without claiming perfect attribution. Revisit definitions after changes to GTM, consent, the form embed, phone tracking or account links. Keep a versioned measurement map so new staff do not repeat the same investigation.