Approval page and connection errors

When an assistant connects, it opens AdCopilot's approval page, Let <assistant> use your AdCopilot?, with Approve and Cancel. If you belong to more than one workspace, pick one under Workspace first: the assistant works only in that workspace. A Heads up box may say a Google product isn't connected yet. That is not an error: you can connect it from the dashboard after approving.

Approve does nothing

What you see. You press Approve on "Let Cursor use your AdCopilot?" and nothing happens. The page stays, Cursor never connects, and pressing again does the same.

Why it happens. After Approve, AdCopilot sends your browser back to the address your assistant registered, and Cursor's address forwards the browser on from there: from www.cursor.com to cursor.com, and on again. The approval page's security settings used to stop the browser on one of those forwards without showing an error. AdCopilot now sends you back through a short Returning you to Cursor… page, which no forward can stop, so Cursor's Approve completes.

Fix.

1. In Cursor's MCP settings, remove AdCopilot and add it again.
2. Press Approve once on "Let Cursor use your AdCopilot?". Cursor connects. If Returning you to Cursor… stays on screen, press Continue to Cursor.

The earlier tries changed nothing in your Google accounts.

If it persists. If Approve still does nothing, in Cursor or another assistant, write to [email protected] with the assistant's name and version, your browser, and the time. Don't send what is in the browser's address bar after signing in: it can hold a sign-in code.

"That connection request isn't valid"

What you see. A page titled That connection request isn't valid, marked "Nothing was changed", with one reason and "What to do: Start the connection again from inside the app you were connecting".

Why it happens, and the fix, by the reason on the page:

If it persists. Write to support with the reason on the page, the assistant, and the time.

The assistant reached the wrong workspace

What you see. The assistant lists AdCopilot's tools, but every call says a product "isn't connected to this workspace yet", or "This connector is not authorised for account …", although the dashboard shows it connected.

Why it happens. An assistant works in the one workspace picked on the approval page. If you belong to several, it may have been approved for another one.

Fix.

1. In the dashboard, use Switch workspace at the bottom of the sidebar to open the workspace the assistant was approved for.
2. Open Connections. Under Connected apps, press Revoke on the assistant and confirm.
3. In your AI app, connect AdCopilot again (reconnect it, or remove it and add it back).
4. On the approval page, pick the right workspace under Workspace and press Approve.

If it persists. Write to support with both workspaces' names and the assistant.

"AdCopilot disconnected … as a precaution"

What you see. The workspace owner gets an email, "AdCopilot disconnected … as a precaution", and that assistant stops reaching AdCopilot. The client may have been told "refresh token is invalid or already used".

Why it happens. An assistant stays signed in with tokens that each work once, and one was used twice. Usually that is a connection that dropped halfway, but a copied token looks the same, so AdCopilot ended the connection. Ending it changed nothing in your Google accounts.

Fix.

1. Read the email. When AdCopilot's log can be read, it says what was changed from that sign-in since the token was first used. Check any such change in Google Ads.
2. Reconnect AdCopilot in that assistant; see Reconnect your assistant.
3. Press Approve on AdCopilot's page.

If it persists. Reply to the email, or write to support, if you didn't do anything unusual or it happens again.

The client says "unauthorized"

What you see. Your AI client says it needs to sign in or authenticate again, or reports unauthorized (HTTP 401) on every call.

Why it happens. AdCopilot no longer accepts that assistant's sign-in: it was revoked under Connections, ended as a precaution, or not used for a long time. Most clients sign in again by themselves.

Fix.

1. Reconnect AdCopilot in the client; see Reconnect your assistant.
2. Press Approve on AdCopilot's page.

If it persists. Remove AdCopilot from the client and add it again. Still failing: write to support with the client and the time.

"invalid or inactive access URL"

What you see. Every call fails with HTTP 403 and invalid or inactive access URL.

Why it happens. Your place in the workspace was removed or switched off, or the workspace itself was switched off. Nothing in the AI client can fix it.

Fix. Ask the workspace owner. Seats are switched on and off through support, so the owner writes to [email protected], the address the Team page gives for seats.

"this trial connector has expired"

What you see. Every call fails with "this trial connector has expired — choose a plan to continue: …/billing", or, for a teammate, "… ask your organisation's owner to choose a plan to continue".

Why it happens. An end date set on this trial seat has passed. It is rare: an ordinary trial moves to Free instead.

Fix. The owner chooses a plan on the Billing page. A teammate asks the owner.

If it persists. Write to support with your workspace name.

"This connector URL has been retired"

What you see. Your client gets HTTP 410 with "This connector URL has been retired. Reconnect in one click at …".

Why it happens. The client still uses an old per-workspace AdCopilot address, one with /c/ in its path. Every assistant now uses the same address.

Fix.

1. Remove that AdCopilot entry from your client.
2. Add AdCopilot again with https://mcp.adcopilot.cloud/mcp; see Connect your assistant.
3. Press Approve on AdCopilot's page.