Establish a real-time authentication connection #

Client side #

1. Enter the [event tracking verification] module, navigate to the left to confirm the application, and select the operating system to be verified on the page - client side.
2. Use the client side (mobile phone) to scan the QR code (WeChat, browser and other functions that can scan the QR code can be used), select Open in the mobile browser in the upper right corner, and click [Start real-time detection] on the mobile page after opening.

   warning

   Please make sure that the correct version of the app (app name, App_name, App_id) is installed on the phone, and the correct evocation scheme is set and opened on the phone.

Mini Program #

1. Enter the [event tracking verification] module, navigate to the left to confirm the application, and select the operating system to be verified on the page - Mini Program.
2. Scan Mini Program Code
   • This page shows the generated and uploaded Mini Program QR code, and the QR code attributes have the relevant attributes to start event tracking verification;
   • After scanning the code to enter the Mini Program, the SDK starts the real-time detection connection according to the event tracking detection attribute;
   • After scanning the code successfully, automatically enter the event tracking detection page.
3. If you have not uploaded the Mini Program QR code, you can generate and upload the Mini Program code according to the relevant attribute instructions.
   
4. Click "Upload Mini Program Code" to enter the Upload Mini Program Code pop-up page; generate the Mini Program code according to the provided attributes and upload it. After the upload is successful, click "Finish" to upload the Mini Program code.
   
5. If multiple users scan the code and do not start detection, you can select your mobile phone to scan the code according to the user who scanned the code and related information listed (in reverse order according to the scanning time), and automatically enter the event tracking detection page after success
   

H5/PC webpage #

1. Enter the [event tracking verification] module, navigate to the left to confirm the application, select the operating system-H5/PC webpage to be verified on the page, enter the webpage address to be tested, and click the [Generate QR code] button.
2. If it is a vertical screen of the mobile phone, you can directly scan the QR code of the mobile phone to enter the test page, and the scan page will automatically jump to the [datagovernor-event tracking verification page]. If it is a horizontal screen of the website, you can click Open after the URL below, open the website you want to test, and then switch back to the [datagovernor-event tracking verification page] on the computer.
   
3. On the [Event Tracking Verification] page, select the verification rule, then follow the procedures, and finally trigger the event tracking report of the webpage.

On-demand verification #

1. The event tracking design plan is entered and reviewed in [request management]. After the development of the event tracking plan is completed, in order to ensure the quality of the data online, it is recommended that the test students perform corresponding verification in [event tracking verification] to ensure that the event tracking plan. The content is reported and the data type and reported value meet the requirements.
2. We provide two sources of validation rules, on demand and per filter, both of which are essentially validation rules, and then use validation rules to verify whether the event tracking data reported by the client side meets expectations.
   1. According to the requirements, the event tracking, attributes, attribute types, values, etc. entered in the requirements of [request management].
   2. By filter, it means to verify according to the event tracking information in "event tracking management" - > "event tracking retrieval".
3. Select Verify by Demand in the verification rules of the real-time verification interface, select the corresponding requirement, and click Start Verification.
4. Here is an example: the validated event tracking is: video_play_end. Verification by demand means to verify only according to the event tracking information in the demand in "event tracking management". The event tracking content and verification results in the demand are as follows:
   
   
5. The system rules for verifying errors according to requirements are as follows:
   1. Whether the event tracking in the requirement has been reported in this verification, otherwise an error will be reported
   2. Whether the mandatory properties set by event tracking in the demand are reported, otherwise an error will be reported
   3. Whether the attribute reporting type is consistent with that defined in the requirement, otherwise an error will be reported
   4. Whether the reported attribute value is within the set value range. If no value is set, it will not be checked by default.
   5. If there is a set scene in the requirement, check whether the scene meets expectations. For details, please see 3.6 Scene Management
6. Verification result description: Because the event tracking information in the demand stipulates that the access attribute only allows 4g, action_type only allows up, the attributes in the event tracking are actually reported to do not match this, so the verification result is abnormal

Validate by filter #

1. Here is an example to illustrate the rules for verifying by filter: by filter refers to retrieving the attributes, attribute types, values, etc. of event tracking in the list by event tracking. The difference between event tracking and requirements is that the event tracking in the event tracking list may be merged according to three feature iterations. For example, A requirement corresponds to an event tracking with 3 attributes, and B requirement corresponds to an event tracking with 4 new attributes. Then the event tracking list has a total of 7 attributes that need to be verified.
2. Select Verify by Filter in the verification rules of the real-time verification interface, select the corresponding filter, and click Start Verification. The filter can also be unselected.
   
3. Here is an example: the validated event tracking is: video_play_end. Verification by filter means that only the content in the basic information in "event tracking management" is verified. The event tracking content and verification results in event tracking retrieval are as follows:
   
   
4. The system rules for verifying errors by filter are as follows:
   1. Whether the mandatory properties of the event tracking in the event tracking details are reported, otherwise an error will be reported
   2. Whether the property reporting type is the same as defined in the event tracking details
   3. Whether the reported attribute value is within the set value range. If no value is set, it will not be checked by default.
   4. If it matches the scene, check whether the properties and values in the scene meet expectations. For details, please see 3.6 Scene Management
5. Verification result description:
   1. Because the event tracking information in the event tracking retrieval stipulates that the access attribute allows 4g, wifi, and the action_type attribute allows down and up. In fact, the attributes in the event tracking are reported to meet the requirements, so the verification result is successful

Advanced features #

1. Filtering conditions: Provide users with the event tracking data reported by the client side to filter, so that users only pay attention to the event tracking they care about.
   1. Event name: Filter by event name, here we also support searching by regular expression. Event names are supported with and without options
   2. Event properties: Support filtering by the properties of the event, selecting a relationship where multiple properties are or
   3. Show only abnormal event tracking: only filter out event tracking with abnormal verification results
2. Backfill filter criteria: When a rule is selected, if a filter is selected, the filter data will be backfilled onto the above criteria options. If a requirement is selected, the events within the requirement are backfilled into the event filter box
3. Save As/Save As Filter: This provides the entrance to quickly save the filter as a filter, which is convenient for users to save the filter and reuse it later.
   1. If you do not select a filter, you can directly save the filter as a filter.
   2. If you selected a filter, you can choose to update or save as a filter.
4. Timeline This shows the event tracking reported by the client side. Here is a simple explanation of the information on the timeline
   1. Time dimension: The default is to display according to the time dimension
   2. Event tracking dimension: The event tracking dimension is convenient for users to view the reporting of an event tracking
5. Delay time: The mouse floats to the time will be displayed. Delay time = time to show event tracking verification platform - time to report to server level on event tracking
6. Highlighting param: This feature can display properties in the form of highlighting, suitable for only focusing on a few certain properties
7. Copy: only the event name and params will be copied, and params will be copied in json format
8. Full copy; the original log reported by the client side will be completely copied intact, of course params will not be json formatted
9. Pause/Continue: Click "Pause" and the event tracking reported by the client side will be directly discarded. Click "Continue", and the event tracking reported by the client side will continue to be pushed to the interface.
10. Clear event tracking: Clicking "Clear event tracking" will discard all current event tracking. For example, when the app first starts, it will report a lot of event tracking, and these event tracking are generally not event tracking to be verified, so you can clear these event tracking
11. Save Report: Click "Save Report" to save the event tracking reported this time for subsequent viewing. After clicking "Save Result", the event tracking reported by the client side will not be pushed to the front end or saved to this result before the save is successful or during the process of canceling the save.

1. After verification, there is a [Save as Report] button in the upper right corner of the interface. After clicking, you can filter the event tracking details you want to keep and save them as reports that can be viewed again.
   
2. In the event tracking verification left menu, select the verification report, you can view all the verification reports retained by the project, and open the report to see the details reported at that time.
   
   

Users can save frequently verified event tracking as validation filters for easy reuse. The conditional options in the filter can refer to the conditional options in the real-time validation, which are consistent.