User Tag Table Data Requirements

Updated at:
Copy as MD

User tag tables imported to Quick Audience must meet specific data format requirements to ensure compatibility between computing and analysis sources.

Note

The MaxCompute data source type for storing raw data is MaxCompute, and the Analysis Source type used by Quick Audience is ADB 3.0 or Hologres. To ensure data flows smoothly between the computing and analysis sources, Quick Audience does not support the following MaxCompute data types: BOOLEAN, CHAR, ARRAY, STRUCT, MAP, BINARY. For the complete MaxCompute data type list, see 2.0 Data Type Version.

A user tag table records dimensional characteristics of users. The following example shows a MaxCompute wide table:

9868

Field requirements:

Field Type

Tag Type

Description

User ID field

Text type, numeric type

  • User IDs are used for marketing, push notifications, and other operations. user_id is the primary key and a required field. Configure additional user IDs based on your business requirements.

  • All ID types enabled in ID Type Management are supported. Only one field per ID type is allowed.

  • User IDs can be stored in plaintext or encrypted form. Supported encryption methods: MD5, SHA256, and AES.

    Exception: Taobao OUID is already encrypted using a proprietary method by Taobao. Keep it as-is without additional encryption.

  • For the ID types and encryption methods supported by each marketing and push channel, see ID Types and Encryption Methods Supported by Each Channel.

  • If you use a mobile phone number as the user ID, the number must be 11 digits without the country code prefix 86. Otherwise, the ID cannot be used for SMS marketing.

Tag field

Text type, numeric type, time type, and multi-value type

  • Tag fields store other dimensional characteristics of users, such as user profiles, pivot analysis dimensions, and group filtering criteria. Configure tag fields based on your business requirements.

  • You can set the field name to a User Attributes property code. The field then stores the corresponding user attribute values and is automatically identified and mapped when you configure the Table Structure Configuration. You can modify this mapping or assign values to user attributes when importing the table schema.

  • Tag fields support multiple values separated by delimiters. Do not use delimiters that may appear in the field values.

Note

  • All field names are customizable.

  • user_id is the primary key. Each user_id must have only one record.

  • Partitioned tables are supported.