Data Retention Policy

01 Overview

User Profile Data includes identifiers, system properties, and custom properties. The data retention policy for user profiles is to store 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.

02 User Profile Data Model

A Plumb5 user profile consists of three things:

• Identifiers: Each user profile is given a unique Plumb5 ID. You can also add other identifiers to recognize the user, including email, phone number, Facebook ID, Google Plus ID, or your own custom identifier.
• Properties: Information stored about the user — for example, age, gender, device, and location. You can extend the default user profile with custom fields specific to your business.
• Events: A log of actions taken by a user in your app or website — for example, a product viewed, a video watched, or an item added to the cart.

03 User Profile Types

The Plumb5 user profile type changes automatically depending on the information set in them. A user profile can only belong to one type.

• Anonymous: Anonymous profiles do not yet contain uniquely identifiable information about the user.
• Addressable: Addressable user profiles are reachable either via email or push notifications.
• Customer: When you record a purchase via the Charged event, that user is marked as a Customer.

04 Event Data

Events track what individual actions users perform in your app or website — for example, a user launching an app, viewing a product, making a purchase, or favoriting an item.

By tracking events, you can better understand what users are doing. In Plumb5, you can analyze these events in many different ways, such as aggregating metrics for a specific event or measuring how an event type trends over time. You can also engage with your users based on these events by creating campaigns triggered by them.

Event Categories — there are two categories of events in Plumb5: System Events are recorded automatically after you integrate our SDK or Web Tracking Script; Custom Events are events you define and track with our SDK or API.

Event Properties — events have details that describe the action taking place, called properties. For example, while recording the "Product viewed" event, you could also store properties like product name, category, and price. Event properties help you answer questions like which category of products is more popular, and help you segment users by which price points they've viewed.

05 Data Retention Policy by Plan Type