Use this reusable conversion tracking QA checklist to verify that Google Ads and GA4 conversions fire at the right time, carry useful data, respect consent choices, and are counted once. It is designed for campaign launches, landing-page changes, tracking updates, and routine data audits.
Overview
Conversion data is only useful when the measurement setup reflects what actually happened. A purchase, lead submission, phone call, or sign-up should be recorded from a defined user action—not from a page view that can occur repeatedly, a test event that was never deduplicated, or a tag that fires before the form is successfully submitted.
Google Ads conversion tracking and GA4 conversion tracking can work together, but they are not automatically interchangeable. A conversion imported from GA4 may have different counting, attribution, or reporting behavior from a conversion action created directly in Google Ads. Before comparing platforms, document which system is the source of truth for each business outcome and why.
Keep a simple measurement register for every primary conversion. Record the conversion name, event or tag that produces it, trigger condition, value rule, counting method, attribution setting, destination account, and whether it is used for bidding. This prevents two tags, two platforms, or two versions of the same event from being treated as separate customer actions.
Checklist by scenario
Before launching a new campaign
- Define the conversion. Write down the exact completed action, such as a confirmed order, successful quote request, qualified form submission, or connected call. Do not use a vague label such as “engagement” for a conversion intended to guide bidding.
- Choose the implementation. Decide whether the action will be measured with a Google Ads tag, a GA4 event imported into Google Ads, a tag-management setup, or a supported call-tracking integration. Avoid implementing multiple methods unless you have a clear deduplication plan.
- Confirm the trigger. For forms, trigger after a confirmed success state rather than on a button click. For purchases, trigger on the order confirmation or transaction event and pass a stable transaction ID when the implementation supports it.
- Check parameters. Review event names and parameters for consistency. Ecommerce actions should carry the relevant order or transaction identifier and, where applicable, value and currency. Lead events should identify the intended form or conversion category without exposing personal information.
- Review consent behavior. Test the site with consent granted and declined. Confirm that tags behave according to the site's consent configuration and that the reporting expectations for consent-limited traffic are documented. Do not assume that a browser preview with unrestricted consent represents every visitor.
- Check URL and campaign tagging. Use a consistent UTM naming convention for manually tagged traffic and verify that redirects do not remove parameters. A UTM naming and GA4 paid traffic audit workflow can help identify attribution breaks before launch.
- Separate primary and secondary actions. Mark the action used for optimization as the primary business outcome. Keep micro-conversions, such as an engaged visit or brochure view, available for analysis without allowing them to inflate the main conversion total.
After publishing tags or a landing-page change
- Use the tag manager's preview or debugging mode to walk through the complete journey, from ad landing page to confirmation.
- Confirm that the expected event fires once, after the success condition, and not when the page loads or refreshes.
- Inspect the browser network activity or platform diagnostics to verify that the request contains the expected event name, value, currency, transaction ID, and consent state.
- Check GA4 real-time or debugging views for the event, then confirm that the event is marked as a key event where appropriate. If it is imported into Google Ads, verify the linked property, event selection, and conversion action settings.
- Test the confirmation page directly in a new session. If direct access records a conversion, consider whether the page can be refreshed or revisited without a genuine new transaction.
For ecommerce and test orders
- Place a controlled test order using a documented test value or payment method.
- Record the order ID, timestamp, landing URL, consent choice, and expected platform results.
- Verify one transaction in the store or payment system, one relevant event in GA4, and one intended conversion in Google Ads where the reporting delay and setup permit.
- Refresh or revisit the confirmation page and confirm that the same order ID is not counted as a second purchase.
- Remove or clearly label the test data in internal reporting. Never use test conversions to judge campaign performance.
For phone calls
- Confirm which calls qualify: all calls, calls above a duration threshold, calls from a particular number, or calls marked as qualified by a sales process.
- Test the phone number replacement or call extension behavior on the relevant device types and landing pages.
- Verify that the call source is mapped to the correct campaign or channel when the tracking system supports that detail.
- Compare call records with Google Ads and GA4 reporting. Differences may reflect separate definitions, processing windows, or attribution rules rather than a broken tag.
What to double-check
Use the following troubleshooting table when a result does not match expectations.
| Symptom | Likely checks |
|---|---|
| No conversion appears | Confirm the trigger can be reached, the tag is published in the correct container, consent permits the intended behavior, and the event is sent to the correct property or account. Check whether reporting delay is being mistaken for failure. |
| Two conversions appear for one action | Look for both a direct Google Ads tag and an imported GA4 event, duplicate containers, repeated form listeners, or a confirmation page that fires again on refresh. Compare transaction IDs and timestamps. |
| Conversions fire on button clicks but include abandoned forms | Replace the click trigger with a confirmed success event, server response, thank-you state, or other reliable completion signal. |
| Revenue is missing or incorrect | Inspect value and currency parameters, data types, order totals, discounts, tax and shipping rules, and whether the transaction identifier changes during checkout. |
| GA4 shows the event but Google Ads does not | Check the property link, event or key-event selection, import status, account permissions, conversion action status, and the reporting date range. Confirm that the event is eligible for the selected destination. |
| Google Ads and GA4 totals differ | Compare conversion definitions, counting methods, attribution settings, time zones, lookback settings, consent effects, and reporting windows. Treat platform totals as related views, not guaranteed duplicates. |
| Call conversions are absent | Test number insertion, call-source configuration, call eligibility rules, forwarding or tracking configuration, and whether the test call meets the defined duration or quality threshold. |
For paid search analysis, annotate any tracking change in the reporting dashboard. This makes it easier to distinguish a genuine performance shift from a measurement change. The same discipline helps when reviewing search term performance, match types, or landing-page changes alongside conversion data. Campaign optimization should not begin until the outcome being optimized is trusted.
Common mistakes
- Counting every submission as a qualified lead. A completed form is not always a sales-qualified opportunity. If qualification happens later, keep the initial lead and qualified lead as separate stages.
- Using page views as purchase conversions. A page view can be repeated, shared, indexed, or reached through navigation. Use a transaction event with a stable identifier for purchases.
- Testing only while logged in or with consent enabled. Authentication, browser settings, extensions, and consent state can change how tags behave. Test representative conditions and record the assumptions.
- Changing names without documenting the change. Renaming or replacing events can break imports, dashboards, audiences, and historical comparisons. Add a change note before altering a conversion definition.
- Mixing primary and secondary actions in one KPI. A dashboard that combines purchases, calls, downloads, and form starts can look healthy while hiding a decline in the actual business outcome.
- Ignoring attribution settings. A conversion can be credited differently across Google Ads, GA4, a CRM, and a call platform. Define the reporting question before deciding which total to use.
- Assuming debugging tools prove production behavior. Preview modes are valuable, but they do not replace a published-container test, a real landing-page journey, and a controlled order or lead validation.
If tracking quality affects campaign decisions, keep the implementation notes beside the account's optimization documentation. Related guides on quality score diagnostics and ad copy testing are more useful when conversion definitions and attribution rules are stable.
When to revisit
Run this checklist before every new campaign, landing-page redesign, checkout change, form-provider migration, tag-manager publication, analytics-property change, or call-tracking update. Recheck it after consent-management changes, domain moves, major platform workflow changes, and seasonal launches when reporting decisions carry more weight.
A practical quarterly audit can be brief: select one recent conversion for each primary action, complete a controlled test where appropriate, compare platform totals with the source system, inspect duplicate behavior, and review whether the conversion is still suitable for bidding. Also confirm that UTMs, campaign naming, and dashboard filters still match the current account structure.
When a discrepancy appears, pause optimization changes, document the symptom and date, identify the first point where the journey diverges, and fix one variable at a time. Then repeat the same test and record the result. A maintained QA log turns conversion tracking from a one-time setup task into a dependable part of PPC campaign analytics.