Feature requests

When applying audience filters, there should be an option to save audience filters. On click of the saved filter, apply the audience filter.

Some events we send out are not relevant for UserMaven, but used on another platform. I'd like the ability to ignore a particular Event to decrease 'noise'

Currently, there is a Javascript SDK and HTML snippet that can be used to track user behaviour for product analytics. Allow options for SDK's for other programming languages such as: iOS Android Python Java PHP And few other languages

I would love to see a list of events that I am currently sending UM. This would help me work with my team internally to send new ones that I am missing. Perhaps they could be displayed here for reference: https://app.usermaven.com/events-recommendations

We are a B2B SaaS. Almost all of our activity happens during the week. Our weekend data is noise. I'd love to remove it as a default.

Events should be auto-captured after installing the pixel. This will help lessen the dependency on getting developers involved in sending events to Usermaven.

We should be able to create multiple reports in feature adoption module to segregate features/actions in different reports. This will help: build uncluttered reports compare actions performed by users on a specific module

Ability to export power users in a CSV

Similar to first touch and last touch attribution model, Linear attribution is a multi-touch attribution model which splits conversion credit equally across each touchpoint or interaction along a customers journey. Simply, this attribution model gives a participation award to every marketing channel a business used.

Allow an option to provide different attribution models i.e first touch, last touch and linear attribution for Attribution. First touch attribution: With first-touch attribution, the first time that a customer interacts with your company is deemed to be the single most important reason they ended up purchasing from you. Last touch attribution: With last-touch, it's the opposite — the last interaction that a customer has before converting is considered the most important touchpoint.

An option to exclude stats from analytics by blacklisting users using IP or domains or browser footprint. The idea is to exclude the data of the internal team using/testing the product.

This is to avoid the blocking of cross-site cookies from browsers. Tracker will appear to be as e.g. events.example.com CNAMEed to events.usermaven.com. The creation and renewal of SSL certifcates for the custom domains should be automated on usermaven's end.

Ability to segment a group of users who meet a specific rule, or set of rules. Segments will allow to filter users meaningfully with multiple conditions, and identify users who have (or haven’t) taken important actions inside the product. Here are some typical segments: Trialing Users Paying Users Advanced Users Churned Users

Allow users to upload CSV to import historical contacts.

We should be able to see which sources, referrers and UTM-based links are converting best based on different attribution models like first touch and last touch.