Pre-launch tracking QA checklist

Before a campaign launches, everyone looks at the creative, the audience, the budget, and the landing page design.

Tracking often gets a quicker look, or no look at all.

That is risky because a landing page can look perfectly fine while the measurement layer is broken or incomplete. The form can be visible, but the lead may not reach the inbox. The WhatsApp button can open, but the click may not be tracked. GTM may load on the homepage, but not on the new campaign page. A thank-you page can change without anyone updating the conversion trigger.

For agencies, this creates two problems:

The goal of pre-launch QA is not to prove perfect attribution. The goal is to reduce obvious risk before traffic starts.

Do not begin with tags. Begin with the action that creates business value.

For most SMB and lead-generation campaigns, that means:

Ask one simple question:

Can a real visitor still complete the action you are about to pay for?

If the answer is not clearly yes, tracking is not the first problem. The lead path is.

After the lead path, review the visible tracking layer.

For a basic pre-launch review, check whether these appear visible where expected:

A visible browser-side check is not the final proof. It does not access ad accounts or analytics accounts. But it is a fast way to catch missing or limited signals before the campaign is live.

Many conversion tracking issues start after the form.

A page may still have a form, but the post-submit behavior changes. The user may stay on the same page instead of reaching the old thank-you page. A redirect may be removed. A new thank-you URL may be used. A form plugin may switch from page redirect to inline success message.

Before launch, test:

This is where manual testing is still important. A visible scan can help, but it cannot prove that the lead reached a CRM or that every conversion event fired correctly.

A lot of paid traffic is mobile, and mobile lead paths often behave differently.

Check the campaign page on a real phone if possible.

Review:

Do not expose full WhatsApp numbers or sensitive contact targets in a public report. For client-safe reviews, summarize the action without showing the raw value.

If something looks wrong, make the developer handoff specific.

A vague message like “tracking may be broken” is easy to ignore.

A useful handoff says what page was checked, what visible signal appears limited or missing, and what should be reviewed.

Example:

“The campaign landing page should be reviewed before launch. The form is visible, but the expected Google Ads conversion signal appears limited in a browser-side check. Please confirm GTM loads on this page, the intended conversion tag or trigger is still present, and the form submission or thank-you flow matches the tracking setup. Manual verification in Google Ads and GTM may still be needed.”

This is much easier to act on than a general warning.

Use this before sending paid traffic to a landing page:

This checklist is intentionally simple. The point is to build a habit that catches common problems.

Pre-launch QA reduces risk, but it does not stop future changes.

A client may edit the page next week. A developer may update a plugin. A new landing page variation may go live. A widget may be replaced. A consent tool may change. GTM may disappear from one template.

That is why monitoring matters after launch.

A one-time check tells you whether the page looks okay now. Monitoring helps you notice whether visible tracking or lead-action signals appear to change later.

For agencies managing several active client sites, that can be the difference between finding the issue early and finding it during a client report call.

Before the next launch, run a free check on the exact page that will receive traffic. Review the lead path, visible tracking signals, and developer handoff before spend starts.

If you manage multiple client sites, use the agency pilot to review up to 5 important sites together.