1. How do I report H5 data to my mini program?
For example, an activity page developed by H5 in the mall mini program only appears in the mall mini program.
The business wants to see all access data of all users from the perspective of mall mini programs, including all data of H5 activity pages and mini programs.
There is no need to create an independent application and appkey for the H5 in the background of QuickTracking, and the mini program can be directly used.
The mini program needs to be integrated with the mini program SDK of QuickTracking, H5 needs to be integrated with QuickTracking H5 SDK, and the appkey of H5 needs to be set as the appkey of the mini program
H5 needs to obtain the device ID and account ID of the current mini program and set them to its own device ID and account ID. The account ID needs to be set in h5 when the user logs on and in the logon state.
In the global attributes of H5, you must report the global attributes of the mini program obtained from the mini program, the scenario value of the mini program, the channel parameter, openid (optional, if the device ID is openid, this field is not uploaded in the global attributes), and unionid (optional, if the device ID is unionid, this field is not uploaded in the global attributes).
How to report "H5 data with multiple terminals" to each terminal in 2
For example, integral mall H5 is embedded in many small programs such as mall small programs and membership hub small programs. integral mall H5 can also be directly entered through official account.
The business of each mini program hopes that the data of the user will be analyzed together with the mall mini program when browsing the H5 by the mall mini program, the data of the user will be analyzed together with the member mini program when browsing the H5 by the membership mini program, and the data of the H5 directly accessed through the browser will be analyzed by the H5 business itself.
Create an independent application and appkey for the H5 instance in the background of QuickTracking.
It is necessary to judge which mini program H5 is in first. If it is an independent H5 page, use H5's own appkey. If it is in a mini program, use the appkey of the mini program currently in it. Note that mini programs need to be integrated with QuickTracking's mini program SDK, and H5 also integrates QuickTracking H5 SDK.
H5 needs to obtain the device ID and account ID of the current mini program and set them to its own device ID and account ID. The account ID needs to be set in h5 when the user logs on and in the logon state.
In the global attributes of H5, you must report the global attributes of the mini program obtained from the mini program, the scenario value of the mini program, the channel parameter, openid (optional, if the device ID is openid, this field is not uploaded in the global attributes), and unionid (optional, if the device ID is unionid, this field is not uploaded in the global attributes).
How to report "multi-end H5 data" to H5 applications in a unified way 3
For example, integral mall H5 is embedded in many small programs such as mall small programs and membership hub small programs. integral mall H5 can also be directly entered through public numbers.
The mini program's business does not want H5 data to appear in its own business data, while H5's business wants to see today's total page view together in H5 applications, including the number of users accessed through mall mini programs or membership hub mini programs.
Create an independent application and appkey for the H5 instance in the background of QuickTracking.
H5 integrates QuickTracking H5 SDK and uses H5's own appkey
H5 needs to obtain the device ID and account ID of the current mini program and set them to its own device ID and account ID. The account ID needs to be set in h5 when the user logs on and in the logon state.
In the global attribute of H5, you must report the global attribute of the mini program obtained from the mini program, the scenario value of the mini program, the application name of the mini program, the channel parameter, openid (optional, if the device ID is openid, this field is not uploaded in the global attribute), and unionid (optional, if the device ID is unionid, this field is not uploaded in the global attribute).