Help for your workspace

First-time setup

1. Sign in, then open Dashboard → Connect.
2. Authorize Google (and Microsoft if you use Bing or Clarity OAuth). You will be asked to pick Search Console, GA4, Ads, and related properties for each site.
3. Add Clarity with your project ID and API token on the site form when prompted.
4. Optional CRM, email, and LLM keys live under Dashboard → Integrations.

Step-by-step consent notes: Connecting Google & Microsoft.

Google sign-in and connectors use read-oriented permissions: profile/email for your account, Search Console and Analytics reporting, Google Ads reporting, and Tag Manager read access when enabled. Conversion Console does not change Ads campaigns, budgets, or creatives through the API.

If you expand permissions later (for example Ads after a basic login), use Re-authorize on Connect so Google shows the updated consent screen.

Sync now pulls connected sources into your workspace so charts and insight recipes can run. Missing connectors simply hide related insights — they do not break the rest of the dashboard.

More detail: Sync explained.

Ads insights need an authorized Google account with access to the customer accounts you select on Connect. Reporting stays read-only: use Conversion Console to find opportunities, then make changes in Google Ads itself.

Bing Webmaster connects through Microsoft sign-in from Connect when your workspace has that integration enabled. Clarity uses the project ID and Data Export API token from your Clarity project settings — paste those on the site Connect form.

Built-in insight recipes run on your synced metrics without requiring an LLM. Strategy chat can use optional keys you add under Integrations (OpenAI, Claude, or Gemini). Keys stay in your workspace configuration.

• Empty charts — confirm each source finished syncing on Connect.
• Permission errors — re-authorize Google or Microsoft from Connect.
• Ads or Bing still missing — check you selected the right customer / site and that your Google/Microsoft user can access them.
• Full checklist: Troubleshooting