Salesforce Integration
Pull Salesforce accounts, opportunities, contacts, and leads into Revenue Proven to attribute LinkedIn ad engagement to your Salesforce pipeline and won revenue. Requires the Growth plan or above.
The Salesforce integration is available on the Growth plan and above. It connects Revenue Proven to your Salesforce org via OAuth, pulling the CRM records used to match LinkedIn ad engagement to accounts and pipeline. Access credentials are encrypted before storage, and Revenue Proven handles token refresh automatically to keep the connection healthy.
Salesforce editions and API access
Revenue Proven uses the Salesforce API to read your records. Enterprise, Unlimited, Developer, and Performance editions include API access by default. If you are on the Professional edition, you may need to add an API access add-on through Salesforce before connecting.
Objects synced from Salesforce
Revenue Proven pulls the following standard Salesforce objects on each sync cycle.
- Accounts: account name, website, industry, employee count, Salesforce account ID
- Opportunities: name, stage, close date, amount, associated account
- Contacts: name, email, title, associated account
- Leads: name, email, company, status
Won-stage mapping
Revenue Proven uses your Salesforce opportunity stages to identify won deals for attribution reporting. Because stage names vary across orgs, you select the stage that represents a closed deal during setup. This setting lives on the Connections page, under your Salesforce connection's Won Stages section. You can update it there at any time.
How to connect Salesforce
- In the left sidebar, open Connections (under Workspace)
- Click Connect next to Salesforce
- You will be redirected to Salesforce to authorize Revenue Proven
- Accept the permission request and you will return to Revenue Proven
- On the Connections page, open your Salesforce connection and select your won opportunity stage under Won Stages
- Revenue Proven will begin the first sync immediately
Field sync errors
If your Salesforce org has field-level security restrictions or has removed certain standard fields, some fields may not sync correctly. Revenue Proven shows these errors on the Connections page alongside the affected object type. Sync continues for all other fields while a specific field issue is present. Ask your Salesforce administrator to confirm that the connected user profile has visibility into the fields Revenue Proven reads.
Domain changes and reconnecting
If your Salesforce org's login URL changes, for example after a My Domain change or a sandbox-to-production migration, use the Reconnect button on the Connections page to update your stored credentials. The OAuth reconnect flow is the safest way to restore a healthy connection. Avoid editing connection details manually.