Your properties are organized as follows: To review the list of properties available in your Heap account, navigate to Definitions > Properties. For more information on how personal and shared data is managed, see Shared vs. Personal properties only appear on your account, wheres shared properties are available for all of your team members to use in analysis. You won’t see these names in the app, though the distinction is important to understand when using properties.Īdditionally, properties in Heap are grouped by whether they are personal or shared. Server-side properties are what you are capturing on your backend. What is the difference between client-side and server-side properties? Client-side properties are all of the actions we are capturing on the app or site you have installed Heap onto. Filter your reports by users who have started or stopped doing an event, who are repeat users or are users who are re-engaging with the event. Active usage properties: Digging deeper into the concept of user behavior, active usage properties allow you to better understand engagement with your features.Examples include ‘users who have done a count of’, ‘users who have done’. Behavioral properties: Behavioral properties can be used to filter your reports by users who have or have not done something for more granularity.These types of properties are specifically for refining your queries when conducting analysis: Event properties: Metadata about the actions users are taking, such as the target text on the button they clicked, or what browser they used.Unlike event and user properties, you are unable to create your own session properties. Session properties: These roll up into the user and the events taken during a session.Other than “initial” properties, these can change. User properties: Metadata that we know about a user, such as where were they the first time they visited your homepage, or what city were they in during their most recent session.The following properties are named based on how where the property fits in Heap’s user > session > event hierarchy data model: Enriched properties: If you’re using one of our integrations, this property type refers to the information we are pulling from those sources.Details about these properties and steps to define them are available further on in this guide. This can be useful for things like grouping app screens or blog pages into one property. Defined properties: You can define your own properties to create a new schema on top of existing properties in your account. ![]() For example, you can use the addUserProperties API to assign custom properties to any of your users from your servers, such as account-level information from your database, or demographic info. Custom properties: These are brought in via Heap’s APIs or Snapshots, and allow you to enrich your autocaptured data.A full list can be reviewed in Autocaptured Data. Autocaptured properties: Once Heap is installed on your website or app, these properties are automatically captured.The following properties are named based on whether they are automatically captured by Heap, brought in via an implementation of one of our APIs, defined within the app, or brought in via an integration. There are many different types of properties in Heap, as described in the sections below. Heap gives you complete organizational control over the extensive set of property data available to you. You can also bring in additional custom properties via Heap’s APIs and define new properties. Heap automatically captures a wide variety of properties for you, as listed in Autocaptured Data. ![]() Properties are bits of metadata that are captured during user interactions with your app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |