LinkedIn Ads to Data Studio: connectors, costs and the API limits that break B2B reports

Does Data Studio have a native LinkedIn Ads connector?

No. Data Studio's built-in connectors cover Google's own products (GA4, Google Ads, Search Console, YouTube, Campaign Manager 360, Display and Video 360, Ad Manager), Sheets, BigQuery and a set of databases. LinkedIn is not one of them, and nothing changed when Google renamed Looker Studio back to Data Studio in April 2026.

The gap goes one level deeper than most guides admit. Google's BigQuery Data Transfer Service can load Facebook Ads, Google Ads, HubSpot, Salesforce, Shopify and other sources into BigQuery on a schedule, but when I checked its list of supported data sources on docs.cloud.google.com on October 21, 2026, LinkedIn Ads was not on it. So even the warehouse route needs a third-party ETL tool or your own script calling the LinkedIn Marketing API.

That means every LinkedIn Ads to Data Studio setup depends on an outside vendor or code you maintain. The choice is which dependency you are happiest owning.

What are the ways to get LinkedIn Ads data into Data Studio?

There are four routes, and they differ mainly in cost, how much history you keep and how well LinkedIn data joins to your CRM. A B2B team running two or three campaigns a quarter needs something very different from a team spending across several ad accounts and reporting pipeline by company.

A partner connector sits in the Data Studio gallery and calls LinkedIn when charts load, or reads the vendor's cached copy. A Sheets add-on pulls Campaign Manager data into a Google Sheet on a schedule, and Data Studio reads the sheet through the free native connector. An ETL tool such as Fivetran, Airbyte, Windsor.ai or Porter Metrics writes LinkedIn data into BigQuery tables each day. Manual export means downloading a CSV from Campaign Manager and uploading it.

How much does a LinkedIn Ads connector for Data Studio cost?

Entry plans run from free to about $49 a month. I read these prices on each vendor's own pricing page in October 2026; they change often, so check before you buy.

A free plan can be enough for one ad account. The cost question changes when you add Google Ads and Meta to the same vendor, because most entry plans cap data sources. Google Ads never needs a paid connector, since Data Studio connects to it natively, so count only the non-Google platforms when you size a plan.

How do you connect LinkedIn Ads to Data Studio step by step?

The clicks take ten minutes. The decisions around them decide whether the report still works next year, so the checklist below includes them.

The most important decision is which LinkedIn login authorises the connector. Data Studio data sources run on the owner's credentials by default, which is why viewers do not need LinkedIn access. If that login belongs to an agency contact or an employee who later leaves, the data stops the day their Campaign Manager access is removed, and Data Studio does not warn anyone. Authorise with a company-owned profile that holds a role on every ad account, and record who it is.

• Check roles: the authorising profile needs access to each ad account in Campaign Manager; reporting access requires the r_ads_reporting permission on LinkedIn's side.
• Add the connector: in Data Studio create a data source, search the gallery for your vendor, and sign in to the vendor if asked.
• Authorise LinkedIn: approve the permissions on LinkedIn's own consent screen with the company-owned login.
• Select accounts: pick ad accounts, then decide between one data source per account or a combined source with an account field.
• Choose fields deliberately: spend, impressions, clicks, landing page clicks, leads and conversions first; add demographic breakdowns as a separate data source.
• Reconcile: compare last month's spend and clicks at account level with Campaign Manager before sharing.
• Share the report, not the data source, with people who only read it.

What LinkedIn API limits break Data Studio reports?

Every connector reads LinkedIn through the same Marketing API, so its rules apply whatever vendor you choose. These come from LinkedIn's Reporting documentation on Microsoft Learn (version 202610, updated June 2026). They explain why a LinkedIn report can break or drift with no change on your side.

Retention is split. Performance data by account, campaign or creative is kept for ten years. Professional demographics data, such as job title, job function, seniority, industry and company, is kept for two years. Daily data is kept for six months; beyond that, requests are rounded to whole months. A year-on-year chart by seniority works today and quietly loses its left side as the months pass.

Demographic results are thinned for privacy. LinkedIn returns only the top 100 demographic values per creative per day, drops values with fewer than 3 events, and returns nothing for ads that reached too few members. Some metrics, including conversion value, card metrics and approximate member reach, are not available with demographic breakdowns at all. Demographic metrics can also arrive 12 to 24 hours late, while campaign metrics are near real time.

Responses are capped at 15,000 rows and the endpoint does not paginate, and LinkedIn throttles any app that requests more than 45 million metric values in five minutes. Large accounts pulling daily data by creative and job title hit these limits, which shows up in Data Studio as partial tables or errors.

Why don't my LinkedIn Ads numbers match Data Studio?

Usually the report is asking a slightly different question from Campaign Manager. LinkedIn's own documentation says demographic metrics are approximate, so you will see small differences when you compare 7 days against 8 days, add daily figures against a full-period total, or add up campaigns against the account total. Its advice is to pull a full period at the highest level you need rather than summing smaller pieces, and that is how I build LinkedIn charts.

Work through these checks in order before blaming the connector.

• Level of aggregation: a scorecard that sums campaign rows will not equal the account figure for approximate metrics; use account-level data for totals.
• Daily versus period totals: summing daily demographic rows drifts from a single full-period request.
• Conversion rule windows: LinkedIn attribution windows are set per conversion rule, and API-created rules accept post-click windows of 1, 7, 28, 30 or 90 days (180 and 365 for some lead and purchase types).
• Time zone and date range: Data Studio's date range and the ad account's reporting dates may cut days differently.
• Currency: costInLocalCurrency is each account's currency; summing accounts in different currencies gives nonsense.
• Non-targeted companies: company breakdowns can include companies you never targeted, because members change jobs, work at two firms, or audience expansion was on.
• Late demographic data: the last 12 to 24 hours may still be filling in.

Why did my LinkedIn Ads connector stop working?

The most common cause is an expired authorisation. According to LinkedIn's OAuth documentation, access tokens last 60 days and refresh tokens last 365 days, after which the member must sign in and approve the app again. A connector that refreshes properly keeps working for a year, then fails on the anniversary unless someone re-authorises it. Put a calendar reminder against the date you first connected.

The second cause is LinkedIn's versioned API. LinkedIn retires old Marketing API versions on a published schedule; its reporting documentation currently warns that version 202511 will be sunset on November 16, 2026. Reputable connector vendors update before each sunset, but a home-built Apps Script or Python job pinned to an old version will simply stop. If you run your own script, check its LinkedIn-Version header now.

The third cause is people. A removed Campaign Manager role, a renamed ad account or a new account that was never added to the data source all produce empty charts with no error. Data Studio does not alert you when a connector breaks, so a simple weekly check of last week's spend against Campaign Manager is worth keeping.

Should LinkedIn Ads data go through BigQuery?

Yes, if you need more than two years of demographic history, report pipeline by company from your CRM, or run several ad accounts. No, if one account and current-quarter campaign metrics are all you need; a connector is cheaper and simpler.

Because Google's transfer service has no LinkedIn source, the load runs through an ETL vendor or your own code. Load two tables rather than one: daily campaign and creative performance, which LinkedIn serves for years, and demographic breakdowns by month, which you must capture before the two-year window closes. Partition both by date, build a summary view with the columns your report needs, and point Data Studio at the view so queries stay small.

BigQuery also solves the CRM question. LinkedIn's own revenue attribution metrics require connecting Salesforce, Dynamics 365 or HubSpot to LinkedIn Business Manager, and the API serves them only for the last year. If your CRM data already sits in BigQuery, you can join LinkedIn spend to opportunities by company and campaign yourself and keep the history.

How do you report LinkedIn beside Google Ads, Meta and GA4?

Stack the platforms into one table with matching columns (date, platform, account, campaign, spend, impressions, clicks, leads) and report from that, rather than blending live connectors. Blends in Data Studio take at most 5 data sources and support equality joins only, and LinkedIn campaign names almost never match Google Ads or Meta names, so a blend on campaign quietly drops rows.

Keep LinkedIn's demographic data on its own page. Job function, seniority and company size have no equivalent in Google Ads or Meta, and because LinkedIn's demographic figures are approximate, mixing them into a cross-channel total produces a number nobody can reconcile.

Projects I've led at Greenwolf Tech Labs include marketing dashboards built on this pattern: multi-channel spend, leads and return across Google Ads, Meta, LinkedIn, GA4 and Search Console in one view, so a marketing lead stops opening five platform tabs every Monday.

When should you hire a consultant for LinkedIn Ads reporting, and when not?

Do it yourself if you run one LinkedIn ad account, report on campaign metrics only, and are happy with a vendor template. A free or entry connector plan and an afternoon is the right spend, and hiring anyone would be wasted money.

Bring in help when LinkedIn must sit beside several other platforms, when demographic or company reporting matters to sales, when you need history past LinkedIn's retention windows, or when the report must survive the person who built it. Those are design problems (owned credentials, a combined table, a warehouse, approximate-data labels) more than connector problems.

When I take on a LinkedIn Ads to Data Studio project, I start with a free review of your ad accounts, the decisions the report supports and any reports you already have. I recommend the cheapest route that will hold up, often a connector you already pay for, and quote a fixed price for the build. The reports, data sources and any BigQuery tables live in your accounts from the first day.