Transcript

In this video, we’ll add attributes to the Data Modeler. Major topics include: User attributes and account attributes.

We’re starting within Global Settings under Data Management, Data Modeler. The available attributes are different depending on whether you’re on the Account or User tab. Let’s say I want to track whether a customer has agreed to be a reference. Should I add this attribute at the user level, the account level, or both? It depends on how you will use this information.

Let’s look at each option, starting with user level. When I click to add a new attribute from here, I can give it a name, and then choose the data type. We’ll keep it simple for now and choose Text, but we’ll come back to this later. I’ll also choose the dimension, which determines how to group this attribute. You can find more information on these options in another video, and then the last option ensures that we allow other Totango users to edit this attribute’s value, which of course in this case, we do so that CSMs have the ability to track this data point themselves.

Now that the attribute is added to the database, we can find it immediately within any user profile by clicking add and then searching for the name of the attribute. Because we chose text, I could enter anything here–Yes or True or Y. This makes it difficult to filter on the value.

Instead, let’s go back into the Data Modeler and delete this Text attribute. And this time, let’s add it as a multi-select list. Now, we can choose what values are allowed: Yes or No. After refreshing, now when I add this new attribute, I can only choose from those options. When we save a value, it shows up in the user’s profile.

Also, when we create a user segment and filter by this attribute and value, we can see all users where reference is marked yes. Additionally, we can use this same user filter to find the accounts where any user reference is marked yes. In other words, we don’t *have* to create a separate Reference attribute at the account level to be able to create a segment. However, there are some use cases for creating at both levels, depending on your needs for viewing historical changes or mapping with other systems.

If we go back to Data Modeler and create this attribute at the account level, we see similar options for choosing name, dimension, type, and editiability. For type, account attributes have the option to use a simple list rather than a multi-select, so I’m going to choose that option instead. Just like we saw with the user attribute when it’s added to the database, you can immediately go to any account profile, click the All Tab, and search for this attribute to set a value if marked as editable. And again, we can create an account segment using this account attribute.

And just like we did before, we can also create a list of users whenever their related account is marked referenceable. In this scenario, assuming we didn’t have a reference attribute at the user level, we could also pull in a filter for key contact to isolate which users on the account we should reach out to.