Your first useful check
Start here.
Segment the Google Ads report by conversion action. Write down which action should correspond to a CRM submission, contact, booking or qualified demo. If the definitions differ, fix the comparison before touching the implementation.
Is this the right guide?
Use this when reported conversions exceed the CRM outcome you expected. It does not diagnose campaign profitability or prove that every attributed conversion is a new person.
What you can check and who can help.
- You can start here
- You can compare reports, search for a test lead and note submission times. Ask the account owner for access if a report is hidden.
- Bring in the responsible specialist
- Ask the person responsible for the website or CRM to inspect delivery errors, change form tracking or repair the connection. Changing a conversion used for bidding should be agreed with the campaign owner.
Tools and access you need
Google Ads conversion settings, the form submission log, CRM records and website tag debugging. Ask an administrator for read access before changing anything.
Before changing settings, keep a copy of the current configuration so you can restore it. Use approved test records and remove customer details from shared evidence.
Follow the steps.
Start at step 1. Each result tells you what to check next; you do not need to change every setting mentioned.
Compare the same action
Start yourself: read-only report comparison.
- Look here
- Open the Google Ads report and split its totals by conversion action, the named action being counted, such as a demo request. Beside it, open the CRM report you are comparing.
- Check this
- Does each total mean a form request, a new contact, a booking or a qualified demo? Write the definition beside each number.
- What it means
- A person can submit a form, book a meeting and later qualify. Those are three actions, not three new people. A repeat request can also update an existing contact.
- Next move
- Compare demo requests with delivered demo requests first. Compare new contacts and qualified demos separately.
Line up dates and counting settings
Read the settings yourself; agree changes with the campaign owner.
- Look here
- Open the settings for the chosen conversion action in Google Ads. Note the date range and time zone used by each report.
- Check this
- Note whether the report shows Conversions or All conversions. Check One versus Every, which determines how repeat conversions after an ad interaction are counted. Also check whether the report uses the ad interaction date or conversion date.
- What it means
- The same request can appear on different days in different reports. Primary actions are generally used for campaign goals; secondary actions are usually observation only. Custom goals are an exception, so check the campaign's actual goal settings.
- Next move
- Use matching dates and equivalent actions. Allow processing time before comparing a finished period. Do not change the bidding goal just to make totals match.
Follow one successful form request
Start yourself with an approved test record.
- Look here
- Open the published form and the form tool's saved submissions. Search the CRM using an approved test email address.
- Check this
- Submit once. Record the time, success message and saved submission reference. Then check whether the CRM created a new record or updated an existing one.
- What it means
- A success message alone does not prove the CRM received the request. A saved submission plus a matching CRM record shows where delivery succeeded.
- Next move
- If both exist, move to report definitions. If the form saved the request but the CRM did not receive it, check the connection next.
Find the first failed handoff
Specialist check: website or integration owner.
- Look here
- Ask the CRM or integration owner for the delivery history of that specific submission. This history records attempts to send the form data and the destination's response.
- Check this
- Look for a rejected required field, expired connection, failed delivery or an update to a record you did not initially find. Also check whether tracking counted success when the form actually failed.
- What it means
- A delivery failure is a connection problem. A conversion recorded without a successful request is a tracking problem. They require different fixes.
- Next move
- Repair the demonstrated fault and replay only the approved test. Keep the original submission available for recovery; do not delete it to clean up the dashboard.
Explain the remaining difference
Marketing and CRM owners review together.
- Look here
- Compare a small set of submissions against CRM records and the chosen conversion action.
- Check this
- For each request, note delivered, existing contact updated, repeated request, date difference or unexplained failure. Use record references rather than sharing customer details.
- What it means
- A smaller new-contact total can be correct even when all requests were delivered. Unexplained missing submissions still need investigation.
- Next move
- Fix confirmed failures before changing campaign bidding. Keep the reconciliation as the agreed explanation of the numbers.
Keep the useful evidence.
Use this table as a reference while following the steps. Keep the information that identifies where the journey failed; remove names and email addresses before sharing it.
| Where to look | Capture | What it tells you |
|---|---|---|
| Reporting definition | Action name, primary/secondary setting, counting method and date basis | Compare equivalent actions; keep calls and sales milestones separate. |
| Form result | Timestamp, success response and backend submission reference | If success is absent, an ad conversion does not establish a delivered lead. |
| CRM delivery | Connector response, create or update result and record reference | A successful update may explain why the new-contact count is lower. |
| Repeat behaviour | One repeat submission using the approved test record | Document whether repeated events and existing contacts are counted differently. |
Platform behaviour and current access requirements: Google Ads: Analytics conversion discrepancies ↗ · Google Analytics: DebugView ↗ · Google Ads: Primary and secondary actions ↗
See how the problem happens
A mismatch that should not be fixed with a tag change
Suppose an ad report contains 12 conversions: eight demo requests and four qualified-demo imports. The CRM contains six newly created contacts and two existing contacts updated by those requests. Twelve conversion events, eight requests and six new contacts can all be correct. The next question is whether each request reached the CRM and whether the four qualification events are valid, not where the six missing people went. These numbers are a teaching example, not reported client results.
What did you find?
Use the observed behaviour to choose your next check.
No submission exists in the form backend
Check whether the tag fires on click or attempted submission. A conversion event is not proof that the form succeeded.
Submission exists, but no CRM record can be found
Inspect the connector request and response, required fields and update-versus-create behaviour.
Records exist and test flow works, but aggregate totals differ
Check that both reports count the same action, use comparable dates and handle repeat requests as intended. Only then investigate an unexplained tracking gap.
The tempting fix to avoid
Do not force the two dashboards to match by deleting conversion actions or multiplying CRM totals. Preserve an explanation of each legitimate difference.
Test success and the cases that should fail.
One successful test is not enough. Run the applicable cases below with approved test records. Write what happened beside the expected result, so a difference is visible before you release the change.
| Try this | This should happen |
|---|---|
| Successful request | Backend stores the submission; CRM creates or updates the intended record; the selected success event fires. |
| Required-field validation fails | No delivered submission and no success conversion. |
| Existing contact submits again | CRM behaviour follows the create or update policy; the event follows the documented counting policy. |
| Connector temporarily fails | Error is visible, the submission remains recoverable and the agreed retry or review path is used. |
Prove the fix
Tick a check only after you have tested it. Your ticks last while this page stays open; they are your own record of checks, not an automatic account test.
0 of 4 checks completed
When you can stop investigating.
Stop changing tracking when every request reaches the correct CRM record and the remaining differences are explained by dates, repeat requests or different actions being counted. Keep the explanation with the report. If requests are genuinely missing, continue at the first failed handoff.
Keep the problem from returning.
Keep a shared list of conversion definitions with event name, business meaning, owning tool, counting policy and CRM destination. Review it when a form, CRM integration or bidding goal changes. Use saved form submissions as the record of delivered requests and CRM qualification as a separate commercial milestone. A small recurring reconciliation sample is more informative than a monthly argument over dashboard totals.
Questions that change the diagnosis.
Should Google Ads and GA4 totals match exactly?
Not necessarily. First align the event, attribution scope, date basis and counting settings. Investigate unexplained differences after that alignment, rather than using exact equality as the acceptance test.
Can I repair missing historical attribution?
Only where retained evidence supports the association. Do not assign a campaign to old records merely because it was active when the contact arrived.
When you need help
Give the website or CRM owner the test record reference, submission time, conversion settings and delivery error. Remove names and email addresses from screenshots. Ask them to investigate the first missing handoff rather than sending a full lead list.
Documentation to keep beside you
Official references checked on 12 October 2026. Menus, permissions and feature availability can change; confirm the details for your account.
Need another pair of eyes?
Show me the step that fails and what you have checked so far. We can trace where the record, event or workflow first goes off course.
Explore the relevant capability ↗ · Read the broader strategy ↗