Guide
Setting up cross-platform attribution
Reading spend and conversions from Google Ads and Meta into one normalized view, so the operator drafts off a unified picture instead of one platform at a time.
Why attribution is a read problem first
Cross-platform attribution sounds like a write feature, but in SpendSignoff it starts entirely on the read side. Before the operator can propose moving budget from Meta to Google, it needs both accounts normalized into one view — same units, same windows, same conversion definitions. All of that is read access, ungated, no spend involved.
Getting to a unified view
Attribution improves with each account you link read-only.
Link Google Ads read-only
OAuth into Google Ads. SpendSignoff reads campaigns, spend, and conversions. No change is possible yet.
Link Meta read-only
OAuth into Meta the same way. Now SpendSignoff has both platforms to normalize against each other.
Review the normalized view
Spend and conversions from both platforms land in one Reporting view with consistent units and windows. This is a read — it costs nothing and is available on Free.
Let the operator draft across platforms
With a unified picture, the operator can propose moves like shifting budget toward the platform converting better. Each move is still a draft you approve, capped by the per-account 24h spend envelope.
Reads are free on every plan
What is live today
Google Ads and Meta are the live platforms, so cross-platform attribution today means those two normalized together. LinkedIn and TikTok are coming; when they link, they fold into the same normalized view.
Next
REST API
The /v1 namespaces behind reporting and reads: internal, app, and webhooks.