Google Ads + ChatGPT: check your connection options.

There are two common tasks: using ChatGPT to help manage an existing Google Ads account, and buying ads that appear inside ChatGPT. This page covers the first. Copywriting from a brief or analyzing an uploaded report needs no live integration, but those workflows do not keep your campaign data in sync.

Installing Notfair in Claude does not install it in ChatGPT. Codex is also a separate client with its own setup guide. NotFair provides a hosted MCP endpoint; the AI client decides which transports, tools, and account permissions it supports. This custom setup is not yet verified end to end by NotFair. For a published connector with a dedicated installation guide, use Claude.

OpenAI currently documents full MCP, including write actions, for eligible Business and Enterprise/Edu workspaces on the web. Pro access is described as read/fetch in developer mode. Availability and permissions can change; use OpenAI’s current requirements linked below.

• Ask your workspace administrator whether you can create or use a custom MCP app. Once access is granted, enable developer mode under Settings → Apps → Advanced Settings, or from Workspace settings → Apps → Create where available.
• If the necessary controls are unavailable, use an exported report for analysis or follow our published Claude connector guide.

Sign in to NotFair, choose your workspace, and connect the Google identity that can access your Google Ads account. Confirm the selected customer IDs. NotFair hosts the Google Ads API integration, so customers do not apply for a separate Google Ads developer token.

• Hosted MCP endpoint: https://notfair.co/api/mcp/notfair
• Authentication: OAuth. Keep credentials out of chat messages.

Where your account permits it, open Apps or the equivalent Plugins settings, create a custom MCP app, enter the NotFair endpoint, and select OAuth. Complete sign-in and inspect the returned tool list. Settings labels vary by rollout. If discovery or sign-in fails, the connection is not ready.

• Confirm the intended workspace during NotFair sign-in.
• Verify that your plan exposes the read capabilities you need; do not assume write access from the presence of a server URL.

Select the app in a new chat and request the connected Google Ads customer IDs. Then request a campaign’s spend and conversions for a specific date range. Compare the answer with Google Ads using the same customer ID, dates, and time zone. A plausible summary without a successful tool call does not verify the integration.

• Check the account first, then the report.
• If the app does not appear or the tool call errors, return to app access and authentication settings before requesting account work.

A successful read does not establish permission to change campaigns. Only consider writes when your client and workspace expose supported actions. Review the exact account, target, and proposed edit before approving it. Check the resulting operation record; undo applies only to supported changes.

• Keep initial verification read-only.
• If you need a published NotFair connector today, use the Claude setup guide below.