Website form tracking checklist

A website form can look fine and still fail as a lead path. The form may be visible, but the submit button may not work on mobile. The success message may appear, but the lead may not reach the inbox or CRM. The thank-you page may have changed, so the old conversion trigger no longer matches. Or the form may still collect leads, but the tracking around it has disappeared. That is why form QA should happen before paid traffic starts, not after leads look strange in a report.

TrackCanary checks visible browser-side signals. It does not prove final attribution accuracy, ad account setup, analytics account data, legal compliance, or every possible conversion event. Manual verification may still be recommended.

Why form tracking fails quietly

Form problems are easy to miss because the page often looks normal.

A visitor sees a form. The agency sees a form. The client sees a form. Everyone assumes it works.

But small changes can break the lead path or the tracking around it:

The dangerous part is that none of this necessarily makes the page look broken.

a form plugin update changes the submit behavior
a thank-you page is removed or renamed
the form now shows an inline success message instead of redirecting
GTM is missing from the landing page
the conversion trigger still expects the old URL
the mobile layout hides part of the form
the submit button fails after a design change
the lead goes to the wrong email address or CRM pipeline
consent behavior changes when tags fire

Start with the real lead path

Before checking tags, test the action that matters.

Ask:

Can a real visitor submit the form and become a lead?

For most lead-generation pages, that means checking:

A visible scan can help review the page and the tracking layer, but manual submission testing is still important for serious campaigns.

the exact landing page URL used in the campaign
desktop and mobile versions
all required fields
the submit button
the success message or thank-you page
the destination inbox, CRM, or lead notification
what happens if the visitor uses a different browser or device

Visible form and lead-path review

A browser-side review can help identify whether key lead elements appear on the page.

For a basic form tracking checklist, review whether these are visible:

This does not prove that the form reaches the CRM. It helps you see whether the visible lead path and the visible tracking layer deserve attention before campaign traffic starts.

contact form
quote request form
booking form
demo request form
newsletter or lead capture form
thank-you or confirmation page
WhatsApp or call alternative
visible tracking signals around the page

Tracking signals around form pages

For many agencies, the form page is only one part of the conversion path.

You may also need to review:

If the form changes, the tracking setup may also need to change. A conversion trigger that worked for an old thank-you page may not work after the form switches to an inline success message.

That is why form QA and tracking QA should be checked together.

Google Tag Manager
GA4
Meta Pixel
Google Ads conversion tracking signals
thank-you page visibility
post-submit state
redirects
consent or cookie behavior
mobile layout differences

Manual submission testing

Do not skip the manual test.

Before launching paid traffic, submit the form yourself and check:

This is not glamorous work, but it catches the problems that cost money.

1. Did the form submit successfully?
2. Did the expected success message or thank-you page appear?
3. Did the lead reach the correct inbox or CRM?
4. Did the notification include the right page or campaign context?
5. Did the same flow work on mobile?
6. Did the same flow work after accepting or rejecting cookies where relevant?

Developer handoff checklist

If something looks wrong, send a specific handoff.

Instead of saying “the form tracking is broken,” send something like:

“The campaign page should be reviewed before launch. The form appears visible, but the expected post-submit or conversion tracking path may need review. Please confirm the form submits correctly, the lead reaches the intended inbox or CRM, GTM loads on this page, and the intended conversion tag or trigger still matches the current form behavior.”

This gives a developer something concrete to check.

When monitoring helps

A form can pass QA today and change next week.

That is common on client sites. Someone updates a plugin, edits a landing page, changes a form provider, replaces a widget, or removes a thank-you page during a redesign.

Monitoring helps when:

A one-time checklist is useful before launch. Monitoring helps you notice later changes.

paid campaigns are always running
the client changes the site without telling the agency
several client sites need review
forms, WhatsApp, calls, or booking flows drive revenue
developers regularly update themes, plugins, or landing pages
you want a client-safe summary when something appears to change

Next step

Before sending traffic, use the free Website Form Checker on the exact page that will receive visitors. Review the visible form, lead path, tracking health summary, and developer handoff.

If the site is important or you manage several clients, request the assisted agency pilot and add up to 5 sites for first checks.

Next step

Before sending traffic, use the free Website Form Checker on the exact page that will receive visitors. Review the visible form, lead path, tracking health summary, and developer handoff.

Website Form Checker Free tools