← Back to list
conversion-value-mapper ✓ Security reviewed
Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map m…
⚡ Productivity By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
6.7Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "conversion-value-mapper" skill by following the instructions at https://skill123.me/install/conversion-value-mapper.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/conversion-value-mapper.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 5 KB

About this skill

Overview

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

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: ad/activate/conversion-value-mapper

Evaluation

AI-evaluated 2026-09-03: Explicit net-value formulas, proxy-value derivation rules, Measured/User-provided/Estimated labeling, and a value-vs-count reconciliation step give an unusually rigorous workflow. Niche value-based-bidding audience needing margin/COGS exports; untrusted-data handling, never inventing margins, and ask-before-save keep it safe.

Score breakdown

Quality
7.0
Usability
5.0
Security
8.0
Popularity
7.0