All Products
Search

This Product

    Quick Audience:User Behavior Table Data Requirements

    Document Center

    Quick Audience:User Behavior Table Data Requirements

    Last Updated:Jun 23, 2026

    Learn about the data requirements for user behavior tables before importing them into Quick Audience.

    Note

    Because 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, Quick Audience does not support the following MaxCompute data types to ensure smooth data flow between the computing and analysis sources: BOOLEAN, CHAR, ARRAY, STRUCT, MAP, BINARY. For the full MaxCompute data type list, see 2.0 Data Type Version.

    A user behavior table records user actions such as logon, browsing, adding to cart, collecting, and purchasing. The following example shows a MaxCompute wide table:

    124235

    Field requirements:

    Field Type

    Field type

    Description

    The ID of the user who executes the statement.

    Text type, numeric type

    • The user ID can be used for marketing and push messaging. Set at least one user ID based on your business needs.

    • You can use all ID types enabled in ID Type Management. Only one field per ID type is allowed.

    • You can save the original or encrypted user ID. Supported encryption methods: MD5, SHA256, and AES.

      Taobao OUID is an exception. Taobao OUIDs are already encrypted by Taobao before being provided externally. Keep them as-is.

    • 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, ensure the number is 11 digits without the 86 country code prefix. Otherwise, it cannot be used for SMS marketing.

    The time when the behavior occurred.

    Time

    • All fields are required. Specify one field for each type.

    • Valid behavior type values include login, browse, add to cart, collect, purchase, share, and delete.

    behavior channel

    Text type, numeric type

    The type of the behavior.

    Text

    Behavior attribute

    Text, numeric, and time

    Examples include products, categories, brands, shops, coupons, discounts, and pre-sale periods. Optional. You can specify multiple fields.

    The statistical metric. Valid values:

    Numeric types

    Examples include quantity and amount. Optional. You can specify multiple fields.

    Note

    • All field names are customizable.

    • The table has no primary key. The same user ID can have multiple records. If any value in the behavior time, behavior type, behavior channel, or behavior attribute differs, a separate row is required.

    • Partition tables are supported.

    FAQ

    Why was the behavior object field removed from the data table sample?

    Answer: Starting from V4.4.0, to store reported Event data as a user behavior table, the behavior object field was renamed to behavior attribute. The existing behavior attribute field remains unchanged. You can still use the original user behavior table schema. Behavior object fields in configured schemas are automatically converted to behavior attribute fields. When you perform operations such as User Behavior Table Structure Configuration, Audience Filtering, AIPL Model generation, and Preference Tags, behavior object and behavior attribute configuration items are merged.