Folder traits let you automatically aggregate traits that reside within the same folder and all child folders into a targetable segment.
A folder trait contains all the traits in a parent folder and its associated child folders. This lets you automatically segment and target your users at different folder levels. For example, let's say you have a folder structure like this:
Folder traits qualify all the users in these folders in an automatically created Electronics Folder Trait (based on the name of the parent folder). And, this process repeats itself as you move down the file structure. In this case, folder traits capture all of the users in the Laptops and Brands folders in an automatically created Laptops Folder Trait.
Folder traits are selectable in segment expressions. Selecting a folder trait is equivalent to selecting all the traits within that folder and its subfolders with an "OR" grouping.
The frequency count of a folder trait is the sum of realizations of the traits in its folder and its child folders. The illustration below shows traits A, B and C, which live in the Automobile folder. Consider that each of the traits have the following realizations:
In this case, the Automobile Folder Trait has 7 realizations.
Folder traits capture all the users from the traits in the folder structure below them. If you move a trait from a folder to another folder, the change propagates to our data collection servers just like a trait rule change. The reporting updates in the next reporting run to reflect this change across the reporting date ranges (1, 7, 14, 30, 60, 90, lifetime). The old reporting numbers from the previous days will not change.
For companies using Role-Based Access Controls (RBAC), your users with the appropriate RBAC permissions are able to change the data source associated to the folder trait. A user must belong to a group with either of the following:
Learn how to assign RBAC permissions in our administration documentation.
|Trait type||Onboarded traits and algorithmic traits contribute at most 1 realization to a folder trait's frequency.|
|Moving traits between folders||Moving a trait from a folder to another will disqualify that trait from the first folder trait and qualify it for the second folder trait. This means that if you delete or move a trait from the folder, the users in the trait's population will be unsegmented from the segments using the folder trait as a segment expression.|
|System variables||Folder traits cannot be realized in event calls using the d_sid parameter.|
|Reporting||Folder traits are autocalculated traits and do not appear in Overlap Reports.|