You don’t need a tuxedo for this kind of event. Find out how to start tracking the events in your website or app and which are the most relevant tools in the market today.
What is an event?
A word that you definitely heard when working in product analytics is “Event”. According to Amplitude, an event is:
“any distinct action a user can perform in your product (e.g. add to cart) or any activity associated with a user (e.g. in-app-notifications, push notifications).”
To be a little more specific, an event can be a slide, a scroll, a click, a download, a text field being filled, a page loading, an audio or video playing. Usually, every event is tagged with the user action’s name as well as the element type and its name. So you can usually find, for example, events like “Create Account”, “Share Blog Post”, “Play Tutorial”, “Brochure download” or “Select Option”, to name a few.
An event may or may not be a conversion. There are things that people do on your website and that aren’t necessarily your main goal, but you want to be aware of them.
For example, an event can be “download a PDF” (something you want people to do on your page). However, an event can also be clicking on a button that leads to an external website, such as a button that leads to a customer’s site (something you don’t want people to do). With events, you can track when traffic is sent to the external page and from there improve your strategy.
Events are not just about clicking this or that, they also allow you to visualize the context in which those clicks occur. You can usually view details such as activity duration, the time of day when it happened, from which device it was made & where the person was geographically located.
At Google Analytics, for example, with each event, you can send parameters (additional pieces of metadata that add more context to the event). They can be used to provide context about the event that occurred and where, how, and why it occurred.
These metrics can help you paint a clear picture of usage patterns for any website or digital product, like mobile applications.
Why would you want to track events then?
Usage data tends to be much more reliable than just relying on qualitative information (such as user surveys or product testing).
For product teams, data can bring you a more complete picture and let you make the right decision to drive business outcomes and improve the product experience.
It’s not a secret:
To correct or improve your products or applications, you must obtain detailed knowledge about your users.
Tracking the metrics within the product provides that information: you can know in detail how, when & where your users interact with your product’s components.
With the right info, you can stop guessing what your users like and you can really know which features generate more engagement.
Get to know your star features and use them to generate a higher percentage of retention among your users (and therefore, a higher profit).
The big question: How can you start event tracking?
Amplitude also said about events: “When deciding what events to track, it is helpful to think of event categories first.”
Google Analytics records many parameters and events automatically, which allows to obtain a lot of information without so much effort. You can find information about all the pre-established events that Google Analytics has.
Besides, the number of events that can be registered is unlimited. This freedom, if paired with poor planning, can lead to problems in the setup of the data you wish to track.
Problems like: omitted events, poor names, and improper use of properties, can generate complications and prevent you from getting the full value of your data.
On the other hand, keep in mind that although the information may be unlimited, your time to analyze it and apply it to the product is not.
So before you even start tracking events, the most important task you need to do is think carefully about the priorities that your team must respond to, in order to measure them.
If you’re starting, maybe focus on two or three business objectives to pick which events you need to follow. Some objective examples could be improved user acquisition, optimized conversion, increased retention, or improved engagement.
Example time: Suppose that improved engagement is really important at the moment in your company. You have a lot of visitors or downloads, but just a few active users. In the case of a video platform/app, you can begin to track the duration of the plays per user or the number of videos the users upload daily/weekly.
Note: When your company is using a PLG strategy, it is important that you use product-oriented metrics and not simply the same metrics that marketing or sales teams use.
Now you have the basics to know how to track an event, you need to know which tools are available for the task.
Most popular analytics tools
No analytics article will be complete without mentioning the most common and popular analytics tool: Google Analytics.
Although Google Analytics is one of the first tools (and free!) that appeared on the market, it was developed thinking of tracking metrics for websites, at a time when there were only a few actions to perform and everything was more static.
So while it is still one of the best tools in general, it is not the best for tracking events within digital products.
In response to this, many other competitors have emerged and have established themselves as leaders in the area, such as Amplitude, Mixpanel, Hotjars, Looker, Heap, and Pendo.
These types of tools, unlike Google Analytics, allow you to choose which metrics you want to see by default and are designed for product team collaboration. They also offer a much friendlier user interface and clear terminology.
In this sea of product analytics applications and complex metric reports, what does Palabra add?
At Palabra, we analyze the needs of product teams. Thanks to this, we have developed a tool capable of displaying data easily with a super friendly interface for non-coders.
In short, you can see in real-time the paths that users have taken in your product (even drop-off) and all the possible combinations, just with a few clicks. It’s simpler and painless.
Solidify the foundations of your product team by tracking the correct events with the right tools. Book a discovery call and start learning how to unleash the power of event tracking.
There are 4 aspects that companies with a Product-led growth approach have in common and that could be the key to their success. Find out what they are and maybe apply some of them to your own company.
Not so long ago, B2B software sales used to involve an executive who made the decision about whether to purchase or not. And that decision impacted the end-users (employees) who suffered the consequences of the selection of incorrect software for their workflow.
However, as the software industry shifted towards an end-user orientation, more B2B businesses are approaching a Product-led growth methodology.
In a previous article, we explored the definition and benefits of Product-led growth. Now we want to dive into what those B2B companies that successfully apply this business model have in common with each other.
At Palabra we did our homework and, given our recent research, we can mention that there are 4 aspects that repeat throughout several PLG companies:
- Solve employee/end-user pain
- UX matters more than design
- Integration to employee stack
- Deliver value before the paywall
Let’s check each of those points separately to see what they mean.
Solve employee/ end-user pain
Some people recognize this point as “virality”. But the reality is that there is no virality if there is not a good product, and a good product solves the problems of users.
B2B companies are very used to focusing solely or primarily on solving executive problems. They have a very different look at what the product or the company means to them. Therefore they look for tools that allow them to increase ROI.
Spoiler alert: this does not work the same with end-users (which in this case will be the employees of that company).
It can be easy to ignore end-user pain points if executives buy your product anyway. But that won’t bring you profit at the end of the day, because no one will talk about your product and no one will want to use it, because it was not designed to solve their needs.
Creating a successful product for end-users means identifying their issues and worries and solving them. It would be useless for your application to be full of glitter if it does not add value to those who use it.
UX Matters more than design
We have all gotten used to seeing pretty and bright designs on the internet. Therefore, a very important differentiator for your brand will be that this application may be able to solve a problem that the user has.
According to Forbes, a well-designed User Interface (UI) could raise your website’s conversion rate by up to 200%. Ok, that’s good, right?
Well, a better UX design could raise your conversion rates up to 400%. That’s even better.
Applying methodologies and research focused on end-users in the development of your products is key to getting to know their real needs and not simply assuming that you know what they are.
Do not jump directly to create a solution, first think about your user-person, then about their problem and the way to approach it and that path will lead you to the solution.
This point is intrinsically linked to the previous one. Both of them are necessary to create products for end-users.
Let’s stop here to give an example of what we have been talking about so far.
One great platform that solved an end-user pain point has been Trello.
Trello understood that work teams could suffer from great disorganization and that sticking post-its that could have unintelligible handwriting from a co-worker (sorry, Kevin) just wasn’t enough.
That is why they created a digital solution, with a simple design, that allowed all team members to see the progress of tasks and projects. And that allowed them to be more in communication with each other without having to talk so much between them or send hundreds of hard-to-find emails.
Integration to employee stack
To achieve this you must think like an end-user and not like an executive (surely there is something in your work environment that you think could be done better).
Your products will be better integrated into the team’s workflow if you manage to reduce the friction that prevents it from reaching them. For example, if you have to pay for the product to start using it, you will probably never use it.
So no more “Talk to sales” button and more “Sign Up”.
It’s much easier for end-users to use and buy your product if they find value in it.
Deliver value before the paywall
Imagine that you enter a store they asked you to leave your credit card details or to pay for shoes that you have not tried on yet. It sounds a bit crazy, like a science fiction story.
Users are intelligent, they do not need you to be on top of them explaining every detail of your application. Your software must be able to speak for itself and convince users with its functionalities.
Nobody wants to pay for an app without knowing if it’s going to make all their days miserable because it constantly crashes.
That is why companies that apply freemium, free-trial models or that sometimes do not even require payments are so loved by people. This is one of the best ways to acquire customers quickly according to ProfitWell.
Still in doubt of how to apply this to your company? If you’d like us to talk about how to follow up on your users to learn and improve your features, feel free to book a demo of Palabra.