--- name: tracking-audit description: Audit a business's website tracking (GA4, Google Tag Manager, consent, ad platform tags, WhatsApp and call tracking, offline conversions) and say what is broken, what is missing and what to fix first. Use when someone asks whether their analytics or conversion tracking can be trusted, or before changing ad budgets. --- # Tracking audit The goal is one answer: can this business trust the numbers it uses to spend money? Judge everything against that. A tag that fires is not enough; the question is whether a booked client can be traced back to the click, search or chat that started it. ## What to ask for first Ask only for what you cannot see yourself: - The website address and the two or three pages that bring most enquiries. - How enquiries arrive: forms, WhatsApp, phone calls, booking tools, chat widgets. - Where enquiries end up: a CRM, a spreadsheet, a shared inbox, or the ad platforms' own lead forms. - Which ad platforms run today (Google Ads, Meta, TikTok, LinkedIn, Snapchat, Microsoft). - Whether the business sells in the EU or UK as well as the Gulf, because consent rules differ. If you can open the site in a browser, do the checks yourself. If you cannot, give the person the exact steps and ask them to paste what they see. ## Checks, in order Work through these in order and stop to report anything marked critical before moving on. Later checks depend on earlier ones being right. ### 1. Tags on the page - View the page source or the network requests. Note which tags load: Google tag (gtag.js), Google Tag Manager container IDs, Meta pixel, TikTok pixel, LinkedIn Insight, Snap pixel, Microsoft UET, any call tracking script. - Critical: two GA4 properties or two GTM containers on the same page counting the same visits. Duplicate page views and conversions inflate every number downstream. - Critical: tags present on the homepage but missing on landing pages or thank-you pages. - Check that one measurement ID is used consistently across the site. ### 2. Consent - Is there a cookie banner, and does declining it actually stop marketing tags? Test it: decline, reload, and check whether the pixels still fire. - If Google Consent Mode is used, check that a default state is set before any Google tag loads, and that it updates when the visitor chooses. - For the Gulf, check the business against the UAE Personal Data Protection Law and the Saudi Personal Data Protection Law where they apply. For EU or UK visitors, consent before marketing cookies is required. - Do not give legal advice. Say what the site does today and where a privacy lawyer should look. ### 3. Conversions that matter List every action that counts as a lead and check each one fires exactly once, with the right name: - Form submits: test a real submission. A tag on button click is weaker than one on a confirmed success (thank-you page, success message or a dataLayer event pushed after the server accepts the form). - WhatsApp: clicks on wa.me or api.whatsapp.com links. A click is intent, not an enquiry. Note whether the business can match chats back to the ad or page (a reference code in the prefilled message is the simplest way). - Phone: tap-to-call clicks, and whether call tracking numbers are used on paid traffic. - Booking tools and chat widgets: these often live in iframes and need their own events. Critical: a conversion counted in Google Ads or Meta that is not a real lead, such as page views, scroll depth or any button click. Platforms optimise towards whatever they are told is a conversion. ### 4. Source captured on every lead - Do UTM parameters, gclid, gbraid, wbraid, fbclid and ttclid survive to the CRM record? Submit a test form from a URL with UTM tags and check the record. - Does the source survive when a visitor lands on one page and enquires on another? If the site does not store the first-touch source, it is lost. - Are WhatsApp and phone enquiries given a source at all? Usually they are not, and they are often the largest channel in the Gulf. ### 5. Results sent back to the ad platforms - Google Ads: is there an offline conversion import or enhanced conversions for leads? Google accepts click-based imports for up to 90 days after the click. - Meta: is the Conversions API sending qualified or booked leads, with an event ID that matches the browser pixel so events are not counted twice? - If nothing is sent back, the platforms are optimising for enquiries, not clients. Flag this as the largest opportunity, not as an error. ### 6. GA4 settings - Data retention set to 14 months, not the 2-month default. - Internal traffic and the business's own staff filtered out. - Key events marked to match the real conversions in step 3, and nothing else. - Cross-domain measurement set up if the journey crosses domains (for example a separate booking or payment site). - Google Ads and Search Console linked. ## Report Write the report for a marketing manager, not a developer. Use this shape: 1. **Verdict** in two or three sentences: can the numbers be trusted for budget decisions today? 2. **Critical** issues that make current reporting wrong, each with what is happening, how you know, and the fix. 3. **Missing** pieces that limit what the business can learn, most valuable first. 4. **Good** things already in place, briefly. 5. **Fix order**: a numbered list, with who usually does each step (marketer, developer, CRM admin). Do not invent figures. If you could not test something, say so and say how to test it. Never ask for passwords or API keys; ask the person to share screenshots or to give view access instead.