In this article
What belongs in a conversion tracking QA checklist?
Define the action before testing. A quote-button click, an accepted form and a booked appointment are separate events. Give each a clear name and expected result. AI Growth Systems' conversion tracking service reviews the measurement setup; this worksheet prepares the event list and evidence needed to discuss that scope.
| Action | Expected website result | Business record |
|---|---|---|
| Quote-button click | Correct form opens | No lead claimed yet |
| Valid submission | Acceptance is confirmed | One received inquiry |
| Invalid submission | Specific correction shown | No completed inquiry |
| Booking | Appointment is confirmed | Matching booking record |
Which test submissions should you run?
Run a valid inquiry, an incomplete form, a repeated click and a controlled failure in the test environment. Record browser, page and result. These 4 cases are proposed review scenarios, not a claim that every form behaves alike. Use clearly labeled test data and follow the team's cleanup process.
| Scenario | Question to answer | Evidence |
|---|---|---|
| Valid inquiry | Was exactly one request accepted? | Receipt and CRM record |
| Missing required field | Was the visitor told what to fix? | Error and event observation |
| Repeated click | Was a duplicate request prevented or identified? | Request and record counts |
| Controlled failure | Was success withheld when delivery failed? | Test response and visible message |
How do you inspect GA4 and Tag Manager events?
Use Google Tag Manager's preview tools to inspect tag behavior, then check the relevant events in Google Analytics 4, or GA4. Google documents DebugView for observing events during debugging. Record the event name and test condition, and compare them with the measurement plan rather than treating any visible event as a successful lead.
Keep the test record small enough to trace. One form attempt should have a timestamp, page and expected event sequence. If the sequence differs, identify whether the problem begins in the form, the trigger or the destination configuration before changing several settings.
How should you check the handoff to your team?
Match the accepted form to its CRM entry and the notification intended for the responsible team. Check the service, originating page and assigned owner. AI Growth Systems treats tracking setup and CRM integration as distinct scopes, so record a missing business record separately from a missing analytics event when requesting help.
| Destination | Check | Record |
|---|---|---|
| CRM | Correct service and owner | Test inquiry identifier |
| Notification | Correct recipient and useful context | Delivery observation |
| Analytics | Expected event and page | Debugging observation |
| Booking system | Correct date and availability | Test booking outcome |
What should you send for a tracking quote?
Send AI Growth Systems the website, form locations, analytics tools and one example of the mismatch. Name the receiving team. The entry growth audit costs $300; implementation is quoted separately. Ask the written scope to identify event setup, form changes, CRM work and post-release testing as separate deliverables.
| Item | Price or basis | Question |
|---|---|---|
| AGS entry growth audit | $300 | Which contact routes will be reviewed? |
| Tracking implementation | Written project quote | Which events and destinations are included? |
| CRM changes | Confirm separate scope | Who owns the handoff? |
| Outside products | Confirm separately | Which subscriptions are required? |
When should you repeat the tests?
Repeat the affected tests after changes to a form, tag container, consent interface, CRM connection or booking route. Save the release date with the test result. For an AGS project, put responsibility for that retest in the agreed scope, including who can confirm the final inquiry record and close the issue.
Sources and further reading
Read the original guidance alongside the practical examples in this article.