Backlog

Next up

In Progress

Done

Main Roadmap

In Review

Filter by contact properties

retein.io support

Filter by session properties

Custom date ranges in dashboard

Create a PHP version of the SDK for event tracking

PHP SDK

Allow users to customize the visualization type of each dashboard card. Users can choose to display a card as a plain metric, line chart, column chart, or bar chart, depending on the nature of the data—especially useful for time series analysis.Feature Behavior:<ul><li>Each card has an “Edit” option</li><li>Users can switch the visualization type:<ul><li>Metric</li><li>Line chart</li><li>Column chart</li><li>Bar chart</li></ul></li><li>Visualization choice is saved per card and persists across sessions</li><li>Default display remains as metric unless changed by user</li></ul>Acceptance Criteria:<ul><li>Users can change a card’s visualization type via an edit option</li><li>Changes are reflected immediately and saved</li><li>Visualization options include: metric, line chart, column chart, bar chart</li><li>Selected visualization persists across sessions</li></ul>

Make Individual Dashboard Cards Editable (Metric or Chart)

Possibility to tag a user in order to cluster users and have an aggregated view by category, also in relation to a specific time period (1 day / 7 days / 1 month). From the user profile, I can assign them a category that will be saved, and in this way, I imagine being able to select the category (i.e., the reference tag) from a filter in the dashboard and get an aggregated view of the events only for that category (e.g. consultants mostly sign in person, mostly use PDF, etc.).

Tagging users

Marco HEU

Problem Users cannot filter the dashboard to specific event sets. Solution Add an “view” dropdown to the dashboard where users can select, or create, views based on lists of events. Selecting a view results in the dashboard showing only specific.

Dashboard views (using events)

Allow users to save filtered groups of contacts (based on events and properties) as named "cohorts". This enables users to track and analyze the behavior of specific user groups over time.Feature Behavior:<ul><li>Saved cohorts are accessible from a dropdown on the home page/dashboard</li><li>Selecting a cohort from the dropdown updates dashboard metrics to reflect only that cohort's behavior</li><li>Useful for comparing different user types, e.g. "discoverers" vs "reviewers", or "consultants" vs "companies"</li></ul>Acceptance Criteria:<ul><li>Cohorts are listed in a dropdown on the home/dashboard</li><li>Selecting a cohort filters the dashboard metrics to reflect that group only</li></ul>

Save user cohorts (using tags)

<ul><li>have, in "events" main menu page, a tab for looking either at events or at sessions</li><li>they expect the session table to have filter</li><li>the sessions button from home could be a shortcut to reach the filtered table immediately</li><li>when clicking on a session, they expect a page that is similar to the one of contact: meta data information of the session on the left, list of the events of the individual session on the right</li><li>in the individual contact page, they want a tab "session" similar to events, showing the session of the individual contact </li></ul>

Completed

Display sessions information

Add auto-tracking from client SDK for OS, user agent, device Add possibiliy of inserting ip address from client SDK Display the metadata in the main app

Add user agent, OS, and device (mobile, desktop) tracking and display

Create conversion funnels to see how many users doing an event also do other events consequently

Events Funnel

From the dashboard, always knowing the number of online users in real time

See number of online users in dashboard

Add two new user engagement metrics to the main dashboard:<ul><li>Active Users: users who performed any event in the selected time range</li><li>Returning Users: users who were also active in the previous corresponding time range</li></ul>Example logic: For a 7-day range:<ul><li>Active Users = users with any event in the last 7 days</li><li>Returning Users = users with events in both the last 7 days and the previous 7 days</li></ul>Acceptance criteria:<ul><li>"Active Users" count displays correctly based on selected time range</li><li>"Returning Users" count reflects users active in BOTH the current and previous time range of equal length</li><li>Time ranges supported: 1 day, 7 days, 30 days, 3 month</li><li>Data updates appropriately when the time range is changed</li></ul>