Setup guide
Connect LinkedIn
Straightforward, with one catch: you need a LinkedIn Company Page, and personal profiles cannot be connected at all.
Check these first
Each of these blocks everything after it, and none of them is checked until the very last step — so it is worth thirty seconds now.
- A LinkedIn Company Page that you are a Super Admin of. LinkedIn has no analytics API for personal profiles — not restricted, simply absent.
Steps
Create the app
linkedin.com/developers/apps → Create app. It asks which Company Page the app belongs to — pick the one whose analytics you want.
Verify the page
LinkedIn generates a verification link. Open it as a Page admin and confirm. Takes about thirty seconds and nothing works until it is done.
Set the redirect URL
Auth tab → OAuth 2.0 settings → Authorized redirect URLs. Paste the URI SIGNAL gives you.
Request the products
Products tab → request "Share on LinkedIn" and "Sign In with LinkedIn using OpenID Connect". These are granted instantly. Community Management API is the one that needs an application — you only need it for full page analytics, so start without it.
Copy the credentials
Auth tab → Client ID and Primary Client Secret. Paste both into SIGNAL.
Developer console: www.linkedin.com/developers/apps
Permissions to request
Read-only. None of these let anything post on your behalf — if a console offers you publishing permissions, you can leave them off.
- r_organization_social
- r_basicprofile
If something goes wrong
These are the real failures, with the errors the platform actually shows. Most of them point somewhere other than the actual cause.
- "unauthorized_scope_error" on the consent screen.
- A requested scope belongs to a product that has not been granted to the app. Check the Products tab — approved products appear under "Added products".
- Connects fine, but no page data arrives.
- You are a Page admin but not a Super Admin, or the app was attached to a different Page than the one you are looking at.
Console layouts change. These steps were checked in July 2026 — if a screen does not match, the developer console’s own documentation is the authority.