conversion-signal-qa

# 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](../ad-account-auditor/SKILL.md) 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](../../scale/attribution-reconciler/SKILL.md). 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 pe...