Working tool · published
Call and form tracking QA checklist
Test conversion events, source context, deduplication, fallbacks, privacy, CRM handoffs, and failure states for calls and forms.
Reviewed 2026-07-20 · National guidance, Austin proofBrowser checklist
0%Work through the release gate.
Progress stays in this browser tab and is not submitted to VOID.
The task and the failure mode
Built for: Marketing, analytics, and operations teams responsible for lead-path reliability.
A tag can fire while the form fails, a call goes unanswered, source fields overwrite, or personal data leaks into analytics.
Workflow
- 01Write the allowed event contract.
- 02Test success, error, duplicate, and blocked-script states.
- 03Follow source context into downstream systems.
- 04Reconcile analytics against operational records.
- 05Monitor changes and failures continuously.
Evidence to retain
- Network and event-queue observations.
- Operational receipt or explicit failure for each test.
- No prohibited values in URLs or analytics payloads.
Release checklist
- Form success event
- Form error event
- Duplicate-submit guard
- Phone click and connected-call distinction
- Dynamic number fallback
- UTM/referrer preservation
- CRM source persistence
- PII and consent review
Boundaries and caveats
Client-side events alone do not prove a lead reached operations.
Call recording and personal-data rules require jurisdiction-specific review.
Primary sources
- Google Analytics: About key eventssupport.google.com
- Google Analytics: Collect campaign data with custom URLssupport.google.com
- Google Search Console performance reportingsupport.google.com