User Events are actions tracked on Users. They occur exactly once per action. User Events can be re-sent to specific connectors using Hull’s Event Replay feature:

Account Events are not supported today.

Events Data Model

User Events are composed of a:

  • Event name
  • Timestamp
  • Set of properties
  • Context (e.g. IP address, location)
  • Source connector_id (e.g. Mailchimp)

Capturing Events

User Events are captured via Connectors, Hull Track calls, and bulk import.

Capturing Events via Connectors

Connectors capture events and send them to Hull. For example, Email opened from Mailchimp.

Capturing Events via Track calls

You can track Events on your website or in your product using Hull.js.

You can also create new Events in Processor and Scheduled API Calls by writing hull.track() calls.

Warning: Hull Track calls can create billable infinite loops in your Hull Organization. See our guide to best practices and pitfalls with Hull Track.

Capturing Events via Bulk Import

You can also bulk import many User and their User Events at once via API.

Syncing Events to Tools

User Events can be forwarded to tools through Connectors by whitelisting them.

Examples of User Events include:

  • Page viewed
  • Form submitted
  • Demo requested
  • Email replied
  • Redirect link clicked

User Events can be used to:

How Events are Displayed

User Events are displayed in the right hand column in User Profiles, as a timeline.

Each Events’ properties and context that can be viewed on click.

Hull User Event

Events limits

Event retention depends on your billing plan. Events will be deleted from your Hull Organization after your period.

Built-in Events

In addition to User Events captured from external services there are some Events which are emitted by the Hull Platform itself marking important moments in Hull User lifecycle. They are described in Data Lifecycle Compute section and here is the full list of them: