An agency proves ad spend turns into revenue by tying each client's campaigns to the opportunities and closed deals in the client's CRM, then reporting cost per opportunity, pipeline and ROAS next to spend against budget. It starts at kickoff: agree the campaign naming, the UTM rule and read-only CRM access before the first dollar is spent.
Why it matters for agencies
Clients rarely leave an agency because of cost per click. They leave when they cannot see what the budget produced. An agency that reports pipeline and revenue moves the conversation from cost to return, and makes a budget increase easier to justify.
What to agree at kickoff
| Item | Why | Who owns it |
|---|---|---|
| Campaign naming and utm_campaign rule | The key that joins spend and CRM | Agency |
| Read-only CRM access | To count leads, opportunities and deals by campaign | Client |
| Definitions of MQL, SQL and opportunity | So cost per stage means the same thing every month | Client and agency |
| Revenue number and attribution rule | So ROAS is not argued every month | Client and agency |
| Monthly budget by campaign | So pacing has a plan to measure against | Client |
The monthly client report
- Spend against budgetSpend so far, projected month end and any campaign off pace, with what you changed.
- Leads to pipelineMQLs, SQLs and opportunities by campaign, with cost per stage.
- RevenueWon revenue, ROAS and CAC over the last 6 or 12 months.
- What you moved and whyBudget shifted toward the campaigns with the best cost per opportunity.
- Next monthThe plan and the pipeline it should produce.
A worked example
A software client spends $25,000 a month. Over six months:
| Before reallocation (months 1 to 3) | After reallocation (months 4 to 6) | |
|---|---|---|
| Spend | $75,000 | $75,000 |
| Opportunities | 25 | 33 |
| Cost per opportunity | $3,000 | $2,273 |
| Pipeline | $625,000 | $825,000 |
| Pipeline per $1 | 8.3 | 11.0 |
All dollar figures in the examples are illustrative. They are not results from any account.
Same budget, about a third more opportunities. That is the line a client remembers at renewal, and it only exists if the CRM is connected to the campaigns.
Pitfalls
- Claiming every deal. Report paid deals by a stated rule and show the deals that did not come from paid ads. Credibility is worth more than a bigger number.
- Reporting too early. Revenue needs a full sales cycle. Show cost per opportunity first.
- One workspace for clients with separate CRMs. Keep each client's CRM data apart.
What Pacing Console shows
Pacing Console was built by PlanConversion, an agency, for this work. The client map assigns each ad account to a client once, and the Clients page shows each client's budget, spend, forecast and pace across Google Ads, Microsoft Ads, LinkedIn Ads and TikTok Ads. A workspace holds one connection per CRM, so when clients have their own HubSpot, Salesforce or Pipedrive, give each client a workspace and connect their CRM there. Clients get a read-only report link with pacing and forecast on every plan; Pro adds your branding and scheduled emails, and the Pipeline and Revenue pages (Enterprise) export CSVs for the revenue section. Open the live demo to see a client view on sample data.
Plans: CRM lifecycle stages (contacts, MQLs, SQLs and opportunities by campaign, with cost per stage) are on Pro, USD 49 per workspace per month. The Pipeline and Revenue pages, revenue forecasts, what-if scenarios and budget targets need Enterprise. See Plans, pricing and billing.
Questions people ask
How do agencies show ROI on ad spend to clients?
By connecting the client's CRM to campaign spend and reporting cost per opportunity, pipeline, won revenue and ROAS, alongside spend against budget.
What if the client will not share CRM access?
Ask for a monthly export of leads and deals with utm_campaign and stage. Pacing Console accepts the same data by CSV upload.
Should the client see pacing numbers?
Yes. A read-only report link with spend, pace and forecast builds trust between monthly reports, and shows budget is under control.
How do I handle clients with long sales cycles?
Report cost per SQL and cost per opportunity monthly, and revenue quarterly over a rolling 12 months.
Can one workspace hold many clients?
Yes, for pacing. Map each ad account to a client and use per-client report links. For CRM-based revenue reporting, a workspace per client keeps each CRM separate.
Related articles
Last updated 2026-11-22. Platform and CRM rules change, so check their own help for the current details.