What does a pay-for-performance media relationship need to protect?
It needs to protect five things: the budget, the ad accounts, the money, the measurement and the traffic quality. When a partner pays per lead, per paying user or on revenue share, both sides carry risk. The partner risks paying for low-quality traffic, inheriting a policy problem or losing sight of spend. The media buyer risks running budget against outcomes that are later rejected, or against tracking that silently breaks.
Most disputes in these relationships come from things nobody wrote down: which system counts a conversion, what happens when a source underperforms, who can see the accounts. Settle each of those before the first dollar is spent.
How should budgets be set per traffic source?
Approve budgets per campaign and per traffic source, and give each one a ROAS target and a floor. A single blended budget hides losing sources behind winning ones. Per-source budgets make every source earn its spend on its own numbers.
This guide deliberately gives no thresholds, percentages or timings. The right values depend on the partner’s economics and the offer, so the useful part is how to choose them:
| Guardrail | What to decide | How to choose it |
|---|---|---|
| ROAS target | The return a source must reach to keep or grow spend | Work back from the payout or revenue per conversion and the margin the partner needs |
| ROAS floor | The level where spend comes down and then pauses | The point where the source loses money even after expected cohort revenue matures |
| Evaluation window | How long a source runs before it is judged | How long revenue takes to arrive, and how long the source needs to produce enough conversions to read |
| Daily and total caps | Maximum spend per source per day and per period | The partner’s cash-flow tolerance and the cost of a bad week |
| Scale rule | When budget is allowed to rise | Only after the source holds target over the window, with the partner’s written sign-off |
Write the response to each state into the agreement. Below the floor, spend comes down quickly. If it stays below, the source pauses. Above target, budget can rise, but only with approval. Pre-agreed rules remove the temptation to argue about a single bad day.
Who should own the ad accounts and the funds?
The partner should own the ad accounts or hold admin access from day one, and partner funds should be kept separate from any other client’s money.
On Google Ads, admin access is the level that can give or change access and accept or unlink manager accounts, so the partner can always see and control who is in the account. On Meta, assets owned in one business portfolio can be shared with a partner at full control or partial access by task. A partner with full control cannot re-share the asset with another business; only the owning organization can. Either way, the partner should be able to open the accounts and see every campaign without asking.
For the money, use a funding method dedicated to that partner, spend it only on that partner’s campaigns, and reconcile it against the platforms’ own billing records. Commingled funds make audits slow and disputes likely. Separate funds make the account audit-ready at any time.
How do you reconcile reporting to the partner’s tracking?
Treat the partner’s tracking as the source of truth for payable events, and reconcile to it every week. Platform-reported conversions are useful for optimization, but the partner pays on what its own system records.
- Agree definitions in writing. What counts as a lead, a paying user or attributable revenue. Whether events are dated by click or by conversion. How duplicates, refunds and chargebacks are handled.
- Connect the systems server to server. The partner’s platform sends a postback to the buyer’s tracker when a conversion is confirmed, carrying the click ID passed at the start of the session.
- Reconcile weekly by source. Spend from the platforms against confirmed conversions and revenue from the partner, campaign by campaign and source by source. Flag gaps and agree a cause for each one.
- Send confirmed value back to the platforms. Meta’s Conversions API connects server or CRM data to Meta for optimization and measurement. On Google Ads, conversion adjustments let you restate a conversion’s value or retract it, within a limited window, when a sale is refunded or rejected.
Our Meta Conversions API guide covers the setup and deduplication details.
Why optimize on cohort revenue instead of front-end CPA?
Because front-end CPA measures what a conversion cost, not what it was worth. The cheapest leads or signups often come from the sources and placements with the weakest intent, and they show up later as rejections, refunds or users who never pay again.
Group users by acquisition week and source, then track revenue for each cohort at fixed ages. Early in a cohort’s life, use a predicted value (from the partner’s historical data on similar users) to judge sources before revenue has matured, and check those predictions against matured cohorts as they arrive. Where the platform supports it, feed value back so bidding optimizes to it; our guide to value-based bidding covers that on Google Ads, and CAC payback and cohort ROAS covers the cohort math.
What traffic quality and fraud controls belong in the agreement?
Ban bots, incentivized clicks, cloaking and review workarounds outright, and give the partner the right to audit. These are not just quality issues. They put the ad accounts, and the partner’s brand, at risk.
- Cloaking. Google’s Circumventing systems policy prohibits cloaking (showing Google different content than users see), treats violations as egregious, and allows suspension on detection without prior warning. Meta’s Spam standard defines cloaking as intentionally presenting different off-platform content to its integrity systems than to users.
- Deceptive offers. Google’s Misrepresentation policy covers unacceptable business practices, including concealing material information about a business or offering products that cannot be delivered.
- Invalid traffic. Google defines invalid clicks as clicks that do not represent genuine interest, including clicks from automated tools and bots. Platform filtering helps, but the agreement should also cover sources outside those platforms.
- Source transparency. Every source and placement is visible to the partner. No sub-sourcing to third parties without written approval.
- Monitoring. Watch for sudden conversion-rate spikes, duplicate user details, implausible time from click to conversion and unusual geographies, and agree in advance how disputed conversions are handled.
Age-gating. Where the product, local law or platform policy restricts the audience, age-gate. Meta’s alcohol policy says ads may not target people under 18 at a minimum, with higher ages in some countries. Google’s alcohol policy says ads must not target those under the legal purchase age. Use platform age targeting and verify age again on the landing page or at signup where required.
How MSG approaches this
MSG buys media for networks and advertisers who pay per lead, per paying user or on revenue share. Budgets are approved per campaign and per traffic source, each with a ROAS target and a floor. Ad accounts carry the partner’s admin access, partner funds are kept separate, and weekly reporting reconciles to the partner’s tracking. We optimize on cohort revenue and predicted ROAS rather than front-end CPA. No bots, incentivized clicks or cloaking, and age-gating where required. See our media buying and planning service and measurement work.
Sources
- Google Ads Help: About access levels in your Google Ads account
- Meta Business Help Center: Give a partner access to business assets in your business portfolio
- Meta for Developers: Conversions API
- Google Ads Help: How to adjust your conversions
- Google Ads Help: Invalid clicks, definition
- Google Ads Policy Help: Circumventing systems
- Google Ads Policy Help: Misrepresentation (unacceptable business practices)
- Meta Transparency Center: Spam (Community Standards, cloaking definition)
- Meta Transparency Center: Alcohol (Advertising Standards)
- Google Ads Policy Help: Alcohol
Platform features and policies change. This guide reflects the sources above as of October 7, 2026.