Skip to content
← Integrations

Website & advertising

The expansion argument the customer is already making.

For software and subscription businesses, usage is the earliest and most honest commercial signal there is. An account at the limits of its plan is making the expansion case itself; one that has stopped logging in is making a different case entirely.

What connects

Your product analytics or usage platform, through its API.

What crosses the boundary

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

What this makes possible

  • Evidences an expansion case from the customer's own behaviour
  • Surfaces accounts whose usage dropped before a renewal
  • Separates a quiet account from a departing one

Setting it up

  1. 1Authorise a read-only connection.
  2. 2Confirm which usage metrics indicate commercial need.
  3. 3Map usage accounts to customer records.

Permissions

Read-only and aggregated at account level. Individual-level data requires a permitting consent state, and an absent state is treated as a refusal.

Where it stops

Usage evidences a need; it does not establish one. An account at its plan limit may be about to leave rather than about to upgrade, and the platform shows the signal rather than concluding. Aggregated by default, and the mapping between usage accounts and customer records is only as good as you make it — unmapped usage is reported as unmapped rather than guessed.

Make sure every opportunity gets a next action.

Let AI handle the repetitive engagement, keep follow-up moving, and bring your team in when a customer needs a real conversation.

Agents identify themselves on every call · Nothing commits without you · [email protected]