CS – Čeština Sign in Request access
Menu
Sign in Request access Čeština

How dashiox works

dashiox is a marketing-intelligence product for PPC specialists and agencies. It evaluates data from the accounts you connect and delivers structured analyses and findings. This page briefly describes how to work with it; detailed guides are available in the portal after signing in. Features are rolled out gradually during the beta.

1. Access and account

Your account is created from an invitation you receive by e-mail. When accepting it you set a password and two-factor authentication (TOTP) in an authenticator app. Instead of a password you can also accept the invitation with Google — using the Google account with the same e-mail the invitation was sent to; sign-in security is then governed by your Google account and you sign in with Google from then on. You can request an invitation.

2. Connecting data sources

Before connecting Google: Google requires a passkey (sign-in with your fingerprint, Face ID or screen lock) for access to Google Ads. Without it the connection will not go through. If you don't have a passkey yet, create one now – Google usually activates it within 1–2 days (7 at most); during that time please don't delete it or click “Approve”. The detailed steps are below.

You connect your platform accounts in the portal under Data sources (Zdroje dat in the Czech-language portal). For Google you sign in with your Google Account and on the consent screen confirm only the permissions you need (Google Ads, Google Analytics 4, Search Console, Merchant Center, Tag Manager). The permissions we request and why are described in the Privacy Policy. dashiox accesses Google Ads through its own Google Cloud project; each user signs in with their own Google account and grants access themselves. Connecting Meta and Sklik is coming soon. Each user connects with their own consent; connections and access tokens are never shared between users.

Passkey for connecting Google

dashiox connects Google Ads, Google Analytics 4, Search Console and Merchant Center with a single Google sign-in (one consent). Since 5 August 2026 Google requires a passkey every time you newly authorize an app to access your Google Ads account – a password plus a code from an authenticator app is not enough for this step. This is a Google security rule, not a dashiox one, and it cannot be turned off (not even in the Google Workspace admin console). Because the consent includes Google Ads, without a working passkey the whole connection fails, not just Google Ads. Until your passkey works, you can uncheck Google Ads when connecting and connect the other services right away; you then connect Google Ads separately. Existing connections keep working – a passkey is needed for a new connection or for Reconnect (Znovu připojit in the Czech-language portal).

What you need:

  1. A passkey in your Google account. Check it at myaccount.google.com/signinoptions/passkeys. If there is none, create one with “Create a passkey” on the device you use most.
  2. Allow for a waiting period. Google does not trust a new passkey right away. It usually starts working within 1–2 days, the wait can be up to 7 days and it cannot be shortened, not even through Google support. Create it well in advance, ideally right after you create your dashiox account.
  3. Don't delete and re-create the passkey. Every deletion and re-creation restarts the waiting period.
  4. Don't click “Approve” on the passkey. The button is only for people who already have another, older passkey. Otherwise it leads to a loop (“Approve passkey to continue” → “Create a passkey” → settings → Approve again). During the waiting period this is expected behaviour, not an error; the passkey starts working on its own once the period is over.
  5. Connect dashiox on the same device and in the same browser where you created the passkey, and verify with it (fingerprint, Face ID or screen lock).
  6. Company Google Workspace: an admin must allow passkeys in the Admin console: Security → Authentication → Passwordless → Skip passwords → check “Allow users to skip their password and authenticate with a passkey” → Save. The message “Your admin has not enabled passkeys for sign-in” means this is missing.

Troubleshooting:

  • “Your admin has not enabled passkeys for sign-in” – your Google Workspace admin must allow passkeys (point 6).
  • “Approve passkey to continue” or a loop back to “Create a passkey” – the passkey is still in its waiting period. Close the window, don't delete the passkey and try again no earlier than 7 days after you created it (the date is shown in your passkey list).
  • The passkey was deleted and created again – the waiting period runs from the date of the new passkey.
  • It still doesn't work 7 days after creation (without deleting it) – contact Google Workspace support (Admin console → question-mark icon → Contact support) and dashiox support.
  • It's urgent – the connection can be authorized by a colleague with access to the Google Ads account who already has an older, previously used passkey. The connection then runs under their Google account.

3. Receiving results in your AI assistant

Your AI assistant is one of the places where you receive dashiox results. You add dashiox to your AI client (for example Claude or ChatGPT) as a connector via the open MCP protocol (Model Context Protocol) and sign in with your dashiox account; the assistant can then request analyses and findings only within your workspace and only when you ask. You can remove the AI client's access at any time by removing the connector in the AI client, or in the portal under Connected AI apps (Připojené AI aplikace in the Czech-language portal).

How to connect your AI assistant

Your assistant sees Google account data only after you connect your Google account in the portal under Data sources (Zdroje dat in the Czech-language portal) – Google requires a passkey for that, so prepare it in advance (steps).

dashiox MCP server address: https://mcp.dashiox.com/mcp. You never enter passwords or keys into the AI assistant – after you add the connector, the assistant sends you to the dashiox sign-in, where you choose the workspace and confirm access with Allow (Povolit).

  • Claude (claude.ai and the Claude apps): Settings → Connectors → Add custom connector, enter a name and the server address above, then Connect and sign in. On team plans, only an organisation admin may be able to add connectors.
  • ChatGPT: in the settings section for apps and connectors, add a custom MCP server with the address above and OAuth authentication (this may require developer mode and a suitable plan; ChatGPT menu names change often, so follow OpenAI's help).

Once connected, the assistant has read-only access to the selected workspace (client registry, notes, thresholds, saved analysis results). The assistant receives the results of dashiox tools (overviews, analyses and findings) only for the accounts you connect in this workspace under Data sources (Zdroje dat); it does not write anything to your platform accounts. The portal section Connected AI apps (Připojené AI aplikace) lists your connected apps and when each was last used.

4. Analyses and findings

Ask naturally: "Compare campaign performance this month and last month", "Find search terms that spend without converting", "Check my conversion tracking". dashiox evaluates the data of your connected accounts in its semantic layer – unified metric definitions, thresholds and benchmarks, rules such as search-term waste, budget pacing or measurement errors, and your client context (goals, margins, brand terms) – and returns the result as a structured analysis with findings, evidence and recommended next steps. We are gradually rolling out dashboards and per-client reports in the portal.

5. Changes to accounts

Change proposals are coming soon: if an analysis leads to a change in an account (for example a negative keyword or a budget adjustment), dashiox will prepare it as a proposal that is carried out only after your explicit approval in the portal, with an audit record. During the beta dashiox makes no changes to your accounts.

6. Disconnecting and deletion

You can disconnect a connection at any time in the portal under Data sources → Disconnect (Zdroje dat → Odpojit in the Czech-language portal), ask us by e-mail (we handle it within 3 business days at the latest), or remove access directly in your Google Account. A connection you do not use for 90 days is disconnected by the service after an e-mail notice. A query or analysis that you run (from your AI assistant or in the portal) counts as use; the daily background refresh of the account list does not. Under Account & data (Účet a data), a workspace admin or owner can download a copy of the data and the owner can delete the account. See the Data Deletion page.