conversion-value-mapper

name	conversion-value-mapper
slug	aaron-conversion-value-mapper
displayName	Conversion Value Mapper · 付费广告转化价值建模
summary	付费广告转化价值建模/利润出价/价值规则QA
description	Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — 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 — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA
version	19.2.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 value-based (tROAS / max-conversion-value) bidding, when the conversion VALUE model needs defining or checking: per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count reconciliation. Run it to BUILD the value model so tROAS chases profit; run conversion-signal-qa first to confirm the events even fire, and ad-account-auditor after to SCORE whether R1/R2 pass.
argument-hint	<account/offer topic> [bid goal: tROAS|max-value] [GA4 purchase-value + margin/COGS export]
metadata	{"author":"aaron-he-zhu","version":"19.2.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 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 owns the plumbing — and it does NOT score the ROAS R1/R2 vetoes — ad-account-auditor 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; 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 20-70% by SKU — map net margin onto the conversion value and QA it before I relaunch. [GA4 + COGS export attached]

Skill Contract

Expected output: a conversion value-model spec (per-conversion value + net-value/margin adjustment + rule logic), a static-vs-dynamic value-rule decision, proxy values for non-revenue actions with a stated derivation, a value-vs-count reconciliation (does the value the platform receives track the profit the business books?), and the standard handoff summary.

• Reads: account/offer topic and bid goal (tROAS vs max-conversion-value); the user's own GA4 purchase-value / ecommerce revenue export and a margin or COGS breakdown (by SKU, category, or blended); optional lead→sale close-rate and average-order-value inputs for proxy-value derivation.
• Writes: a user-facing value-model spec + value QA sheet to memory/ad/conversion-value-mapper/.