>_

SpendSignoff documentation

The always-on operator for your ad accounts. Read and draft from your AI client — approve before anything goes live.

Data integrations

Google Analytics 4

SpendSignoff reads GA4 conversion events, audience sizes, and revenue figures to give the operator grounded context when drafting ad changes. It does not write to GA4 and does not spend through it.

What SpendSignoff reads from GA4

SpendSignoff pulls three categories of data from GA4: conversion events (purchases, leads, sign-ups) to validate ROAS figures already in Google Ads; audience sizes from GA4 audience definitions so the operator can reference real user segments when drafting targeting changes; and revenue by source/medium so the operator can cross-check attributed spend with downstream revenue in a single read.

All reads go through the GA4 Data API v1 using the reporting.read OAuth scope. No write scopes are requested, and no GA4 property settings, goals, or audience definitions are modified.

Read-only, no spend

SpendSignoff holds the GA4 reporting.read scope only. It cannot create or modify GA4 events, audiences, or properties. It cannot spend money through GA4. This integration exists purely to enrich operator context before a draft reaches the approval queue.

What the operator can do with GA4 data

  • Ask: "What is the conversion rate for the Google Ads brand campaign versus organic last 30 days?" — answered from GA4 without switching tabs.
  • Draft a bid change that cites a specific GA4 conversion event count as justification in the diff.
  • Surface an audience size estimate alongside a targeting-expansion draft so you see the scale before approving.
  • Flag when GA4 revenue attribution diverges sharply from Google Ads reported revenue — a sign of a broken conversion tag.

Connect Google Analytics 4

1

Open Accounts in the SpendSignoff app

Go to Accounts in the sidebar, then Add data source. Select Google Analytics 4 from the list.

2

Authorize via Google OAuth

SpendSignoff requests the https://www.googleapis.com/auth/analytics.readonly scope. Select the Google account that owns the GA4 property, then grant access.

3

Pick a GA4 property

After authorization, SpendSignoff lists the GA4 properties accessible to the account. Select one. You can link additional properties later from the same Accounts screen.

4

Confirm the link

SpendSignoff runs a test read against the property to confirm the token is valid and the property is accessible. The property status shows Active when the handshake succeeds.

Token handling

The GA4 OAuth token is stored encrypted in the SpendSignoff vault under the same KMS envelope used for ad-platform tokens. SpendSignoff refreshes it automatically before expiry. If the token becomes invalid — property deleted, permission revoked, or consent withdrawn — the data source shows Token invalid and the operator cannot pull GA4 context until you re-authorize.

You can revoke access at any time from Accounts → [property name] → Disconnect, or directly from your Google account at myaccount.google.com/permissions.

Next

Klaviyo

Connect Klaviyo to surface email revenue and segment data alongside ad spend.

    Google Analytics 4 — SpendSignoff Docs