https://api.linkedin.com/rest), using a developer app you own and a refresh token from one member who already has access to your ad accounts. Configview sends only GET requests. It never creates, changes, pauses or deletes anything on LinkedIn.
You will end up with 3 required secrets (LINKEDIN_CLIENT_ID, LINKEDIN_CLIENT_SECRET and LINKEDIN_REFRESH_TOKEN) in Configview when setup is complete.
Scope of this integration today. Configview answers “which ad accounts do we have, who can spend money and grant access on them, who administers the Company Pages behind them, and which live campaigns have no owner”: ad accounts (status, type, currency, serving state, linked Page), who holds which role on each account (viewer to billing admin) and since when, campaign groups and campaigns by name, status, type, objective, budget settings and schedule, and Company Page roles including pending requests. It does not read ad creatives, targeting, audiences, lead forms or leads, performance reporting, posts, or member profiles. LinkedIn returns members as an opaque member id only (no name or e-mail), so people appear as member ids and are not linked to your directory. LinkedIn has no audit log in this API, so none is collected.
What you need
- A LinkedIn account that holds a role on your ad accounts in Campaign Manager (Viewer is enough) and, if you want Page administrators, is an Administrator of the Company Page
- A LinkedIn developer app linked to your Company Page with the Advertising API product approved. The Advertising API is open to any approved developer; you apply from the app’s Products tab and describe your use case. New apps start in the Development tier, which can read any ad account you administer, so no upgrade to the Standard tier is needed for Configview.
- Programmatic refresh tokens enabled for the app. LinkedIn grants these to approved Marketing Developer Platform apps; if the token response has no
refresh_token, ask LinkedIn Developer Support to enable it before continuing.
Step 1: Open the LinkedIn Ads page in Configview
Open Configview in a second browser tab and leave it open:https://{companyname}.configview.com/admin/integrations/linkedin-ads
Step 2: Create or open the developer app
- Go to
https://www.linkedin.com/developers/appsand create an app (or open the one you use for advertising), linked to your Company Page - On the Products tab request Advertising API and wait for approval
- On the Auth tab copy the Client ID and the Primary Client Secret
- Paste them into
LINKEDIN_CLIENT_IDandLINKEDIN_CLIENT_SECRETin the Configview tab under Credentials
Step 3: Get the refresh token
- Add a redirect URL you control on the Auth tab
- As the member from “What you need”, open the authorization URL (authorization code flow) requesting only these scopes:
r_adsandr_organization_admin - Exchange the returned code at
https://www.linkedin.com/oauth/v2/accessTokenwithgrant_type=authorization_code - Copy the
refresh_tokenfrom the response intoLINKEDIN_REFRESH_TOKENand save
rw_ads, rw_organization_admin, r_ads_reporting or any posting scope.
The refresh token is valid for 365 days from this consent and is not renewed when it is used. Put a reminder in your calendar for about 11 months out and repeat this step then. The health check warns when fewer than 14 days remain.
Step 4: Connect and verify
- Click Connect. Configview creates its tables and schedules every collector at your default run time:
- Click Verify now. The health check reads the three secrets, exchanges the refresh token and reads one page of ad accounts.
- 400 or 401 on the refresh exchange. The refresh token expired, was revoked or belongs to another app. Repeat Step 3.
- 403 or 404 on ad accounts. The app does not have the Advertising API product, or the member holds no role on any ad account.
- Page roles empty. The member is not an Administrator of that Page, or
r_organization_adminwas not requested in Step 3.
Data Tables
Each table has arun_at column and keeps only the newest run.
Things worth knowing
People are member ids. The Marketing API returns the opaque LinkedIn member id for ad account and Page roles, never a name or e-mail address. Configview shows the id; map it to a person in Campaign Manager (Manage access) or the Page admin tools when you need to. Only what the member can see. The member’s own role limits the lists. A Viewer sees accounts and users but a Page the member does not administer returns 403 and is skipped. Use a member with a role on every account you want covered. Budgets are settings. Daily and total budget values are the configured limits, not spend. Spend and performance are never collected. Rate limit. LinkedIn does not publish numbers. Each endpoint has a daily application quota and a daily per-member quota that reset at midnight UTC, with HTTP 429 beyond. You can read them for your app under Analytics in the developer portal. Configview paces itself at 30 requests a minute and waits as long as LinkedIn asks. Campaign groups, campaigns and ad account users need one request per ad account, Page roles one per Company Page. API version. Configview sends aLinkedin-Version header (currently 202610). LinkedIn retires each version about a year after release, so Configview moves to a newer one before then.
Known gaps
- No audit or activity log, and no ad spend or reporting, through this connector
- Member names and e-mail addresses are not available
- Creatives, audiences, lead forms and conversions are not collected
- Individual Page (organic) analytics and posts need the separate Community Management API and are not collected
What isn’t collected
- Ad creatives, copy, images and landing-page URLs
- Targeting criteria, audiences and their members
- Lead forms and leads
- Reporting and conversion data
- Client secrets and tokens
- Member profiles