Compare GA4 and Google Ads by aligning the action, reporting scope, dates and attribution settings before investigating missing or duplicate data.
A higher conversion total in one report does not automatically make the other report wrong. The screens may describe different actions, channels or dates. Start by establishing a comparable question, then investigate missing or duplicated measurement. The objective is to explain which number supports a business decision, not to force every total to match.
Build the comparison around one action
Choose a specific outcome such as a successful quote request, purchase or appointment. Record the event name, conversion action, accounts, report and date range. Avoid comparing page views with submissions or all-channel outcomes with advertising-related outcomes.
Imagine a hypothetical website reporting enquiries from every channel while an Ads report displays one advertising conversion action. Different totals are unsurprising, but the settings and data still need to confirm the explanation. The first task is to document scope rather than immediately changing tags. A reproducible comparison gives the technical team a much clearer starting point.
Distinguish a key event from an advertising conversion
Google Analytics describes a key event as an event measuring an important business action, while a Google Ads conversion supports advertising performance measurement and optimisation. A standard GA4 key-event total should therefore not automatically be treated as equivalent to a selected Ads conversion column.
Create a measurement dictionary for the action. Clicking a submit button, successfully submitting a form and becoming a sales-qualified enquiry are different stages. Give each a purpose. If the same outcome is collected through two methods, document how both measurements should be used in reporting and optimisation rather than assuming both belong in every total.
Check time and attribution settings
Google's data-discrepancy guidance explains the use of conversion-time columns for comparisons. Selecting the same date range is not necessarily selecting the same time basis. Check which date a report assigns to the outcome, particularly when an advertising interaction and the completed action occur at different times.
Analytics' attribution-settings documentation covers comparison factors including time zones, counting and channels eligible for credit. Do not change settings solely to bring totals closer together. Confirm that the settings support the business purpose and document the reporting or optimisation decisions affected by any change.
| Comparison field | Record | Question |
|---|---|---|
| Action | Event and conversion names | Is this the same customer action? |
| Scope | Channels and report filters | Is the reporting scope equivalent? |
| Time | Time zone and date column | Is the period interpreted in the same way? |
| Counting | Treatment of repeated actions | Do the counting rules match? |
| Maturity | Date the data was retrieved | Could the outcomes still be processing? |
Build an evidence trail for the remaining difference
Once definitions align, follow a controlled action through the journey. Did the site complete the task, create the business record, trigger the expected event and associate it with the intended account? Different forms, subdomains or payment returns may behave differently. Record the conditions for each path.
Keep personal customer information out of general debugging sheets. The action type, time and an appropriately limited record identifier can be more useful for technical discussion. Explaining the reproducible path and conditions is clearer than circulating large collections of customer records.
Carry an explainable number into management reporting
Show the compared metrics, the explained difference and the remaining uncertainty. Operational records may answer how many enquiries arrived, while advertising reports answer a question about attributed contribution. Make that distinction explicit rather than expecting one metric to represent the entire journey.
Repeat the same check after a correction. Record previous and updated settings, the review period and the decision owner. Known differences then stop being rediscovered as new errors every month, while a genuinely new measurement issue becomes easier to identify.