1---2name: tracking-audit3description: >-4 Checks the conversion tracking behind each ad platform a B2B SaaS company pays for (conversion actions, what5 bidding optimizes for, enhanced conversions for leads, click IDs in the CRM, consent, offline imports and CRM6 stage mapping), reconciles platform conversions with CRM leads, and returns a pass or fail table per platform with7 severities and the fix order. Use it before any budget, bid or channel decision rests on platform conversion data,8 after a site or form change, or when platform and CRM figures disagree. Not for UTM naming (use utm-check), for9 designing which CRM stages to send back (use crm-feedback-loop) or for pipeline by channel (use pipeline-report).10license: MIT11compatibility: >-12 Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Reads a connected ad account or CRM13 read-only if the agent has one, otherwise exports, screenshots or pasted rows. Python 3 is optional, for the14 reconciliation.15metadata:16 author: SHAKEUP17 version: "1.0.0"18 stage: check19 plugin: markops20 homepage: https://www.shakeuphq.com/skills/tracking-audit21---22 23# Tracking audit24 25Finds out whether each ad platform's conversion data can carry a budget decision, and what to fix first when it can't.26 27## Purpose28 29- One job: check the measurement chain from ad click to CRM stage, per paid platform, and say which platform's data is safe to act on.30- Stage: check. It ends in a verdict with severities.31- It never changes an account, a tag or a CRM setting. It reads, checks and writes the fix list.32- It never passes a check without evidence. A check with no input is `not checked`, never `pass`.33 34## Use when / not35 36| Situation | Use |37| --- | --- |38| A budget, bid or channel decision is about to rest on platform conversions | this skill |39| Platform leads and CRM leads disagree | this skill |40| A form, site, tag manager or CRM change went live | this skill |41| UTMs land in the wrong GA4 channel or in Unassigned | `utm-check` |42| Planning which CRM stages to send back to each platform | `crm-feedback-loop`, after this skill |43| Pipeline by channel for the board | `pipeline-report` |44 45## Inputs46 47| Input | Required | Ways to provide, in order | If missing |48| --- | --- | --- | --- |49| Paid platforms in use | yes | `## Channels` in the profile; the reader's request | ask once |50| Conversion actions per platform: name, source (tag, import, API), what bidding uses, counting, window, status | yes, per platform | a connected ad account, read-only; an export or screenshot of the conversions list; pasted rows | that platform is `NOT CHECKED` |51| Platform lead conversions for one recent period, click-through only | no | connected account; export; pasted figures | skip the reconciliation for that platform |52| CRM leads created in the same period, with source, medium, click ID columns and whether an email exists | no | a connected CRM; a CSV export; pasted rows | skip the reconciliation and the click ID check; coverage `partial` |53| Offline import status: method, last upload, upload frequency, errors in the last 7 days | no | the platform's upload history or diagnostics; the reader's answer | D checks `not checked` |54| Diagnostics: enhanced conversions, server event status, match quality | no | each platform's diagnostics screen | B4 `not checked` |55| Consent setup: banner, consent mode, which regions see it | no | browse the site; a tag debugger output; the reader's answer | C checks `not checked`; open item if the profile's regions need consent |56| CRM stages: names, entry rule, date fields | no | CRM settings; a pasted list | E checks `not checked` |57 58## Profile read59 60From `company-profile.md`: `## Company` (Regions, Sales cycle, Business model), `## Channels` (paid platforms, status, monthly budget), `## Targets` (target cost per lead, the rates a budget decision uses), `## Accounts and data` (CRM, analytics, which ad accounts are connected or export only), and every `## Learnings` entry for `tracking-audit` with status `noted`, `fact` or `accepted`.61 62No profile: ask in one message for the paid platforms with their monthly budgets, the CRM, and the regions the company sells in. Say that `company-profile` saves this next time.63 64## Steps65 661. **Apply learnings.** Read them first. An accepted learning that changes a check or a threshold overrides the default here; name it in the output when it fires.67 682. **Scope the platforms.** List every paid platform with status `active` or `testing`. Order them by monthly budget, largest first: the biggest budget decision gets checked first. A platform with no budget figure goes last and is named in open items.69 703. **Gather the inputs per platform** in the fallback order. Read connected accounts only; never save or change a setting. Record where each input came from.71 724. **Run the checks.** Use the tables below on every platform in scope. Platform screens, field names and limits are in `references/platform-checks.md`: open it at this step. Give each check 1 of 4 results: `pass` (evidence shown), `fail` (with its severity), `not checked` (the input is missing; say which input would check it) or `n/a` (it doesn't apply, such as upload checks when nothing is uploaded).73 74 **A. Conversion definitions**75 76 | ID | Passes when | Severity if not | Why |77 | --- | --- | --- | --- |78 | A1 | At least 1 conversion action is a CRM lead or a later stage (a form that creates a CRM record, or an imported stage) | critical | Bidding has nothing to learn that the CRM agrees with |79 | A2 | What bidding uses is a lead or later event, never a page view, click, scroll, chat open or video view | critical | The platform buys the cheap event, not the lead |80 | A3 | Each real lead is counted once: no tag and GA4 import for the same form both used for bidding; pixel and server events share an event ID | critical | Double counting halves the reported cost per lead |81 | A4 | Lead actions count once per click or person, not every submit | warning | Repeat submits inflate leads |82 | A5 | The conversion window is at least the reader's median days from click to the stage imported, inside the platform's limit | warning | Stages after the window are dropped |83 | A6 | Every live campaign is attached to the conversion it is measured on | warning | Unattached campaigns show 0 and bid blind |84 | A7 | Conversion values, if used, come from the reader's data and say how; no placeholder value such as 1 | warning | Value bidding chases a made-up figure |85 86 **B. Identifiers and matching**87 88 | ID | Passes when | Severity if not | Why |89 | --- | --- | --- | --- |90 | B1 | 80% or more of the platform's CRM leads carry a match key (its click ID or an email) | critical under 50%, warning from 50% to 79% | Imports match only rows with a key; under half, bidding learns from whichever forms happen to keep the ID |91 | B2 | Google: enhanced conversions for leads is on, the tag collects hashed email or phone on the lead form, and the import sends the same hashed data | warning; critical when there is neither a GCLID import nor enhanced conversions for leads | Leads without a stored GCLID can't be matched |92 | B3 | Server events send hashed email plus the platform's click ID where stored, and share an event ID with the pixel | warning | Unmatched or duplicated events |93 | B4 | Each platform's diagnostics show no open errors | warning | Failures there are silent everywhere else |94 95 **C. Consent**96 97 | ID | Passes when | Severity if not | Why |98 | --- | --- | --- | --- |99 | C1 | Where the profile's regions include the EEA, the UK or Switzerland: a consent banner decides before ad tags set cookies or send data, and Google consent mode receives the choice | critical | Data is sent for people who refused, or lost for people who accepted |100 | C2 | Uploads to Google carry the ad user data consent value | warning; critical for EEA traffic | Google's API says uploads without it may not be attributable |101 | C3 | No personal data in URLs (an email in a thank-you page address); user data sent to platforms is SHA-256 hashed where the platform expects hashes | critical | Personal data reaches every tool that reads the URL |102 103 **D. Offline imports**104 105 | ID | Passes when | Severity if not | Why |106 | --- | --- | --- | --- |107 | D1 | Each platform that bids receives at least 1 stage past the lead (MQL, SQL, opportunity or closed-won) | warning | It bids for leads, not pipeline: hand to `crm-feedback-loop` |108 | D2 | Uploads run at least daily, and the gap between uploads never exceeds the platform's event age limit | critical when the gap exceeds the limit; warning when uploads are less than daily | Late events are rejected (Meta and OpenAI: 7 days) |109 | D3 | Upload errors in the last 7 days: none | warning above 0; critical above 10% of rows | Above 1 in 10, the signal is too damaged to read conversion data |110 | D4 | Each imported event carries the date the stage happened, not the upload date | critical | Wrong dates move conversions across days and out of windows |111 112 **E. CRM stage mapping**113 114 | ID | Passes when | Severity if not | Why |115 | --- | --- | --- | --- |116 | E1 | Each lifecycle stage has 1 written entry rule (a field value or an event) | warning | Stages mean different things to sales and marketing |117 | E2 | Each stage records the date it was entered | critical | No stage dates: no imports and no timing |118 | E3 | Stages sent to platforms map 1 to 1 to conversion actions with matching names | warning | Reports and bidding read different events |119 | E4 | New leads with a blank or "offline" source are fewer than the leads of the smallest paid platform in scope | warning | The unknown bucket is bigger than a channel you are judging |120 | E5 | One person is one record before leads are counted or uploaded | warning | Duplicates inflate leads and uploads |121 1225. **Reconcile platform conversions with the CRM.** Run the script with the period's CRM leads and each platform's click-through lead conversions:123 124 ```125 python3 scripts/reconcile.py --crm leads.csv --count google=48 --count linkedin=21 --start 2026-09-01 --end 2026-09-30126 ```127 128 Without Python, count by hand for each platform: the CRM leads created in the period; those carrying the platform's click ID, or a paid source and medium for it; the share of those with a click ID or an email. Then apply the same rules: platform conversions above the CRM's total leads plus 5% is critical (ceiling); conversions with no CRM lead tied to the platform is critical (orphan); a ratio of platform conversions to the platform's CRM leads below 0.7 or above 1.3 is a warning (the band is wide because windows, time zones and dedup rules differ). Never add platform conversions together to count leads: each platform credits itself for shared leads. Say which way you ran it.129 1306. **Grade each platform.**131 132 | Result | Condition (first match wins) |133 | --- | --- |134 | `NOT CHECKED` | No conversion settings for the platform |135 | `FIX FIRST` | 1 or more critical findings |136 | `CHECK` | Warnings only |137 | `TRUSTED` | Every check passed; `not checked` items listed |138 1397. **Write the fix list.** One line per failed check: the fix, the screen or field where it happens, and the role that does it (from `## Channels` owners if named). Order: critical before warning, then by platform budget. Never write a fix that changes a target or a rate.140 1418. **Say what budget decisions can rest on.** Per platform: `safe` when it is TRUSTED, or CHECK with no warning in A, and B1 and the reconciliation were both run and passed; otherwise `not yet`, naming the check that blocks it or the input that would check it. A check that wasn't run never makes a platform safe.142 143## Check and verdict144 145| Verdict | Condition (first match wins) |146| --- | --- |147| `BLOCKED` | No paid platform named, or every platform in scope is `NOT CHECKED` |148| `FAIL` | Any platform with budget is `FIX FIRST` |149| `PASS WITH NOTES` | Warnings only, or a platform is `NOT CHECKED` while others pass |150| `PASS` | Every platform `TRUSTED` |151 152Named stop: `BLOCKED` asks for the missing input (the platform list, or the conversion settings of the largest platform). No other stops.153 154## Learn155 156Append a learning to the profile when:157 158- the reader overrides a severity or a check ("our demo and pricing forms are 2 real leads, so we count every submit"): write the reason as a `proposal`;159- a fix is confirmed later (upload errors gone, match keys up): write a `fact` with the new figure and its source;160- a platform limit in `references/platform-checks.md` turns out to have changed: write a `fact` naming the page and the date read.161 162Example: `- 2026-10-24 | tracking-audit | fact | LinkedIn match keys rose from 41% to 88% after li_fat_id was added to the demo form | Why: CRM export, 2026-10 | Status: noted`163 164## Output165 166```167Verdict: <PASS | PASS WITH NOTES | FAIL | BLOCKED> · Coverage: <complete | partial (what's missing) | blocked> · Reconciliation: <script | by hand | not run>168 169Budget decisions:170- <platform>: <safe | not yet (check ID and why)>171 172| Platform | Check | Result | Severity | Evidence | Fix | Owner |173(platforms by budget, largest first; inside each, critical first; "not checked" rows say what input would check them)174 175Reconciliation: <platform>: <conversions> platform vs <n> CRM leads tied to it (ratio <r>), match keys <n%>; CRM leads in period <n>176Per platform: <platform>: <TRUSTED | CHECK | FIX FIRST | NOT CHECKED>177Fix order: <numbered list>178Learnings applied: <list, or none>179```180 181Then the handoff block.182 183## Hand off184 185```handoff186skill: tracking-audit187version: 1.0.0188verdict: FAIL189coverage: partial (Meta not checked: no access)190for: <company> paid platforms, <period>191outputs:192 platforms: {google: FIX FIRST, linkedin: CHECK, meta: NOT CHECKED}193 critical: 2194 match_key_rate: {google: 0.62, linkedin: 0.91}195 imports_past_lead: {google: none, linkedin: none}196 stage_dates: yes197next: [utm-check, crm-feedback-loop]198open: [Meta conversion settings]199```200 201`crm-feedback-loop` reads `match_key_rate`, `imports_past_lead` and `stage_dates`. `pipeline-report` reads the verdict to say how far platform figures can be trusted beside CRM figures.202 203## Failure modes204 205| Problem | Do this |206| --- | --- |207| Only screenshots, no exports | Check A, C and D from the screenshots; mark B1 and the reconciliation `not checked` |208| The CRM export holds emails | Count whether an email exists; never repeat an address in the output |209| The reader asks whether their setup is legal | Say the skill checks the setup against the platforms' documented rules, not the law, and name the question for their legal adviser |210| Platform and CRM use different time zones | Widen the period by 1 day on each side for the reconciliation and say so |211| The reader asks for a "normal" match rate or conversion rate | Say there is none in this skill; compare against their own last period instead |212| A platform's documented limit differs from `references/platform-checks.md` | Use the platform's current page, cite it with today's date, and write a `fact` learning |213| Google Ads auto-tagging is off | B1 for Google fails: no GCLID reaches the site; the fix is to turn it on |214 215## Influenced by216 217- Google's documentation on enhanced conversions for leads, an upgraded offline import that matches hashed form data to signed-in users: https://support.google.com/google-ads/answer/15713840?hl=en218- LinkedIn's Conversions API documentation, for match keys, the 90-day event limit and campaign association: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api219- SHAKEUP's MarkOps practice: tracking is checked per platform, ordered by budget, and every check needs evidence before it can pass.