The five-minute tracking audit before launch

Contents (10 sections)

• What the five-minute check can and cannot tell you
• The quick verdict
• The five-minute smoke test
• Use Tag Assistant, but know what it proves
• The fastest duplicate-event check
• Check consent and attribution
• The smoke-test worksheet
• What happens when the smoke test fails
• Why five minutes is not a full audit
• What to do next

A five-minute check catches obvious tracking failures before the first dollar is spent. It cannot prove the complete path from ad interaction to booked job.

That distinction is the whole point of this page.

• Five steps before any spend.Confirm the conversion action, submit one real form and one broken form, test the phone path, and check the thank-you page cannot be triggered by loading its URL.
• Record pass, pass with limitation, or hold.Hold the launch if a blank form counts, a tag fires twice, or the event reaches the wrong ad account.
• A tag firing is not revenue.The smoke test proves tag behaviour, not CRM receipt, attribution, or booked-job payback. That needs the full audit.

What the five-minute check can and cannot tell you

This five-minute smoke test checks live tag fires before you spend a dollar. It verifies that forms, call links, and confirmation paths send events once without false triggers. However, it cannot prove CRM receipt, Google Ads attribution, or booked-job payback.

The quick verdict

There are three outcomes for a pre-launch check. Tracking is rarely a simple pass or fail. Use these three labels to decide whether to launch, launch with known limits, or stop until the tag setup is fixed.

• Pass: the test path works and no clear blocker appears.
• Pass with limitation: the live path works, but a later stage like the CRM handoff or Offline Conversion Import is not yet checked.
• Hold: a key event fails, fires twice, counts the wrong click, or cannot reach the right account.

The five-minute smoke test

Run these five steps in a clean browser before turning on ad spend. Test both a good form and a broken form so you know the tag only fires on real leads.

Four notes on the steps above, because each one hides a common failure.

On step 1. Google uses primary conversion actions for bidding and main reports. Secondary actions stay for observation only. If an account marks a button click as primary when the shop needs booked jobs, Smart Bidding will chase the wrong goal.

On step 2. Google Tag Manager (GTM) has a “Check Validation” box on form triggers. When checked, the trigger waits for a valid send. Without it, the tag may fire on every failed attempt. Never count a button click as a real lead.

On step 3. This test catches fake results fast. A button click proves someone tried. It does not prove a lead arrived.

On step 4. Google Ads tracks calls from ads and calls to a website number. A call length rule helps filter wrong numbers, but it is only a rough proxy. No call timer proves the caller lived in your area, liked the quote, or booked a job. Call tracking setup covers the full setup.

Use Tag Assistant, but know what it proves

Google Tag Assistant checks unverified conversion tags and tests live conversion actions in your browser. It shows what fired on the page, not what arrived in your office.

Use it to check which tags fired, which triggers ran, which variables loaded, and whether the conversion hit left the page.

Then check the receiving tools. Tag Assistant does not prove that your CRM saved the lead, that the call booked, or that the client paid.

The fastest duplicate-event check

Double counting breaks CPA and ROAS bidding fast. Check your account for two tags firing on the same user action before you launch.

• Native Google Ads tag plus an imported GA4 event.
• GTM tag plus a hard-coded site tag.
• Button-click event plus a form-success event.
• Thank-you page event plus a Server-Side Tagging event.
• Browser click-to-call event plus a call-system conversion.
• Extra fires when a user refreshes the thank-you page.

Do not delete a tag just because two tools log similar events. First check whether one is set to Secondary for observation while the other is Primary for bidding.

The goal is not “one tool.” The goal is one clear rule for each outcome.

Check consent and attribution

One clean test in your own browser does not cover every buyer. Check how your tags behave under Consent Mode v2 and across page hops.

• Test both granted and denied states in Consent Mode v2.
• Confirm thelanding page keeps the gclid across redirects.
• Check whether booking widgets strip source data when opening a new domain.
• Verify the form or call tool saves the source tag in the lead record.

Use only the tracking IDs and data flows allowed by law, your privacy notice, user consent, and platform rules.

The smoke-test worksheet

Use this table to log your pre-launch test. Save the result and note any limits before you turn on spend.

What happens when the smoke test fails

Hold the launch if the main event fails to fire, a blank form counts as a lead, or a tag fires twice. Also hold if the event hits the wrong ad account, a direct visit to the thank-you URL logs a conversion, or the CRM loses the lead.

The fix is usually small. Launching without fixing it is expensive. A broken tag turns your proving period into a test of bad plumbing instead of a test of your ads.

Why five minutes is not a full audit

This section keeps the smoke test honest. A five-minute check cannot prove the full chain across every page and CRM stage:

• Whether every landing page uses the same GTM container.
• Whether every trade line fires the right conversion action.
• Whether call logs remove duplicate rings.
• Whether Offline Conversion Import and Enhanced Conversions work.
• Whether the conversion window fits your sales cycle.
• Whether Smart Bidding uses the right primary goals.
• Whether CRM stages match real dispatch status.
• Whether closed revenue and gross profit match the ad report.

Your one-page monthly report

What the smoke test can put on the record

Money out Time before launch, not media spend Cheaper than buying a fixed test period with an event that counts the wrong action. State the advertising budget separately from tracking, call-system, management, and implementation costs.

Measured outcomes What the test session recorded, what the platform displays, and what the CRM, calendar, dispatch, completion, or payment record confirms The smoke test does not establish payback. It makes the later measurement more credible by removing obvious tracking uncertainty before spend begins.

Decision Pass, pass with limitation, or hold before launch Keep the worksheet, record the evidence, and name the limitation. A tag fire is not a booked job.

This page verifies plumbing, not economics. Later stages still have to be reconciled with the business record. I count conservatively: each call and form once, and nothing I cannot show.

What to do next

Five minutes catches the failures that surface later. The full tracking checklist covers the rest of the chain, and the conversion tracking audit is the deep version when something still does not reconcile.

Questions owners ask

Is five minutes enough to test Google Ads tracking?

It is enough for a quick smoke test of representative paths. It is not enough to prove a complete implementation across forms, calls, consent, attribution, CRM, offline outcomes, and booked jobs.

How do I test a Google Ads conversion?

Test the real action, inspect the event with Tag Assistant or the relevant debugging tool, verify the receiving system, check that it fires once, and document what the test does not cover.

Should I test by opening the thank-you page?

No. Opening the page directly may create a false conversion if the URL is accessible without a genuine successful submission. Test the complete form flow instead.

Should a form button click count as a conversion?

Usually not, if the business wants to measure a successfully received enquiry. A button click is an attempt. Define and test the accepted-success condition.

What call duration should count as a conversion?

There is no universal duration that proves a qualified lead or booked job. Use a provisional threshold only after comparing it with your own call records and business outcomes.

Does a firing tag prove tracking works?

It proves the tag fired in the tested context. It does not prove CRM receipt, Google Ads attribution, consent coverage, deduplication, booking, completion, revenue, or contribution.

When should I hold a campaign launch?

Hold it when a key event fails, counts the wrong action, duplicates without explanation, reaches the wrong account, creates false success events, or cannot be connected to the receiving business system.

What is the difference between this smoke test and a full tracking audit?

The smoke test checks representative paths in a single session before spend begins. A full audit checks every landing page and service line, deduplication, offline booked-job imports, conversion windows against the sales cycle, primary action selection, CRM stages, and revenue reconciliation.