ID Mapping has implemented to identify the same user in the data of cross-source channels, assign them a unique identification QAID in Quick Audience, and pull the data under their names. When you import a user tag table, you can obtain user attribute information from the pulled data and establish rules to resolve data conflicts. This way, you can build a user attribute information system. Then, you can use the unified user attribute information and User Profile in subsequent operations.
After the user attribute information system is specified, the actual value comes from the imported user tag table. For more information, see Tag Field Mapping Attribute Method. When the label field mapping a user attribute, the user attribute value will take the value of the field. For example, user attributes include age, gender, birthday, and city. When you import a user tag table, map the corresponding fields with these user attributes.
If tags from different tables field mapping the same user attribute, the user attribute values of the same user may conflict. You can resolve conflicts based on the specified assignment logic to facilitate consistency in subsequent use. For example, in the imported user tag table A, the age record is 20, and in the imported user tag table B, the age record is 21, and the user attribute "age" is mapped. The assignment logic specified for the user attribute is "retain the field value with the latest update time". In this case, the record retained for the age user attribute is 21.
When used later, only the mapped user attributes are displayed, and the original labels are no longer displayed. In this case, user attributes are essentially user tags, and their usage information is managed on the Tag Management page.
User Attribute List
Choose Workspace> Configuration Management > Data Import Management > Data Import > User Attributes. The following figure shows the user attributes. 
The list displays all user attributes in the space. The following information is displayed:
Display Name: Name of the property.
Attribute Code: the English name of the attribute.
Type: the data type of the property. The data type of the property can be text, multi-value, numeric, or time.
Source: includes system preset and custom. The system presets some common properties. You can edit the preset properties or customize new properties based on your business requirements.
Display Status: indicates whether the property is displayed in operations such as tag management, filtering, and marketing. That is, whether the property is put into use does not affect the field mapping of the property when the user tag table is imported.
Tag field mapping attribute methods
User attribute values come from the user tag table. When a tag field mapping a user attribute, the user attribute value will adopt the value of this field after scheduling and importing.
Two methods of tag field mapping attributes are supported:
Automatic mapping by field name: If you set the field name to property encoding, the field is automatically identified and mapped to the corresponding user property when you configure the Table Structure Configuration.
Manually configure mappings: You can manually configure and map fields to corresponding user attributes during User Tags.
The configured user tag table can be mapped by editing the table structure configuration. On the next scheduled import, the attribute starts to fetch data.
Custom User Attributes
Procedure
In the left-side navigation pane, choose Configuration Management > Data Import > Data Import > User Attributes.
Click Add Property in the upper-right corner.
Configure the following parameters:
Parameter
Guide
Name
Enter the user attribute name.
Attribute encoding
Enter the English name of the user attribute.
If you set the field name of the user tag table to Attribute Encoding, the field stores the corresponding user attribute value. This field is automatically identified and mapped to the corresponding user attribute when you configure the Table Structure Configuration.
Data types
The type of the data. Valid values: Text, Multi-value, Number, and Time.
assignment logic
The assignment logic that is used when multiple fields that are associated with a user attribute conflict with each other.
Retain the field value with the earliest creation time
Retain the field value with the latest update time
Retain the field value with the highest frequency of occurrence
Nullable value logic
The value logic when the field is empty. Valid values:
Valid values take precedence: If one of the fields contains null values, null values are excluded by default, and values are obtained among the remaining non-null fields based on the selected assignment logic.
Assignment logic takes precedence: If a field in multiple fields has a null value, the value is strictly based on the selected assignment logic, regardless of whether it is a null value.
Data dictionary configuration
For text attributes, you can configure a data dictionary to specify the correspondence between the field value in the encoding and the display value. The display value is on the left. If the field value is not matched, the corresponding display value will be displayed later. If the field value is not matched, the original field value will still be displayed.
Click Add Configuration, as shown in the following figure. In the Add Configuration dialog box, set Display Value and Encoding Value. Click Add to add a group.
Click OK.
Change the display status
The display status indicates whether the attribute is displayed in operations such as tag management, filtering, and marketing. That is, whether the attribute is put into use does not affect the field mapping of the attribute when the user tag table is imported.
To change the display state of an attribute, simply toggle the switch in the list, as shown in the following figure.
View user property details
Click View in the list to view the details of the user property, including the configuration and the source channel of the associated field, as shown in the following figure.
Edit User Properties
Click Edit in the list to modify user attributes, as shown in the following figure. For more information, see Customize User Attributes.
You cannot modify the property encoding and data type.
After the assignment logic, null value logic, and data dictionary configuration are modified, the modification takes effect when the fields associated with the attribute are imported in the next scheduling.
Delete a custom user attribute
You can click Delete in the drop-down list to delete a custom property.
After deletion, the user attribute is no longer used, and the mapped fields are automatically unmapped.