---
title: Ad Conversion Tracking Skill for Claude Code
canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-conversion-tracking
content_type: text/markdown
description: ad-conversion-tracking by mbfinotti - This skill verifies that conversion events are set up correctly before a paid campaign launches.
---

# Ad Conversion Tracking Skill

Title: Ad Conversion Tracking Skill for Claude Code

> ad-conversion-tracking by mbfinotti - This skill verifies that conversion events are set up correctly before a paid campaign launches.

Canonical: https://skillselion.com/skills/mbfinotti/advertising-skills/ad-conversion-tracking

This skill verifies that conversion events are set up correctly before a paid campaign launches. It covers tag debugging, test conversion tracing, browser and server event deduplication including Conversions API setups, value and currency checks, and consent handling. It ends in a go or no-go decision. A solo founder reaches for it before spending money on ads that depend on conversion data.

## Key facts

- Installs: 26,732
- GitHub stars: 2
- Author: mbfinotti
- Repository: mbfinotti/advertising-skills
- Works in Grok Bot: yes
- Install command: `npx skills add https://github.com/mbfinotti/advertising-skills --skill ad-conversion-tracking`
- Last updated: October 26, 2026

## What Ad Conversion Tracking does

Checks that ad conversion events fire once, carry the right value and are deduplicated before a campaign launches.

Ads spend against broken or duplicate conversion data.

A verified tracking setup and a clear launch decision.

Best for: Founders about to launch paid campaigns on tracked conversions.

Not for: Campaigns that do not use conversion tracking.

- Tag debugging and test conversion tracing
- Browser and server event deduplication
- Go or no-go decision on tracking

## SKILL.md

## Conversion Tracking

Verify that conversion tracking actually measures reality before a single dollar of campaign budget spends.

- **The anti-pattern this skill exists to prevent:** teams treat tracking as a launch-checklist checkbox, tick it off from a settings screenshot, and discover it was broken only once the spend report stops making sense. 70-80% of B2B SaaS search accounts audited by GrowthSpree carry at least one significant conversion tracking issue.
- **The governing principle:** bad conversion data does not merely misreport, it actively trains the bidding algorithm to find the wrong people - "if your tracking is inaccurate, every optimisation decision made by the platform will be based on incorrect data" (PPC Hero).

The output is a verification report with per-check evidence, ending in an explicit GO / NO-GO decision with a named approver.

### Scope and handoffs

This skill verifies; it never implements. It produces the checklist, walks the evidence, and issues the verdict - writing or installing tracking code belongs to whoever owns implementation (identified in the Interview). Adjacent ground goes to siblings:

- Reconciling cross-platform numbers after launch → `mbfinotti/advertising-skills@ad-attribution-gap`.
- Account-level performance root-cause diagnosis → `mbfinotti/advertising-skills@ad-account-diagnostic` (it hands tracking FAILs back here).
- Landing-page conversion-rate review → `mbfinotti/advertising-skills@paid-landing-page-audit`.
- Ongoing creative decay monitoring → `mbfinotti/advertising-skills@ad-creative-fatigue`.

### Interview

Ask one question at a time; skip anything already known or visible in the setup. This is a tactical pass, not an interview - keep it brief.

1. Which platform(s) will the campaign run on?
2. Funnel type: B2B lead gen, B2C ecommerce, or both?
3. Do server-side events run alongside the browser pixel/tag, or browser only?
4. Who owns implementation - you, a dev team, an agency? (Fixes get addressed to them.)
5. Is a consent banner live, and does traffic include a consent-regulated region?
6. Budget behind this launch? (Sets how much is at risk behind the gate.)
7. Is the launch date hard or movable? A hard date promotes the near-zero-effort settings and trigger fixes and pushes the click-identifier chain past launch as a risk-accepted item; a movable date lets the whole defect batch ship in one release and relearn once.
8. One-off clearance for this campaign, or a tracking setup you intend to trust for quarters? Compounding intent promotes the click-identifier chain and the shared event ID - they pay every future campaign; one-off intent promotes only the checks that clear this launch.
9. Effort ceiling before launch: your own hours in a tag manager, dev and CRM coordination, or a legal sign-off too? No dev access caps the fix list at settings and tag-manager work, and everything below that line is deleted from the list by name in the report, with the measurement it costs and who accepted the loss - never silently dropped and never left ranked last.

Answers 7-9 re-rank the fix ordering in the Defect checklist. Record them - the report has to say which defects were deferred and on whose authority.

### Evidence gate

Never issue a GO verdict from configuration screenshots alone - a settings page that looks right, or even a tag firing green in a debugger, is not proof of accurate measurement. A GO requires at least one real test conversion traced end to end:

1. Action performed.
2. Payload inspected.
3. Event received in the platform UI with correct value and currency.
4. Deduplicated.
5. Test data excluded.

One named exception: a brand-new property with no traffic yet cannot show a platform-UI conversion within the verification session (events can take hours to appear, and a fresh conversion action starts in a waiting status). It may receive a **provisional PASS, labelled as such**, on the strength of debug-mode evidence plus a correct payload - with a mandatory re-verification the moment the first live conversions land.

### The verification sequence

Nine steps, fixed order. Each step's evidence is only readable once the steps before it hold:

- The platform UI cannot be judged until what the tag actually sent is known.
- You cannot judge deduplication until events arrive from both sources.
- Test-data exclusion must exist before the soak period generates data - exclusion filters are not retroactive.

Do not rank these steps by efficiency, and do not reorder them to front-load the cheap ones: the sequence is a dependency chain, so a value-per-effort ordering here would be false precision. Efficiency ordering belongs to the fix list this sequence produces (Defect checklist), not to the sequence itself.

Record per-step evidence as you go.

1. **Settings and conversion-action configuration.** Confirm the primary conversion designation matches the business goal - revenue-relevant actions primary, page views and micro-actions secondary and excluded from bidding. Rawsoft found an account with 13 primary conversion actions of which only 4 were business outcomes, so smart bidding optimized against 1.5M+ monthly noise conversions. For lead gen, confirm count-once (not count-every) per click. _Evidence: list of primary actions, each mapped to a business outcome; counting method per action._
2. **Enter tag debug / preview mode.** Use the tag manager's preview mode and the platform's test-event or tag-inspection tool. _Evidence: the conversion tag visible and armed on the conversion page, firing on the intended trigger only._
3. **Perform a real test conversion end to end.** Walk the exact user journey a paid click takes - land with the click identifier in the URL, accept (and separately reject) the consent banner, complete the action. B2C: place a real low-value test order (near-zero discount code, or refund it later). B2B: submit a test lead with a unique QA value and confirm it lands in the CRM record. _Evidence: the test order/lead ID, and the identifier it carries._
4. **Inspect the event payload.** In the browser's network inspector or the tag debug tool, read the actual request: correct event name, value, currency, a per-conversion event ID, the click identifier, and hashed identifiers where used. _Evidence: the payload fields, copied into the report._
5. **Confirm the event in the platform UI.** The test event appears in the platform's event manager, marked browser or server, and the conversion action shows a healthy recording status. Any primary action in a misconfigured or no-recent-conversions status is an automatic NO-GO. Allow a few hours of reporting lag before concluding an event is missing. _Evidence: status per primary action; the test event visible with correct value and currency._
6. **Verify deduplication** (section below) whenever browser and server events both run. _Evidence: one counted conversion for the test action; dedup rate._
7. **Exclude and clean the test data** (section below). _Evidence: filter state active, test conversion retracted, test order refunded/removed._
8. **Soak.** Let real signals accumulate for a few days before scaling judgment - practitioners confirm the conversion has been reporting signals for a few days so the platform understands the goal (Pearmill); reconciliation against backend or CRM should wait roughly 4 days for data to settle (Enalitica). _Evidence: daily counts trending, gaps within thresholds (Objective section)._
9. **Document and sign off.** Fill the output-shape report, name the approver, date it, and issue GO / NO-GO. Launch checklists that skip an explicit approval field get skipped under launch pressure (Marketing Machine's template carries a GO/NO-GO block with approver and date). _Evidence: the completed report itself._

### Deduplication check

When a conversion is sent from both the browser tag and a server-side endpoint, the platform needs a shared key to count it once. Three conditions must hold (Analyzify):

- A **shared, per-conversion event ID** (an order ID works well) sent identically by both sources.
- **Matching event names** (exact, including casing).
- **Timestamps within the platform's matching window** - ideally seconds apart.

Failure modes to check for:

- The server generates a different event ID, or omits it entirely - the platform cannot match, and every conversion counts twice.
- A new event ID generated per page load instead of per conversion - a refresh mints a "new" conversion.
- Event-name casing or naming mismatch between the two sources.
- Timestamp drift pushing the pair outside the matching window.

Name the wrong fix explicitly, because it is the tempting one: **deleting the server event to stop double-counting is exactly backwards** - it silently discards the more resilient signal source. The fix is always the shared event ID.

Three confirmations exist, and they are not worth equal time:

```
efficiency (do first) : dedup rate > browser-vs-server count comparison > match-quality score
effort                : browser-vs-server count comparison > dedup rate == match-quality score
value for this goal   : dedup rate > browser-vs-server count comparison > match-quality score
```

Effort and value disagree on the match-quality score. It ties the dedup rate at the bottom of the effort axis: both are a single number the event manager has already computed and shows on one screen, nothing to pull, nothing to align. That is also why it ranks last on efficiency despite costing nothing: it is the least useful of the three here.

1. **Dedup rate**, in the platform's event manager - one screen, near-zero effort, and it answers the question directly. Healthy setups show ~90%+ of browser events deduplicated (TAGGRS shows a monitored setup at 95.35% browser / 100% server). Start here every time.
2. **Browser vs server event counts** for the same action - roughly an hour of pulling and aligning two reports. Run it when the dedup rate looks wrong, is unavailable, or when the test action counted twice; when the rate is healthy and the test action counted once, this is confirmation rather than discovery, so it can wait for the soak.
3. **Match-quality score** - read it as a **completeness** signal, never an accuracy signal. It rates how well-formed and matchable the event data is, not whether the conversions are real (AnyTrack), so it never confirms deduplication on its own. Record it; do not spend the launch window improving it.

Re-rank this against the account: where the platform's event manager hides the dedup rate, or where an analyst already maintains a browser-vs-server count report, step 2 moves to the front.

### Defect checklist

The defects that waste spend, with the check that catches each.

Impact says how badly the defect corrupts measurement:

- **Critical** blocks launch.
- **High** blocks unless explicitly risk-accepted in the report.
- **Medium** goes on the fix list.

Fix effort says what clearing it costs the reader in hours, coordination and reversibility.

**Rows are ordered by efficiency - impact bought per unit of fix effort - so the top row is the one to fix first, not the cheapest one and not the most critical one.**

| Defect                                                                           | Check that catches it                                                            | Impact                           | Fix effort                                                                             |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | -------------------------------- | -------------------------------------------------------------------------------------- |
| Noise actions designated primary                                                 | Settings review (step 1)                                                         | Critical                         | Near-zero - a designation toggle, reversible in a click                                |
| Container works in preview but was never published                               | Test the live site outside preview mode                                          | Critical                         | Near-zero - publish the container                                                      |
| Count-every set on a lead form                                                   | Settings review (step 1)                                                         | High                             | Near-zero - one counting setting per action                                            |
| Internal/QA traffic counted as conversions                                       | Filter state check (Test-data exclusion section)                                 | Medium                           | Near-zero - flip the filter from testing to active                                     |
| Tag fires on page load / all-pages trigger, not the completed action             | In debug mode, load the page without converting                                  | Critical                         | An hour - retrigger in the tag manager, no dev                                         |
| Fires on button click, not confirmed success                                     | Abandon a submit mid-way; check nothing fired                                    | High                             | An hour - same, plus a success signal to bind to                                       |
| Bot/spam form fills counted - and taught to the algorithm                        | Spam protection on forms; inspect lead quality in the soak                       | Medium                           | An hour - form-level protection, self-service                                          |
| Confirmation page refires on refresh/back (no unique transaction ID)             | Refresh the confirmation page after the test conversion; look for a second event | Critical                         | An hour if the order ID already reaches the tag; a week of dev if it does not          |
| Single-page-app route change refires the tag                                     | Navigate between virtual pages in debug mode                                     | High                             | An hour if a tag-manager rule fixes it; a week if the app must emit its own event      |
| Missing/hard-coded value, wrong or missing currency                              | Payload inspection (step 4)                                                      | Critical for value-based bidding | An hour if the value sits in the data layer; a week of dev if it must be exposed first |
| Browser + server both counted (no shared event ID)                               | Deduplication check                                                              | Critical                         | A week - dev coordination across both senders, and a redeploy to reverse               |
| Consent banner blocks the tag entirely, or consent state never reaches it        | Run the test conversion on both the accept and the reject path                   | High                             | A week, plus a legal sign-off - see compliance cost below                              |
| Click identifier stripped by redirect chain, or truncated by browser cookie caps | Inspect the landing URL and the persisted identifier at conversion time          | High                             | A week to a quarter - touches redirects, storage and every funnel step                 |
| Cross-domain checkout drops identity mid-journey                                 | Walk the full cross-domain journey in debug mode                                 | High                             | A week to a quarter - coordination across two domain owners                            |

Two axes disagree with that order, so state them separately:

```

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

## Ad Conversion Tracking FAQ

### Is Ad Conversion Tracking safe to install?

skills.sh reports 3 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/)
