Integrations
Connect the data source needed by a visible EqualAI workflow and understand permission and disconnection boundaries.
View as MarkdownEqualAI exposes connection setup inside the feature that uses it. Start with the workflow below rather than assuming every provider mentioned in a connection screen is an available integration.
| Connection | Open in EqualAI | What it supplies |
|---|---|---|
| Google Analytics 4 | AI Visibility → Traffic Analytics | Sessions, users, conversions, and landing pages attributed to recognized AI-related sources. |
| Cloudflare | AI Visibility → AI Agents | Zone request totals and recognized crawler user-agent activity. |
| Google Search Console | AI Visibility → Prompt Explorer → Google Search Console | Search queries to turn into draft tracked prompts. |
| AI Assistant Access | AI Assistant Access in the account/project menu | Approved assistant access and the available connection-management workflow. |
These connections serve different purposes. Search Console queries do not become GA4 sessions, Cloudflare requests do not establish brand mentions, and connecting a provider does not automatically run tracked prompts.
Prepare a connection
- Select the intended EqualAI project.
- Ask a workspace administrator to connect or change analytics/search credentials.
- Use a provider account with access to the correct property or zone, and grant only the required access.
- Complete the feature's selection step and confirm the displayed property, site, or zone before interpreting results.
- Check the status, data time, and any error. Connected does not necessarily mean data is available for the selected range.
OAuth or service configuration may be unavailable in a particular deployment, and plan or permission restrictions can block a connection. Follow the message shown rather than treating a disabled button as a successful setup.
Disconnect deliberately
Disconnecting in EqualAI and revoking access at the provider are separate operations. A local disconnect removes or disables the saved connection; it does not delete provider data or necessarily revoke Google consent or a Cloudflare token. It also should not be treated as an erasure of previously saved reports or project prompts.
Read the relevant guide for the controls actually offered. In particular, the Search Console prompt wizard does not currently expose a dedicated disconnect button. Never paste a token into prompts, logs, screenshots, or support messages.
Other analytics provider cards that offer a request action are not working analytics connections. Use the documented available connection rather than assuming a request immediately enables a provider.