Every system lives on its own
Ads in one console, web analytics in another, CRM and call tracking in a third. The summary is stitched together by hand at month end — after the decisions were made.
Data Hub shows where your data comes from, what it is assembled into and where it goes: 29 sources, 14 destinations and five ready-made datasets. Flows ship switched off, and writing to an external system waits for the owner's approval.
Ads in one console, web analytics in another, CRM and call tracking in a third. The summary is stitched together by hand at month end — after the decisions were made.
A zero on the dashboard is either a real zero spend or a sync that failed. Until those are told apart, the report and the AI summary are wrong with equal confidence.
Your own developer app, a scope list, screenshots and a review on the platform's side. The integration sits for weeks and nobody remembers which step it stopped at.
The catalog holds 29 connectors. Each one shows its readiness — live, partial, planned or waiting on platform review — and the current state of the connection.
Five ready templates: PPC, SEO, ecommerce, lead quality and an executive summary. Currencies are normalised, rows deduplicated, suspicious zeros flagged.
Dashboard, report builder, client portal, spreadsheets, BI tools and exports. Writing turns on only with the owner's approval, and every run is logged.
Ad platforms, web analytics, ecommerce, CRM, finance, call tracking and aggregators — each with its auth type and the list of streams it provides.
Every source says whether it is live, partial or still planned, and what exactly is blocking the connection right now.
From the dashboard and report builder to Google Sheets, Excel, Looker Studio, Power BI, BigQuery, Snowflake, webhooks and CSV/JSON exports.
The dataset separates a zero the platform returned from data that never arrived, and shows source coverage next to the metric.
An AI answer has to cite the dataset, the source, the date range, freshness and row count. On stale or thin data the recommendation is blocked.
Each provider gets a packet: required scopes, the developer portal link, the evidence list and the current status. Review and approvals stay with a human.
The catalog holds 29 sources: ad platforms, web analytics and Search Console, ecommerce, CRM, finance, call tracking and aggregators. Each carries a readiness status — some are live, some partial, some waiting on the platform's own review. The catalog states this openly instead of hiding it behind a wall of logos.
Writing is supported: every destination lists its write modes — replace, append, merge, snapshot or dated history. It stays off by default, because it needs the owner's approval, an explained write mode and a run log before it is enabled. Several warehouse destinations are still marked as planned.
Data Hub separates a zero the platform returned from a sync that never landed. Next to the metric you see source coverage, the time of the last successful run and the row count, so a zero day does not automatically become the conclusion that the ads stopped working.
Often yes: platforms require their own app, a scope list and a review. The setup assistant builds a packet per provider — scopes, the developer portal link, the evidence list and the current status. Passing review, entering verification codes and accepting legal terms stay manual on purpose.
Yes, with a limit: the answer must cite the dataset, the source, the date range, the freshness and the number of rows behind it. If the data is stale or the sample is below the threshold, the recommendation is blocked rather than delivered with false confidence.
The source catalog is open to browse and the flows ship switched off. Nothing is written outward until you allow it.