The basic application scenarios of e-commerce are: page browsing, product list browsing, product list clicking, adding to favorites, adding to shopping cart, and settlement of payments. In order to facilitate the transaction of goods, product operators need to use data to insight into user behavior in every link. They can’t wait to add event tracking points to the entire process of every marketing activity or business function, and each time it continues with the development of the business Optimization, operations also need to continuously submit each version of the buried point change requirements for products and development.
The problem that this brings is that the demand for data is becoming more and more complex and marketing strategies change faster. If you rely on traditional hard-coding methods, efficiency and agility will be greatly compromised, leading to miss the best marketing time.
The method of burying points configured with DTM is undoubtedly a good solution. Its no-code, flexible and dynamic data labeling capability allows non-technical personnel to directly participate in the departmental code work, saving communication costs between departments and no need for technical development. People can track marketing data on demand to help refine operations.
1 Next, I will show how DTM realizes page browsing monitoring on the WEB side.
First, for different browsing depths, set page browsing 25%, 50%, 75%, 90%, and 100% as reporting events.
1.1 The conditions are configured as follows:
1.2 The code is edited as follows:
1.3 The docking analysis platform we selected in the configuration is GA. When an event occurs, the screenshot of the event is automatically sent to GA.
If you do not use DTM to monitor user behavior, you can only simply see the screenshots of web browsing (below) from GA, and you can't learn more and more specific user behaviors.
2 In the same way, the APP can easily realize page browsing monitoring
2.1 The code is edited as follows:
2.2 Screenshot of the last event sent to GA:
3 DTM realizes product list browsing on the WEB side
First, set the browsing depth to be equal to or greater than 37% and stay for 2 seconds as the trigger condition for the product list event.
3.1 The conditions are configured as follows (here, according to the settings, there should be 2 conditions):
3.2 The code is edited as follows:
3.2 The code is edited as follows:
4 DTM realizes product list browsing on APP
First, set the product list page sliding as the trigger condition of the product list event.
4.1 The conditions are configured as follows:
4.2 The code is edited as follows:
4.3 Screenshot of the last event sent to GA:
5 DTM realizes product list click on WEB
5.1 First, we first click on the Mate series of products and set three conditions.
5.2 Next, set up the code and quote these three conditions:
5.3 Finally, as long as any one of the conditions is met, it will be sent to the GA event screenshot:
6 DTM realizes product list click on APP
First, set each product on the product list as the trigger product click event.
6.1 The conditions are configured as follows:
6.2 The code is edited as follows:
6.3 Screenshot of the last event sent to GA:
7 DTM realizes that goods are added to favorites on the WEB side
7.1 First, set a "custom event", add it to favorites and name it "collectGood", as shown in the figure below:
7.2 When setting the collectGood event, let developers push related product data to the data recording layer
7.3 Configure code and reference record layer data:
7.4 Screenshot of the last event sent to GA:
8 DTM realizes that goods are added to favorites on the APP side
First, set a collection event to be generated when the collection button is clicked on the product details interface
8.1 The conditions are configured as follows:
8.2 The code is edited as follows:
8.3 Screenshot of the last event sent to GA:
9 DTM realizes that goods are added to the shopping cart on the WEB side
9.1 First, set a "custom event", add it to the shopping cart and name it addToCart, as shown in the following figure:
9.2 When setting the addToCart event, developers need to push relevant product data to the data recording layer:
9.3 Configure code and reference record layer data:
9.4 Screenshot of the last event sent to GA:
10 DTM realizes that goods are added to the shopping cart on the APP side
First, set a shopping cart event to be generated when the shopping cart button is clicked on the product details interface.
10.1 The conditions are configured as follows:
10.2 The code is edited as follows:
10.3 Screenshot of the last event sent to GA:
11 DTM realizes settlement and payment on the WEB side
11.1 First, set a "custom event", settle the payment and name it "settlement", as shown in the figure below:
11.2 When setting the settlement event, developers will be asked to push the overall transaction data to the data recording layer:
11.3 Configure the code and reference the record layer data, the product data is sent through "myprod":
11.4 When setting the settlement event, developers will also be asked to push related product data myprod to the data recording layer
11.5 The transaction situation can be seen in the sales performance:
You can view the specific product performance (equivalent to the order and order line have been combined):
12 DTM realizes settlement and payment on the APP side
First, set a settlement payment event after the payment is completed in the payment interface,
12.1 The conditions are configured as follows:
12.2 The code is edited as follows:
12.3 Screenshot of the last event sent to GA:
The above is the actual operation process of DTM to realize all basic application scenarios of e-commerce. We can see that the above-mentioned uncomplicated burying requirements can be realized only through DTM configuration. The advantage of this deployment method is that it is non-technical. After simple training, personnel can also participate in code maintenance. It can be seen that DTM provides a very flexible deployment plan that can be adapted to a variety of different scenarios and requirements. Using a series of DTM preset labels, you can complete tasks for days or even weeks in a few minutes. Such a powerful multi-scene coverage capability and user-friendly settings will make DTM an excellent tool that is favored.
How to access Huawei Dynamic Tag Management (DTM)?
To learn more about Huawei Dynamic Tag Management (DTM), please visit the official website of Huawei Developer Alliance.
For information about the integrated SDK, please refer to the integration guide:
Mobile Android
Sample code: https://github.com/HMS-Core/hms-dtm-demo-android-studio
Web page JavaScript
Sample code: https://github.com/HMS-Core/hms-dtm-demo-web
If you encounter problems during the integration process, you can contact us via the online bill of lading .
For more details, please refer to:
Huawei Developer Alliance official website:https://developer.huawei.com/consumer/cn/hms?ha_source=hms1
Get the development guide document:https://developer.huawei.com/consumer/cn/doc/development?ha_source=hms1 To
participate in the developer discussion, please go to the Reddit community:https://www.reddit.com/r/HuaweiDevelopers/ To
download the demo and sample code, please go to Github:https://github.com/HMS-Core to
solve integration problems, please go to Stack Overflow:https://stackoverflow.com/questions/tagged/huawei-mobile-services?tab=Newest
Original link:
https://developer.huawei.com/consumer/cn/forum/topic/0204391049754110077?fid=18&pid=0304391049754110413
Author: pepper