Heap automatically captures user actions - clicks, taps, gestures, form submissions, page views - and allows you to add any additional custom properties you’d like. What makes Heap unique is that as analytics requirements continue to grow and change and new events are added for tracking - these events are automatically updated sequentially, so you have a full view of the new event’s data. This block will help you establish the foundation of your analysis, which you can then augment with additional objects based on your customized schema.

Heap offers a product called Heap SQL, which provides retroactive data access in a managed Redshift data warehouse to all of these automatically defined and custom events. As changes are made to event definitions in Heap, these are reflected in the Redshift data warehouse too, going forward and retroactively.

The Heap Block provides a starting point to model and explore the data in Heap SQL, based on the components of the schema that are common across customers. These tables include:

  • Events: The Events table contains a full event stream of all defined events. There are additional tables available for each event type custom to the customer. But the event stream table is useful for looking​ at combined behavior at the visit or user level, and contains columns common to all event tables, as well as the event type.

  • Sessions: The session table contains a row for each user visit or session. This table is smaller than the events table, which can make querying for metrics at the session level more performant to analyze than the raw events table when querying for large date ranges.

  • Users: The users table contains information about each of the users, and can be joined to the events or sessions table to provide more user level information about activity.

The Heap Block builds on these three tables to provide commonly sought after metrics when analyzing web or mobile activity.