conversion-value-mapper

# Conversion Value Mapper Defines and QAs the conversion VALUE model behind value-based paid bidding — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — delivered as a value-model spec plus a pre-launch value QA sheet. **Scope line: this skill BUILDS and QAs the *values* the platform bids toward so tROAS/max-conversion-value chases profit, not raw order count; it does NOT verify that the event fires or that UTMs are clean — [conversion-signal-qa](../conversion-signal-qa/SKILL.md) owns the plumbing — and it does NOT score the ROAS `R1`/`R2` vetoes — [ad-account-auditor](../ad-account-auditor/SKILL.md) judges those.** It is a `Return`-dimension prerequisite, not the verdict. It is also **not** the standing cross-platform de-dup / incrementality reconciliation — that is [attribution-reconciler](../../scale/attribution-reconciler/SKILL.md); here you only define the value the platform *receives*, not resolve which platform gets credit for it. ## Quick Start ``` Set up my conversion values so tROAS bids to profit, not revenue. Bid goal: tROAS. Here is my GA4 purchase-value export and my margin / COGS by product-category export: [paste/path]. ``` ``` Build value rules for my non-revenue conversions — assign a proxy value to lead, phone-call, and newsletter-signup so max-conversion-value has something to bid toward. ``` ``` My tROAS optimizes to revenue but our margins vary...