Lifecycle emails or behavioural emails are triggered based on a user’s activity while using a product. But is it enough to measure the performance of these emails? Let’s find out!
In-depth Guides that are easy to consume and fun to read
Data democratization is the ongoing process of enabling everybody in an organization, irrespective of their technical know-how, to work with data, feel comfortable talking about data, and as a result, make data-led decisions.
A Customer Data Platform or CDP enables companies to collect and collate customer data from different sources, clean and organize that data, and then send
Data type is an attribute associated with a piece of data that tells a computer system how to interpret its value. Understanding data types ensures that data is collected in the preferred format and the value of each property is as expected.
Introduction A data tracking plan (usually referred to as just tracking plan) is a document that acts as the source of truth for your customer
To decide which events to track and what data to gather, you need to list down questions you have about your users and their product usage. Once you start listing those questions down, you will realize that there is so much you want to know.
Customer Data comprises Event Data and Entity Data — you already know that if you have gone through the previous parts of this series. In this guide, you will learn about the components of event data, the preferred naming convention to define events, the categories of entity data, and the two main types of entities.
Event data helps decipher what is going on inside a product while entity data tells you who is performing those events, enabling you to get a grip on your user personas and create user cohorts.
Event data helps you understand exactly how your product is being used — whether or not users are performing critical actions and completing the tasks that will lead them to derive the product’s core value, or in other words, reach the aha moment.