Read-only by default.
OAuth-based. Consent-aware.
Attributed connects to the tools already running your business. Access is scoped, auditable and revocable at any time. Any implementation access is explicitly agreed with your team — most changes are shipped by Attributed operators or your team through normal platform governance.
Six supported integrations today.
OAuth-based, read-only, consent-aware.
Attributed connects to the platforms already running your business. Connections are read-only by default and revocable from your workspace at any time.
- Google Analytics 4Events & sessions
- Google Tag ManagerServer & web
- Google AdsSpend & conversions
- ShopifyOrders & customers
- HubSpotCRM & pipeline
- SlackAlerts & workflow
Additional platforms onboarded per engagement.
What each connection contributes.
Sessions, events, funnels. Confidence bounded by consent state, ITP and cross-device gaps.
Server and web tag coverage. Foundation for reconciling event definitions across sources.
Spend, click and conversion signals. Reconciled against orders / CRM rather than taken at face value.
Orders, refunds, discounts and customer records — the landed revenue anchor for reconciliation.
CRM pipeline, contact, deal and lifecycle data — the anchor for pipeline attribution.
Operational alerts and workflow — Findings and Alerts land where operators already work.
Every reconciled view is annotated with confidence bands and known limitations — iOS attribution, ITP, consent posture, view-through and cross-device paths reduce deterministic visibility, and Intelligence documents that rather than hides it.
Principle of least privilege, by default.
- OAuth-based authorisation — no shared credentials or exported service accounts
- Read-only scopes by default; any implementation access is explicitly agreed, scoped and time-limited
- Access is logged, reviewed with your team and revocable at any time
- Derived evidence is scoped per workspace and used only for your engagement — see the Privacy Policy for detail
- Consent state is respected end-to-end — nothing is inferred where a customer said no
- The data flow can be walked through in your Growth Review before any connection is authorised
Consent is a first-class input, not a formality.
- Consent state is read at ingestion and preserved through the evidence graph
- Customers who declined tracking are not inferred back into deterministic reporting
- Server-side event enrichment respects the same consent state as web-side tags
- Data-processing agreements and privacy documentation are shared before any connection is authorised
What we don't do.
- We do not sell or resell your data to any third party
- Your data is not used to train third-party models — the Privacy Policy sets out the full detail
- We do not connect platforms outside those listed above without an explicit engagement scope
- There is no autonomous write-back — implementation goes through operators and your team's governance
How connections are onboarded.
- 1Walk through the flow
Every connection is demonstrated in your Growth Review before anything is authorised.
- 2Authorise read-only
OAuth-based, scoped to the minimum required to produce the reconciled view.
- 3Verify with your team
The first reconciliation is reviewed with your operators before it informs any Packs.
- 4Document confidence
Every reconciled view ships with confidence bands and known limitations documented.
- 5Revoke at any time
Access is auditable in your workspace and revocable without support.
Additive, per engagement.
Additional platforms are onboarded during specific engagements, where the connection materially improves reconciliation. The list above reflects the current supported connection ecosystem; other platforms are actively evaluated and may be added per engagement.
Where connections sit in the system.
The always-on evidence layer these connections feed.
The bounded monitoring modules that use these inputs.
The shippable output of the evidence graph.
The senior operators who own reconciliation and governance.
Behavioural and conversion evidence, reconciled with orders and pipeline.
Commerce source of record for orders, refunds and repeat behaviour.
Directional B2B pipeline evidence — contacts, deals, owners, lifecycle.
Walk through the connection flow.
A Growth Review starts with a look at what we can reconcile from your stack today. Nothing is authorised without your explicit consent.