Google Ads
Connect Google Ads and manager accounts to Adrails, check permissions and the first sync, then use the same accounts from your AI assistant through MCP.
Connect Google Ads once in Adrails. The workspace can read campaign results and prepare changes, and your Google Ads MCP client uses the same connection.
Google Ads
Before connecting
You need an owner or administrator role in the Adrails workspace and a Google account with access to the customer accounts you want to use. Access can be direct or through a Google Ads manager account. A manager is a container for customer accounts, not a campaign account of its own.
You do not need to bring a Google Ads developer token. Adrails supplies the API integration; Google handles your sign-in.
Connect and verify
- Open Ad accounts and choose Add account.
- Choose Connect Google Ads. If the option is unavailable, read the reason shown on the card.
- Sign in with the Google identity that reaches your ad accounts and review Google's permissions screen.
- Return to Adrails. Check that the expected customer accounts appear, including accounts reached through a manager.
- In In use, enable the accounts you want to work with. Wait for their first sync before judging whether campaign data is missing.
- Open Analysis, select one of those accounts and a completed date range, then compare spend with Google Ads using the same dates, account time zone and currency.
Connecting does not publish a campaign or change its budget. A Google login and an Adrails workspace are different identities: being signed in to Google does not choose which workspace an AI client can access.
Permissions
| Permission | Purpose |
|---|---|
Google Ads (adwords) | Read customer accounts, campaigns and results, and apply supported advertising changes. Google uses the same scope for reads and writes. |
Data Manager (datamanager) | Send conversions through Google's Data Manager API when you configure that tracking workflow. This permission is optional for reading and managing campaigns. |
| OpenID and email | Identify the Google profile that authorized the connection. |
The provider scope is broader than a read-only MCP connection. Adrails separately checks the workspace role and the permissions granted to each AI client. Advertising proposals made through MCP need approval in Adrails. Automations you enable have their own configured limits.
Connect Claude, ChatGPT or another MCP client
After the account sync, follow Connect an AI client. Select the same workspace and grant Read workspace data for a first reporting check.
Try: “List the Google Ads accounts available in this workspace. For the account I select, compare spend and conversions in the last seven complete days with the previous seven. State the dates and freshness of the data. Make no changes.”
Check the account ID and dates in the answer. The tools reference explains accounts_list, performance_period and campaigns_structure. The Google Ads MCP server page covers keyword research, campaign builds and the approval flow.
Troubleshooting
- The account is absent: confirm the Google identity and its access in Google Ads. If it comes through a manager, confirm that customer is still linked to that manager. Reconnect after fixing access.
- The account exists but a report is empty: enable it in In use, check sync status and select dates with activity. Keep the account's currency and time zone when comparing reports.
- Permission was declined or expired: reconnect from Ad accounts and review the requested Google Ads permission. Missing Data Manager access affects conversion sending, not campaign reporting.
- The assistant cannot see it: check which Adrails workspace you selected on MCP consent. Switching workspace in the web app does not move an existing MCP connection.
Stop using or disconnect
Switch an account off in In use to remove it from working views without removing the Google connection. To remove a connection, use its removal action in Ad accounts and review the confirmation. Previously imported history can remain in the workspace.
You can also remove Adrails from your Google account's third-party connections. Revoke the MCP connection separately if you also want the assistant to lose access to the workspace.