A plain-language overview of the access we request, what each permission lets us do, who on your team should connect, and what to expect during setup.
What to expect
The LinkedIn integration syncs the posts published by your organization's LinkedIn Pages: the images, videos and documents attached to them, each post's status, and its engagement figures. It does not sync personal LinkedIn profiles.
Connecting takes a couple of minutes. When you connect LinkedIn in Medialake, you're redirected to the official LinkedIn sign-in page, then to LinkedIn's consent screen listing the permissions requested, which are explained in the tables below. You approve it yourself and can revoke access at any time. We never see or store your password: the login happens entirely on linkedin.com, and once you approve you're returned to Medialake.
Medialake is a reporting and media platform. The LinkedIn connector only ever reads from LinkedIn: it never posts, comments, reacts, or changes anything on your Pages or ad accounts. All data is read through LinkedIn's official Marketing APIs.
You Medialake LinkedIn │ connect source │ │ │────────────────────────▶│ │ │ redirect to LinkedIn │ │ │◀────────────────────────│ │ │ log in & grant access │ │ │──────────────────────────────────────────────────▶│ │ redirect with code │ │ │◀──────────────────────────────────────────────────│ │ │ exchange code │ │ │────────────────────────▶│ │ │ access token │ │ │◀────────────────────────│ │ source authorized │ │ │◀────────────────────────│ │
Two ways to connect
LinkedIn can be connected through Medialake's OAuth app or through your own OAuth app:
Medialake's OAuth app (default). Accounts connect using Medialake's central LinkedIn app. No setup is required: just sign in and approve.
Your own OAuth app (optional). If your organization would rather own the app that appears on the consent screen, you can create an app in the LinkedIn Developer Portal and add its credentials to Medialake. Your organization owns the app and can disable it at any time. Setup steps are below.
The permissions requested, and everything else on this page, are identical for both options.
Setting up your own OAuth app (optional)
Most organizations connect with Medialake's app and can skip this section. An app of your own needs LinkedIn's approval for every permission Medialake requests (listed in the tables below). LinkedIn grants permissions through the API products you request for the app and reviews those requests itself, so allow time for approval. If the app is missing any requested permission, LinkedIn refuses the sign-in. One of the requested permissions, r_ads_leadgen_automation, was deprecated by LinkedIn in July 2023 and is no longer listed under any API product, so an app created now may not be able to get it. If LinkedIn refuses the sign-in for that reason, connect with Medialake's OAuth app instead.
In the LinkedIn Developer Portal, create an app for your organization.
On the app's Products tab, request the products that grant the permissions in the tables below. LinkedIn's Increasing Access page lists which product grants each Marketing API permission;
openid,profileandemailcome from the Sign In with LinkedIn using OpenID Connect product.On the app's Auth tab, add an authorized redirect URL made of the address you use to sign in to Medialake followed by
/linkedin-redirect. For example, if you sign in atyourcompany.medialakeapp.com:
https://yourcompany.medialakeapp.com/linkedin-redirect
On the same Auth tab, copy the app's Client ID and Client Secret.
>Keep the Client Secret private. Store it in an approved password manager or secret-management system. Do not email it, paste it into a support ticket, or commit it to source control.
Adding the credentials to Medialake
You need Medialake administrator privileges for these steps.
Open Administration → Integrations from the sidebar.
Open the LinkedIn integration.
In the Access Keys section, click Create New Setting.
In the New access key panel, give the key a Name your team will recognize, such as "Marketing LinkedIn app".
Under Credentials, enter the Client ID in Enter your LinkedIn Client ID without any spaces and the Client Secret in Enter your LinkedIn Client Secret without any spaces. Medialake stores these encrypted and never shows them again.
Under Who can use it?, choose which teams can connect LinkedIn accounts with this key.
Click Save access key.
Verifying it's really us
On LinkedIn's consent screen, check that the app requesting access is the one you expect: Medialake's LinkedIn app, or the app your organization created and named. If the name doesn't match, stop and contact us. Never approve a LinkedIn access request you weren't expecting.
Who should do the connecting
The connection is tied to the LinkedIn member who signs in. Please have it done by someone who:
Is a Super admin of each LinkedIn Page you want to sync. Medialake lists only the Pages where the connecting member holds LinkedIn's administrator role (LinkedIn's API calls it
ADMINISTRATOR). Content admins, Analysts and paid media admins don't see their Pages in Medialake.Is a permanent member of your team. If the person who authorized us leaves your company or loses their admin role on a Page, syncing for that Page stops and someone else will need to connect it again.
Their LinkedIn login is used only to authorize the connection. The only member details the connector reads are their name, email address, profile photo and LinkedIn member identifier, to confirm who authorized. It does not read their personal posts, messages or connections.
Limiting what Medialake can access
Medialake inherits the connecting member's access, enforced by LinkedIn on every request. To keep the connection as narrow as possible, have someone who is a Super admin of only the Pages in scope do the connecting. Pages they don't administer are never listed. The token's advertising and lead permissions (listed below) also reach whatever ad accounts and lead forms that member can access, so the narrowest choice is someone without ad account access they don't need.
Connect and choose what to sync
Anyone on your team who is allowed to connect sources can do this.
Open Connections → Catalogue from the side menu.
Find LinkedIn and click Connect.
Under How do you want to connect?, choose Connect it myself. If your organization has saved its own LinkedIn app as an access key, an OAuth app dropdown appears: choose your app, or leave it on Medialake's OAuth app.
Sign in to LinkedIn and approve the request. LinkedIn asks you to approve all of the requested permissions together.
Back in Medialake, choose which Pages to sync. Each Page you administer is listed as Page: followed by its name.
For each Page you select, Medialake reads the Page's posts and brings in:
The images, videos and documents attached to each post, with multi-image posts split into one file per image. Each video's cover image is brought in too.
Each post's visibility and publishing state, described in Organic Post Availability and Visibility.
Each post's likes, comments, shares and views. Views come from LinkedIn's unique impressions count. See the Performance Metrics Reference for how organic metrics are captured.
Posts with no image, video or document attached, such as text-only posts, link shares and polls, have nothing to bring in and are skipped. By default Medialake checks for new posts once a day; you can change the schedule under Source Synchronization on the source's General tab.
The permissions we request
LinkedIn shows every permission below on its consent screen. The middle column summarizes LinkedIn's own description of each one.
Permissions the LinkedIn connector uses
Permission (scope) | What LinkedIn says it allows | How Medialake uses it |
| Sign in with LinkedIn: your name, profile photo and email address. | Confirms who authorized the connection. |
| Retrieve your organization's Pages and their reporting data, including follower, visitor and content analytics. | Lists the Pages you administer. Medialake also requests each Page's details (name, description, website, headquarters city and language) and your posts' likes, comments, shares and impressions under this permission. |
| Retrieve your organization's posts, including comments, likes and other engagement data. | Reads your Pages' posts and downloads the documents attached to them. |
| Manage and read the ad accounts you have access to. | LinkedIn's Images API only returns an image's download link to a token holding this permission, the organization posting permission |
Also requested, not used by the LinkedIn connector
These permissions are part of the request LinkedIn shows you, so the access token carries them, but the LinkedIn connector doesn't rely on any of them.
Permission (scope) | What LinkedIn says it allows |
| Use your basic profile including your name, photo, headline and public profile URL. |
| Use your name and photo. |
| Retrieve your advertising accounts. |
| Retrieve reporting for your advertising accounts. |
| Retrieve your organization's events. |
| Retrieve the number of 1st-degree connections within your network. |
| Access your lead generation forms and retrieve leads. |
| An older lead generation permission that LinkedIn has deprecated in favor of |
Medialake does not request LinkedIn's posting permissions (w_organization_social, w_member_social), its Page management permission (rw_organization_admin), or access to members' personal posts (r_member_social).
What Medialake can and cannot do
Regardless of who connects, Medialake cannot:
See or store your password, or log in as you
Post, comment, or react on your Pages or on your behalf
Edit your Pages, or add or remove Page admins
Read your personal LinkedIn posts or messages
The connector also does not create, edit, pause, or delete anything in your ad accounts.
Staying connected
LinkedIn access tokens last 60 days. What happens after that depends on whether LinkedIn issues a refresh token to the app you connect with. LinkedIn only does this for apps it has enabled for programmatic refresh tokens.
With a refresh token, Medialake renews the access token automatically in the background whenever LinkedIn rejects an expired one. The refresh token itself has a fixed lifetime set by LinkedIn (a year from when you first approve) and isn't extended by renewals, so you need to re-approve once it runs out. Medialake shows a warning on the source 48 hours before it expires.
Without a refresh token, the connection stops working when the 60-day access token expires, and the source needs to be re-authenticated.
The connection also stops if access is revoked on LinkedIn. Whenever LinkedIn stops accepting the connection, Medialake stops syncing the source and shows a Service Disconnected notice on it. The person who connected it can click Re-Authenticate to sign in again, or Check connection if they think it was disconnected by mistake. Other team members see who to contact.
If the connecting member loses their Super admin role on a Page, the connection itself stays valid but LinkedIn no longer returns all of that Page's data to it, so new posts or their figures stop coming in. Have a current Super admin of the Page connect LinkedIn and select it.
Revoking access
You're in control at any time. To remove the connection:
On LinkedIn, signed in as the connecting member, click Me → Settings & Privacy → Data privacy. Under Other applications, click Change next to Permitted Services, then Remove next to the app, or
Remove every Page admin and paid media admin role the connecting member holds on the Page, or
Delete the source in Medialake: open it and, on its General tab, click Delete Service.
Revoking on LinkedIn's side invalidates the token and data collection stops; no action is needed on our side.
Troubleshooting
What you see | Likely cause | What to do |
No Pages are listed after you connect | The member who signed in isn't a Super admin of any Page. Content admins, Analysts and paid media admins aren't listed. | Have a Super admin of the Pages connect, or ask one to give the member the Super admin role. |
LinkedIn shows an error instead of its consent screen (your own app only) | The app isn't approved for every requested permission, or its redirect URL doesn't match the one Medialake sends. | Check the app's Products and Auth tabs against the steps above, or connect with Medialake's OAuth app instead. |
You're returned to Medialake with an error and no source is created | The sign-in was cancelled, or LinkedIn refused the code exchange, often because the Client Secret in the access key is wrong or has been regenerated. | Try again. If you use your own app, create a new access key with the current Client ID and Client Secret. |
Some posts didn't come in | The posts have no image, video or document attached. | Nothing to fix: text-only posts, link shares and polls are skipped. |
A post has no likes, comments, shares or views | LinkedIn's share statistics cover a rolling 12-month window and leave out posts with no activity. | Nothing to fix. |
New posts from a Page stopped coming in, but the source isn't disconnected | The connecting member is no longer a Super admin of that Page. | Have a current Super admin of the Page connect LinkedIn and select it. |
The source shows Service Disconnected | The access token or refresh token expired, or access was revoked on LinkedIn. | Click Re-Authenticate on the source, signed in as a Super admin of the Pages you sync. |
If you get stuck, contact [email protected] and we'll walk you through it.
Further reading (LinkedIn documentation)
LinkedIn 3-legged OAuth flow: the authorization flow used to connect, including redirect URL rules and access token lifetime
Refresh tokens: which apps receive refresh tokens and how long they last
Increasing Access: every Marketing API permission and the product that grants it
Organization access control by role: the Page roles LinkedIn recognizes
Posts API: the API the connector reads posts from
Third-party applications data use: reviewing and removing app access on your LinkedIn account
You can review or withdraw access at any time from your LinkedIn account's Permitted Services settings.
