| name | conversion-signal-qa |
| slug | aaron-conversion-signal-qa |
| displayName | Conversion Signal QA · 付费广告转化追踪QA |
| summary | 付费广告转化追踪QA/UTM规范/跨平台去重 |
| description | Use when the user asks to "QA my conversion tracking before launch", "check my UTMs / pixel / event firing", "set up a tracking pre-flight", or "set the dedup rule so Meta and Google stop double-counting"; builds and fixes the measurement plumbing — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — as a pre-flight checklist plus a UTM/event-spec builder. Not for scoring R1/R2 — that is a scored veto in ad-account-auditor; not for account structure — use campaign-architect. 付费广告转化追踪QA/UTM规范/跨平台去重 |
| version | 19.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use before launching or scaling paid campaigns, when the measurement plumbing needs verifying or fixing: conversion events firing, UTM consistency, cross-platform dedup, attribution-window alignment, and offline/iOS-ATT modeled-gap flags. Run it to BUILD the signal pre-flight; run ad-account-auditor to SCORE whether R1/R2 pass. |
| argument-hint | <site/account topic> [platforms] [GA4 conversions + traffic-acquisition export] |
| metadata | {"author":"aaron-he-zhu","version":"19.0.0","discipline":"ad","phase":"activate","geo-relevance":"low","hermes":{"tags":["marketing","ad","activate"],"category":"ad"},"openclaw":{"emoji":"🎯","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Conversion Signal QA
Pre-flight QA of the measurement plumbing behind paid ads — conversion-event firing, UTM hygiene, cross-platform dedup rules, attribution-window alignment, and offline/iOS-ATT modeled-gap flags — delivered as a tracking pre-flight checklist plus a UTM/event-spec builder. Scope line: this skill BUILDS and FIXES the signal pre-flight so the data is trustworthy; it does NOT score the ROAS R1/R2 vetoes — ad-account-auditor judges those as scored red lines. It is the R1/R2 prerequisite, not the verdict. It is also not the standing monthly de-dup / incrementality reconciliation — that is attribution-reconciler. Here you only gate that a dedup rule and aligned attribution windows exist pre-launch; the actual order-ID matching, double-count quantification, and incrementality read happen in attribution-reconciler.
Quick Start
QA my conversion tracking before I scale. Platforms: Google + Meta. Here is my GA4 Conversions export and Traffic-acquisition (source/medium) export: [paste/path].
Build me a UTM scheme and event spec for this campaign, then give me a pre-launch tracking checklist I can run myself.
My Meta and Google numbers don't match my GA4 orders — find the dedup, attribution-window, and UTM problems. [GA4 exports attached]
Skill Contract
Expected output: a tracking pre-flight checklist (pass/fail/needs-input per item), a UTM/event-spec builder block (naming convention + the conversion-event spec table), cross-platform dedup + attribution-window alignment notes, offline/iOS-ATT modeled-gap flags, and the standard handoff summary.
- Reads: site/account topic and platforms; the user's own GA4 Conversions report export and Traffic-acquisition (source/medium) export; one manual test conversion the user performs (NOT pixel/tag-manager API access).
- Writes: a user-facing pre-flight report plus a reusable UTM/event spec to
memory/ad/conversion-signal-qa/.
- Promotes: signal-integrity blockers (events not firing, UTM gaps, dedup/window mismatch, missing test conversion) and the UTM/event spec to
memory/hot-cache.md and memory/open-loops.md.
- Done when: every pre-flight item is marked pass/fail/needs-input from evidence; the UTM scheme + event spec are written; dedup rules and attribution-window alignment are stated per platform; offline/iOS-ATT modeled gaps are flagged (never silently passed); and the report says the plumbing is launch-ready or names exactly what to fix.
