In addition to the clearly predefined events, developers can report custom events according to their own analysis needs.
Custom event names can be defined by the developer.
Here are the naming conventions for event names:
A custom property is a JSONObejct object where each key-value represents a property.
Key: Property Name
Value: Property Value
Custom Property Types
The data type of custom event properties is determined by their data types reported for the first time and cannot be changed once confirmed. For subsequent reporting of the same properties, only properties with the same data types as the first occurrence will be stored in the database.
Data Type | Description | Example |
---|---|---|
number | Range from -9E15 to 9E15, without quotation marks. | 1234, 12.34 |
string | Limit 2KB. Numbers with quotation marks will also be identified as strings. | "dashen", "北京", "1234", "true" |
date | "yyyy-MM-dd HH:mm:ss.SSS", "yyyy-MM-dd HH:mm:ss", or "yyyy-MM-dd 00:00:00" | "2023-03-01 12:34:56","2023-03-01 12:34:56.789","2023-03-01 00:00:00" |
boolean | True or false without quotation marks. | true, false |
array | All elements in an array will be converted into strings. | ["a","1","true"] |
Note:
The data type of the property determines their analysis logic available in analysis models. For example, the numerical type can perform calculations such as maximum value, minimum value, and summation, while the Boolean type can perform calculations of true and false values. Therefore, when determining the format of data reporting, you need to consider the analysis scenarios and business needs and formulate a complete event tracking plan as directions.
Parameters supported:
Parameter Name | Parameter Meaning | Parameter Type | Mandatory |
---|---|---|---|
customEventName | Developer custom event name | String | YES |
customEventData | Developer custom event property | JSONObject | NO |
preEventData | Preset properties: only two keys, _pay_amount and _currency_type, are supported. | JSONObject | NO |
Call example:
const data = {
eventName:"testEvent",
customProperties:{
test1:"key1",
test2:2,
test3:[1,"2"],
}
}
globalThis.solarengine.trackCustom(data);