Skip to content
← Integrations

Website & advertising

The signal that makes a next action worth acting on.

Which pages somebody read, how often, and whether they returned. This is the single connection that most improves the quality of a next action — “visited pricing twice yesterday” is the difference between a reason and a guess.

What connects

Your website analytics or behavioural platform, through its API.

What crosses the boundary

  • Into the platform: page views, return visits and session context, subject to the visitor's consent state.
  • Out of the platform: nothing.
  • Never: individual behavioural data where consent does not permit identifying the visitor.

What this makes possible

  • Explains why now — the reason a contact is at the top of the list today
  • Escalates a sequence from email to a call when intent rises
  • Surfaces dormant customers who have quietly started looking again

Setting it up

  1. 1Authorise a read-only connection.
  2. 2Confirm which pages count as commercial intent.
  3. 3Confirm the consent categories that gate identification.

Permissions

Read-only. Individual-level behaviour requires a consent state that permits it; an absent or unreadable state is treated as a refusal, and there is no setting that makes it permit.

Where it stops

Identifying a visitor as a known contact depends entirely on their consent state, and where that is absent the platform sees aggregate behaviour only — which is the correct outcome, not a degraded one. It also cannot tell you why somebody read a page. Four visits to pricing is a fact; what it means is a judgement, and the platform proposes rather than concludes.

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]