Events: understand everything that happens in your product!

Yes, we spent some time with no new posts — but for a great reason. Like every company in an early stage, there’s more work than people to accomplish it. And with us it’s no different, deep down we can say, this huge amount of work is what motivates us.

In recent months, we have been focused on coddling some features to be part of our product core and being ready for the official release. We are still in the beta phase, validating ideas, conversations with users, and quick direction changes.

Now, we are getting closer and closer to going to the market, indeed. Like our plans, August 02 will be our official launch and we are very pleased with this. But, holding up the excitement of this special moment, I bring you our last feature before launch. This one will completely change our product and how you manage yours.

Event monitoring!

By a simple setup in your product, through our code, you are able to monitor any users movements that make sense in your strategy.

Based in a new feature launch as an example, you obviously want to know which users, use that feature the most (or less). How many times is it used per day/week/month. What times it is used more. Which users use it the most.

Those information can provide you insights to improve your product. For example, if a feature has been used with VERY frequency by its user base, any simple tuning in it can create an overload on your support team. Or even your users’ lack of interest in your product. Don’t you believe it`s better to know who are the users who use that feature the most, talk to them, understand any movement in it and/or any improvement, release in a cadenced way and, after successfully validating, drop this to everyone at your base?

This is what event monitoring is about. Without visibility, you’ll hardly get the right things right for your product. Any decision made without a database is a shot in the dark — which can often hit an innocent without the intention.

And installing it is very simple!

See the example:

anallytica.event(3, ‘save-new-user’, { plan: ‘Basic’, cs: ‘leo@anallytica.com’ });

How does this work? Note that we have 3 setups in our function: a number, a text and an object.

That is when this is configured in key places in your product, the more points the user wins lowest is the possibility of a churn. This scale has 5 different numbers: 3, 2, 1, 0, and -50.

From 1 to 3 are features that generate more and fewer points, according to what is essential for your SCORE. The score of 0 does not directly influence the score, but can be used as a LOG within the user and in automation in Anallytica (which we will talk about further in this article). And the -50 is a critical score that dramatically decreases your user’s score — we can use this when a user goes on a cancel page, for example. If he got there, it wasn’t just out of curiosity, right?

Our second parameter, the text is just the identifier of what that event is: save-new-user, update-client, delete-email, etc… here you configure according to what the event is monitoring. Remembering that when you’d better write this title, it’ll be easier for you to keep up with this within our product.

And lastly, an object field where you insert any custom information from that event, using this for filters in the future. In the above example, I’ve gone through my user’s Plan and Customer Success that serves that account, so I’m able to get a big detail of which plans take more or fewer actions.

What will the future bring us using events?

Our part of automation in the future will be amazing. With everything set up within your product we have the possibility to build whatever you want, according to what you want and what makes sense to you.

According to X events in X days, we can create a new list (updated in real-time), send an email to the account’s Customer Success, trigger an event via Webhook for a Slack, for example. The possibilities of the future are endless.

And for sure, we don’t just stay at the events. Why not combine events with non-use days with NPS notes and any URL that was accessed on such day? This is because we haven’t even talked deeply about our Health Score yet (next post, I promise!)

This is our next step. Where we are working now. Event monitoring is on the street. You can already configure it. Automations are in the oven and I’ll soon bring this novelty to you guys, with a lot of pride and excitement!