Break-even ROAS: prospecting vs retargeting
Last updated: 2026-07-31
Written and reviewed by Seller Profit Guard Editorial Team.
Prospecting and retargeting share a ROAS boundary only when retained revenue, conversion value, product mix, costs, expected loss, target, and attribution conventions match. They usually differ in audience eligibility, lookback, overlap, frequency, conversion delay, order mix, and measured spend, so compare those fields explicitly.
Hold economics constant first
Use identical retained revenue, conversion value, cost, fee, expected loss, and target fields. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
This isolates traffic mechanics from unit-economics drivers. Review point 1 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Describe prospecting
Record broad or acquisition audience, exclusions, objective, creative set, product coverage, window, and delay. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
Prospecting is not automatically incremental. Review point 2 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Describe retargeting
Record eligibility event, lookback, suppression, frequency, product coverage, window, and delay. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
Retargeting is not automatically cheaper or more profitable. Review point 3 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Compare attribution
Use the same conversion action and value convention or label the comparison noncomparable. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
Different windows can claim different value from the same order. Review point 4 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Compare product mix
Measure retained contribution for products actually sold in each scenario. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
Higher reported ROAS can coexist with a weaker product mix. Review point 5 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Compare spend and headroom
Place planned or realized spend against each scenario's target-safe ceiling. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
Traffic labels do not excuse target overruns. Review point 6 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Choose with separate gates
Require valid order economics, campaign control, attribution maturity, and business objective evidence. Add the result to the traffic-scenario comparison matrix with its cohort alias, source version, evidence date, owner, currency, window, denominator, scope, and affected output. This makes a like-for-like channel decision reproducible instead of dependent on memory or an unversioned dashboard.
No single ratio proves incrementality or the correct budget allocation. Review point 7 must distinguish observed data, explicit assumptions, unresolved evidence, and decisions outside the calculator. Keep retained revenue, reported conversion value, spend, variable costs, attribution, refunds, delay, target, and maturity separate.
Reconcile the reported-value gap and operating headroom
Keep ad-platform conversion value and retained seller revenue as separate confirmed fields. Calculate their absolute difference as a percentage of retained revenue, compare it with a dated seller-entered maximum, and investigate value rules, attribution, taxes, shipping, refunds, duplicate treatment, timing, or cohort mismatch before interpreting the ratio.
Also divide target-safe spend headroom by the positive target-safe spend ceiling. A plan below the ceiling can still route to Review when its normalized headroom is below the seller's minimum. The example thresholds of 25% maximum value gap and 10% minimum spend headroom are owner-controlled policies, not universal benchmarks or platform rules.
Protect advertising and customer data
Use aggregate cohort values, product-profile aliases, synthetic examples, and redacted evidence pointers. Keep buyer names, emails, addresses, messages, order IDs, click identifiers, audience membership, payments, refunds, raw exports, credentials, tokens, and OAuth material in authorized systems with access and retention controls.
Public content needs only declared model fields, non-sensitive scenario labels, validation state, and aggregate outputs. Do not place private evidence in URLs, screenshots, image metadata, schema, console output, analytics dimensions, issue reports, generators, or downloadable examples.
Keep reporting states separate
Track planned, configured, served, clicked, viewed, attributed, converted, charged, paid, cancelled, refunded, returned, recovered, adjusted, billed, reconciled, and closed as distinct states. A later state can change value or retained revenue, so never backfill it into an earlier snapshot without a dated correction.
Tie value, spend, fees, refunds, reimbursements, and expected loss to source state and maturity. Pending, estimated, approved, posted, settled, failed, reversed, disputed, waived, and expired values are not interchangeable.
Test audience overlap
Identify value claimed by both scenarios without exposing user identities. Deep review 1 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the traffic-scenario comparison matrix. Retain counterexamples even when they do not support the preferred campaign decision.
Compare the result with a like-for-like channel decision, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.
Test branded demand
Separate existing intent from acquisition evidence. Deep review 2 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the traffic-scenario comparison matrix. Retain counterexamples even when they do not support the preferred campaign decision.
Compare the result with a like-for-like channel decision, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.
Test frequency changes
Record saturation as an operational signal, not a cost rewrite. Deep review 3 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the traffic-scenario comparison matrix. Retain counterexamples even when they do not support the preferred campaign decision.
Compare the result with a like-for-like channel decision, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.
Test delayed conversion
Compare mature windows before declaring a winner. Deep review 4 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the traffic-scenario comparison matrix. Retain counterexamples even when they do not support the preferred campaign decision.
Compare the result with a like-for-like channel decision, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.
Test same-product subsets
Use a stable SKU mix to isolate traffic effects. Deep review 5 stores the tested input, source state, numeric delta, authority boundary, reviewer, expiry, correction condition, and next action in the traffic-scenario comparison matrix. Retain counterexamples even when they do not support the preferred campaign decision.
Compare the result with a like-for-like channel decision, not a generic benchmark or another cohort at a different grain. Explain which single driver moved, which fields stayed constant, what remains unknown, and whether the response is collect, reconcile, stress, review, observe, correct, pause, release, or restore.
Hold economics constant first: verification drill
Recreate “Hold economics constant first” from a clean synthetic cohort instead of copying the primary example. Use identical retained revenue, conversion value, cost, fee, expected loss, and target fields. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the traffic-scenario comparison matrix.
This isolates traffic mechanics from unit-economics drivers. Drill 1 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a like-for-like channel decision.
Describe prospecting: verification drill
Recreate “Describe prospecting” from a clean synthetic cohort instead of copying the primary example. Record broad or acquisition audience, exclusions, objective, creative set, product coverage, window, and delay. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the traffic-scenario comparison matrix.
Prospecting is not automatically incremental. Drill 2 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a like-for-like channel decision.
Describe retargeting: verification drill
Recreate “Describe retargeting” from a clean synthetic cohort instead of copying the primary example. Record eligibility event, lookback, suppression, frequency, product coverage, window, and delay. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the traffic-scenario comparison matrix.
Retargeting is not automatically cheaper or more profitable. Drill 3 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a like-for-like channel decision.
Compare attribution: verification drill
Recreate “Compare attribution” from a clean synthetic cohort instead of copying the primary example. Use the same conversion action and value convention or label the comparison noncomparable. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the traffic-scenario comparison matrix.
Different windows can claim different value from the same order. Drill 4 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a like-for-like channel decision.
Compare product mix: verification drill
Recreate “Compare product mix” from a clean synthetic cohort instead of copying the primary example. Measure retained contribution for products actually sold in each scenario. Change one driver, retain all other fields, calculate the before-and-after difference, and attach source state and expected output to the traffic-scenario comparison matrix.
Higher reported ROAS can coexist with a weaker product mix. Drill 5 includes a supported case, broken case, late-evidence case, and correction case. Explain why each path produces Block, Review, Ready, no spend room, changed headroom, or a revised threshold for this specific a like-for-like channel decision.
Sources and further reading
- Seller Profit Guard methodology: Contribution equations, evidence versions, privacy, correction, release, and rollback.
- Seller Profit Guard data privacy: Local-first boundaries for customer, order, advertising, payment, refund, audience, and raw-record data.
- Google Ads Help: Conversion value per cost definition: Official reporting formula: conversion value divided by cost.
- Google Ads Help: About Target ROAS bidding: Official definition of Target ROAS as an average conversion-value-per-cost objective and guidance on conversion-delay evaluation.
- Google Ads Help: About conversion values: Official context for conversion values, reporting, and value-based bidding.
- Google Ads Help: Data exclusions: Official limits for conversion-tracking data exclusions; exclusions apply to click periods and do not alter reporting.
Related Seller Profit Guard tools
- Break-Even ROAS Calculator: Run the browser-local retained-contribution and ROAS calculation.
- Break-Even ROAS and Return-Loss Guide: Review the existing nine-cost model and return-loss example.
- Etsy Ads Break-Even Calculator: Use the Etsy-specific fee and campaign model when that scope fits.
- Contribution Margin Calculator: Reconstruct retained contribution before advertising.
- Maximum Discount Calculator: Keep merchandise promotion headroom separate from paid-media headroom.
- Methodology: Review evidence, privacy, calculation, correction, release, and rollback.
- Data Privacy: Protect buyer, order, ad-platform, audience, payment, refund, and credential data.
- Break-Even ROAS Formula and Inputs: Derive break-even and target ROAS from retained revenue, conversion value, variable order costs, expected loss, contribution target, and ad spend.
- Break-Even ROAS Prospecting Example: Follow a USD 100 prospecting cohort through retained revenue, cost layers, contribution before ads, spend ceilings, ROAS thresholds, and headroom.
- Break-Even ROAS for Retargeting: Model a retargeting cohort without reusing prospecting attribution, audience, conversion value, product mix, or spend assumptions.
- Break-Even ROAS Calculation Mistakes: Fix numerator, denominator, attribution, fee, refund, return-loss, product-mix, timing, target, and false-profit errors before using ROAS.
- Break-Even ROAS Evidence Sources: Map every ROAS input to advertising reports, retained-order records, cost libraries, fee statements, return cohorts, target policy, and delay evidence.
- Set a Safe ROAS Decision Threshold: Separate break-even, target, stress, warning, and stop thresholds while preserving attribution uncertainty and seller governance.
- Weekly Break-Even ROAS Review Cycle: Run a repeatable ROAS review from source refresh and cohort closure through calculation, approval, observation, correction, and rollback.
- Interpret Break-Even ROAS Results: Read contribution, spend ceilings, break-even ROAS, target ROAS, planned ROAS, post-ad margin, and headroom without false precision.
- Break-Even ROAS Audit Checklist: Audit cohort scope, values, costs, attribution, delays, formulas, fixtures, privacy, release evidence, corrections, and rollback in one log.
Next step: Open Seller Profit Guard.
This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.