What permissions each integration needs and why

Revenue Proven requests a specific set of OAuth permissions for each integration. This guide explains what each permission covers and why it is needed, so you can make an informed decision before authorising access.

LinkedIn Ads permissions

Revenue Proven requests read access to your LinkedIn Ads analytics data. This covers campaign performance metrics, company-level engagement signals from the Ad Analytics API, organization profile data for matched companies, and basic ad account information. Revenue Proven does not request permission to create, edit, pause, or delete campaigns unless you are using the Ads Manager feature, which requires an additional write scope.

• r_ads_reporting: read ad analytics data including impressions and clicks by company.
• r_organization_social: read organization profile data to resolve company names and websites.
• rw_ads (optional, Ads Manager only): create and update campaigns, ad sets, and ads.
• rw_media_plans (optional, Media Planning only): sync media plans to LinkedIn.
• No permission to access your personal LinkedIn profile or connections is requested.

HubSpot permissions

Revenue Proven requests read access to CRM objects. The scopes cover companies, deals, contacts, deal pipelines, and pipeline stages. Write access to HubSpot is only requested if you enable the CRM push feature, which sends matched account data back into HubSpot. If that feature is off, Revenue Proven operates in read-only mode.

Salesforce permissions

The Salesforce OAuth token grants Revenue Proven access to the same data your Salesforce user can see. Revenue Proven reads Accounts, Opportunities, Contacts, and Opportunity Stage metadata. It does not request access to any object you have not explicitly granted your user account access to in Salesforce. Revenue Proven never writes to Salesforce.