Custom Events

   In addition to the clearly predefined events listed in the last chapter, developers can report custom events according to their own analysis needs.

   The custom event names should be customized by the developer.

   Here are the naming rules:

• String type
• Start with letters only.
• No more than 40 characters.
• Contain numbers, lowercase letters and underscores only.

Custom Properties

    A custom property is an NSDictionary object where each element represents a property. "Key" is the property name.

   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.

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.

   Here is an example code of a user purchasing a product:

[[SolarEngineSDK sharedInstance] track:@"isFirstBuy" withProperties:properties];

Preset Properties for Custom Events

Function

- (void)track:(NSString *)eventName withCustomProperties:( NSDictionary * _Nullable )customProperties withPresetProperties:( NSDictionary * _Nullable )preProperties;

Sample Code

NSDictionary *customProperties = @{
           @"orderId":@"1234567",
           @"payType":@"success"
 };

 NSDictionary *presetProperties = @{
          @"_pay_amount":@4.9,
          @"_currency_type":@"USD"
};
        
[[SolarEngineSDK sharedInstance] track:@"order" withCustomProperties:customProperties withPresetProperties:presetProperties];