Skip to main content

How it works

The inspector attaches itself to window as soon as possible.

Everything is event driven so it will sit idle until it detect user activity.

Once it occurs, we don't want to impact the site performance, this leads to a event module gathering as little data as possible and then it dispatches an event to an event bus. Which in turn, will figure out the optimal time for data processing; when the page experiences as little computation as possible. Once that times comes it will start to process the event and gather useful & formatted data for us to look at.

For a simple event such as user click the timeline will look like this:

  1. User clicks

  2. The click module gathers the click position, what the user clicked on (e.g. a <button>), the timestamp of the action & on which page.

  3. This gets dispatched to an event bus

  4. The click module is then allowed to run some more calculations and sync it to our backend

This allows us to impact your site performance as little as possible. Do not worry we will not lose any of your data doing this, we have systems in place to ensure this. But we'll get to that later.