Apple Ads to ChatGPT in 2026: 4 free ways to connect

boltTL;DR

To connect Apple Ads to ChatGPT:

1. Sign up free at portermetrics.com and connect your Apple Ads account with your Apple account.
2. 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 Apple Ads orgs/accounts with no usage limits on ChatGPT’s free plan. No credit card required.

What makes Porter different:

• 120+ Apple Ads metrics and dimensions, and the only MCP that includes attribution coverage in the same connection.
• Universal Apple Ads MCP. Read and analyze Apple Ads campaigns alongside Google Ads, GA4, Shopify, HubSpot, and 20+ more sources in one chat. Build cross-channel dashboards, blend attribution data, and run competitor analysis. Your whole Apple Ads operation runs from one chat.

Connect Apple 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 Apple 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 Apple 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 Apple Ads to Porter, point ChatGPT at the Porter MCP, and ask your first question.

1. Connect your Apple Ads data to Porter

Porter sits between Apple’s Apple Search Ads 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 Apple. In Porter, click Create → pick ChatGPT as the destination → select Apple Ads as the source → sign in with Apple to grant access to your orgs/accounts.

Select your orgs/accounts. Choose the Apple Ads orgs/accounts you want ChatGPT to query. When you select multiple orgs/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 orgs/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 Apple 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.

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 Apple Ads in plain English. ChatGPT calls Porter behind the scenes, pulls live data from Apple, 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, keyword optimization, client reporting, agency, e-commerce, cross-channel), jump to the prompts section below.

Alternative ways to connect Apple 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 Apple Ads data in front of ChatGPT, though. The most common alternatives are Apple Ads’ 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.

• 🔌 Apple Ads’ direct API — Talk to Apple’s Apple Search Ads API yourself. Maximum control, but you handle auth, rate limits and pagination — and you only get one source. (Apple 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 orgs/accounts or agencies running multi-org/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:

1. Open the Porter Metrics app page in ChatGPT (or search “Porter Metrics” in the apps gallery).
2. Click Connect and sign in with the same account you use in Porter.
3. Authorize it and ask your first Apple 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 Apple Ads’ direct API

Apple does not ship an official MCP for Apple Ads as of June 2026. All Apple Ads MCPs are third-party wrappers over the Apple Search Ads API.

If you’re building a product around Apple Ads — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Apple’s Apple Search Ads API yourself, or — where it exists — Apple Ads’ own official MCP. Apple does not ship an official MCP for Apple Ads as of June 2026. All Apple Ads MCPs are third-party wrappers over the Apple Search Ads API. Whichever route you pick, you still follow Apple’s rate limits & quotas. Either way you skip Porter and call Apple from your own code, from Codex, or from Apple Ads’ 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 Apple 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 Apple 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 Apple Ads into a Sheet, then let ChatGPT read the Sheet. You can automate the Apple Ads → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Apple Ads’ native UI for static analysis.

The trade-off to know. With the MCP path, ChatGPT calls Apple’s API directly and Apple 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.

Via Google BigQuery (for scale)

This is the path most people overlook — and it’s the one that saves you when your Apple Ads org/account gets serious. A single large advertiser or an agency managing 10+ orgs/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 Apple 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 Apple 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 orgs/accounts with millions of impressions, agencies running multi-org/account analysis across 10+ clients, or any team already using BigQuery as a data warehouse. Porter loads Apple Ads (and 25+ other sources) directly into BigQuery so you don’t have to build your own ETL.

Connecting Apple 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 Apple 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 Apple 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.

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 Apple Ads is connected to ChatGPT

Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Apple Ads data — from simple Q&A to full client-facing workflows.

1. Chat and ask questions directly

The simplest use case — and still the one 80% of marketers start with. Open ChatGPT, ask a question, get an answer grounded in live data.

It’s the fastest way to replace a daily Apple Search Ads dashboard check-in. But chat is table stakes — the interesting use cases come next.

2. Blend Apple Ads with your sales data (Stripe, HubSpot, Shopify)

This is where a 360° view gets real. When you connect Apple Ads and your revenue source (Stripe for SaaS, HubSpot CRM for B2B, Shopify for e-commerce), ChatGPT can map ad campaigns to actual closed-won deals or purchases — using UTMs, campaign names, and timestamps — and give you attribution that no platform-side number can.

ChatGPT handles the UTMs, campaign names, and timestamps mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.

3. Automated alerts and notifications on Slack or Gmail

With Codex you can turn Apple Ads monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Codex scheduled task that pulls performance every morning and pings you only when something actually needs attention.

No dashboards, no daily check-ins. The report comes to you — and only when it matters.

4. Client-ready presentations with live data (Gamma, HTML, PDF)

A common agency pain: you send clients a Data Studio link, Looker breaks, the client panics — and you spend an hour explaining a broken dashboard. With ChatGPT you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.

The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.

Apple 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 120 Apple Ads fields and 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 Apple Ads with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.

Prompts you can copy-paste today

Below are prompts organized by job: performance checks, keyword & search term optimization, client reporting, prompts for agencies managing multiple clients, prompts for e-commerce teams, and cross-channel prompts.

Performance checks

When you need a quick health check on your Apple Ads account.

Keyword & search term optimization

When you’re optimizing discovery and exact match campaigns.

Client reporting

When you need to draft or build reports for stakeholders.

Prompts for agencies managing multiple clients

When you’re overseeing multiple Apple Ads accounts.

Prompts for e-commerce teams

When you’re driving app installs for e-commerce or DTC apps.

Cross-channel prompts

When you need to blend Apple Ads with other marketing platforms.

Limits, safety, and best practices for Apple Ads via ChatGPT

Unlike Meta Ads or Google Ads, Apple Search Ads operates through a fully public, documented API with no history of punitive account bans for legitimate API usage. The closest thing to a “cautionary tale” in the Apple Ads ecosystem is not a ban story — it’s the silent pipeline failure. Marketers running high-volume reporting via custom scripts or MCP integrations have hit Apple’s undocumented rate ceilings during end-of-month reconciliation, causing incomplete data pulls that went unnoticed until dashboards showed suspiciously flat spend curves. The cost is not a suspended account; it’s a week of decisions made on stale data. This makes Apple Ads the safest major ad platform to connect via Claude, but also the one where “safe” can lull you into ignoring data-integrity checks.

Apple’s rate limiting is quota-based and communicated dynamically, not tool-based. Apple doesn’t ban or throttle accounts because you used Claude, an MCP server, or a third-party connector. It throttles because of how the API was used: bursty parallel requests, sustained high-frequency polling, or unauthenticated retry loops. The Apple Ads Campaign Management API confirms that rate limits exist and are detailed in the documentation, but Apple does not publish exact numerical thresholds such as requests per minute, hour, or day. Instead, the API returns standard HTTP 429 responses with Retry-After headers when limits are exceeded, and developers must implement exponential backoff to recover gracefully. Read-only reporting calls are safe. Aggressive write bursts (e.g., bulk bid changes across thousands of keywords) or parallel polling from multiple services without coordination are not.

The two patterns that lead to inaccurate Apple Ads reports

After reviewing official docs and community threads, two patterns come up again and again.

1. Parallel API bursts without backoff. Sending concurrent requests from multiple scripts, dashboards, or MCP instances to the same Apple Ads Org ID can trigger throttling even if each individual caller stays within reasonable volume. Apple’s rate limits are applied at the API-key or account level, and the thresholds are not documented publicly. When exceeded, the API returns HTTP 429 errors with Retry-After headers, but tools that don’t implement backoff will retry immediately, amplifying the problem and potentially causing extended lockouts. — developer.apple.com/documentation/apple_ads/calling-the-apple-search-ads-api

2. Programmatic writes at scale without campaign structure discipline. Using Claude Code or scripts to bulk-modify bids, budgets, or keywords across campaigns without Apple’s recommended semantics-based structure leads to unstable spend patterns and algorithmic confusion. Apple’s documentation recommends limiting bid adjustments to 20% increments per keyword and structuring campaigns around no more than 5 core campaign types (Brand, Category, Competitor, Discovery, and Exact Match). Violating these structural guardrails doesn’t trigger a ban, but it degrades campaign performance in ways that are hard to reverse — effectively “breaking” the account’s learning phase. — developer.apple.com/documentation/apple_ads

Both behaviors trigger rate throttling and data quality degradation. If you want to use ChatGPT for Apple Ads safely, stick to read-only reporting queries through a managed MCP like Porter’s, which batches requests and implements backoff automatically.

The 5-rule best-practice protocol

Based on Apple Ads’ documented policies and the behaviors that have actually caused data integrity issues — not guesswork:

• Batch your API calls and respect the 20% bid-adjustment ceiling. Apple’s algorithm is sensitive to large bid swings. Adjust one keyword’s bid by no more than 20% per change, then monitor performance before further modifications. This number is documented in Apple’s campaign management best practices as the threshold that maintains stable spend patterns without resetting the learning algorithm. — developer.apple.com/documentation/apple_ads

• Structure campaigns into no more than 5 core campaign types. Apple’s recommended semantics-based structure caps the top-level campaign taxonomy at five: Brand, Category, Competitor, Discovery, and Exact Match. Exceeding this creates overlap, internal competition, and degraded CPA trends. When querying via Claude, always include campaign_name filters that map to these five buckets to keep analysis aligned with Apple’s intended architecture. — developer.apple.com/documentation/apple_ads

• Limit custom product pages to 35 per app. Apple Ads allows associating custom product pages with Creative Sets for ad-group-level personalization. The platform supports up to 35 custom product pages per app. Exceeding this doesn’t trigger enforcement, but pages beyond 35 are ignored by the ad-serving system, leading to “broken” creative rotations where Claude-recommended variants never serve. — developer.apple.com/documentation/apple_ads

• Add exact-match negative keywords from your 3 core campaigns into Discovery. Apple’s Discovery campaign type is designed to surface new search terms, but it can cannibalize Brand, Category, and Competitor campaigns if negatives aren’t applied. The rule of three: extract your top exact-match keywords from Brand, Category, and Competitor campaigns and add them as negatives to Discovery. This prevents paying for traffic you already capture elsewhere and is the single most effective budget-protection rule in Apple Ads. — developer.apple.com/documentation/apple_ads

• Check Apple Ads recommendations daily — they refresh once per day. The Recommendations API and in-dashboard suggestions update on a 24-hour cycle. Checking more frequently wastes API calls and creates false urgency. Schedule your Claude-driven audit queries to run after Apple’s daily refresh (typically early morning Pacific time) to ensure recommendations and performance data are synchronized. — developer.apple.com/documentation/apple_ads

What Porter MCP does differently: it enforces read-only API access by default, eliminating the risk of programmatic write storms. All Porter Apple Ads queries use the Reporting API endpoints, not the Campaign Management API write endpoints, which means bid changes, budget adjustments, and campaign creation cannot be triggered accidentally through Claude prompts. Porter also implements request batching and per-account connection pooling, ensuring that parallel queries from multiple team members or automated reports are coalesced into a single throttled stream rather than independent bursts. That’s the behavior Apple’s automated systems handle gracefully — steady, predictable, read-only traffic with proper Retry-After backoff — and it’s why Porter MCP users have not reported throttling incidents even during high-volume month-end reconciliation workflows.

Frequently asked questions

Ready to chat with your Apple 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 Apple Ads account — you’ll be chatting with your campaigns in under five minutes.

rocket_launchStart free Porter trialopen_in_newOpen ChatGPT