1. Overview

The following functions are supported in the event table:

NounExplanationExample
Events

A series of actions triggered by the analyzed object within the product, such as clicking, browsing, etc.

For the e-commerce industry, meta events such as login, add_to_cart, and pay_order need to be created.
Custom Events

Multiple events are combined to form a custom event.

Filter criteria can be set for each event.

To analyze new users, meta-events app_start and page_view are combined to form a new virtual event, which can be selected for analysis in Sensors Analytics.

Visual LabelingBased on the SDK's full buried point function, users can realize the definition of buried points by circling on the page.For ease of analysis, will add to cart The button click event ($AppClick) is defined as Add Cart button Click event .
Properties

Properties are dimensional information that describes the object or event being analyzed. Common attribute is a kind of attribute, which refers to the actual field in the underlying physical table, and the data can be obtained through buried point collection or data mapping.

The add to cart event has common attributes: product_id, product_name, time, and so on.
Custom Properties

Custom Property refers to a new property value generated by secondary processing of property or other extended property.

If you want to analyze the data according to "week X", you can extract and create a virtual attribute from the time attribute:

SQL expression:dayofweek(EPOCH_TO_TIMESTAMP(events.register_time))

Lookup Tables

In addition to creating custom properties directly based on properties, you can also create more complex custom properties by establishing dimension association and introducing more properties.

Suppose there is a pay_order meta event in Sensors Analytics, and the event has attributes such as product_id and product_name. Now the user wants to use the product_manufacturer field to perform analysis, but this attribute is not inserted into the system. In this case, you can associate the event table with the product table that has this attribute, and introduce the product_manufacturer field to meet the analysis requirements.