Closed-loop reporting for paid media means every CRM contact and deal carries the ad campaign that brought it, so outcomes can be reported against the spend that created them. With HubSpot, Salesforce or Pipedrive this comes down to landing every ad with utm_campaign, keeping that value on the contact or lead and the deal, and joining it with spend by campaign.
What closing the loop means
The open loop is common: ad platforms report spend and conversions, the CRM reports leads and revenue, and nobody can line the two up by campaign. Closing it means one shared key, usually the campaign name or ID in utm_campaign, appears on both sides. There is a second, separate loop worth knowing: sending CRM outcomes back to the ad platform for bidding, which Google Ads supports through offline conversion imports (About offline conversion imports (Google Ads Help)). This guide covers the reporting loop.
Where the campaign lives in each CRM
| CRM | Where Pacing Console finds the campaign | Access it needs |
|---|---|---|
| HubSpot | The original source and first-visit utm_campaign of the deal's earliest contact, or the deal's own original source | A private app token with contact read access, plus deal read access for pipeline and revenue |
| Salesforce | UTM fields on the lead the opportunity came from, then UTM fields on the opportunity, then its primary Campaign and Lead Source | A connected app with the api scope and the Client Credentials Flow |
| Pipedrive | The deal's utm_campaign and utm_source fields, or Channel and Channel ID | A personal API token |
| Any other CRM | utm_source, utm_campaign and stage columns | A CSV upload or the ingest API |
HubSpot documents how it sets original source and its drill-downs in Understand traffic source properties (HubSpot Knowledge Base).
Setup checklist
- Agree on the keyUse the ad campaign's exact name or ID as utm_campaign. Do not invent a second naming scheme for UTMs.
- Set it in the ad platformAdd utm_campaign through a tracking template or final URL suffix so every ad carries it automatically.
- Capture it on the recordCheck a few recent paid leads in the CRM: the UTM fields or original source should show the campaign.
- Keep it on the dealCreate opportunities from the contact or lead so the source carries over. For Salesforce, copy UTM fields from lead to opportunity on conversion.
- Connect and compareConnect the CRM read-only, then compare the All CRM deals total in your reporting with the CRM's own report. They should match.
A worked example: matching
| utm_campaign on the deal | Ad campaign | Result |
|---|---|---|
| NA_Search_Category_Q4 | NA_Search_Category_Q4 | Matched: counted for that campaign |
| na-search-category-q4 | NA_Search_Category_Q4 | Depends on the tool. Avoid it by using one spelling |
| Paid search, no campaign | None | Shown as paid with no campaign under its channel |
| Organic or referral | None | Not from paid ads |
A program with 120 paid deals in six months where 18 show no campaign has a 15% gap to fix before anyone argues about the other 85%.
All dollar figures in the examples are illustrative. They are not results from any account.
Common breaks
- Redirects or forms that strip the query string, so UTMs never reach the CRM.
- Sales creating opportunities without a contact.
- Campaigns renamed after launch.
- Deals in several currencies, which should not be added together without a stated rate.
What Pacing Console shows
Pacing Console connects to HubSpot, Salesforce and Pipedrive with read-only credentials, or takes any other CRM by CSV or API. It refreshes twice a day, and Sync now updates straight away. Pro shows lifecycle stages and cost per stage by campaign. Enterprise reads opportunities and deals from the last 12 months for the Pipeline and Revenue pages, gives each deal to the campaign of its first touch, and keeps unmatched paid deals and non-paid deals visible so the total matches your CRM. It stores counts and, on Enterprise, deal name, amount, status, dates and campaign, never contact details. See Connect your CRM or open the live demo.
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
What is closed-loop reporting in marketing?
Reporting where sales outcomes from the CRM are tied back to the marketing source that created them, so spend can be judged on opportunities and revenue rather than leads.
Which CRMs does Pacing Console connect to?
HubSpot, Salesforce and Pipedrive directly. Any other CRM can send stage counts and deals by CSV upload or the ingest API.
Does Pacing Console write anything to my CRM?
No. It uses read-only access to count records by campaign and, on Enterprise, to read deals.
Why do some paid deals show no campaign?
Their utm_campaign is missing or does not match a budgeted campaign. They appear as paid with no campaign under their channel, so you can see the size of the gap.
Should I also import conversions back into Google Ads?
It is worth doing when you have enough qualified leads or deals, because bidding then learns from outcomes. It complements closed-loop reporting rather than replacing it.
Related articles
Last updated 2026-11-22. Platform and CRM rules change, so check their own help for the current details.