Performance-Based Pricing
By the AdFlint research team · Last reviewed July 2026
Ties compensation to results such as leads, sales, or revenue, so the manager is paid on outcomes rather than on time or budget.
Payment tied to agreed outcomes, such as cost per qualified lead, a share of tracked revenue, or bonuses at defined targets, often with a small base fee. It appeals when you want risk shared and your tracking is clean. The hard part is attribution: both sides must agree in advance which conversions count, whose data is authoritative, and how refunds and offline sales are handled.
Key takeaways
- Define exactly which conversions count, and which are excluded such as refunds or existing customers, in writing before the campaign launches.
- Anchor the payment calculation to a first-party source like your CRM or GA4, not solely the provider's own platform dashboard.
- This model fits clean, short-cycle conversions best; it fits poorly for brand campaigns or long B2B sales cycles with no clear near-term conversion event.
- Cap total performance payout to avoid an unpriced windfall fee in an unusually strong month.
In practice.
A performance-based arrangement usually pairs a reduced base fee with a variable payment tied to agreed outcomes - a bonus per qualified lead, a percentage of tracked revenue, or a milestone bonus once a target is hit. The mechanism only works if there is a single, mutually agreed source of truth for what counts as a result before the campaign launches, whether that is a CRM record marked qualified, a platform conversion event, or a specific GA4 event, because the entire payment structure depends on being able to count something both sides trust.
The settings that make or break this model are defined outside the ad platforms: the conversion window, meaning how long after a click or impression a result still counts, explicit exclusions such as refunds, chargebacks, and existing customers who would have converted anyway, and audit or reporting rights so the client can verify the numbers being used to calculate payment rather than taking the provider's dashboard at face value. iOS-side tracking limitations mean pixel-only attribution on Meta undercounts conversions in ways neither side fully controls, which is one more reason to anchor the payment calculation to a first-party source like a CRM rather than platform-reported numbers alone.
Because a performance deal pays more when results are strong, both sides benefit from agreeing on a baseline period before the arrangement starts, meaning a few months of history showing what the account was already producing under the prior pricing model, so the bonus structure rewards genuine improvement rather than results the account would have generated anyway. Skipping this step is especially common when a provider transitions an existing client from a retainer to a performance deal mid-relationship, since the temptation is to set targets based on optimism rather than the account's actual trend line.
This model works best when tracking is genuinely clean, meaning one clear, countable conversion event, reliable attribution, and a sales process short enough that results show up within a reasonable window, and when the stakes are high enough to justify the setup overhead of defining all of this in writing. It works poorly for brand or awareness campaigns that have no hard conversion event to tie payment to, and for long B2B sales cycles or multi-touch journeys where attributing a specific sale to a specific ad months later is inherently disputable.
The classic dispute is not defining, before launch, exactly which conversions count - a lead that never responds, a sale that closes six months later, a customer who would have bought anyway - because by the time the disagreement surfaces, both sides have already built expectations around different definitions. A second mistake is letting the provider's own platform dashboard be the sole source of truth for a payment calculation, rather than reconciling against your CRM or GA4. A third is not capping total performance payout, which can produce a windfall fee in an unexpectedly strong month that neither side priced for.
The habit worth building is watching platform-reported conversions and independently tracked conversions from a CRM or GA4 side by side every reporting period rather than just the headline number. A small, stable gap between the two is normal and largely explained by attribution-window and tracking differences; a gap that keeps widening over time is an early warning that a dispute over what counts is coming, and it is easier to fix before a large invoice is on the table than after.
Base fee plus per-lead bonus
Suppose your agreement sets a $500 a month base fee plus a $40 bonus for every lead your CRM marks as qualified. In a month where the campaign generates 60 CRM-qualified leads, the fee is $500 plus 60 times $40, or $500 plus $2,400, for $2,900 total.
Compare that to a flat $2,000 a month retainer for the same work. In a strong month like this one, performance-based pricing costs $900 more than the flat retainer would have - but in a slow month with only 20 qualified leads, the performance fee would be $500 plus 20 times $40, or $1,300, which is $700 less than the flat retainer. The performance structure shifts risk: you pay more when results are strong and less when they are weak, which is the entire point of the model, not a flaw in the arithmetic.
Performance-Based Pricing compared with
The settings this gets confused with, and how to tell them apart.
Common questions.
What counts as a qualified result in a performance deal?
Whatever the contract defines before launch - commonly a CRM status change, a completed form plus a follow-up call, or a specific purchase event - and it needs to be specific enough that neither side can argue about an individual case after the fact.
Whose data determines whether a conversion counts?
Ideally a first-party source both sides can see, like your CRM or GA4, rather than only the provider's platform dashboard, since platform-reported numbers can diverge from what actually happened in your business, especially with iOS tracking limitations affecting pixel-only data.
Can performance-based pricing work for a brand-awareness campaign?
Not well - awareness campaigns generally lack a single hard conversion event to tie payment to, so performance pricing is much better suited to campaigns with a clear, countable action like a lead form or a purchase.
What happens to a performance fee when a lead turns out to be junk?
This should be defined in the exclusions section of the agreement - most well-structured deals only pay out on leads that clear a qualification bar, such as a CRM status or a sales-team review, rather than paying on raw form submissions, precisely to avoid this dispute.
You should not need to know this to advertise.
AdFlint handles the settings for you, inside the Google and Meta accounts you already own.
Try AdFlint free