Quickstart Guide
Connect your accounts and see attribution data in under 5 minutes.
This quickstart takes you from a new account to your first attribution view. The whole flow is a handful of steps: connect LinkedIn Ads, connect your CRM, run a sync, and read the results. You do not need any engineering help, and each connection uses OAuth, so there are no API keys to copy or passwords to share.
Step 1: Connect LinkedIn Ads
From Settings, open Connections and connect LinkedIn Ads through the OAuth flow. This is the source of your company-level engagement data — the record of which organizations engaged with your ads — so it is the foundation everything else builds on. Authorize the account that runs the campaigns you want to measure.
Step 2: Connect your CRM
Still in Connections, connect HubSpot or Salesforce. This is the other half of the bridge: it brings in the accounts, deals, and pipeline stages that Revenue Proven matches engagement against. If you run both CRMs, connect the one that holds the pipeline you report on.
Step 3: Run your first sync
With both sides connected, start a sync. The pipeline pulls your LinkedIn engagement and CRM data, matches engaged companies to accounts by domain, and calculates influenced pipeline and revenue. The first sync does the most work, so give it a little time; afterward it stays current on a schedule.
Step 4: Read your attribution
Open the Company Insights table to see which engaged accounts have open pipeline and which campaigns touched them. From there you can save views, schedule an email report, and start answering the question you came for: which LinkedIn spend actually influences revenue.
That is the entire loop. Once it is running, keeping it current is automatic, and every future report is just a matter of opening the dashboard. If something looks off after your first sync — fewer matched accounts than expected, or revenue that does not line up — the usual cause is a CRM domain or a closed-won stage that needs confirming, both of which you can fix from Settings without re-running the whole setup. From here, the natural next steps are saving a view that matches how you report and scheduling it to land in your inbox.