How Do I Test Whether Google Ads Conversion Tracking Is Working?

The direct answer

Do not call Google Ads conversion tracking working just because a tag is installed or a dashboard shows a green status. Run one traceable test through the same path a customer uses, then verify five layers: the intended action happened, the tag fired once, the correct conversion action received it, the event was eligible for the campaign's reporting or bidding setup, and the matching form, call, booking, or sale reached the business system.

Start with Google Ads Tag Assistant. Trigger the form, phone-click, booking, purchase, or other action yourself and inspect what fired. If the action also uses Google Analytics, confirm the event in DebugView or Realtime. Then compare the timestamp and test label with the form provider, inbox, call-tracking platform, booking tool, CRM, or order system. A browser event without a real business outcome is incomplete measurement; a real lead without an ad-platform event is a tracking gap.

Illustrative conversion-QA interface, not a client account, campaign result, or performance claim.

• Define the exact customer action that should count.
• Trigger it on the live site with debugging enabled.
• Confirm one correct event, not zero events or duplicates.
• Verify the right Google Ads action, goal, and optimization role.
• Match the test to the business's actual lead or sales record.

Write the pass condition before opening Tag Assistant

Name the result in business language first: a submitted estimate request that reached the inbox, a connected call that met the chosen duration, a completed booking, or a purchase with the correct value and currency. Avoid vague definitions such as 'engagement' when the campaign is expected to create leads or sales.

Then identify the exact Google Ads conversion action that represents that result. Record its source, category, counting rule, value rule, attribution window, and whether it is primary or secondary. Google's primary and secondary conversion guidance explains that primary actions can appear in the Conversions column and support bidding when the related goal is used, while secondary actions are normally observation-only in All conversions.

This settings review prevents a common false pass: the tag fires correctly, but the campaign is optimizing toward the wrong action. Page views, button clicks, test events, imported analytics events, and direct Google Ads tags can all coexist. List them before testing so you know which one should fire and which ones should not.

• Business outcome and completion screen or event
• Google Ads conversion action name and source
• Primary or secondary optimization role
• Expected count, value, currency, and lead destination
• A unique test label and exact test time

Use Tag Assistant to prove the trigger

Open Goals, Conversions, and Summary in Google Ads, choose the action, and launch troubleshooting when the account offers it. Google's conversion-action troubleshooting guide says Tag Assistant can verify actions marked Unverified, Tag inactive, or Needs attention by connecting to the website and guiding a test conversion.

Complete the full live path instead of visiting only a thank-you URL. Start on the landing page, accept or reject consent as the test requires, submit the form or finish the booking, and watch the event sequence. Confirm the Google tag loads before the conversion event, the intended conversion ID and label are used, and the conversion event fires at the completion point—not when the page first loads or when someone merely focuses a field.

Run negative tests too. Open the form without submitting, trigger validation errors, refresh the confirmation page, use the back button, and try the mobile path. The conversion should not fire for abandoned or failed actions. If a refresh produces another event, determine whether the implementation or an order or transaction identifier prevents duplicate counting before accepting the setup.

Check Analytics separately when Google Ads imports the event

If Google Ads imports a Google Analytics key event, verify the Analytics event before waiting for the Ads interface. Google's DebugView documentation says DebugView displays events and parameters from a debug device in real time. Inspect the event name and the parameters needed to distinguish a genuine completed lead from an ordinary page view or button click.

Also check the Realtime report. Google's key-event reporting guide identifies Realtime and DebugView as tools for confirming that key events are being recorded. Seeing the event in Analytics proves receipt there; it does not by itself prove the event has been imported into the intended Google Ads account, assigned to the right goal, or used for bidding.

Keep direct Google Ads actions and imported Analytics actions clearly named. If both measure the same form completion and both are primary, reporting or optimization can count two signals for one business outcome. Decide which action is the bidding source and keep any diagnostic duplicate secondary or remove it only after reviewing campaign dependencies.

Read the Google Ads status without overreacting

After the debug session, return to the conversion summary and inspect the action's tracking status and diagnostics. Google says verified actions may initially show No recent conversions and later change when attributed conversions are recorded. A low-volume action can be technically healthy without recent attributed activity, so the label alone is not a reason to rebuild the tag.

Statuses such as Unverified, Inactive, Misconfigured, or Needs attention require investigation, but use the details rather than guessing. Google's sitewide-tag troubleshooting guide recommends checking the Google tag across landing and conversion pages, Tag Diagnostics, auto-tagging, Conversion Linker when Google Tag Manager is used, and duplicate or legacy tags.

Allow the interface time to update after a successful debug session. Google notes that actions verified through Tag Assistant may take roughly 30 minutes to update in the account, while some diagnostics take longer. Record the test time and result instead of repeatedly submitting forms and filling the reports with unlabeled tests.

Match the platform event to a real business record

The strongest test continues beyond the browser. Put a unique, non-customer label in the test form or booking, then find the same label and timestamp in every required destination: form provider, notification inbox, CRM, scheduling system, call log, or order database. Confirm the staff-facing notification contains the fields needed to respond and that the lead was routed to the correct person.

For phone calls, test each measured path separately: a tap on the website number, a call from an ad asset when used, and any dynamic number replacement. A phone-link click is not the same as a connected call. If the chosen conversion is based on call duration or another qualification rule, confirm that the test satisfies or intentionally does not satisfy that rule.

For purchases or variable-value bookings, compare value, currency, transaction or order identifier, and item or service context. Do not accept an event merely because its name is correct. A conversion with the wrong value can distort value-based reporting and bidding even when the action status looks healthy.

• One browser action maps to one expected event.
• The event reaches the intended Ads or Analytics destination.
• The business receives the matching lead, booking, call, or order.
• Values and identifiers match the source record when applicable.
• The test is labeled so it can be excluded from business totals.

Test the conditions that usually break tracking

Repeat the critical path on mobile and desktop, on the production domain, and through any external scheduler, payment page, embedded form, or cross-domain step. Check that redirects preserve the expected journey and that the conversion fires only after success. A test on a staging URL does not prove the production container, consent rules, environment variables, or form endpoint match.

Test the site's consent behavior rather than disabling it and declaring success. Google's Tag Assistant guidance notes that consent tools, browser extensions, firewalls, proxies, and content security policies can block or change tag behavior. The goal is not to force every browser to send data; it is to confirm the implementation follows the site's consent policy and fails predictably when measurement is unavailable.

Review the path again after domain migrations, form replacements, booking-tool changes, checkout updates, tag-container publishes, consent-platform changes, and major site deployments. Those releases can change URLs, event names, data-layer values, or load order without producing a visible error for the customer.

Keep a short conversion QA record

Save the test date, production URL, device and consent state, conversion action, event name, expected parameters, Tag Assistant result, Analytics result when used, Google Ads status, and matching business record. Add screenshots or exported debug details when they help another person reproduce the finding. Do not store customer secrets or unnecessary personal data in the QA record.

A practical pass statement is specific: 'The live estimate form produced one submit-lead event, Tag Assistant showed the intended Google Ads action once, Analytics DebugView received the expected event, the test arrived in the CRM with the matching timestamp, and the action is primary for the campaign goal.' A practical failure statement names the first broken layer and the next owner.

If you are spending on clicks but cannot reproduce that chain, pause major optimization conclusions until the measurement path is understood. Review DigitalWiz Paid Ads Management, use the broader guide to track where website leads come from, or contact DigitalWiz for a conversion-tracking review.