Google Ads to Claude: first-read checklist Adrails | Updated October 15, 2026 https://adrails.ai/connect/google-ads-to-claude PURPOSE Verify one read-only account comparison before asking for advertising changes. The worked example is synthetic. This file does not connect an account or run tools. BEFORE CONNECTING [ ] I can access the intended Adrails workspace and Google Ads account. [ ] The advertising account is connected in Adrails and its initial sync is complete. [ ] My assistant plan and workspace policy allow this custom connection. [ ] I know the conversion event and attribution scope I want to review. CONNECT 1. Open Customize, then Connectors, choose Add, then Add custom connector 2. Name it Adrails, paste https://adrails.ai/api/mcp as the server URL and keep Use Claude's published identity under OAuth client 3. Add the connector, then connect it: Adrails opens, you sign in, choose the workspace and the permissions, and choose Allow access 4. In a conversation, open the plus menu, then Connectors, enable Adrails and ask your first question For the first check, read access is sufficient. Do not enable advertising writes just to read performance. Current client documentation: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp Adrails setup: https://adrails.ai/docs/mcp/connect FIRST PROMPT List the Google Ads accounts available in this workspace. Show their IDs, currencies and time zones. Make no changes. SECOND PROMPT For account [replace with the returned account ID], compare October 5 to 11, 2026 with September 28 to October 4, 2026. Show spend, purchases, purchase revenue, CPA and ROAS. State currency, time zone, purchase definition and data freshness. Identify missing data and conversion delays. Make no changes. Replace the example dates with two completed, comparable periods for your review. VERIFY THE ANSWER [ ] Account ID matches the account I selected. [ ] Dates, currency and time zone match the source report. [ ] Purchases are separated from leads and other conversion events. [ ] CPA = spend / purchases; ROAS = attributed purchase revenue / spend. [ ] Missing or undefined values are unavailable, not silently set to zero. [ ] The answer identifies what was measured and what still needs checking. [ ] No campaign, budget or delivery setting was changed. WORKED EXAMPLE Example store (synthetic); USD; America/New_York. Previous: 2000 spend, 100 purchases, 8000 purchase revenue. Current: 2400 spend, 80 purchases, 6400 purchase revenue. Spend rose 20% while purchases fell 20%. CPA rose from $20 to $30, a 50% increase. Check conversion lag and campaign-level changes before deciding what caused it. The paired example CSV preserves the dates and calculations. It is an illustrative review output, not a recorded response from a live customer account or an MCP payload. TROUBLESHOOT No custom connector option: check your assistant's plan and organization policy. Authentication required: reconnect from the assistant and choose the right workspace. No accounts: check the separate advertising connection and sync in Adrails. Tool missing: enable Adrails for this conversation and refresh the tool list. Numbers differ: align dates, conversion definition, currency, time zone and freshness. Do not paste credentials into prompts or share an account report without authorization. MY REVIEW Account ID: Periods: Currency and time zone: Conversion definition and attribution scope: Data last synchronized: Evidence checked: Unknowns: Next action and owner: Next review date: