What are the data requirements for importing user behavior tables for QuickAudience - Quick Audience

This topic describes the data requirements for importing user behavior tables in Quick Audience.

Note

Due to the fact that the Data Source type for storing raw data is MaxCompute, and the Analysis Source type used by Quick Audience is ADB 3.0 or Hologres, in order for data to flow smoothly between the computing and analysis sources, Quick Audience does not support the following data types of MaxCompute: BOOLEAN, CHAR, ARRAY, STRUCT, MAP, BINARY. Please refer to the 2.0 Data Type Version for the MaxCompute data type list.

The user behavior table records the logon, browsing, purchase, collection, and purchase behaviors of users. Example of MaxCompute large-width representation:

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 pushing. Set at least one user ID based on your business needs. You can use all the ID types that are enabled in ID Type Management. You can store only one field of the same ID type. You can save the original user ID or the encrypted user ID. The encryption method supports MD5, SHA256, and AES. Except for Taobao OUID, Taobao OUID has been encrypted in a unique way when Taobao provides it to the outside. Please keep it as it is. For more information about 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 user ID of the mobile phone number type, make sure that the mobile phone number format is 11 digits and 86 is not added before the number. Otherwise, it cannot be used for SMS marketing.
The time when the behavior occurred.	Time	All fields are required, one for each type. The behavior type value can be login, browse, add purchase, collection, purchase, share, delete, etc.
behavior channel	Text type, numeric type
The type of the behavior.	Text
Behavior attribute	Text, numeric, and time	such as products, categories, brands, shops, coupons, discounts, and pre-sale periods. Optional. You can specify multiple fields.
The statistical metric. Valid values:	Numeric types	such as quantity, amount, etc. Optional. You can specify multiple fields.

Note

You can customize the names of all fields.
The table does not have a primary key. The same user ID can have multiple records. If any of the conditions in the behavior time, behavior type, behavior channel, and behavior attribute are different, a separate row must be used.
Support partition table.

FAQ

There was a kind of behavior object field in the previous data table sample, why not now?

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