conversion-value-mapper
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 d
npx skills add aaron-he-zhu/aaron-marketing-skills --skill conversion-value-mapper --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 an
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the conversion-value-mapper skill do?
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 d
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill conversion-value-mapper --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
