Conversion Tracking Verification Audit
Test that forms, calls and purchases are counted once and correctly.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Verify my conversion tracking. Conversions defined and how they fire: [CONVERSION_DEFINITIONS]. Recent counts from analytics and from the business records for the same period: [COUNT_COMPARISON]. Tag setup description: [TAG_SETUP]. Compare analytics counts with real records to estimate over- or under-counting, and list likely causes: duplicate firing, thank-you page refresh, missing consent, ad blockers, cross-domain gaps, or test traffic. Design a test plan with specific test actions and the expected result for each. Return a table with Conversion, Analytics count, Real count, Gap and Likely cause, a score from 1 to 10 for reliability, and a fix sequence. Consent requirements are [VERIFY] for [JURISDICTION]. Add a monthly reconciliation routine. Also check the effect of consent choices on counts, and describe how to estimate the share of missing conversions without pretending to be precise. Suggest a lightweight way to tag offline conversions, such as calls or in-person bookings, using a question on the booking form. Then design a permanent reconciliation process. Specify the weekly comparison between analytics counts and the business system, the threshold at which a gap triggers investigation, the person responsible and the steps to follow. Provide a log template with date, conversion type, counts from each source, gap, suspected cause and action. List the most common causes of gaps for each conversion type: form submissions, phone calls, purchases and bookings. Add a protocol for changing tracking, with a staging test, a test plan with sample submissions, and a release note. Explain how to handle consent-related undercounting without inflating numbers, and how to describe the uncertainty when reporting results to managers. Include a short list of questions for the agency or developer who maintains the tags, and a reminder to document the tracking plan so that it survives staff changes. Consent rules are [VERIFY] for [JURISDICTION]. Add a final section on how to explain tracking limits to non-technical colleagues in three sentences, so that nobody treats the numbers as exact when they are estimates.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.