Practical guide: how to audit GA4 and UTMs before Black Friday
A 7-step walkthrough to audit your UTMs, channels, Consent Mode, and purchase events in GA4 before the sales peak.
by Eleonora Diniz
This article was automatically translated by Galiléo.
Black Friday is just days away, and the question we hear most is: where do I even start reviewing my tracking? This guide breaks down the exact sequence we use in Dr. Métricas audits, prioritized from most critical to least.
If you haven't read it yet, start with our article on the 5 silent tracking errors—it explains why every step below matters.
Step 1. List every channel you're running
Before opening GA4, build a simple list: paid media (Google, Meta, TikTok, Pinterest), email, WhatsApp, influencers, affiliates, and organic. Every channel needs a clearly defined utm_source and utm_medium standard.
Step 2. Define your campaign UTM taxonomy
- utm_source: who sends the traffic (google, meta, email, whatsapp)
- utm_medium: the media type (cpc, paid_social, email, ai-assistant)
- utm_campaign: a unique name for each phase (bf26_warmup, bf26_week, bf26_cybermonday)
- Keep everything lowercase, no accents, and no spaces
Step 3. Validate all links before launch
Run every link through the Dr. Métricas UTM Check-up. It flags uppercase letters, missing parameters, unrecognized mediums, and the exact channel grouping the visit will land under in GA4.
Step 4. Check the last 30 days of channel reports
In GA4, go to Traffic acquisition and inspect three rows: Unassigned, Direct, and Referral. A high Unassigned count indicates non-standard UTMs. High Direct traffic often hides untagged WhatsApp and Stories links. Referral traffic from chatgpt.com should sit under AI Assistant; perplexity.ai may still show up in Referral because it's not yet on Google's default list of AI assistants.
Step 5. Test Consent Mode with and without user consent
Open your site in an incognito window, decline cookies, and browse all the way to the cart. Then repeat the process and accept them. Use GA4's DebugView to confirm events are firing correctly in both scenarios based on your setup.
Step 6. Run a test purchase and verify the purchase event
- The purchase event fires only once per order
- The transaction_id matches the payment gateway identifier
- The order value and currency match the actual order
- Delayed payments (like Pix or bank transfers) approved after closing the tab are still recorded
If your GA4 purchase count doesn't match your payment platform, not a single ROAS metric in your dashboard is reliable.
Step 7. Set up a daily 3-minute check
| Check | Where to look | Warning sign |
|---|---|---|
| New UTMs | UTM Check-up | Unrecognized medium |
| Unassigned | Traffic acquisition | Sudden spike |
| Purchases vs. orders | GA4 vs. platform | Discrepancy over 5% |
| Ad spend | Performance dashboard | Channel missing imported cost |
Download the complete checklist
Every step in this guide is mapped out in a ready-to-use spreadsheet you can run through for each account before the rush begins.


