If you are looking to instrument your web application and start sending usage data directly to Natero while the client is using your product. Below describes the general concept and logical model we use to define an event, session and product modules and features to help you understand the types of product usage data we are looking for. For step-by-step setup instruction, please go to Natero Javascript Library.

If you are already collecting usage data from your product, you can send a copy of those events to Natero using the Event REST API.

If you use a third party data collection service such as Segment, please refer to our Third-Party Integration section for connection details.


Events can be anything that happens related to a user or account at a specific point of time.

Common examples include:

  • User performs an action in the application such as “send an email” or “add a chart to the dashboard”.
  • Support agent opens a case to handle a phone call.
  • Sales executive creates a new contact in CRM or logs an email exchange with an existing account

Module and Feature

Modules are logical parts of your application that indicate where your customers spend time in your product. Natero will track the amount of time your customers spend in each of the modules you define.

Features are the user interactions that occur in a module, which can include buttons clicked, actions taken etc.. For example: "Create a report" or "Add a user". Natero will track how many times a feature is used to assess your customers' engagement level.

With each event, module and feature attributes are included, if set. The module and feature specify a hierarchy by which to categorize events.  Modules may include multiple features; while features are mapped to individual clicks or events within a module.

Common examples include:

  • In an HR management app, “Recruit” can be a module, while the specific action of adding a candidate or tracking an offer is associated with a feature.
  • In an email campaign app, “Campaign” can be a module, while the action of creating a new newsletter or scheduling the delivery of a newsletter is associated with a feature.
  • In a customer support app, “Tickets” can be a module, while the action of creating a new ticket or changing the status of a ticket is associated with a feature.


A session simply records the fact that the user interacted with the application in some way. Time is tracked on a per module and per session basis. Specific actions that the user took during the course of a session will be reported as different events to Natero.