All Docs
a blue background with lines and dots

Integrations

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.

2 min read

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 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.

Current product workflow

Attribution combines matched LinkedIn company engagement with CRM accounts and opportunities to calculate influenced pipeline and closed-won revenue. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Attribution page showing influenced pipeline and revenue KPIs, monthly charts, filters, and Company Insights
Attribution page showing influenced pipeline and revenue KPIs, monthly charts, filters, and Company Insights. Captured from /dashboard/attribution.

Set the engagement lookback, account, CRM provider and deal filters, then use Company Insights for account-level drill-down. Model thresholds and currency are workspace settings. Interface labels and availability follow the current plan, role, connection, and workspace context.

Shawn’s attribution data is real synchronized test-system data. Figures are not customer benchmarks, and lookback filters describe engagement context rather than every CRM event date. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.