Reconnecting
When Google stops accepting AdCopilot's sign-in, when your assistant needs to pick up tools a release added, or when Connections says it needs re-authorization — how to fix each without changing anything in your accounts.
There are two different things to reconnect, and they have different fixes.
| What you see | What needs reconnecting | Fix |
|---|---|---|
| "Google is no longer accepting this connector's sign-in" | Your Google sign-in | Reconnect Google |
| A tool is missing, or AdCopilot says tools are "available but not in this connection's tool list" | Your AI assistant's connection | Reconnect your assistant |
| Connections marks your assistant Re-authorization needed | Your AI assistant's approval | Approve your assistant again |
Reconnect Google
Google sign-ins can stop working: you changed your Google password, removed AdCopilot from your Google account's connected apps, or your access to an account changed. AdCopilot then says:
Google is no longer accepting this connector's sign-in, so it cannot reach your ads accounts. Reconnect your Google account at … — sign in, one click, and the connector URL does not change.
Open the link in that message, or the same link in the email AdCopilot sends when it finds the sign-in refused, sign in to AdCopilot if it asks, and complete the Google sign-in. The link names your workspace, never a key, so it is safe in a chat. AdCopilot checks every stored Google sign-in each night, so that email can reach you before you next ask your assistant for anything. In the dashboard, Connections marks the affected Google login Needs reauth until you do.
If the sign-in belongs to a teammate, AdCopilot says the connection's owner needs to reconnect it, and emails them.
Until you reconnect, AdCopilot cannot read or change the accounts behind that sign-in. Other connections keep working.
Reconnect your assistant
Your assistant keeps the tool list it was given when you approved it. After an AdCopilot release adds tools, it needs to fetch the list again. AdCopilot says so in the chat, with the steps for your assistant:
- Claude: open Customize → Connectors (layouts vary; the Claude guide has a direct link), choose AdCopilot, press Disconnect, then connect it again.
- Claude Code: run
/mcpand reconnect AdCopilot. If you added it by hand rather than with the plugin, you can also remove it and add it again withclaude mcp add --scope user --transport http adcopilot https://mcp.adcopilot.cloud/mcp. - ChatGPT: open the AdCopilot app in ChatGPT's settings and reconnect it. If its tools still do not appear, remove the app and create it again with the same URL, as in Connect ChatGPT.
- Anything else: reconnect AdCopilot in its connector settings, or remove it and add it again.
Or skip the AI app entirely: in the dashboard, open Connections and Revoke the app. The next thing it asks for gets the full set of permissions.
Then start a new chat. Reconnecting never changes your campaigns.
Connecting another Google product is different: there is nothing to do in your AI app. When you approve your assistant, AdCopilot asks for every Google product it serves, so a product you connect later is already in its tool list and works on the next request.
Approve your assistant again
Connections marks an app Re-authorization needed when its approval does not cover a product your workspace has connected: for example, it was approved when AdCopilot asked for Google Ads alone. AdCopilot says so in the chat too. Revoke it under Connections and approve it when it next asks, or remove the AdCopilot connector in your AI app and add it back. With the Claude Code plugin, use Revoke: adding the connector again by hand hides the plugin's.
Still stuck? See Reconnect troubleshooting.
Run your first audit
Say "Get me started with AdCopilot" — AdCopilot reads what you have connected, tells you what state your account is in, and gives you the next step. Then run the read-only morning audit or a full audit.
Connect your assistant
One connector URL for every AI assistant. Pick yours — ChatGPT, Claude, Claude Code, Codex, Gemini CLI or any MCP client — and follow its steps.