RP
RevenueProven
All Docs
How CRM Objects Map to Attribution Metrics

How CRM Objects Map to Attribution Metrics

Every metric in Company Insights traces back to a specific CRM field. This guide documents the mapping for HubSpot and Salesforce so you can understand and debug your attribution data.

Every metric in the Company Insights table is derived from a specific CRM object and field. Understanding the mapping helps you debug attribution discrepancies and confirm Revenue Proven is reading the right properties from HubSpot or Salesforce.

Company Insights table showing engagement metrics per account
CRM-sourced columns (deal count, pipeline value, revenue) trace back to specific Account and Opportunity fields.

Company matching

Revenue Proven matches LinkedIn-engaged companies to your CRM accounts using company domain as the primary key. When a domain match is not found, Revenue Proven falls back to a name-based match. Each matched row shows a match-confidence indicator: high-confidence for domain matches and lower-confidence for name matches. This helps you spot rows where the match may need review.

Account-level fields

  • Company name: HubSpot company.name or Salesforce Account.Name
  • Company domain: HubSpot company.domain or Salesforce Account.Website
  • Industry: HubSpot company.industry or Salesforce Account.Industry
  • Employee count: HubSpot company.numberofemployees or Salesforce Account.NumberOfEmployees

Deal-level fields

  • Open pipeline value: sum of deal amounts where the stage is not won or lost
  • Won revenue: sum of deal amounts where the stage matches your configured won stage
  • Deal count: number of deal records linked to the matched account
  • Deal owner: the owner field on each deal record

Won stage configuration

Revenue Proven needs to know which deal stage represents a closed deal. For HubSpot, this defaults to the stage named "Closed Won." For Salesforce, you select the won stage on the Connections page, under your Salesforce connection's Won Stages section. If your team uses a non-standard stage name, update the setting there.

Currency handling

Deal amounts are stored in the original CRM currency and converted to your reporting currency using exchange rates that are fetched and cached. The original amount and currency are preserved on each deal record so you can trace the source of any converted value.

Related Reading

See "HubSpot Integration" and "Salesforce Integration" for how each CRM connects and syncs data into Revenue Proven.

How this fits the attribution workflow

Revenue Proven connects LinkedIn Ads engagement to CRM revenue at the company level, so B2B teams can prove which campaigns influenced real pipeline and closed-won deals. This part of the product supports that goal by keeping attribution accurate and easy to act on.

It pulls company-level engagement from the LinkedIn Ad Analytics API across five lookback windows (180, 90, 60, 30, and 7 days), matches those companies to HubSpot or Salesforce accounts by domain and name, and surfaces influenced pipeline and influenced revenue alongside a company-by-company journey timeline. Reviewing this regularly helps you spot which campaigns and accounts are driving measurable pipeline, and which are not yet converting engagement into opportunities.