RP
RevenueProven
All Help Articles
Connect your LinkedIn Ads account

Connect your LinkedIn Ads account

Connect your LinkedIn Ads account using OAuth so Revenue Proven can pull company-level campaign engagement data across five lookback windows. Here is what you need and what to expect.

Your LinkedIn Ads connection is the foundation of Revenue Proven. Without it, the platform has no engagement signal to work with. This guide walks through the connection process and explains what happens once you authorise access.

LinkedIn Ads integration settings panel in Revenue Proven
The LinkedIn Ads card on the Connections page shows connected status and lets you select which ad accounts to sync.

What you need before connecting

  • An active LinkedIn Ads account with at least one campaign that ran in the past 180 days.
  • Admin or Super Admin role on that LinkedIn Ads account — standard user access is not sufficient for API permissions.
  • Pop-ups allowed for your Revenue Proven domain so the OAuth window can open.
  • If you manage multiple LinkedIn ad accounts under one login, you will be prompted to select which account to connect after authorising.

Completing the connection

Navigate to Settings, then Connections. Click Connect next to LinkedIn Ads. A LinkedIn authorisation window will open asking you to review and grant permissions. Click Allow. You will be redirected back to Revenue Proven and the LinkedIn Ads card will show a green Connected status along with the ad account name. Revenue Proven stores only the encrypted OAuth token — your LinkedIn password is never seen or stored.

What happens after connecting

Revenue Proven starts a background sync immediately after the connection is confirmed. This first sync pulls campaign data and company-level engagement signals across all five lookback windows (7, 30, 60, 90, and 180 days). Depending on the size of your ad account, the first sync typically takes 10 to 45 minutes. You can monitor progress from the dashboard home page. Subsequent syncs run daily and are much faster because they process only incremental changes.