All Docs
Connecting LinkedIn Ads

Getting Started

Connecting LinkedIn Ads

Link your LinkedIn Ads account with secure OAuth. No engineering required.

2 min read

Connecting LinkedIn Ads is part of the authenticated Revenue Proven workspace. Core attribution reads LinkedIn analytics. Optional Ads Manager, Composer, CAPI and Lead Sync workflows use separately granted write or automation scopes and always require an explicit user action. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.

What this guide covers

Connections is the owner-controlled integration hub for OAuth state, selected ad accounts, sync windows, Salesforce won stages and sync status. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.

Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.

Current product workflow

Connections is the owner-controlled integration hub for OAuth state, selected ad accounts, sync windows, Salesforce won stages and sync status. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Connections page showing connected LinkedIn Ads, HubSpot, and Salesforce test systems with sync status
Connections page showing connected LinkedIn Ads, HubSpot, and Salesforce test systems with sync status. Captured from /dashboard/connections.

Connect or verify each provider, select the LinkedIn accounts to sync, and inspect last-sync status. Core attribution reads provider data; optional activation, CAPI and Lead Sync workflows can request or use write scopes. Interface labels and availability follow the current plan, role, connection, and workspace context.

Shawn’s three connections are real test/scratch integrations. Disconnect, reconnect, Sync Now and configuration actions change operational state. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.

Data, access, and permissions

Shawn’s three connections are real test/scratch integrations. Disconnect, reconnect, Sync Now and configuration actions change operational state. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.

Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.

Operational guidance

Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.

Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.