Skip to main content

Analytics & Ads

Analytics and ads integrations are grouped because they share Google's account model — connecting one usually unlocks the OAuth scope you need for the others. Three are supported today: Google Analytics 4 for traffic and conversion data, Google Search Console for search performance, and Google Ads for paid-campaign management.

📷 Screenshot: Analytics + ads rows on Settings → Integrations.

Google Analytics 4 (GA4)​

The base of every chart on Discover → Analytics and the Pages tab on Launch → Social.

Connecting​

  • From Analytics' cog icon — opens the Analytics Settings modal where you connect GA4 accounts.
  • From Settings → Integrations — same OAuth handshake.

GA4 supports multi-account connections — attach more than one property (e.g. one per product, or one per environment) and switch between them from the same selector. Every tab on the Analytics page re-queries against the active account immediately.

What it powers​

  • The Analytics page — Summary, Usage, Audience, and Attribution tabs all read from GA4 over the date range you pick.
  • AI insights — the platform's week-over-week movement explanations are generated from GA4 deltas; richer GA4 data → more useful insights.
  • Page-conversion data on Launch → Social → Pages, scoped to the URL each post drove traffic to.

Scopes​

GA4 read access is sufficient for everything the platform does today — there's no write surface that pushes data back into Analytics.

Google Search Console (GSC)​

The data source for the Search tab on the Analytics page.

Connecting​

  • From Settings → Integrations — OAuth handshake. The connected GSC property is automatically associated with the workspace.

What it powers​

  • Search tab — top queries, click-through rates, average position, indexing health for the property.
  • Roadmap suggestions — the AI insight that flags "high impressions, low CTR" queries feeds Roadmap → Backlog candidates with a "fix the metadata for this page" item attached.
  • Sitemap heatmap — the sitemap visualization on the Search tab combines GSC data with your live URL list.

Property scoping​

Each GSC property is connected separately. The platform supports more than one property if your domain has both www.example.com and app.example.com registered as distinct properties.

Read campaign performance and (with write scope) edit campaigns from inside AI Expedite.

Connecting​

  • From Launch → Ads → integrations modal — the standard place to connect.
  • From Settings → Integrations — same OAuth handshake.

Multiple Google Ads accounts per workspace is supported — pick the active account from the campaign-list header on the Ads page.

What it powers​

  • The Ads page — Campaigns, Creatives, and Analytics tabs all read from the connected Google Ads account.
  • Status toggles in place — pause / resume on the Campaigns table writes back to Google Ads immediately.
  • Inline edit screen — name / budget / bid strategy / targeting / ad groups / individual ads / assigned creatives, with diff confirmation on significant changes (e.g. budget jumps).
  • The +New Campaign agent flow — pre-fills from a Roadmap feature: objective, audience, headlines, descriptions, matching creatives sourced from the shared Creatives library.
  • Attribution loop — the spend / impression / conversion data captured here populates Discover → Analytics → Attribution, closing the cross-channel loop.

Scopes​

Ads requires read+write — read-only is too limiting because most of the page's value is editing campaigns. Connect with read-only scope first if you want to inspect the integration before granting write, then upgrade.

Reconnecting​

When any of these tokens lapse (token rotation, scope deprecation, account access removed), the affected page surfaces a Reconnect action — typically inline on the Analytics / Social / Ads page that hit the broken integration most recently. Reconnecting walks the OAuth flow again with whatever scopes you choose.

The workspace stays functional during the disconnected window for any feature that doesn't require the broken integration — e.g. losing GSC doesn't break Analytics → Summary, only Analytics → Search.