Skip to content
← Integrations

Advertising & analytics

Notice the account that stopped using it.

Usage figures, feature adoption and activity trends — the earliest signal that an account is in trouble. Aggregated by default; individual-level behaviour is a separate capability and depends on consent.

What connects

Your product analytics platform, through its API.

What crosses the boundary

  • Into the agent: aggregated usage, adoption and activity figures by account and period.
  • Out of the agent: nothing.
  • Never: individual behavioural records without a consent state that permits it.

The capabilities this exposes

  • Read analytics

Setting it up

  1. 1Authorise a read-only connection.
  2. 2Confirm the metrics in scope.
  3. 3Grant analytics to the agents that need it.

Permissions

Read-only and aggregated. Individual-level data requires the consent engine to report a permitting state, and an absent state is treated as a refusal.

Jobs an agent can own once this is connected

  • Flag accounts whose usage dropped before renewal
  • Report which features a struggling account never adopted
  • Assemble a renewal briefing from usage and support history

Where it stops

Aggregated by default, and individual-level access is gated on consent rather than on your configuration. This connection cannot write, cannot create events and cannot identify a person the consent state does not permit identifying.

Give AI a job.

Build an agent, choose what it can access, define what it may do, and deploy it to work safely across your business.

No code required · Full SDKs and API · Stop any agent instantly · [email protected]