EarShots.dev
Open navigation

Analytics / QA preview

Google Analytics 4 + EarShots

The EarShots Google Analytics 4 integration is designed to read referral and engagement reports from a selected GA4 property, so your team can assess website traffic alongside its AI-search visibility. The initial adapter is in QA and does not modify your Analytics configuration.

Open connection setup

What can you do with this integration?

  • Choose a property your Google account can access
  • Read a bounded report of sessions and key events by source, medium and date
  • Inspect the result in the app, MCP, CLI or REST API

Worked examples

These examples explain the QA adapter. They are not customer results or certification evidence.

Inspect AI-related referral traffic

Input
Illustrative request: select your website's property and a seven-day date range.
Action
Read sessions and key events grouped by date, source and medium; inspect any AI referral sources actually present.
Expected result
A bounded, source-labeled report. Missing referrals remain missing; EarShots does not manufacture an AI traffic total.

Prepare a marketing review

Input
Use a saved EarShots visibility report and a GA4 report covering matching dates.
Action
Compare citation observations with the referral report, keeping the property, time zone and date range visible.
Expected result
Evidence for a review of traffic and visibility. Automatic causal attribution and revenue claims are outside the initial adapter.

Fields and data direction

The selected provider property returns aggregate read-only report data to EarShots.

FieldMeaning
PropertySelected GA4 property ID
DateReport day in the property's reporting time zone
Source / mediumSession acquisition dimensions
Sessions / key eventsAggregated report metrics

How to connect Google Analytics 4

A Google account with access to the selected property, the Analytics Admin and Data APIs enabled, and the analytics.readonly OAuth scope. Workspace owners and admins manage the connection.

  1. Open setup, sign in to EarShots and choose your workspace.
  2. An owner or admin reviews the requested provider access and completes consent. QA setup must first be enabled for this provider.
  3. Select the exact property to use. Other resources are not automatically imported.
  4. Create a preview and run a small test. Read a short reporting period and check it against the provider's own report.
  5. Inspect the saved operation result. Manage or disconnect the account from workspace integrations.

Limits and recovery

Referral reporting is limited by consent, attribution, sampling or thresholding and the data your property collects. AI visibility and referral events are separate observations. This adapter does not establish that an AI citation caused a conversion or import person-level browsing history.

Queued work follows the workspace worker schedule. If authorization expires, reconnect and reselect the resource. Keep the same operation and idempotency key when checking a retry. Disconnect blocks new work; an external request already in progress can still finish.

Common questions

Can I use this through MCP, CLI or the API?

The QA implementation shares the same workspace authorization and operation service across all four surfaces. Start setup from a tool or command, then complete provider consent in your browser. Machine requests do not receive provider credentials.

Is this available now?

This adapter is in QA. Setup depends on provider configuration, your workspace permissions and plan. Live availability will be recorded after account authorization and workflow tests pass.

Does connecting authorize publishing or marketing sends?

No. Connecting grants only the configured provider permissions. Workflow execution, content approval, publication and marketing consent are separate decisions.

Provider reference: Google Analytics 4 developer documentation. Adapter behavior requires live verification before launch.

Explore related integrations