Connect Search Console and GA4 to Aivatar Marketing OS.

Step-by-step setup guide for the Google service-account ingestion path used by Marketing OS today. What you need, what to click in Google Cloud, Search Console, and GA4, how to register properties inside Aivatar, and what every connector status means.

Open ConnectionsBack to Resources

What you need before starting

You do not need your own Supabase — Aivatar runs on a shared backend. You do need your own Google Cloud project, Search Console access to the properties you want to ingest, and GA4 property access. Budget 20–30 minutes the first time.

Ten-step setup

  • 1. Pick or create a Google Cloud project — Any project is fine — the service account is what does the work.
  • 2. Enable the APIs — Google Search Console API and Google Analytics Data API inside APIs & Services → Library.
  • 3. Create a service account — IAM & Admin → Service Accounts → Create. No GCP roles needed.
  • 4. Download the JSON key — Keys tab → Add Key → JSON. Treat the file like a password.
  • 5. Copy the service-account email — Looks like aivatar-marketingos@your-project.iam.gserviceaccount.com.
  • 6. Add the email to Search Console — Settings → Users and permissions → Add user → Restricted (read-only).
  • 7. Add the email to GA4 — Admin → Property access management → Add → Viewer.
  • 8. Send the JSON key to Aivatar — Use the secure channel described in the guide. We set it as a server-side secret — it never appears on your dashboard.
  • 9. Register properties in Marketing OS — Visibility → Connections → add the Search Console property string and GA4 properties/NNN ID.
  • 10. Run Health check, then Sync now — On success, status flips to Connected. Daily cron takes over after that.

What each connector status means

  • Connected — Working. A sync has succeeded recently.
  • Needs auth — No Google credentials on the server yet. Send us the JSON key.
  • Misconfigured — Google rejected the key on this property. Check access grant, enabled API, or property ID.
  • Syncing — A sync is in flight right now.
  • Error — Transient or unexpected failure. Retry Sync now; check the inline error message.
  • Disabled — Registered but no sync has been attempted yet.

Honest current support level

Marketing OS is Live. Automated Search Console and GA4 ingestion via service account is tested and running on a daily cron, feeding the monthly plan's gap / decay / winning buckets. Per-account self-serve OAuth is on the roadmap but not shipped — until then, the service-account path is the real, working setup.