Skip to main content
Open the platform’s card on the Integrations page, click View, then Add one more account and authorize the other login. Both accounts stay connected in the same workspace. Not every platform supports this — see which platforms support several accounts. On the others, disconnect the current account in View and connect the new one.
The primary account. Click the star next to an account to make it the primary. To use a different one, just ask the agent — for example, “show my other Google Ads account” — and it will use that account for the request.
In the platform’s dialog, click the star next to an account. A filled star marks the primary; an empty star means it isn’t primary yet. Setting a new primary only changes the agent’s default — nothing gets disconnected.
Connect the logins you need on each platform and set a primary. If one login reaches many ad accounts or sites, click View on the card and pick Agent default accounts — the agent works with those first and can still reach the rest when you name them. For separate clients, use separate workspaces.
Click Reconnect on the platform card on the Integrations page. If the card shows View instead (another account still works), open View and click Reconnect on the broken account.
Connect whichever other platforms you want the agent to read — for SEO, the store or CMS your articles publish to. The agent sees new connections from your next message.
Go to Integrations → Shopify, enter your .myshopify.com domain (not your custom domain) and approve the Shopify prompt — no app creation or API keys. Use your own custom app if you need theme file edits, URL redirects, or scopes the default connection doesn’t request, such as customer records. See Connect Shopify.
No. Connect the one Google login that has manager access and Ryze reaches the whole hierarchy. Ask the agent “list all Google Ads accounts accessible to my login, including my MCC hierarchy”, then name any client by name or customer ID. Cancelled or never-enabled accounts in the hierarchy may show a CUSTOMER_NOT_ENABLED notice — that’s normal and doesn’t block the live ones.
Ryze sees exactly what the connected login can reach. If an account is missing, reconnect from the Integrations page and tick every permission checkbox on Google’s or Meta’s consent screen, signed in with the login that actually has access — or add that login with View → Add one more account. To see the ad accounts a login reaches, click View on the card and open Agent default accounts, or ask the agent to list them.
Both are settings on Meta’s side. For blocked changes, give the connected user Manage ad account on that ad account (Business settings → Ad accounts → People), then reconnect. For “Verify your account” (error 31), complete the verification prompt in Meta Business Manager — creating any ad manually there usually triggers it; reconnecting in Ryze doesn’t clear it.
The account is connected, but the site or property hasn’t been chosen yet. Click View on the card on the Integrations page, pick the Site (Search Console) or Property (Google Analytics 4) for this workspace and click Save. Your choice is only the default — the agent can still query every site or property on that Google login by name.
Yes — any tool that can add a remote MCP server. Add https://connector.get-ryze.ai/mcp as a custom MCP server in Cursor, or point the MCP/HTTP-MCP node in Make, n8n or Zapier at that URL, then authorize. There are no native one-click apps for these. For scripts and your own agents, create an API key in Workspace Settings → Profile → API keys and call the same tools over MCP or REST — see Ryze API for agents.
There’s no ad account to pick — Ryze sees every ad account the connected login can reach. On LinkedIn, Microsoft, TikTok, Snapchat, Reddit and Pinterest Ads, click View on the card and choose Agent default accounts to tell the agent which ones to use first. OpenAI Ads, Thrad, Criteo and StackAdapt have no default-accounts picker — name the account in chat if you have several. See Connect other ad platforms.
Each platform’s setup guide says where to find it — see the list in Integrations overview. The connect window on the Integrations page also shows a hint under each field.
The API key, token or another pasted value has a character the platform can’t accept — usually a Cyrillic letter, a curly quote or a line break picked up while copying. Copy the value again straight from the platform (not from a chat or document), paste it and click Continue.