Learn to use the Attributes view, hide and show attributes, analyze your data flows and optimize it, see what Hull discovered about your data.
The Attribute List shows you very valuable information about the Schema that Hull detected for your Users and Accounts. It is a very useful debugging and exploration tool. Here's some explanations about what it offers.
You can access it by clicking "Attributes" in the subnav of the "Users" and "Accounts" section of your dashboard.
The User and Accounts attribute list displays all the attributes that were detected while ingesting external data. you can sort it, or filter it using the filter bar on the top right.
The second column of the list shows the number of updates for this attribute in the last 24 hours, across all your users / accounts. A very high nubmer can either be normal (because you have some frequently changing data) or an indicator of something wasteful. The other colums can help understand which it is better.
The third columm shows for how many distinct users this attribute changed in the last 24h. If you have a very high number of updates but a low number of Users (as materialized by the "Updates/User" counter, then it probably means those users are "flip-flopping" between values or that they are continuously updated. This is a very wasteful pattern that consumes traffic in Hull but also in your external services. It should be solved as it probably creates backlogs and delays in updating data, but also might create unstable values in your destination services.
This column shows the number of segments that rely on this attribute. You can hover to see their names. This data is useful to know if you're still using an attribute of if it's a legacy one. Keep in mind that this is only showing usage in Segments - We don't show here if you're sending and/or using this attribute in external services as there is no way to tell for some of them.
This column shows the connectors that generated those attribute changes, and when they did so last. If you see a single attribute being updated by several connectors, you need to apply judgement to see if it's expected or if you're overwriting data from one source with data from another.
Connectors generally try to write in their own attribute groups (i.e. Hubspot captures attributes in the
hubspot group) but some don't have these conventions (think SQL connector, Incoming Webhooks etc...)
This last column (only visible for User attributes) lets you define the behaviour of the platform when this attribute is updated. You can choose between
Visible + Tracked
Attribute Changeevent. It's very useful to be able to access and segment on the past values of an attribute (Think: "All users who went from <$500 MRR to >500MRR in the past 30 days) but it consumes an additional Incoming Record for each generated event. So activate only for the attributes you need to track
The attributes detail view shows you even more precise information about each attribute:
This view helps you get a sense of which user(s) are affected by too many udpates for instance.