Approval rate vs conversion rate
A practical guide to separating raw conversion rate from approved conversion quality before you scale advertiser spend or publisher volume.
Approval rate vs conversion rate in brief
Conversion rate tells you how often users complete the tracked action. Approval rate tells you how often those completed actions remain commercially valid after quality, policy, or fraud review.
If you scale on conversion rate alone, you can grow the wrong traffic. If you scale on approval rate alone, you can miss early funnel friction. The right move is to read both together and decide where the leak happens.
Who this is for
- Advertisers deciding whether a source is safe to scale.
- Publisher managers comparing traffic quality across placements or geos.
- Ops and technical teams reconciling accepted, rejected, and approved outcomes.
Definition
Conversion rate is the percentage of users or clicks that complete the tracked action.
Approval rate is the percentage of accepted or submitted conversions that survive deeper review and remain valid for payout or revenue accounting.
In KiwiWall workflows, conversion rate usually answers “did the user do the thing?” Approval rate answers “did that action still qualify after validation?”
Decision table
| Pattern | What it usually means | First action | Scaling decision |
|---|---|---|---|
| High conversion, high approval | Funnel and traffic quality both look healthy | Review caps and pacing | Eligible for controlled scale |
| High conversion, low approval | Weak downstream quality or fraud/policy issues | Review rejection reasons and source mix | Hold or reduce |
| Low conversion, high approval | Good traffic quality but weak front-end or offer fit | Review creative, placement, or event friction | Tune before scaling |
| Low conversion, low approval | Both funnel and quality are weak | Rebuild source and tracking baseline | Do not scale |
How it works
Step 1: Use one shared event definition
Make sure every team agrees on what counts as a conversion and what counts as an approval. If one dashboard calls accepted a win while another waits for approved, your reporting will drift.
Step 2: Review the same source through both lenses
For every source, placement, or geo:
- check raw conversion rate,
- check approval rate,
- compare rejection reasons,
- confirm postback latency is not hiding delayed approvals.
Step 3: Diagnose the gap
If conversion rate is healthy but approval rate falls, the problem is usually downstream:
- poor lead quality,
- invalid traffic,
- policy mismatch,
- or missing tracking fields.
If approval rate is healthy but conversion rate is weak, the problem is usually earlier:
- weak offer fit,
- wrong placement,
- slow funnel,
- or unclear user intent.
Step 4: Decide which metric leads the next action
Use conversion rate to improve funnel efficiency. Use approval rate to protect commercial quality. In most advertiser-scale decisions, approval rate should block spend increases when it trends down.
The practical rule is simple: conversion rate tells you whether users are reaching the event, while approval rate tells you whether that event still deserves budget. When the two metrics disagree, investigate the gap before changing caps or adding volume.
Example
A campaign in one geo shows a 12% conversion rate and a 38% approval rate. That is not a scaling win. The tracked action is happening, but too much of that activity is failing later validation.
Another source shows an 8% conversion rate and an 82% approval rate. That source may deserve front-end optimization or higher-quality placement before budget cuts, because the commercial quality is already stronger.
Common mistakes
-
Treating conversion rate as final quality Fix: review approval and rejection beside it.
-
Comparing different windows Fix: use the same date range for both metrics.
-
Ignoring latency Fix: separate delayed approvals from true rejections.
-
Reading approval without source context Fix: review by publisher, placement, geo, or offer segment.
Checklist
- Conversion and approval definitions are shared across teams.
- Both metrics use the same time window and source grouping.
- Rejection reasons are available for low-approval sources.
- Postback latency is checked before assuming quality failure.
- Spend increases are blocked when approval quality trends down.
- Weekly reviews record which metric drove the decision.
FAQ
Which metric should block scaling first?
Approval rate, because it is closer to commercial quality.
Can a low conversion rate still be acceptable?
Yes, if approval quality is strong and the economics work after optimization.
Can a high conversion rate be misleading?
Yes. It can hide low-intent leads, fraud, invalid postbacks, or loose approval rules downstream.
Should publishers care about approval rate?
Yes. It is one of the best signals for whether traffic quality is sustainable.
Conversion link
Use this comparison with Advertiser performance scaling, Performance campaign quality scorecard, and CPA vs CPL vs CPI. If the source passes both quality lenses, continue to Advertisers.
Evidence notes
- Strategy source:
docs/content-silo-plan.mdand the synced Obsidian note dated2026-06-18. - This page is intentionally decision-led because it is a comparison page, not a glossary exception.