Connect HubSpot or Salesforce

Ad engagement data alone cannot tell you which LinkedIn-touched accounts are in your pipeline. Connecting your CRM gives Revenue Proven the revenue context it needs to show you which engaged companies have open deals, how much pipeline they represent, and which ones have already closed.

HubSpot is supported on all plans including Free. Salesforce requires a Growth plan or above. You need Super Admin or App Marketplace access to connect HubSpot, or System Administrator access to connect Salesforce.

Connecting HubSpot

In the left sidebar, open Connections (under the Workspace group).
Click Connect next to the HubSpot tile.
Sign in with a HubSpot account that has Super Admin or App Marketplace permissions.
If you have access to multiple HubSpot portals, select the one you want to connect.
Click Connect app. Revenue Proven requests read access to companies, contacts, deals, and pipelines.
The connection status changes to Active once authorization is complete.

Connecting Salesforce

In the left sidebar, open Connections (under the Workspace group).
Click Connect next to the Salesforce tile.
Sign in with a Salesforce user that has the System Administrator profile or equivalent API access.
Salesforce may prompt you to allow access for the Revenue Proven connected app. Click Allow.
The connection status changes to Active. Revenue Proven reads Accounts, Contacts, Leads, and Opportunities.

CRM connection screen showing HubSpot and Salesforce options — The Connections page lets you authorize HubSpot or Salesforce with a single OAuth flow.

Best practices

Use a dedicated service account or integration user for the OAuth connection rather than a personal login, so the connection survives staff changes.
Confirm deal pipeline stage names in your CRM match the won-stage mapping in Revenue Proven before your first sync.
Connect your CRM before running your first sync so attribution has revenue data to match against immediately.
If you have a HubSpot sandbox or Salesforce sandbox, test the connection there first to confirm permissions are correct before connecting production.

Common mistakes

Connecting HubSpot with an account that lacks Super Admin or App Marketplace permissions. The authorization may succeed but Revenue Proven will not be able to read all required objects.
Connecting Salesforce with a profile that lacks Read access on Account, Opportunity, Contact, and Lead objects. Missing object access means those records do not appear in attribution.
Assuming Revenue Proven writes back to your CRM. All reads are one-way. Revenue Proven never creates, modifies, or deletes CRM records.
Not selecting the correct HubSpot portal when you manage multiple portals. Revenue Proven connects to one portal per workspace.

FAQ

Does Revenue Proven write to my CRM?

No. Revenue Proven reads company, deal, and contact data to build the matching layer. It never modifies, creates, or deletes CRM records.

Which HubSpot plans are supported?

HubSpot connects on any HubSpot plan including the free CRM; you need a HubSpot user with Super Admin or App Marketplace permissions to authorize (free-tier API rate limits are lower, but the connection works).

Which Salesforce editions work with Revenue Proven?

Enterprise, Unlimited, Developer, and Performance editions include API access by default. Professional edition may require an API add-on. Salesforce connection also requires a Growth plan or above in Revenue Proven.

What data does Revenue Proven read from my CRM?

For HubSpot: companies, associated contacts, deals, and pipeline stages. For Salesforce: Accounts, associated Contacts, Leads, and Opportunities including stage and amount. This is the minimum needed to power the attribution matching layer.

Troubleshooting

HubSpot "Portal not found": disconnect and reconnect, making sure you select your company's portal during authorization.
Salesforce "INVALID_SESSION_ID": your Salesforce session expired. Reconnect from the Connections page.
Salesforce missing records: verify your Salesforce user profile includes Read permission on Account, Opportunity, Contact, and Lead objects.
Connection shows Disconnected unexpectedly: corporate firewall rules occasionally block token refresh. Reconnect from the Connections page.

With both integrations connected, you're ready to pull your first dataset. See "Run Your First Attribution Sync" to start the matching process, and "Reading the Attribution Dashboard" once your data appears.