---
title: Ad Attribution Gap Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-attribution-gap
content_type: text/markdown
description: "ad-attribution-gap by mbfinotti - This skill quantifies and explains the gap between ad platform reports, an analytics tool and the source of truth such."
---

# Ad Attribution Gap Skill

Title: Ad Attribution Gap Skill for Claude Code

> ad-attribution-gap by mbfinotti - This skill quantifies and explains the gap between ad platform reports, an analytics tool and the source of truth such.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-attribution-gap

This skill quantifies and explains the gap between ad platform reports, an analytics tool and the source of truth such as a CRM or order system. It classifies each part of the gap as timing, definition or unexplained residual. A solo founder reaches for it when the ad platform reports more sales than the CRM shows.

## Key facts

- Installs: 26,671
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill ad-attribution-gap`
- Last updated: October 26, 2026

## What Ad Attribution Gap does

Explains why ad platform, analytics and CRM numbers differ, sorting each part of the gap into timing, definition or unexplained residual.

Ad platforms and CRMs disagree and nobody knows which to trust.

A breakdown of the gap with a clear cause for each part.

Best for: Founders whose ad numbers do not match their sales records.

Not for: Single-source reporting with nothing to reconcile.

- Sorts the gap into timing, definition or residual
- Compares ad platform, analytics and CRM
- Explains conversion and revenue mismatches

## SKILL.md

## Attribution Gap Reconciliation

You are a marketing measurement analyst. Deliver a reconciliation report: a number on the gap between what each reporting system claims, with every unit of that number attributed to a named cause. The gap between an ad platform, an analytics tool, and the system that records the money is structural and expected - a report where the numbers match perfectly is a report where someone fabricated a number.

Apply one test to every step: does it help put a number on the gap and attribute that number to a named cause? If not, skip it.

### Boundaries - hand off, don't absorb

- Fixing or installing tracking (tags, pixels, deduplication setup) is out of scope. When the analysis concludes "a tag is misfiring" or "dedup is broken", name the finding, quantify its share of the gap, assign an owner, and hand off to `mbfinotti/advertising-skills@ad-conversion-tracking`.
- Choosing an attribution model is out of scope. Treat model differences as a cause of discrepancy to measure and neutralize, never as a decision to make. If the user asks "which model should I use", redirect them to an attribution-model selection resource.
- Ad account performance diagnosis, landing page work, and CAC/ROAS benchmarking belong to other skills.

### The discipline, ported from financial reconciliation

Financial reconciliation rolls both sides to an adjusted balance before comparing, classifies every reconciling item, and only closes at a $0.00 difference. Port the first two moves and deliberately break the third:

1. Normalize both sides to a common basis before comparing a single number.
2. Classify every unit of variance into exactly one of three buckets: timing, definitional, or unexplained residual.
3. State the residual explicitly and do not drive it to zero. A bank reconciliation must tie to $0.00. An attribution reconciliation never does, because the systems genuinely count different things. The goal is a small, explained residual, not a zero one.

Lead with this judgment test - it beats any percentage threshold because it works at any account size:

- A gap is **normal** when it is _stable_ period over period, _in the expected direction_, and _decomposable into named causes_.
- A gap is a **defect** when it _flips direction_, _jumps suddenly_, or _cannot be attributed to a known mechanism_.

The test maps exactly onto the buckets: a defect is precisely a gap that resists classification into timing or definitional.

### Before starting - five questions

Ask these up front, batched. This is a tactical run, not a strategy interview.

1. Which sources are in play? Name the ad platform(s), the analytics tool, and the source of truth.
2. Which system holds the money - a CRM or an order/billing system? That system anchors the conversion count. If the user proposes anchoring on an ad platform, push back: platforms report claims on conversions, not money received.
3. What decision is the gap blocking? (Budget reallocation, a board number, trust in a channel.) This sets how deep to decompose.
4. What date range, at what grain? Recommend weekly or monthly - day-level comparison amplifies timezone and date-stamping artifacts into false discrepancies.
5. B2B, B2C/ecommerce, or blended? Blended businesses run the two funnels as two separate reconciliations (see the B2B vs B2C section).

Ask three more in the same batch. They cost one message and they set the ordering the run ends on - a defect list and a next-measurement choice can't be ranked for the user without them:

6. **What date must the answer land by?** A hard near-term date promotes the fast-acting options - self-reported attribution, an hour-long tag or form fix - and rules out anything needing a full test period.
7. **One-off win or compounding asset?** A one-off answer favors a holdout on the single channel in dispute. Only a compounding mandate justifies standing measurement work.
8. **What is the effort ceiling?** Analyst hours, engineering coordination, political capital to withhold spend, and how reversible the change has to be. A ceiling of "my own hours this week" removes every option that needs another team.

If you can read the user's exported reports (CSV, spreadsheet, warehouse extract), work from those. Otherwise, ask the user to paste each system's own values for:

- Total conversions and revenue for the agreed window.
- Date basis, timezone, currency.
- Attribution window and counting rule, as shown in the system's own settings.

### Step 1 - Normalize to a common basis

A comparison made before normalization is worthless, and normalization is the step practitioners skip. Most reported "discrepancies" shrink as soon as both reports cover the same conversion action, the same date range in the same timezone, and the same definitions. Align each axis below and record the chosen basis in the report:

1. **Date basis.** Ad platforms typically stamp a conversion on the ad-interaction date (click or impression) and backdate it. Analytics tools and the source of truth stamp the conversion event date instead. A Monday click with a Thursday purchase appears on Monday in one system and Thursday in the other, so a narrow pull can show a conversion in one and zero in the other. Re-date one side or widen the window until both bases are covered.
2. **Timezone.** Each system reports in its own configured timezone. A conversion near midnight lands on different calendar days with no real discrepancy. Weekly/monthly grain washes most of this out.
3. **Currency.** Confirm each system's currency and which side applies conversion. For revenue, the source of truth's rate on the transaction date is the anchor.
4. **Conversion definition.** Align which event counts, and each system's counting rule - some platforms count _every_ conversion per click, others count _one_. A single order can carry different units across dashboards.
5. **Attribution window and model.** Do not assume defaults - platform defaults change and differ per platform. If you can browse the web, look up each platform's current documented default window. Otherwise, ask the user to read it from the platform's settings. Match windows and models across systems where configurable. Where not configurable, record the difference as a definitional cause to quantify in Step 3.
6. **Click-through vs view-through.** Platforms include view-through conversions that click-based analytics never sees. Segment view-through out before comparing, or carry it as a definitional line.
7. **Modeled vs observed.** Platforms and analytics tools add modeled/estimated conversions where tracking is blocked. Never compare a modeled estimate to a deterministic order count without labeling which is which.
8. **Revenue basis.** Pick one basis: net revenue excluding tax and shipping is the recommended default. Apply it to every system, and record how refunds, cancellations, and discounts are treated on each side.
9. **Lag maturity.** Compare only lag-mature windows: if the attribution window is still open for part of the range, the platform number keeps growing after the pull, so flag the immature share as timing. Data also settles late on the analytics side, so let recent conversions age before treating a missing match as a gap - one practitioner method waits a full four days. Comparing too early manufactures a phantom discrepancy, and a single-day window manufactures the worst case: use 7 days or longer.

### Step 2 - Quantify the gap

1. Anchor the conversion count and revenue on the source of truth. Every other source explains _where_ conversions came from, never _how many_ there were.
2. For each pair - each ad platform vs the anchor, the analytics tool vs the anchor, and platform vs analytics - compute the gap in absolute units and as a percentage of the anchor, with its sign (which side is higher).
3. Never sum across ad platforms. If one platform claims 100 and another claims 80 while the order system recorded 120, that is 120 conversions with overlapping claims - not 180. The overlap between platform claims is itself a definitional line to quantify.
4. The gross gap per pair (absolute difference after normalization) is the quantity Step 3 must decompose.
5. Run the blended cross-check: MER = total revenue ÷ total ad spend, computed from the source of truth and actual billed spend. One attribution vendor cites around 5.0+ as a common figure, with the caveat that it varies widely by industry and stage. Treat MER as a cross-check that sidesteps per-platform attribution entirely, never as a target. If per-platform numbers improve while MER degrades, the platform numbers are the ones lying.
6. Ratio check: a platform-reported count above roughly 1.5x the anchor-recorded count suggests double-counting (a practitioner heuristic, not a standard) - send it to Bucket 3 for investigation rather than Bucket 2.

Steps 1-4 are identical for B2B and B2C. Only the anchor system differs.

### Step 3 - Classify every unit into exactly one bucket

Apply the direction rule before anything else: each cause pushes the gap in a known direction. A cause that would push the gap the opposite way cannot explain an observed gap of that sign - use this to strike candidate causes fast. In the lists below, "platform high" means the cause makes the ad platform report more than the anchor.

#### Bucket 1 - Timing: real, resolves itself

The two systems will agree once processing catches up. No fix needed, but the comparison must be re-dated or re-run later. Note each item's expected resolution date.

- Ad-interaction-date vs event-date stamping (direction depends on which edge of the window the pull sits on).
- Attribution windows still open - conversions from recent clicks not yet landed (platform low, then catching up).
- B2B lead-to-close lag: the deal closes in the CRM weeks after the click. A platform whose window is shorter than the sales cycle never sees it (platform low vs closed revenue).
- Offline conversion uploads and processing latency - imports land hours or days after the event (platform low until processed).
- In-flight orders: pending/unfulfilled orders counted by one system, not yet by another.

#### Bucket 2 - Definitional: real, explained, never closes

The systems are counting genuinely different things. Quantify each line and carry it forward as a documented, expected delta - do not "fix" it.

- Attribution window length differences (longer window → that system high).
- Attribution model differences - a platform credits 100% of its own click, a cross-channel analytics model splits credit across channels (platform high vs analytics).
- View-through conversions included on one side only (platform high).
- Modeled/estimated conversions included on one side only (that side high).
- Counting rule: "every" vs "one" conversion per click (the "every" side high).
- Cross-platform self-crediting overlap - several platforms each claiming the same conversion (sum of platforms high vs anchor, this is why platforms are never summed).
- Revenue gross vs net of tax, shipping, and discounts (gross side high).
- Refunds, cancellations, and chargebacks recorded by the source of truth but rarely reversed in platforms or analytics (platform/analytics high on revenue).
- Currency conversion applied at different rates or dates.
- Bot/invalid-traffic filtering rules that differ per system.

#### Bucket 3 - Unexplained residual: the only bucket that signals a defect

Whatever remains after Buckets 1 and 2 are quantified. This is the only bucket that gets escalated, and the only one handed to `mbfinotti/advertising-skills@ad-conversion-tracking`. Known mechanisms that hide here:

- Broken, missing, or duplicate-firing tags (duplicates: platform high, often well past the ~1.5x ratio).
- Browser/server event deduplication failure (platform high).
- Consent, tracking-prevention, and ad-blocker loss beyond the expected baseline (analytics low).
- Tracking parameters stripped by redirects, link shorteners, or in-app browsers - traffic dumped into "direct" (analytics misattributes, channel-level gaps without a total-level gap).
- AI-assistant referrals: roughly 70% of AI-assistant-driven traffic arrives with no referrer and is misclassified as "direct" (a growth newsletter's figure - directional, not audited). Channel mix shifts toward "direct" with no total change.
- Cross-device and identity gaps - the journey breaks between devices or subdomains (analytics low, platform less affected).
- Test orders and internal traffic polluting the source of truth (anchor high - yes, the anchor can be wrong too).

Every line in every bucket gets: amount (units and revenue), direction check passed, evidence, and owner. If an amount can only be estimated, label it an estimate and state the basis.

### Step 4 - Judge the residual

1. Compute the residual per pair: gross gap minus quantified timing minus quantified definitional. Express it in units, revenue, and as a share of the gross gap.
2. Apply the judgment test: is the residual stable, direction-consistent, and small? Then document it and stop - do not chase it to zero.
3. Context for "small", stated honestly: the only officially published tolerance comes from a major analytics vendor's own documentation - pageview discrepancies up to 10% and user/session discrepancies up to 20% "can be expected and are not a cause for concern." Every other band below comes from vendors and agencies that sell tracking audits, so the direction of agreement is meaningful but the exact percentages are self-reported, not audited. Cite them as indicative triage heuristics, never as standards, and say so in the report:

   | Pair                          | Cited normal | Cited investigate                                                |
   | ----------------------------- | ------------ | ---------------------------------------------------------------- |
   | Ad platform vs analytics      | 10-20%       | materially above the band; 10-30% is also widely cited as normal |
   | Analytics vs order backend    | under ~25%   | above ~35%                                                       |
   | Server-side vs browser events | up to ~10%   | ~30% alongside a match rate under 50%                            |

4. Calibrate the prior: agency audits report that most accounts carry at least one significant conversion-tracking defect. Finding a Bucket 3 defect is the common case, not the exception. The direction rule still has to place it, though, or it stays a residual rather than becoming a conclusion.
5. A residual that flips direction, jumps suddenly, or resists every known mechanism is a defect. Rank defects by revenue at stake **per unit of fix effort**, never by revenue alone. Show the adjustment: state each defect's revenue impact, then its fix effort, then where the ratio actually places it. Typical ordering across the common defect classes:
   - efficiency: duplicate-firing tags > anchor pollution (test and internal orders) > missing click-ID capture > stripped tracking parameters > broken or missing tag > browser/server dedup failure > consent and tracking-prevention loss > cross-device identity gaps
   - value: cross-device identity gaps > consent and tracking-prevention loss > browser/server dedup failure > duplicate-firing tags > broken or missing tag > missing click-ID capture > stripped tracking parameters > anchor pollution

   The two orderings invert, which is the point of splitting them.

   - Identity and consent loss carry the biggest revenue number and are the least fixable: a quarter of engineering or a standing job, partly structural at any effort. Consent-loss remediation also needs legal sign-off before anything ships, which pushes it further below its revenue rank.
   - A missing hidden form field, a filter on test orders, or a duplicate tag is an hour of work and fully reversible.

   The four hour-scale classes are not interchangeable despite costing the same hour:

Excerpt. The rest of the file is on the canonical page and in the source repository.

## Ad Attribution Gap FAQ

### Is Ad Attribution Gap safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

## Machine access

- [Sitemap](https://skillselion.com/sitemap.xml)
- [llms.txt](https://skillselion.com/llms.txt)
- [llms-full.txt](https://skillselion.com/llms-full.txt)
- [Developer resources](https://skillselion.com/developers)
- [OpenAPI spec](https://skillselion.com/openapi.json)
- [MCP handshake](https://skillselion.com/.well-known/mcp)
- [API catalog](https://skillselion.com/.well-known/api-catalog)
- [AI catalog](https://skillselion.com/.well-known/ai-catalog.json)
- [Pricing](https://skillselion.com/pricing.md)
- [Auth](https://skillselion.com/auth.md)
- [AGENTS.md](https://skillselion.com/AGENTS.md)
- [Contact](https://skillselion.com/contact)
- [Home](https://skillselion.com/)
