Conversion Signal QA
Use when the user asks to "QA my conversion tracking before launch", "check my UTMs /...
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill conversion-signal-qa -g -a claude-code -y- Repository
- aaron-he-zhu/aaron-marketing-skills3k
- Category
- Testing
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,995 tokens
- Runs scripts
- No, instructions only
What it does
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规范/跨平台去重
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), field-level evidence observations, a versioned UTM/event-spec binding (naming convention + conversion-event table + exact ref/hash), cross-platform dedup + attribution-window alignment notes, offline/iOS-ATT modeled-gap flags, and the standard handoff summary.
