To connect LinkedIn Ads to ChatGPT:
- Sign up free at portermetrics.com and connect your LinkedIn Ads account with your LinkedIn account.
- In ChatGPT, click + → Connectors → Manage connectors → Add custom connector, name it Porter, paste
https://mcp.portermetrics.com/mcp, then click Add and authenticate with Google.
That’s it, you’re connected. Porter’s free plan covers up to 3 LinkedIn Ads ad accounts with no usage limits on ChatGPT’s free plan. No credit card required.
What makes Porter different:
- Read + write, safely. Porter’s MCP lets you create, update, and pause LinkedIn Ads campaigns, adjust budgets and targeting, and manage creatives from inside ChatGPT, through deterministic code components. Nothing hallucinates, and built-in rate limiting keeps your ad accounts safe from throttling.
- 800+ LinkedIn Ads metrics and dimensions, and the only MCP that includes attribution coverage in the same connection.
- Universal LinkedIn Ads MCP. Hosted white-label dashboards and client portals, competitor tracking with creative analysis, idea validation with Google Trends and keyword data. Your whole LinkedIn Ads operation runs from one chat.
Prerequisites
- A Porter Metrics account with your LinkedIn Ads account connected (free tier is enough to try it end-to-end)
- A ChatGPT account — the free plan works for ChatGPT Web; a Pro subscription is needed for Codex and Desktop MCP features
- Admin or standard access to the LinkedIn Ads ad accounts you want to connect
Connect LinkedIn Ads to ChatGPT with MCP
For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for LinkedIn Ads.
MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Codex and others access and use external APIs — the things that make tools like LinkedIn Ads work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.
The full setup takes under 5 minutes and breaks into three moves: connect LinkedIn Ads to Porter, point ChatGPT at the Porter MCP, and ask your first question.
1. Connect your LinkedIn Ads data to Porter
Porter sits between LinkedIn’s Marketing API and ChatGPT. It handles OAuth, rate limiting, pagination and all the plumbing so ChatGPT only ever sees clean, structured data.
Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.
Connect your LinkedIn. In Porter, click Create → pick ChatGPT as the destination → select LinkedIn Ads as the source → sign in with LinkedIn to grant access to your ad accounts.

Select your ad accounts. Choose the LinkedIn Ads ad accounts you want ChatGPT to query. When you select multiple ad accounts under a single connection, Porter automatically blends their data together so you can query them as one.

Optional: enable automatic BigQuery storage if you’re connecting multiple ad accounts with large data volumes. This keeps ChatGPT’s responses fast even at scale.
2. Connect the MCP to ChatGPT
Porter’s MCP URL is what you paste into ChatGPT. Once added, ChatGPT can query LinkedIn Ads data on demand in any conversation.
Go to chatgpt.com and click the + icon in the chat input to open the tools menu.

In the menu that opens, hover over Connectors and click Manage connectors.

In the Connectors panel, click the + button at the top of the list to start adding a new connector.

Pick Add custom connector from the dropdown that appears.

A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.

In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.

Click Add at the bottom right of the dialog. ChatGPT opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.

Once the authorization finishes, you’ll see Porter’s tools appear in the connectors panel. You’re ready to start asking questions (and, for connectors that support it, running actions).

For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.
3. Start building questions and dashboards
With Porter connected, open a new ChatGPT chat and ask anything about your LinkedIn Ads in plain English. ChatGPT calls Porter behind the scenes, pulls live data from LinkedIn, and answers with tables, charts, or summaries.
Try one of these to verify the setup is working:
For a full catalogue of copy-paste prompts organized by use case (performance, fatigue, budget, agency, B2B, lead gen, cross-channel), jump to the prompts section below.
Alternative ways to connect LinkedIn Ads to ChatGPT
Porter MCP is the path we just walked through and the one we recommend for most marketers. It is not the only way to get LinkedIn Ads data in front of ChatGPT, though. The most common alternatives are LinkedIn Ads’s direct API, a live Google Sheets bridge or CSV upload, and BigQuery for scale. Each has trade-offs, so pick the one that fits how your team already works.
- 🔌 LinkedIn Ads’s direct API — Talk to LinkedIn’s Marketing API yourself. Maximum control, but you handle auth, rate limits and pagination — and you only get one source. (LinkedIn doesn’t ship an official MCP yet.)
- 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
- 🗄️ Google BigQuery — For large ad accounts or agencies running multi-account analysis. BigQuery aggregates; ChatGPT only queries pre-built summaries.
Via the Porter Metrics app in the ChatGPT marketplace
If you’d rather not paste a connector URL, install Porter straight from ChatGPT’s app gallery — it’s the same Porter connection behind the scenes, published as an approved ChatGPT app:
- Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
- Click Connect and sign in with the same account you use in Porter.
- Authorize it and ask your first LinkedIn Ads question — same live data as the MCP.
The trade-off to know: the marketplace app only updates after each ChatGPT review cycle, while the MCP updates the moment Porter ships. If you want every new tool and data source immediately, use the MCP; if you want the one-click install and don’t mind waiting for new features, the marketplace app is the shortest path — including write actions through your connected Porter account.
Via LinkedIn Ads’s direct API
If you’re building a product around LinkedIn Ads — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to LinkedIn’s Marketing API yourself, or — where it exists — LinkedIn Ads’s own official MCP. LinkedIn doesn’t ship an official MCP yet, so going direct means writing API calls yourself in Codex or your own scripts. Whichever route you pick, you still follow LinkedIn’s rate limits & quotas. Either way you skip Porter and call LinkedIn from your own code, from Codex, or from LinkedIn Ads’s own connector.
The trade-off to know. Going direct gives you maximum control and the freshest possible data — every endpoint, every parameter, no abstraction layer in between. But you’re now responsible for OAuth flows, refresh tokens, rate limits, pagination, schema changes, and error retries. And critically, you only get one source. The moment you also want Google Ads, GA4 or Shopify in the same conversation, you’re back to building (or stitching together) more integrations.
When this makes sense: engineering teams that need a single source with full control, products that ship LinkedIn Ads data as a feature (where you own the integration anyway), or one-off scripts where you don’t mind writing the auth and pagination code yourself. For marketers who want to ask questions in plain English and blend LinkedIn Ads with the rest of their stack in a single conversation, the Porter MCP path is dramatically less work.
Via Google Sheets (live Sheet or manual CSV)
If your team already lives in Google Sheets — or you want a paper trail before ChatGPT touches anything — feed LinkedIn Ads into a Sheet, then let ChatGPT read the Sheet. You can automate the LinkedIn Ads → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from LinkedIn Ads’s native UI for static analysis.
The trade-off to know. With the MCP path, ChatGPT calls LinkedIn’s API directly and LinkedIn does the filtering and aggregation on its side — clean and deterministic. With the Sheets path, ChatGPT aggregates inside the Sheet itself, which can introduce hallucinations on totals, averages, and joins when you have thousands of rows. The upside is speed: for very large date ranges or historical analysis, a pre-built Sheet is dramatically faster than live API calls.
When this makes sense: finance teams that want to review numbers before ChatGPT acts on them, agencies already delivering client reports in Sheets, historical analysis across years of data, or any case where you care more about speed than real-time freshness.
Read the full Sheets tutorial →
Via Google BigQuery (for scale)
This is the path most people overlook — and it’s the one that saves you when your LinkedIn Ads advertiser gets serious. A single large advertiser or an agency managing 10+ ad accounts will hit API rate limits and latency problems querying ChatGPT directly. ChatGPT will literally tell you it’s taking too long or timing out on big pulls.
BigQuery fixes that. You load LinkedIn Ads data into BigQuery tables on a schedule, then connect BigQuery to ChatGPT — either through a BigQuery MCP or via Codex with SQL queries. Instead of asking ChatGPT to pull raw LinkedIn Ads data, you let BigQuery aggregate into small, optimized tables, and ChatGPT only queries the summarized output. Scale problem solved.
When this makes sense: enterprise ad accounts with thousands of leads, agencies running multi-account analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads LinkedIn Ads (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.
Read the full BigQuery tutorial →
Connecting LinkedIn Ads to Codex
Most marketers lump ChatGPT and Codex together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with LinkedIn Ads data seriously.
ChatGPT is a chat interface. You ask a question, ChatGPT pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.
Codex is ChatGPT running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for LinkedIn Ads, a whole category of work becomes possible.
What Codex unlocks that ChatGPT alone cannot
This is where the MCP ecosystem pays off most. Because Codex can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.
Feed Codex your LinkedIn Ads targets and goals — CPA goals, daily budgets, ROAS thresholds — and ask it to generate a custom ROI dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load.
Best for:agencies that want white-label client dashboards without Looker or Data Studio dependencies.
Combine your own LinkedIn Ads performance from Porter with competitor landing pages and live ads from the Meta Ad Library scraped via Firecrawl. Codex stitches both into a weekly competitive intelligence report — your numbers next to their creative angles and pricing, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning.
Best for:in-house teams that need market context, not just internal numbers.
Use Airtable or Notion as the schema, Porter as the data source. Codex keeps every page populated with current spend, CPA, and ROAS for every ad account — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account.
Best for:agencies and ops teams onboarding analysts or rotating account managers frequently.
A Codex routine on cron pulls LinkedIn Ads via Porter, evaluates thresholds — CTR drops below 1%, daily spend spikes 2× the trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look.
Best for:any team that’s ever discovered a problem 48 hours too late because nobody opened the report.
Bottom line: ChatGPT is for quick questions and ad-hoc dashboards. Codex is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.
Use cases: what you can actually do once LinkedIn Ads is connected to ChatGPT
These use cases run on real LinkedIn Ads ad accounts, from full campaign management to client-facing reporting.
1. Manage campaigns from the chat
The biggest shift from a dashboard: ChatGPT does not just read your account, it operates it. Create, update, and pause LinkedIn Ads campaigns, adjust budgets and targeting, and manage creatives through Porter’s deterministic components, with built-in rate limiting so your account stays safe. One habit to keep for every prompt that changes the account: ask ChatGPT to show the change and wait for your confirmation.
2. Manage budgets and pacing
Adjust daily and total budgets, monitor spend pacing, and reallocate budget across campaigns based on performance — all from a chat prompt.
3. Upload and manage creatives
Create, update, and manage LinkedIn Ads creatives including Sponsored Content, carousel ads, and video ads. All creative changes are created in PAUSED status by default for review.
4. Reporting: questions, dashboards, alerts and client decks
Condense Q&A + blends (Stripe, HubSpot, Shopify) + alerts Slack/Gmail + decks Gamma/HTML/PDF into hosted dashboards or client decks.
LinkedIn Ads fields and metrics you can query with ChatGPT
Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives ChatGPT access to 800 LinkedIn Ads metrics across every reporting level, plus breakdowns by audience, placement, device, and geography. And the same MCP URL also unlocks 25+ other sources — so ChatGPT can blend LinkedIn Ads with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.
Prompts you can copy-paste today
…organized by job: campaign management, budgets and pacing, creative management, agencies, B2B marketers, lead generation & ABM teams, and cross-channel blends.
Every prompt that changes the account has the safety habit built in: review first, then apply.
Campaign management
For marketers who need to create, update, pause, and manage LinkedIn Ads campaigns directly from ChatGPT.
Budgets and pacing
For teams monitoring spend, adjusting budgets, and optimizing pacing across campaigns.
Creative management
For teams managing Sponsored Content, carousel ads, video ads, and creative performance.
For agencies
Agencies managing multiple LinkedIn Ads accounts need fast client reporting, anomaly detection across portfolios, and segment comparisons.
For B2B marketers
In-house B2B marketers optimizing pipeline efficiency and audience quality on LinkedIn.
For lead generation & ABM teams
LinkedIn Ads is B2B-native. This section covers lead gen form optimization and account-based marketing workflows.
Cross-channel
Blending LinkedIn Ads with CRM, web analytics, and other ad platforms for full-funnel attribution.
Limits, safety, and best practices for LinkedIn Ads via ChatGPT
No public Reddit threads, news articles, or forum posts documenting irreversible LinkedIn Ads API bans were found between 2024 and 2026. LinkedIn’s enforcement model is throttle-first, not ban-first. The real-world “horror story” is operational, not existential: a demand-gen team running a quarter-end analysis triggers the daily request quota, receives HTTP 429 responses, and loses 6–12 hours of automated reporting until the quota resets at midnight UTC. The cost is not a suspended account—it is missed optimization windows and stale Claude insights during high-stakes reporting periods.
LinkedIn’s rate-limiting enforcement is quota-based and application-scoped, not tool-based. LinkedIn does not ban ad accounts because you connected Claude or an MCP server. It throttles API keys that exceed their daily or per-minute call allocations. The platform tracks two independent quotas: (1) an application-level total across all users of your app, and (2) a member-level total per authenticated LinkedIn user token. Both reset at midnight UTC. When you approach the application-level ceiling, LinkedIn sends an email alert; when you exceed it, the API returns HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. Read-only analytics usage within quota is safe. Bursty, unbatched, or parallelized API traffic is not.
The two ways to burn through your LinkedIn Ads quota
After reviewing official docs and community threads, two patterns come up again and again.
1. Unbatched, parallel API bursts during reporting. Making individual API calls for every campaign, ad group, and creative simultaneously—instead of using batched or filtered endpoints—burns through the 500-call daily quota in minutes. This triggers HTTP 429 throttling and leaves the integration offline until UTC midnight. . Use date-range filters and request only the specific fields you need.
2. Ignoring rate-limit headers and retrying immediately. When LinkedIn returns HTTP 429, the X-RateLimit-Reset header contains the Unix timestamp when the quota refreshes. Retry loops that ignore this header and hammer the API every few seconds waste quota and extend the blackout window. The correct pattern is exponential backoff with jitter, respecting the Retry-After or X-RateLimit-Reset value. — Microsoft Learn: LinkedIn API Rate Limits
3. Requesting write scopes when read-only analytics is the goal. LinkedIn Marketing API scopes are granular. Asking for r_ads (read ads) plus unnecessary w_ads (write ads) or r_ads_reporting scopes increases token privilege and audit surface area without benefit. If the integration only reads performance data, minimize scopes to reduce both security risk and potential compliance scrutiny. — Stitchflow: LinkedIn Ads API Guide
Both behaviors trigger quota throttling. If you want to use ChatGPT for LinkedIn Ads safely, batch your requests, respect rate-limit headers, and use minimal scopes.
The 5-rule scaling protocol
Based on LinkedIn Ads’s documented rate limits and quotas and the behaviors that have actually caused throttling — not guesswork:
-
Batch your requests and filter by date range. LinkedIn’s standard Marketing API quota is 500 calls per day per application (resetting at midnight UTC), with some endpoints limited to 100 calls per minute. Requesting one record per call burns this quota in under an hour for mid-size accounts. Porter MCP batches requests and applies date-range filters automatically, keeping call volume well below the threshold. — Microsoft Learn: LinkedIn API Rate Limits
-
Monitor the ~75% quota alert and stop before the ceiling. LinkedIn sends an email alert when your application-level quota hits approximately 75% consumption. Treat this as a hard warning: pause non-essential syncs, defer exploratory queries, and let high-priority reporting finish. Ignoring the alert means hitting the wall at 100% and waiting for UTC midnight. — LiSeller: How to Handle LinkedIn API Rate Limits
-
Respect HTTP 429 and back off exponentially. When throttled, LinkedIn returns HTTP 429 with
X-RateLimit-Reset. Do not retry blindly. Implement exponential backoff starting at 1 second, doubling to 2s, 4s, 8s, 16s, 32s, 64s, and capping at ~5 minutes with random jitter. This maximizes the chance of success on the next quota window while avoiding additional penalty. -
Use read-only scopes and audit token privileges quarterly. Grant the minimum viable scopes (
r_ads,r_ads_reporting,r_basicprofile). Avoidw_adsorw_organization_socialunless you are explicitly creating or editing campaigns via API. Reviewing scopes every 90 days catches scope creep from early experiments and reduces both security exposure and compliance risk. — Stitchflow: LinkedIn Ads API Guide -
Cache reporting data and avoid real-time polling. LinkedIn Ads reporting data has a freshness delay of several hours (commonly 4–6 hours for final metrics). Polling every 15 minutes wastes quota on stale data. Cache results and sync once or twice daily for historical reporting, or every 4 hours for active campaign monitoring. Porter MCP caches and deduplicates automatically, reducing redundant API calls by .
What Porter MCP does differently: it enforces these limits and safeguards at the platform level. Porter’s LinkedIn Ads connector is read-only by default—no write scopes are requested, eliminating the risk of accidental campaign edits or scope overreach. Requests are automatically batched and filtered by date range and account, keeping daily call volume well below the 500-call application quota. Rate-limit responses trigger built-in exponential backoff with jitter, so throttling never cascades into a hard failure. Per-account caching prevents redundant polling, and sync frequency is configurable (hourly, twice daily, or daily) to match LinkedIn’s data-freshness reality rather than wasting quota on premature polls. That’s the behavior LinkedIn’s automated systems handle gracefully: predictable, scoped, batched, and within quota.
Frequently asked questions
Ready to chat with your LinkedIn Ads?
Open ChatGPT, add the Porter connector, and ask your first question. If you don’t have Porter yet, start a free trial and connect your LinkedIn Ads account — you’ll be chatting with your campaigns in under five minutes.
rocket_launchStart free Porter trialopen_in_newOpen ChatGPT