How Do I Check That Google Ads Conversion Tracking Is Set Up Correctly?

Google Ads audit checklist work starts with conversion tracking, because every other report depends on that data being wired correctly. AgencyPlaybook can help here with a read-only conversion tracking audit that shows the logic, thresholds, and raw data behind the finding. The check itself usually takes 10 to 20 minutes if you already have access to Google Ads and the site tag setup.

Choose the right check before you start

The steps change based on how the conversion is set up and what you want to confirm. Pick the path that matches the conversion action first, then test the same event in the same place the account uses for reporting.

Use the conversion type to set the test

  1. Check whether the conversion is a form submit, purchase, phone call, lead step, or another site event, then test that exact action on the live page or in a staging flow that mirrors the live page rules.
  2. Confirm whether the account counts one conversion per click or every conversion, since that setting changes the number you should expect to see after a test.
  3. Verify whether the conversion uses a global site tag, Google Tag Manager, or a direct event tag, because the check needs to match the setup on the page.
  4. Set the pass threshold before you test: one firing event on the expected page, one matching conversion action in Google Ads, and one recorded entry in the report for the test click or action.

If the account has multiple conversion actions, test the one used for bidding first. If a page has both a lead form and a thank-you page, check the one that Google Ads is actually counting.

Check the tag, action, and report in order

  1. Open the conversion action in Google Ads and confirm the name, source, count setting, value setting, and attribution window match the way the site is meant to track that event.
  2. Load the page that should fire the conversion, then use your tag test method to confirm the event fires on the correct page or after the correct action.
  3. Trigger the conversion with a real test flow, such as completing a form with a test email or placing a test order in a safe staging flow, and keep the exact page path and timestamp.
  4. Compare the event name from the site with the conversion action in Google Ads. For example, if the site fires a lead event on /thank-you at 14:32 and Google Ads records a conversion for the same action with the same timestamp range, the setup is aligned.
  5. Inspect the conversion report for the test date and verify that the action appears under the right campaign, source, and status. If the event lands in the wrong action or wrong source, fix the mapping before you trust the report.
  6. Repeat the same test from a second browser or device if the first test looks clean but the report is empty, since browser settings, consent setup, or page caching can change what fires.

AgencyPlaybook for Google Ads fits this stage well because the diagnostic playbook stays read-only and shows the thresholds behind the finding. That makes it easier to trace whether the issue sits in the tag, the action, or the report path.

Confirm the setup worked in reporting

A correct setup leaves a clear trail in Google Ads. You should see the conversion action named the way you expect, the status should show activity or recent data once the event has had time to process, and the report should place the conversion where the account expects it.

Look for these results

  1. Match the conversion action name to the site event name so there is no guesswork when you review the report later.
  2. Check that the conversion count changes only when the intended action happens, such as a completed form or an order confirmation page.
  3. Confirm that the value, if used, matches the number your site passes through. If you test a $25 lead value and the report shows a different number, the setup needs a fix.
  4. Review the campaign view and make sure the conversion appears under the campaign that drove the test click or visit.
  5. Spot duplicate firing by repeating the same test once. If one action creates two conversions, the trigger is too broad or the thank-you page loads more than once.

If the conversion shows in the site test but still does not appear in Google Ads after enough processing time, the problem is usually the action setup, the account link, or the trigger rule on the page. Check those three points in that order.

Frequently Asked Questions

What should I check first in a Google Ads conversion audit?

Start with the conversion action inside Google Ads, then test the tag on the live page, then review the report. That order shows whether the issue is in setup, firing, or reporting.

How do I know if the conversion fired more than once?

Repeat the same test once and compare the count. If one completed action creates two recorded conversions, the trigger or page rule is too broad.

Do I need a live account to test conversion tracking?

You need access to Google Ads and the relevant website or tag setup. A staging flow can help for safe testing, but the live reporting setup still needs a real check in Google Ads.

Where does AgencyPlaybook fit in this process?

AgencyPlaybook for Google Ads includes more than sixty read-only diagnostic playbooks, including conversion tracking audits. It helps surface the finding without changing the account, so you can review the logic before any change plan is approved.

Use the report before you trust the conversion

Trust the conversion only after the tag fires, the action matches the site event, and the report shows the same action in Google Ads. If any one of those pieces disagrees, fix that point before you use the data for bidding or campaign decisions. If you want a structured check, start with AgencyPlaybook and run the conversion tracking playbook alongside your own test flow.

Back to all articles