On Pro, connect HubSpot, Salesforce or Pipedrive, or send any CRM by CSV or API, to see contacts, MQLs, SQLs, opportunities and customers next to each campaign's spend. Enterprise also reads deals for pipeline and revenue.
On this page
Connect
- Open the CRM cardOn Connect, find CRM lifecycle stages (Optional, Pro). Owners and editors connect it.
- Choose your CRMPress HubSpot, Salesforce, Pipedrive, Other CRM: CSV or Other CRM: API.
- Enter read-only credentialsHubSpot: a private app token with
crm.objects.contacts.read(Enterprise: alsocrm.objects.deals.read). Salesforce: a connected app with the api scope and Client Credentials Flow, its My Domain, consumer key and secret. Pipedrive: your personal API token. - Pass the campaign in your adsAds should land with
utm_campaignset to the ad campaign's name or ID. That is how CRM records are matched to campaigns.
Where results show
- A CRM column in the Pacing table with contacts and MQL, SQL and opportunity counts.
- Cost per MQL and Cost per SQL in the campaign window.
- CRM stages by campaign, with cost per stage, on the Performance page.
Each stage counts records that reached it or a later stage, grouped into contact, MQL, SQL, opportunity and customer. Only records created this month are counted.
Below campaign level: ad groups and keywords (HubSpot)
HubSpot leads and deals also keep the ad group (utm_content, or adgroupid in the landing URL), the keyword (utm_term, or keyword) and, for paid search, HubSpot's search term. Records without them stay at campaign level, so campaign totals are always complete. When the landing URL has no utm_campaign, a paid search contact falls back to HubSpot's Original source drill-down 1 for the campaign.
To capture them, set the Google Ads final URL suffix to utm_term={keyword}&utm_content={adgroupid} (alongside your utm_campaign). The results show in the campaign window under Where this budget goes.
Any other CRM: CSV or API
Upload a CSV with utm_source (or source), optional utm_medium, utm_campaign (or campaign), stage and an optional count. Uploading again replaces this month's CSV data. Or send records to the API with your workspace key; each call replaces this month's API data:
POST https://pacing.planconversion.com/api/crm/ingest
{
"key": "your workspace key",
"records": [
{ "utm_source": "linkedin", "utm_medium": "paid_social",
"utm_campaign": "ABM tier 1", "stage": "MQL", "count": 12 }
]
}Deals for pipeline and revenue (Enterprise)
With Enterprise, the same connection reads opportunities and deals from the last 12 months. For other CRMs, upload a deals CSV (a file with an amount column is read as deals) or send a deals list to the API; add "deals_mode": "merge" with an id on each deal to update deals one by one. See Pipeline and Revenue.
- HubSpot, Salesforce and Pipedrive refresh twice a day, at about 11:37 and 23:37 UTC. Press Sync now to update straight away.
- Credentials are encrypted before they are stored and are never shown again.
- We store counts per campaign and stage, not contact names or emails. On Enterprise we also store each deal's name, amount, status, dates and campaign, never contact details.
- Disconnect removes the connection and the counts and deals it sent.