Skip to main content
Workspace admins configure connections in Settings → Integrations. These supply observations; they do not publish website changes.

​
Google Analytics 4 → AI Traffic

Connect Google, choose the GA4 property for the website and import reports. In Analytics → AI Traffic, select the primary business action and inspect identifiable AI referrals by landing page. Google key events and revenue require existing GA4 instrumentation. The connection requests read-only Analytics access. It recognizes configured AI referral domains; direct/untagged visits and generic Google organic traffic are not complete AI attribution. Overview reads saved daily rows in its selected period; coverage may end before today. Source timezone and freshness are in Information. During Google’s OAuth testing period, access can require an invited test account and consent may display an unverified-app warning. The operator must complete Google’s required verification for broad rollout; deployment is not verification.

​
Vercel Drains → Agent Analytics

  1. Use the Vercel project serving the website. Find its Project ID in project settings; a team_ ID is not a project ID.
  2. Prepare the connection in UX Report and copy its public HTTPS destination URL and signature configuration. Never use localhost as a destination.
  3. In Vercel, add a Logs drain for that specific project and Production. Configure the request-log sources supported by the connection, rather than build-only output.
  4. Use JSON and match the signature verification secret to the connection instructions. Test delivery, then create the drain.
  5. Check connection status and incoming data in Analytics → Agent Analytics. A signed test or empty batch proves endpoint delivery only; actual bot reports require real matching requests.
Vercel’s plan and usage terms apply. There is no historical backfill. Reports describe only delivered logs; user-agent labels can be spoofed, and verified-IP coverage is a separate signal. Bot visits do not prove indexing, citations or recommendations. HTTP error evidence can become an Opportunity. Cloudflare and WordPress log connectors are not included in this release.

​
Authority enrichment → Pages

The application operator configures MOZ_API_TOKEN as a server environment secret in the app’s deployment project. Customers do not paste it into prompts or browser code. Redeploy the app after changing production environment variables. The current connector enforces Moz Free without overages: at most 50 shared rows per provider billing period, across all workspaces. Explicit checks reuse saved results for 30 days; reads do not trigger paid expansion. A metric or brand check reserves one row and a backlink batch reserves five; failed attempts retain conservative reservations. Unavailable data stays unknown. For full operator setup, see the repository’s apps/app/src/lib/google-analytics/README.md and Admin Wiki → Integrations.