Events and tracking
The Browser SDK automatically measures clicks, scrolling, form submissions and checkout events on published pages; funnel and automation triggers use those same events (plus CRM, messaging and members events) to start or end a flow.
Role and plan
- Tracking: runs automatically on published pages and funnels with auto-track on — no role required and nothing to configure per event.
- Configuring triggers: requires edit access to the funnel or the automation.
Events measured by the Browser SDK
Events sent to the backend from the page. Each event carries the payload below and a sending priority.
scroll and page_scroll measure different things and do not replace each other. scroll fires when a configured threshold is crossed (75% by default) and is what feeds the Scroll trigger. page_scroll is sent once per page, on exit, with the deepest point reached, rounded into 10% bands — it is what feeds the Avg. scroll metric in the funnel analytics view.
page_engagement and page_scroll are sent when the visitor leaves the page or switches tabs. page_engagement carries a partial interval, so adding up a visit's sends gives the total time; page_scroll carries the running maximum, so the visit's highest value wins.
Sending priorities
Funnel and automation triggers
The events above, together with CRM, messaging, members area and external platform events, make up the catalogue of triggers that start funnels and automations. The full list is in Automation triggers.
Related
- Automation triggers — every funnel and flow trigger.
- Browser SDK: tracking
- Browser SDK reference
- Automations
- Create funnels
If it didn't work
- A page event never reaches the backend: check the error codes.
- A trigger does not start the automation: review the setup and the error codes.
- A list or tag broadcast on WhatsApp does not go out: you may have hit Meta's limit.