Get help
Troubleshooting
The failures below are the ones people actually hit. Most are one action away from fixed, and the first one is not a failure at all.
The connector URL shows 401 Unauthorized in my browser
This is expected. Nothing is broken.
Opening http://localhost:8080/claude in a browser tab returns 401 Unauthorized because it is an MCP protocol endpoint for an AI client, not a web page. It has no HTML to serve and it refuses unauthenticated requests by design. The same is true of the ChatGPT and Grok endpoints.
Paste the URL into your assistant's Add custom connector field instead. If you want a page you can read in a browser, you are already on it: the documentation is the human facing side of this service.
The connector shows as disconnected
Remove the connector and add it again.
Re-adding runs a fresh OAuth flow and registers a new client. That is the single fix for most connection states, because it clears an approval that expired, a registration left over from an earlier attempt, and a client that was never fully bound to your account. It costs about thirty seconds and never touches your Google authorization, so you do not have to reconnect your ad accounts afterwards.
Before re-adding, confirm the endpoint is exactly right, with no trailing characters and no path added. The correct values are on the getting started, ChatGPT, and Grok pages.
This client_id belongs to a different account
Re-add the connector so a fresh client is registered.
Each registered client is claimed by the first AdvisorPPC account that approves it, and it stays bound to that account. If you signed in with a different email, or someone else approved the connection on a shared machine, the client is bound elsewhere and cannot be reassigned. Removing and re-adding the connector registers a new client, which then binds to whichever account approves it.
When you re-approve, check the email shown on the consent screen. Binding to the wrong account is almost always a second sign-in address rather than a fault in the connector.
A tool call was denied on the free plan
Either the monthly allowance is used up, or the tool is paid-only.
Denials are deliberate and always explain themselves. There are two causes:
- The monthly quota is exhausted. The free plan allows 100 tool calls per month. One call is one tool invocation, not one message, so a long audit conversation spends several. The allowance resets monthly, or you can upgrade for a higher quota.
- The tool changes an account. The free plan is read-only. Budget and campaign management are write operations that a paid plan unlocks. On a read-only plan the write tools are not advertised at all, so an assistant may say a capability is unavailable rather than that it was denied.
Either way the call is refused before anything reaches Google, so a denial never leaves a half applied change. Details on plans and limits.
The assistant cannot see any of my accounts
Connecting the connector and authorizing Google are two separate steps.
Approving the AdvisorPPC consent screen proves who you are. It does not grant access to any advertising account. Open dashboard settings and connect Google, then check that the accounts you expect were included in the consent screen. If you manage clients under a Google Ads manager account, authorize the manager account so the accounts beneath it become reachable.
Where do I get help?
If none of the above fixes it, email technical support at support@advisorppc.com. Include what you asked the assistant, which plan you are on, and roughly when it happened with your time zone. The support page lists everything worth sending so the first reply can be a fix rather than a question.
Billing, plan and partnership questions go to contact@advisorppc.com instead, and security reports go to that same address with SECURITY in the subject line.