A new structured attribute model designed to improve data quality, consistency, control, and future segmentation capabilities. Structured attributes replace the previous free-form attribute creation model with a strongly typed framework that includes an attribute ID, data type, label, value, and update timestamp.
Structured attributes are organization-wide definitions that can be reused across projects within the same organization, enabling better profile sharing, reporting, and customer orchestration. Existing Attributes continue to function and are now displayed as Legacy Attributes, allowing organizations to transition gradually without impacting running implementations.
Legacy Attributes will continue to coexist with the new attributes for the time being. Legacy attributes will eventually be deprecated. There is no automatic migration from legacy attributes to the new attributes.
Benefits
Improve data quality through data type validation.
Ensure consistent structured attributes across projects within the same organization.
Reduce duplicate attribute creation by exposing existing organizational attributes during attribute selection.
Enable future attribute-based segmentation capabilities.
Prerequisites
The Structured Attributes feature must be enabled for your environment
You must have access to Project Settings > Profile Metadata > Attributes.
Adding a Structured Attribute
To add a structured attribute, navigate to Project Settings > Profile Metadata > Attributes and select Add Attribute. If no attributes have been added to the project, the page displays the message"No Attributes have been added to this project yet."
Click Add Attribute to open the Add Attribute to Project window.
Attribute Details
Name
Enter the name of the attribute.
If no matching attribute exists, the system prompts you to create a new attribute using the entered name. Click Create to create a new attribute for the project.
If existing organizational attributes are available, they are displayed in the dropdown when you select the Name field.
As you type, the list is filtered to show matching attributes.
If a matching attribute already exists, select it from the list instead of creating a duplicate.
When an existing attribute is selected, the attribute details are automatically populated. This helps promote reuse of shared organizational attributes across projects.
Description
Enter a meaningful description to help users understand the purpose and intended use of the attribute.
When you select an existing organizational attribute, the description is automatically populated from the existing definition.
Type
Select the attribute data type from the drop-down list. Available attribute types include:
Type | Description | Example |
|---|---|---|
String | Stores text values. | Customer Name = "John Smith" |
Number | Stores numeric values. | Loyalty Points = 1500 |
Boolean | Stores true or false values. | Premium Member = True |
List | Stores multiple values in a collection. | Preferred Channels = Email, SMS, RCS |
Object | Stores structured information containing multiple fields. | Address containing Street, City, State, and Postal Code |
Select the appropriate data type when creating the attribute. The data type cannot be changed after the attribute is created. If a different data type is required, create a new attribute.
Structured attributes enforce data type validation. If incoming data does not match the configured attribute type, the update is rejected, and an error is returned. This helps maintain profile data quality and consistency.
After providing the required information, click Add to Project.
The newly added attribute is displayed under the Attributes list and becomes available for use in the project. Structured attributes are organization-wide definitions and can be reused across multiple projects within the same organization.
Updating a Structured Attribute
After a structured attribute has been added to a project, you can update the attribute name and description as needed. Renaming an attribute updates the display name while preserving the underlying attribute definition and identifier. This ensures that the system continues to recognize the same attribute even after its name changes.
If you select an existing organizational attribute and then modify its name while adding it to the project, the system treats it as a new attribute and prompts you to create a new attribute definition. To rename an existing attribute, first add the attribute to the project, then use the Edit (pencil) icon to update the attribute name.
To update a structured attribute:
Navigate to the attributes list and locate the attribute you want to update.
Click on the Edit (pencil) icon in the Actions column. The Edit Attribute window is displayed.
Update the Name and Description as required. Click Update Attribute to save your changes.
Validation Rules
If the updated attribute name already exists within the organization, the update will not be saved, and the following notification is displayed: “Could not update attribute. Structured attribute name already exists for this organization.” For Example:
An attribute was originally created with the name Account type. Later, you decide that Bank Account type is a better name. You can edit the attribute and update its name to Location. After the update, the new name is displayed wherever the attribute is referenced, while the system continues to use the same attribute definition internally
Deleting a Structured Attribute
Structured attributes that are no longer required can be removed from a project. Before deleting an attribute, review its usage carefully because removing an attribute may impact existing graphs that reference it.
To delete a structured attribute:
Navigate to the Attributes list and locate the attribute you want to delete.
Click on the Delete (bin) icon in the Actions column. The Delete Attribute confirmation window is displayed.
Review the warning message and verify that you are deleting the correct attribute, and click Delete to permanently remove the attribute from the project.
The warning message states: “Attribute Name and all of its nested fields will be removed from the project and may impact existing graphs that reference it.”
Best Practices
Choose the most appropriate data type when creating a structured attribute. Avoid storing numbers or dates as string values, as proper data typing enables reliable reporting, filtering, segmentation, and future platform capabilities.
Use business-friendly names that are easy to understand and maintain. Consistent naming makes attributes easier to find, reuse, and manage across teams.
Treat structured attributes as shared organizational assets. Reusing attributes helps maintain consistency and reduces duplication across projects.
FAQ
Can I still create legacy attributes after enabling Structured Attributes?
No. New attributes must be created using the Structured Attributes model. Existing legacy attributes can still be used and managed, but creation of new legacy attributes is restricted.
Will my existing legacy attributes stop working after enabling Structured Attributes?
No. Existing legacy attributes continue to function, and there are no breaking changes to deployed graphs. Legacy and structured attributes can coexist during the transition period.
Can I rename a structured attribute?
Yes. Structured attributes can be renamed after creation, but the data type selected during creation cannot be changed later.
Can I create multiple structured attributes with the same name but different data types?
Yes. Structured attributes with the same name are supported. However, it is recommended to use unique, business-friendly names to avoid confusion and simplify attribute management.
Can I see structured attributes created in other projects?
Yes. Structured attributes are designed to be shared and reused across projects within the same organization.
What happens if incoming data does not match the attribute type?
The update fails, and an error is returned. Structured Attributes enforce data type validation to help maintain data quality and ensure reliable downstream reporting, analytics, and segmentation capabilities.