If something's gone wrong with your subscription management or data source connection, you might encounter one of these error messages:
No accounts foundThe service is not enabled for this user
You can see these errors in the Supermetrics Hub and other destinations, as well as in AI chats, the Supermetrics MCP server, and Supermetrics Studio. Follow the steps for your product below.
Instructions
AI chats, Supermetrics MCP server, and Supermetrics Studio
Accounts work a little differently here. Every request checks live data, so there's no cached account list to clear. Supermetrics Studio doesn't run its own account check either — it uses whichever data source connections are already active in your Supermetrics account, so if accounts are missing in Studio, follow the same steps below.
Ask your AI tool to list the accounts it can see. This runs a fresh check instead of reusing an earlier response.
Reconnect the data source and select every account, page, or business you want to use. If you only select one when your platform login has access to several, Supermetrics only sees the one you selected. See the data source connection guides for what permissions and scopes are required.
Check that your AI chats or Supermetrics MCP server connection is on the subscription and team you expect. This connection stays tied to whichever subscription was active the first time you connected, even a trial. If you've since moved to a different subscription, switch to the correct team and reconnect.
If none of these steps solves the issue, contact our support team.
Data warehouses, spreadsheets, and BI tools
Check that you meet the data source's access requirements. See the connection guide for the data source you're using.
Reauthenticate your connection to the data source. Follow the steps in the reauthentication guide.
Force a refresh for your account data.
If you use Data Studio (formerly Looker Studio) and the issue persists, log out all users and remove the data source.
If you see an error that reads No accounts selected, follow the reauthentication instructions for your data destination and check the "Troubleshooting" section there.