>_

SpendSignoff documentation

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

Data integrations

Klaviyo

SpendSignoff reads Klaviyo flow revenue, campaign revenue, and segment sizes to give the operator grounded context when evaluating ad ROAS and drafting audience changes. It does not write to Klaviyo and does not send emails or modify flows.

What SpendSignoff reads from Klaviyo

SpendSignoff pulls three categories of data from the Klaviyo API: flow and campaign revenue attributed by Klaviyo so the operator can compare email-attributed revenue to the ad spend driving the same traffic; segment sizes from Klaviyo lists and segments so the operator can reference real audience sizes when drafting ad targeting changes; and metric event counts (placed orders, started checkout, viewed product) to cross-check conversion figures already in Google Ads or Meta.

All reads use a Klaviyo private API key scoped to read_only across the metrics, lists, segments, campaigns, and flows resources. SpendSignoff does not request write or full_access on any resource.

Read-only, no sends and no flow changes

The Klaviyo key SpendSignoff holds is read_only. It cannot create or modify flows, campaigns, lists, or segments. It cannot send emails, add profiles, or trigger any Klaviyo action. This integration exists purely to enrich operator context before a draft reaches the approval queue.

What the operator can do with Klaviyo data

  • Ask: "What is the email-attributed revenue from the welcome flow for customers who also clicked a Google Ads brand ad last 30 days?" — answered from Klaviyo without leaving the chat.
  • Draft a Meta audience change that references a specific Klaviyo segment size so you see the addressable scale in the approval diff.
  • Flag when Klaviyo revenue per recipient is rising while Meta ROAS is falling — a signal that email is outperforming paid and the budget mix may need adjustment.
  • Confirm whether a surge in Google Ads conversions corresponds to a Klaviyo flow trigger or is isolated to paid traffic.

Connect Klaviyo

1

Create a Klaviyo private API key

In your Klaviyo account, go to Account → Settings → API Keys → Create private API key. Set the key scope to Read-only on all resources. Copy the key — it is shown only once.

2

Open Accounts in the SpendSignoff app

Go to Accounts in the sidebar, then Add data source. Select Klaviyo from the list.

3

Paste the API key

Enter your Klaviyo account ID and paste the read_only private API key. SpendSignoff stores it encrypted in the token vault immediately — it is not visible again after you save.

4

Confirm the link

SpendSignoff runs a test read against your Klaviyo account to confirm the key is valid and has the expected scopes. The data source status shows Active when the check passes.

Token handling and revocation

The Klaviyo API key is stored encrypted in the SpendSignoff vault under the same KMS envelope used for ad-platform tokens. Unlike OAuth tokens, Klaviyo private API keys do not expire automatically — SpendSignoff holds it until you disconnect.

To revoke access, disconnect from Accounts → [Klaviyo account] → Disconnect in SpendSignoff, then delete the key from Klaviyo under Account → Settings → API Keys. Deleting the key in Klaviyo alone is sufficient to cut access immediately; the SpendSignoff vault entry becomes inert.

Next

Concepts

Drafts, the approval queue, the autonomy loop, the 24h envelope, and rollback.

    Klaviyo — SpendSignoff Docs