Google Ads conversions and GA4 key events can differ even when the tags work. Start by checking whether both reports count the same business action, for the same channels and dates. A mismatch is a reason to investigate, not proof of broken tracking.
First define the action you are comparing
Write down the event name, conversion action name, source and business meaning. A submitted enquiry, a contact-button click and a qualified lead are different actions. Putting all three under a dashboard label called “leads” hides the distinction.
GA4 uses key events for important website or app actions; Google Ads conversions are used for advertising measurement and optimisation. Google’s key events and conversions explanation sets out that distinction.
Use a reconciliation worksheet
| Check | What to write down |
|---|---|
| Business action | The successful action and its exact event name. |
| Report scope | All site traffic or only traffic attributed to Google Ads. |
| Date basis | Interaction date or the date the conversion happened. |
| Counting | One or every conversion, and which actions the column includes. |
| Attribution | Model, eligible channels and conversion window. |
| Completeness | Import delay, missing tags and consent behaviour. |
Understand the reporting differences before changing a tag
Google Ads normally assigns a conversion to the advertising interaction date, while Analytics records the action on the date it occurs. Google Ads also distinguishes its Conversions and All conversions columns, and action counting settings can change totals. Imported Analytics data can take time to appear. These differences are documented in Google’s conversion import guidance.
For example, an ad click on Monday followed by a form submission on Tuesday can land on different dates in the two reports. This is an illustrative example of reporting logic, not a missing enquiry. Compare a mature date range and the appropriate date-based columns before diagnosing collection.
Then investigate collection
If the definitions align but a material gap remains, complete a controlled test using a clearly marked test record. Confirm the form was accepted, inspect the event, and check that it reaches the intended property. Repeat for the actual landing-page templates and consent states your visitors use. Do not change production conversion settings just to make two totals match.
If one successful action produces two identical events, follow the duplicate lead conversion checklist. If the event never appears, inspect the trigger and installation before editing attribution.
Put the explanation in the report
Add a short note to the dashboard defining the lead metric, attribution source and last complete reporting period. Keep actual enquiries or orders as a separate business reference. Platform-attributed conversions do not replace the sales record.
Pixel Pulse Media’s tracking setup and Looker Studio reporting services start with these definitions, so a budget decision does not depend on a misleading total.