Google Ads guide

Google Ads Conversion Tracking Checklist

Use this Google Ads conversion tracking checklist before launch, after a website or checkout change, and during regular reporting reviews. Confirm that each action represents a real business outcome, fires at the correct completion point, counts once according to the business model, passes defensible values, and can be reconciled with the source system.

Pair it with Google Ads conversion tracking best practices, how to set up conversion tracking, and Google’s web conversion setup guide.

1. Business-outcome checklist

Write down:

  • the business result that should receive more budget;
  • the event that represents that result;
  • supporting events used for funnel diagnosis;
  • the owner who confirms whether the outcome is real;
  • the campaign or account goals that should use the action;
  • the review date and stop condition if measurement is incomplete.

Ask whether more of the event would make the business deliberately increase spend. If not, keep it secondary or diagnostic. A page view, form start, or button click can be useful without being a primary conversion.

2. Conversion-action checklist

For every action, record:

  1. Clear name and business meaning.
  2. Primary or secondary role.
  3. Source system, page, or application event.
  4. Trigger and true completion point.
  5. Counting rule.
  6. Value and currency source.
  7. Transaction, order, lead, or other identifier.
  8. Consent behavior.
  9. Owner and last test date.

Look for actions that represent the same outcome through multiple tools. Keep more than one implementation only when the purpose and deduplication behavior are documented.

3. Implementation checklist

Confirm that:

  • the Google tag or chosen foundation loads on the relevant pages;
  • the event implementation is published in the intended environment;
  • forms, checkout, booking, phone, or application flows are covered;
  • redirects and cross-domain steps are understood;
  • single-page routes or dynamic states trigger correctly;
  • Tag Manager, Analytics, server, or CRM ownership is clear;
  • the privacy and consent implementation is approved.

Use Google’s Google tag guidance and the web conversion setup guide to confirm current platform requirements.

4. Trigger and quality checklist

Test each action at its actual completion point:

  • invalid form;
  • abandoned form;
  • successful form;
  • declined or canceled payment;
  • confirmed purchase;
  • checkout refresh;
  • completed booking;
  • phone click versus connected or qualified call;
  • CRM or offline qualification.

A click, page load, or button press should not be a completed conversion unless the business explicitly defines it that way. Check that the page or application does not allow a confirmation URL to create another outcome on refresh.

5. Counting and deduplication checklist

Choose “one” or “every” according to how the business counts success. Check:

  • repeated form submissions;
  • repeat bookings;
  • order refreshes and retries;
  • browser and server events;
  • Analytics imports and direct tags;
  • duplicate webhooks;
  • missing or changing transaction IDs;
  • test traffic and internal visits.

Run one controlled test, then refresh or retry the relevant path. Compare the expected count with the website, checkout, and CRM. Fix the duplicate source rather than deleting records without understanding the cause.

6. Value and currency checklist

Verify that:

  1. The value definition is documented.
  2. Orders use the correct source amount and currency.
  3. Lead values reflect an approved model rather than made-up revenue.
  4. Refunds, cancellations, discounts, tax, and shipping are handled consistently.
  5. Offline or later-stage values have an identifier and source record.
  6. Zero, missing, or wrong-currency values are investigated.

Use Google’s offline conversion setup information when the important outcome happens after the website. Do not pass a value just to make a report appear healthier.

7. Consent and data-handling checklist

Confirm:

  • which signals require consent;
  • what happens when consent is accepted or denied;
  • regional behavior is tested;
  • first-party or Enhanced Conversions data is approved;
  • collection, hashing, disclosure, retention, and access are documented;
  • an owner reviews future privacy or tag changes.

Read Google’s Enhanced Conversions best practices alongside the business’s approved privacy process. Hashing does not authorize data collection that the business has not approved.

8. Pre-launch test checklist

Complete a controlled path and verify:

  1. The foundation loads.
  2. The action fires only after success.
  3. The correct action receives the event.
  4. Count, value, currency, and identifier are correct.
  5. Invalid, abandoned, and duplicate paths do not count incorrectly.
  6. Consent behavior matches the approved implementation.
  7. The event can be found in diagnostics or later reporting.
  8. One source record reconciles across systems.

Google’s Tag Assistant guide can help inspect tags. Save the test date, result, and any known processing delay before launch.

9. Reporting and reconciliation checklist

For a fixed review period, compare:

  • website, checkout, or source-system outcomes;
  • events sent and accepted;
  • Google Ads conversion count and value;
  • duplicate, rejected, canceled, or pending records;
  • qualified leads, orders, revenue, or later sales stages;
  • click-to-conversion delay and timezone.

Totals may differ because of attribution, processing, privacy, and counting rules. The difference should have an explanation and an owner. Do not change bids until a sudden measurement change is separated from a demand change.

10. Change-control checklist

For every website, tag, consent, checkout, CRM, action-role, value, or campaign goal change, record:

  • old state and new state;
  • business reason and expected effect;
  • affected actions and campaigns;
  • test case and result;
  • consent or data review;
  • owner, release date, and next check.

Re-test after a site redesign, domain change, checkout release, analytics migration, or CRM change. If the event changes the bidding signal, treat it as a campaign-relevant change even when no bid was edited.

For diagnosis, use how to fix Google Ads conversion tracking problems. For ongoing improvement, read how to optimize Google Ads conversion tracking. The adz.so product overview is a truthful next step for supported workflows; it does not install tags, validate private account data automatically, or guarantee performance.