Get help

Support

Two inboxes, both read by a person. Which one you want depends on whether the problem is technical or commercial. If you are not sure, send it to technical support and we will route it.

Who should I email?

Technical support

support@advisorppc.com

A connector that will not connect, an error you cannot get past, a tool returning the wrong data, an account that will not link, and data-deletion requests.

Billing and plans

contact@advisorppc.com

Invoices and payment problems, changing or cancelling a plan, quota and upgrade questions, agency and partnership enquiries, and anything commercial.

Security reports go to contact@advisorppc.com with SECURITY in the subject line, not to technical support. Details in the section at the bottom of this page.

Try this first

Two answers cover most of what reaches the technical inbox. A connector showing as disconnected is fixed by removing and re-adding it, and a 401 from opening the endpoint in a browser is expected rather than a fault. Both are explained on the troubleshooting page, which is worth two minutes before writing in.

What should I include?

The more of this you send, the more likely the first reply is a fix rather than a question.

  • What you asked. The prompt or request you gave the assistant, and what you expected to happen instead.
  • Which plan you are on. Free or paid, since a denial reads very differently depending on the answer.
  • Approximately when it happened, with your time zone. That is what lets us find the call in the logs.
  • Which assistant and which endpoint. Claude, Claude Code, ChatGPT, or Grok, and the endpoint you connected.
  • The account involved. The platform and the account name or ID, such as a Google Ads customer ID.
  • The exact message you saw. Copy the text rather than describing it. Our error screens print a reference code near the bottom that points straight at the cause.
  • The email on your AdvisorPPC account, so we can find the right tenant.

Never send passwords, OAuth tokens, API keys, or authentication codes to either address. We never need them, and no one from AdvisorPPC will ask you for one.

What happens next?

You get a reply telling you what we found, or what we still need. Issues affecting live spend are picked up first. If diagnosing the problem means looking inside your workspace, we ask you before we do, and we look only at what the issue requires.

Reporting a security issue

Email contact@advisorppc.com with SECURITY in the subject line. This is the disclosure address published in our plugin repository, so use it rather than technical support. Security reports never go in a public issue tracker, a public forum, or a social post: please give us a chance to fix the problem before any detail is published. Include what you found, how to reproduce it, and what you think the impact is. Do not include credentials of any kind, and please do not test against another customer's account.

Privacy, deletion, and legal

Data deletion requests go to support@advisorppc.com, sent from your account email, and we remove your stored connection records. Revoking AdvisorPPC from your Google account permissions also stops the stored tokens from working, independently of anything on our side. The privacy policy and terms of service apply to every connection, and the security page describes what the connector can and cannot do.