This page describes Plumb5's data retention policy (DRP) for user-profiles and events.
User Profile Data includes identifiers, system properties, and custom properties. The data retention policy for user profiles is stored as the current snapshot of a user profile forever.
Event Data includes system events and custom events. The data retention policy for events depends on both your plan type and the settings you define in the Plumb5 dashboard.
A Plumb5 user profile consists of three things:
The Plumb5 user profile type changes automatically depending on the information set in them. A user profile can only belong to one type.
Events track what individual actions users perform in your app or website. Some examples of events include a user launching an app, viewing a product, making a purchase, or favoriting an item.
By tracking events in your app or website, you can better understand what users are doing. In Plumb5, you can analyze these events in many different ways, such as getting aggregating metrics of a specific event or measuring how a specific event type trends over time. You can also engage with your users based on these events by creating campaigns in Plumb5 that are triggered by them.
There are two categories of events in Plumb5: System Events and Custom Events.
Events have details that describe the action taking place called properties. For example, while recording the “Product viewed” event, you could also store event properties like product name, category, and price. Recording event properties will help you answer questions like which category of products are more popular, and help you segment users based on which categories of price points they’ve viewed.
Plan Type | User Profile DRP | Event DRP |
---|---|---|
Plumb5 On-Demand / SaaS | Data snapshot stored forever. | Automatically set to the maximum DRP of 180 Days for all events. |
Plumb5 Enterprise | Data snapshot stored forever. | DRP set till the end of Contract |
Last Modified: 1st January 2021