agentleFS
F0rger123F0rger123/claude-meta-ads-god-mode/skills/ads-tracking/SKILL.md

ads-tracking

Skill1 starsChanged 23 days agoMITView on GitHub

Conversion tracking and attribution diagnostics - Meta Pixel, Conversions API, datasets, Event Match Quality, Google Ads conversion actions, GA4 key events, GTM, UTM parameters, CRM attribution and landing-page events. Detects missing tracking, duplicates, wrong events, broken UTMs, missing conversion actions, wrong destinations, account mismatches and attribution gaps. Use for "is tracking working", "pixel", "CAPI", "conversions look wrong", "GA4 doesn't match".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    UTMs: - every ad has utm_source/medium/campaign (+content).

    line 19
  2. Distinctive:

    Attribution gaps: - no CRM feedback (offline conversions/CAPI for qualified leads).

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ads tracking

Tracking is checked before any performance conclusion. All diagnostics are read-only; every fix that changes events, conversion actions, datasets, tags or attribution settings is a tracking action: adsgm plan tracking ..., approval required, never destructive without approval.

Platform detail: Meta - skills/meta-ads/references/attribution-and-signals.md; Google - skills/google-ads/references/conversion-tracking.md; concepts - references/attribution.md.

Diagnostic sequence

  1. Inventory - from the profile and platforms: Meta dataset ids + events + custom conversions; Google conversion actions (primary?); GA4 key events (run_report on eventName with keyEvents); GTM container (if accessible); landing pages and their forms/phone numbers.
  2. Fire check - for each conversion path (form, call, booking): is there a Meta event, a Google conversion, a GA4 key event? Open the landing page in the browser and inspect network requests on submit when needed (test submissions only with the user's OK; never submit personal data).
  3. Volume reconciliation - same 14-30 days, by day: CRM leads vs Meta reported vs Google reported vs GA4 key events. Explain gaps (attribution windows, view-through, cross-device, consent, duplicates).
  4. Duplicates - pixel + CAPI without shared event_id; Google tag + GA4 import both primary; thank-you page reloads; multiple tags in GTM.
  5. Wrong event / destination - ad set optimizing for PageView/ViewContent; conversion action "page view" primary; ads sending to a URL without the tag; final URL redirects dropping parameters.
  6. UTMs - every ad has utm_source/medium/campaign (+content); consistent naming; no spaces/uppercase chaos; GA4 shows the sessions under the expected source/medium.
  7. Account mismatch - pixel/dataset/conversion action owned by another business or account; GA4 property linked to the wrong Google Ads customer.
  8. Attribution gaps - no CRM feedback (offline conversions/CAPI for qualified leads); calls not tracked; Jan-2026 Meta view-window removal affecting comparisons.

Output

Table: issue · evidence · impact on optimization/reporting · severity · fix · who does it (Claude via tool with approval / developer / client) · approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.