Skip to main content

Automatic events

Nexly records useful behavior automatically so you can understand traffic before adding custom events.

Pageviews and screenviews​

Web SDKs record pageviews for browser routes. Mobile SDKs record screenviews for app screens — they are stored as pageviews with the screen name in the path, so mobile and web navigation can be compared together.

Pageviews and screenviews power page charts, entry and exit pages, visit counts, and page-based filters.

Engagement​

Engagement events help Nexly understand whether a visit had meaningful activity.

Depending on the SDK and runtime, engagement can include:

  • Scroll depth.
  • Clicks.
  • Input focus.

Alongside engagement, SDKs also emit lifecycle events — heartbeats, active-time pings, session end, and mobile foreground/background transitions. They keep sessions and durations accurate but are stored with the lifecycle event type, not engagement. Tab visibility changes do not produce their own event; they only trigger a lifecycle ping.

The browser SDK can track outbound link interactions such as external links, downloads, email links, and phone links.

Add data-nexly-ignore when an element already sends a more specific custom event.

Sessions and visitors​

SDKs create visitor and session identifiers so Nexly can group events into visits. A new session starts after a period of inactivity.

These identifiers are analytics IDs, not authentication IDs. Avoid putting user identifiers, emails, tokens, or other sensitive values in page paths or custom properties.

When to add custom events​

Automatic events tell you what people viewed and how they interacted generally. Add custom events for business or product actions that need their own names, such as:

  • signup_completed.
  • checkout_started.
  • subscription_created.
  • feature_enabled.
  • invite_sent.

Custom events appear in the Custom analytics widget after they are approved.