Method and device for transmitting burying point data, storage medium and electronic equipment

Abstract

The invention discloses a buried point data transmission method and device, a storage medium and electronic equipment. The method comprises the steps of obtaining a burying point type of to-be-transmitted data in a target application, and under the condition that the burying point type is a preset burying point type and a target data format is found based on the preset burying point type, converting the to-be-transmitted data into target data to be reported based on the target data format, the data formats of the reported data and the to-be-transmitted data are initial data formats, the fields of the target data format are less than the fields of the initial data format, and the data format of the target data is the target data format, performing buried point data analysis on the target data to obtain a first statistical result, the first statistical result comprises the reporting frequency of the data of which the data format is the target data format. According to the method and the device, the technical problem of relatively low transmission efficiency of buried point data in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of computers, and more specifically, to a method and device for transmitting buried point data, a storage medium, and an electronic device. Background Art

[0002] At present, in order to realize the analysis of user behavior habits, adding software tracking analysis is an inevitable way. However, the timing and magnitude of tracking data upload are urgent problems that need to be solved. Sometimes the volume can reach tens of millions or hundreds of millions per day, and the request volume can even exceed the mainstream business functions.

[0003] In the related technology, multiple tracking data are generally generated by determining the interaction type of the interactive operation and obtaining the element identifier of the view interface element. After the tracking data is arrayed, the batch data generated in a short period of time is uploaded through a data compression upload strategy. However, it is currently only effective for a single upload process. For a large number of users of different devices, it cannot serve as a strategy to reduce the amount of data, cannot be expanded according to the actual network situation, and cannot further compress the data.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method and device for transmitting buried point data, a storage medium and an electronic device, so as to at least solve the technical problem of low transmission efficiency of buried point data existing in the related art.

[0006] According to one aspect of an embodiment of the present application, a method for transmitting buried point data is provided, including: obtaining a buried point type of data to be transmitted in a target application; when the buried point type is a preset buried point type and a target data format is found based on the preset buried point type, converting the data to be transmitted into target data based on the target data format for reporting, wherein the target data format represents a data format automatically generated when the number of reports of reported data meets a preset condition, the buried point type of the reported data is the preset buried point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format; performing buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data in the target data format.

[0007] According to another aspect of an embodiment of the present application, a transmission device for buried point data is also provided, including: an acquisition module, used to acquire the buried point type of data to be transmitted in a target application; a processing module, used to, when the buried point type is a preset buried point type and a target data format is found based on the preset buried point type, convert the data to be transmitted into target data for reporting based on the target data format, wherein the target data format represents a data format automatically generated when the number of reports of the reported data meets a preset condition, the buried point type of the reported data is the preset buried point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format; an analysis module, used to perform buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data with a data format of the target data format.

[0008] In an exemplary embodiment, the device is also used to: when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, before converting the data to be transmitted into target data based on the target data format for reporting, obtain the network environment in which the target application is located; when the network environment is a preset network environment and the burying point type is the preset burying point type, determine the target data format based on the preset burying point type.

[0009] In an exemplary embodiment, the device is used to determine the target data format based on the preset burying point type when the network environment is a preset network environment and the burying point type is the preset burying point type in the following manner: determine whether the target terminal is in a weak network environment based on bandwidth information of the target terminal where the target application is located and a device status of the target terminal, wherein the preset network environment includes the weak network environment; and determine the target data format based on the preset burying point type when the network environment is the weak network environment and the burying point type is the preset burying point type.

[0010] In an exemplary embodiment, the device is also used for: performing buried data analysis on the target data and obtaining a first statistical result, retaining the target data format if the first statistical result indicates that the number of reports of data in the target data format is greater than a first threshold; determining a target version number corresponding to the target data format if the first statistical result indicates that the number of reports of data in the target data format is less than or equal to the first threshold, wherein the version number of the target data format is allowed to be updated along with the update of the target application; generating a target comparison result based on comparing the target version number with the current version number of the target application; and determining whether to retain the target data format based on the target comparison result.

[0011] In an exemplary embodiment, the device is used to determine whether to retain the target data format based on the target comparison result in the following manner: if the target comparison result determines that the target version number is different from the current version number, the target data format is deleted; if the target comparison result determines that the target version number is the same as the current version number, the target data format is retained.

[0012] In an exemplary embodiment, the device is used to convert the data to be transmitted into target data based on the target data format for reporting when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type in the following manner: when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, obtain the first key field in the initial data format; replace the second key field in the target data format with the first key field, and fill it with the data to be transmitted to obtain the target data, wherein the second key field is different from the first key field; and report the target data.

[0013] In an exemplary embodiment, the device is also used for: after obtaining the burying point type of the data to be transmitted in the target application, when the burying point type is the preset burying point type and the target data format is not found based on the preset burying point type, reporting the data to be transmitted according to the initial data format; performing burying point data analysis on the data to be transmitted to obtain a second statistical result, wherein the second statistical result includes the number of reports of data with the data format of the initial data format; when the second statistical result indicates that the number of reports of data with the data format of the initial data format is greater than a second threshold, generating the target data format and establishing a mapping relationship between the target data format and the preset burying point type.

[0014] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned method for transmitting buried point data when running.

[0015] According to another aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above method for transmitting buried point data.

[0016] According to another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-mentioned method for transmitting buried point data through the computer program.

[0017] In an embodiment of the present application, after obtaining the point-of-sale type of the data to be transmitted in the target application, the system will check whether the point-of-sale type is a preset point-of-sale type and whether the corresponding target data format already exists. If the conditions are met, the system will convert the data to be transmitted into target data with fewer fields according to the target data format for reporting. The target data format is automatically generated when the number of reports of the reported data meets the preset conditions, and it is allowed to be updated with the application update. This process not only reduces the amount of data reporting, but also reduces the data template format through the magnitude analysis mechanism of the server, further releasing the format retrieval pressure of the server, and by performing point-of-sale data analysis on the target data, the first statistical result is obtained, the data reporting process is further optimized, the efficiency and accuracy of data processing are improved, and the purpose of improving the efficiency of client bandwidth utilization in the case of weak network and poor performance is achieved, thereby achieving the technical effect of improving data upload efficiency and server service life, and then solving the technical problem of low transmission efficiency of point-of-sale data existing in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 It is a schematic diagram of an application environment of an optional method for transmitting buried point data according to an embodiment of the present application;

[0020] Figure 2 It is a flowchart of an optional method for transmitting buried point data according to an embodiment of the present application;

[0021] Figure 3 is a schematic diagram of an optional method for transmitting buried point data according to an embodiment of the present application;

[0022] Figure 4 It is a structural schematic diagram of an optional transmission device for buried point data according to an embodiment of the present application;

[0023] Figure 5 It is a structural schematic diagram of an optional transmission product of buried point data according to an embodiment of the present application;

[0024] Figure 6 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretation:

[0028] Data embedding is a data collection technology that involves embedding code or tags at specific locations in applications or web pages to capture and record user data. When users trigger corresponding behaviors, these embedded codes will report data to achieve a comprehensive analysis of user behavior.

[0029] By using tracking data, you can analyze the user's click path, page dwell time, etc., understand the user's usage habits, and optimize product functions. Tracking can record performance indicators such as the application's startup time and page loading time to help developers find performance bottlenecks. By tracking application crash information, you can quickly locate the problem and improve the stability of the application.

[0030] The present application is described below in conjunction with embodiments:

[0031] According to one aspect of an embodiment of the present application, a method for transmitting buried point data is provided. Optionally, in this embodiment, the above-mentioned method for transmitting buried point data can be applied to Figure 1 In the hardware environment composed of the server 101 and the terminal device 103 shown in FIG. Figure 1 As shown, the server 101 is connected to the terminal 103 via a network, and can be used to provide services for the terminal device or the application installed on the terminal device. The application can be a video application, an instant messaging application, a browser application, an educational application, a game application, etc. A database 105 may be set up on the server or independently of the server to provide data storage services for the server 101, for example, a game data storage server. The above-mentioned network may include, but is not limited to, a wired network and a wireless network, wherein the wired network includes, a local area network, a metropolitan area network and a wide area network; the wireless network includes, Bluetooth, WIFI and other networks that implement wireless communication; the terminal device 103 may be a terminal configured with an application, and may include, but is not limited to, at least one of the following: a mobile phone (such as an Android phone, an iOS phone, etc.), a laptop computer, a tablet computer, a PDA, a MID (Mobile Internet Devices), a PAD, a desktop computer, a smart TV, an intelligent voice interaction device, a smart home appliance, a vehicle-mounted terminal, an aircraft, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a mixed reality (MR) terminal and other computer devices; the above-mentioned server may be a single server, a server cluster consisting of multiple servers, or a cloud server.

[0032] Combination Figure 1 As shown, the above-mentioned method for transmitting buried data can be executed by an electronic device, and the electronic device can be a terminal device or a server. The above-mentioned method for transmitting buried data can be implemented by the terminal device or the server separately, or by the terminal device and the server together.

[0033] The above is only an example and is not specifically limited in this embodiment.

[0034] Optionally, as an optional implementation, as Figure 2 As shown, the above-mentioned method for transmitting buried point data includes:

[0035] S202, obtaining the tracking point type of the data to be transmitted in the target application;

[0036] S204, when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, the data to be transmitted is converted into the target data based on the target data format for reporting, wherein the target data format represents a data format automatically generated when the number of reports of the reported data meets the preset conditions, the burying point type of the reported data is the preset burying point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format;

[0037] S206, performing buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data in the target data format.

[0038] Optionally, in the embodiment of the present application, the above-mentioned "tracking type" may include but is not limited to the behavior identification of the user's interaction with the application, including but not limited to events such as page jumps and button clicks. Tracking type is used to identify the specific operations performed by the user in the application so that these behaviors can be accurately captured and recorded during the data collection process. By identifying and recording these behaviors, developers can analyze user behavior patterns, optimize user experience, and perform performance monitoring.

[0039] Optionally, in an embodiment of the present application, the above-mentioned "target data format" may include but is not limited to a predefined data structure, which is automatically generated after a specific number of reports is met, and guides how to convert the data to be transmitted into more streamlined target data. The target data format is an optimized data reporting template that reduces the volume of data reporting by reducing the number of fields while maintaining the core value of the data. This format can be dynamically adjusted according to application updates to adapt to new needs and changes, ensuring the efficiency and accuracy of data reporting.

[0040] Optionally, in an embodiment of the present application, the above-mentioned "initial data format" may include but is not limited to the original recording method of the user behavior data before any optimization is performed. The initial data format is the default recording format of the user behavior data when the application is not compressed or optimized. This format may contain a large amount of redundant information, resulting in a large amount of data reporting and affecting the reporting efficiency. By comparing with the target data format, it is possible to identify which fields are necessary and which can be omitted, thereby optimizing the data reporting process.

[0041] Optionally, in an embodiment of the present application, the above-mentioned "first statistical result" may include but is not limited to statistical information obtained after performing point-of-sale data analysis on the target data, including but not limited to the number of reports of data in the target data format. The first statistical result is feedback obtained after analyzing the reported data, which provides quantitative information about the reporting frequency of a specific data format. These statistical results are crucial for evaluating the effectiveness of data reporting strategies, monitoring the health of data reporting, and further optimizing the data reporting process. By analyzing these statistical results, abnormal patterns in data reporting can be discovered, and reporting strategies can be adjusted to reduce unnecessary data transmission and improve the efficiency and quality of data reporting.

[0042] It should be noted that the above process of obtaining the tracking point type of the data to be transmitted in the target application may involve a variety of different application scenarios and data types. For example, the tracking point type may include multiple dimensions such as user interface operations, system performance indicators, and user behavior paths. In the user interface operation dimension, the tracking point type may cover button clicks, page browsing, form submissions, etc.; in the system performance indicator dimension, it may include response time, loading speed, error rate, etc.; and in the user behavior path dimension, it may track the user's click stream, page access sequence, etc. This application does not limit this.

[0043] In addition, when the above-mentioned tracking point type is a preset tracking point type and the target data format is found based on the preset tracking point type, the automatic generation and update of the target data format can be based on a variety of conditions and strategies. For example, the preset condition for the number of reports can be a fixed threshold, the amount of data within a time period, or the number of occurrences of a specific event. The fields of the target data format can be streamlined according to the importance of the data and business needs, and may include key information such as user ID, event type, timestamp, etc., while excluding some non-critical redundant fields. In addition, the update of the target data format can be manually triggered or automatically optimized based on a machine learning algorithm. This application is not limited to this.

[0044] On the other hand, the first statistical result obtained by performing the buried data analysis on the target data can include the number of data reports in multiple dimensions. For example, the frequency of data reporting in different time periods can be analyzed from the time dimension, the difference in data reporting in different regions can be analyzed from the geographic location dimension, or the data reporting behavior of different user characteristics can be analyzed from the user group dimension. These statistical results can help understand user behavior patterns, optimize product functions and improve user experience. This application is not limited to this.

[0045] For example, taking the e-commerce platform application scenario as an example, the specific implementation process is as follows:

[0046] S1: Get the tracking type of the data to be transmitted in the target application. In this e-commerce platform, the tracking type may include user browsing product detail pages, adding to shopping carts, submitting orders, etc. For example, when a user clicks the "Add to Cart" button, the system captures this behavior and marks it as the tracking type "addToCart".

[0047] S2: Determine whether the tracking point type is a preset tracking point type and search for the target data format. Assuming that "addToCart" is a preset tracking point type, the system will check the local database to find the target data format corresponding to "addToCart". If it is found, for example, the format number is "001", then go to the next step.

[0048] S3: Convert the data to be transmitted into target data based on the target data format for reporting. The initial data format may contain fields such as user ID, product ID, timestamp, click type, etc., while the target data format "001" may only contain user ID and product ID to reduce the amount of data. For example, the initial data is {"userId":"U291761","productId":"P67890","timestamp":"20241230","clickType":"addToCart"}, and the converted target data is {"userId":"U291761","productId":"P67890"}.

[0049] S4: Report target data. The converted target data is processed by a compression algorithm, such as GZIP compression, and then reported to the server. Assume that the size of the compressed data is reduced by 50%, from 1KB to 0.5KB.

[0050] S5: Perform data analysis on the target data to obtain the first statistical result. After receiving the reported data, the server performs data analysis and counts the number of reports of the "addToCart" behavior. For example, the server finds that the number of reports of the "addToCart" behavior is 500 in the last hour.

[0051] S6: Dynamically update the target data format. If the e-commerce platform updates the design of the product details page, resulting in the need to add a "page version" field to the tracking data of the "addToCart" behavior, the system will automatically update the target data format "001" to include this new field. For example, the updated target data format is {"userId":"U291761","productId":"P67890","pageVersion":"V2.0"}.

[0052] Therefore, the above process can collect and analyze user behavior data in a more efficient way. First, by reducing the number of fields in the reported data, the load of network transmission is reduced and the efficiency of data reporting is improved. Secondly, through compression algorithm processing, the amount of data transmission is further reduced, saving bandwidth resources. Thirdly, by dynamically updating the target data format, the system can adapt to the update changes of the application and maintain the accuracy and integrity of the data. Finally, through statistical analysis of the target data, the platform can quickly obtain the frequency information of key behaviors and provide data support for product optimization and operational decisions. Overall, this process not only improves the efficiency of data processing, but also enhances the availability of data and the response speed of the business.

[0053] Through the embodiment of the present application, after obtaining the point-of-sale type of the data to be transmitted in the target application, the system will check whether the point-of-sale type is a preset point-of-sale type and whether the corresponding target data format already exists. If the conditions are met, the system will convert the data to be transmitted into target data with fewer fields according to the target data format for reporting. The target data format is automatically generated when the number of reports of the reported data meets the preset conditions, and it is allowed to be updated with the application update. This process not only reduces the amount of data reporting, but also reduces the data template format through the magnitude analysis mechanism of the server, further releasing the format retrieval pressure of the server, and obtaining the first statistical result by performing point-of-sale data analysis on the target data, further optimizing the data reporting process, improving the efficiency and accuracy of data processing, and achieving the purpose of improving the efficiency of client bandwidth utilization in the case of weak network and poor performance, thereby achieving the technical effect of improving data upload efficiency and server service life, and thus solving the technical problem of low transmission efficiency of point-of-sale data existing in related technologies.

[0054] As an optional scheme, when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, before converting the data to be transmitted into the target data based on the target data format for reporting, the above method also includes: obtaining the network environment in which the target application is located; when the network environment is a preset network environment and the burying point type is a preset burying point type, determining the target data format based on the preset burying point type.

[0055] Optionally, in an embodiment of the present application, the above-mentioned "network environment" may include but is not limited to the current network status and quality of the target application, including but not limited to the type of network (such as Wi-Fi, 4G, 5G, etc.), the signal strength of the network, the bandwidth of the network, the data transmission rate, the network delay and other parameters. For example, the network environment can be evaluated by monitoring the network connection status of the device to determine whether it is connected to Wi-Fi or a mobile data network, and detecting the signal strength to evaluate the network stability. In addition, the bandwidth and delay can also be evaluated through actual data transmission tests to determine whether the network can support efficient data transmission. This information is crucial for determining the data reporting strategy, because different network environments may require different data reporting frequencies and data volumes.

[0056] Optionally, in an embodiment of the present application, the above-mentioned "preset network environment" may include but is not limited to configurations under specific network conditions, including but not limited to network bandwidth thresholds, delay time thresholds, signal strength levels, etc. For example, the preset network environment may be defined as a situation where the bandwidth is less than 1Mbps or the delay exceeds 200 milliseconds. In this case, the system may choose a more streamlined data format to reduce the volume of data reporting to adapt to environments with poor network conditions. At the same time, the "preset burying point type" may include but is not limited to specific user behaviors or system events that are pre-defined according to business logic and data analysis requirements, including but not limited to user login, product purchase, page visit, etc. For example, for the preset burying point type of "product purchase", the target data format may only include key information such as transaction ID, user ID, and purchase time, while omitting other non-essential fields to optimize the data reporting process and reduce network load. Such a data format helps to maintain the efficiency and accuracy of data reporting when the network environment is poor.

[0057] It should be noted that the process of obtaining the network environment in which the target application is located can be evaluated according to multiple dimensions, and this application does not limit this. For example, the network environment can be evaluated from three dimensions: network type, signal quality, and bandwidth utilization. In the network type dimension, different types of network connections such as Wi-Fi, 3G, 4G, and 5G can be distinguished; in the signal quality dimension, indicators such as signal strength and stability can be evaluated; and in the bandwidth utilization dimension, the current network congestion and data transmission rate can be considered. Comprehensive evaluation of these dimensions helps to determine the best data processing and reporting strategy.

[0058] In addition, when the network environment is a preset network environment and the point type is a preset point type, the process of determining the target data format based on the preset point type can also be diversified according to different application scenarios and business needs, and the present application does not limit this. For example, the preset network environment can be a network condition based on geographical location, such as a high-bandwidth network in the city center and a low-bandwidth network in remote areas; it can also be based on time-based network usage peak and non-peak hours; or it can be based on user behavior patterns, such as adopting different data reporting strategies during periods of high user activity. At the same time, the preset point type can be the behavior of a specific user group, such as the transaction behavior of VIP users, or the monitoring of specific events, such as user interactions during large-scale promotional activities. These diverse situations can affect the determination of the target data format to adapt to different data processing needs and optimize user experience.

[0059] As an optional scheme, when the network environment is a preset network environment and the burying point type is a preset burying point type, the target data format is determined based on the preset burying point type, including: determining whether the target terminal is in a weak network environment based on the bandwidth information of the target terminal where the target application is located and the device status of the target terminal, wherein the preset network environment includes a weak network environment; when the network environment is a weak network environment and the burying point type is a preset burying point type, determining the target data format based on the preset burying point type.

[0060] Optionally, in an embodiment of the present application, the above-mentioned "target terminal" may include but is not limited to devices used by users, such as smart phones, tablet computers, personal computers, etc., which are connected to the Internet via wireless or wired networks. The "bandwidth information" of the target terminal may include but is not limited to parameters such as network upload and download speeds, network delays, packet loss rates, etc., which can reflect the real-time status and performance of the network. For example, the bandwidth information may show that the download speed is less than 100Kbps, the upload speed is less than 50Kbps, or the network delay exceeds 300 milliseconds, which can be used as a basis for judging a weak network environment. At the same time, the "device status" may include but is not limited to the power of the device, CPU usage, memory usage, etc., which may affect the efficiency of data reporting and the responsiveness of the device. For example, if the device power is less than 10%, or the CPU usage exceeds 80%, it may be necessary to reduce data reporting to protect device performance. The preset network environment includes a weak network environment, which means that the system will preset a threshold value based on these parameters. When the actual measured value is lower than this threshold value, the system will consider the target terminal to be in a weak network environment.

[0061] Optionally, in an embodiment of the present application, the above-mentioned "weak network environment" may include but is not limited to a network state with extremely low bandwidth, unstable connection or extremely high latency. In such a network environment, the system will adopt a special data reporting strategy to reduce the occupation of network resources by data transmission. For example, the system may prioritize uploading critical business data and temporarily shelve the reporting of non-critical data. At the same time, the "preset buried point type" may include but is not limited to specific user behaviors or system events pre-defined according to business logic and data analysis requirements, such as user login, product purchase, page access, etc. In a weak network environment, the system may choose a more streamlined data format to report these preset buried point types to adapt to environments with poor network conditions. For example, for the preset buried point type of "product purchase", the target data format may only include key information such as transaction ID, user ID and purchase time, while omitting other non-essential fields to optimize the data reporting process and reduce network load. Such a data format helps to maintain the efficiency and accuracy of data reporting when the network environment is poor.

[0062] It should be noted that when determining whether the target terminal is in a weak network environment based on the bandwidth information of the target terminal where the target application is located and the device status of the target terminal, there are many possible situations, and this application does not limit this. For example, bandwidth information can be considered from three dimensions: network speed, stability, and delay. The network speed dimension may include download speed and upload speed. If the download speed is less than 200Kbps or the upload speed is less than 50Kbps, it may be judged as a weak network environment. The stability dimension involves the network's packet loss rate and connection disconnection frequency. If the packet loss rate exceeds 10% or the connection is frequently disconnected, it may also indicate that the network environment is weak. The delay dimension focuses on the response time of data transmission. If the network delay exceeds 500 milliseconds, this can also be an indication of a weak network environment.

[0063] In addition, when determining whether the target terminal is in a weak network environment, the device status is also an important consideration, which can be evaluated from three dimensions: power, memory usage, and CPU load. The power dimension considers the remaining power of the device. If the power is less than 20%, data reporting may be restricted to extend battery life. The memory usage dimension checks the available memory of the device. If the memory usage exceeds 90%, data reporting may need to be reduced to prevent application crashes. The CPU load dimension monitors the usage of the processor. If the CPU load continues to exceed 80%, it may be necessary to reduce data processing tasks to protect device performance.

[0064] On the other hand, in the case where the network environment is a weak network environment and the tracking point type is a preset tracking point type, when determining the target data format based on the preset tracking point type, it can also be processed in a diversified manner according to the three dimensions of data importance, reporting frequency and business needs. The data importance dimension may involve the distinction between critical business data and non-critical business data, and critical data needs to be reported first even in a weak network environment. The reporting frequency dimension considers the interval and number of data reports, and may need to adjust the reporting frequency according to network conditions to adapt to the weak network environment. The business demand dimension adjusts the data format according to specific business logic. For example, in e-commerce applications, data on purchasing behavior may be more important than data on browsing behavior. Therefore, in a weak network environment, relevant data on purchasing behavior may be reported first. The comprehensive consideration of these dimensions helps to optimize the data reporting strategy in a weak network environment and ensure the transmission of critical data and the stability of system performance.

[0065] As an optional solution, after performing buried data analysis on the target data and obtaining a first statistical result, the above method also includes: retaining the target data format when the first statistical result indicates that the number of reports of data in the target data format is greater than a first threshold value; determining a target version number corresponding to the target data format when the first statistical result indicates that the number of reports of data in the target data format is less than or equal to the first threshold value, wherein the version number of the target data format is allowed to be updated as the target application is updated; generating a target comparison result based on comparing the target version number with the current version number of the target application; and determining whether to retain the target data format based on the target comparison result.

[0066] Optionally, in an embodiment of the present application, the above-mentioned "first statistical result" may include but is not limited to the result of counting and analyzing the number of reports of a specific data format, including but not limited to statistics on the frequency of data reports within a certain time period, a certain function or a certain user group. For example, the first statistical result may show that in the past week, the number of data reports using the data format "001" exceeded 1000 times, and this number is set as the first threshold, indicating that the data format is being frequently used, so the system decides to retain this data format to maintain the continuity and consistency of data reporting.

[0067] Optionally, in an embodiment of the present application, the above-mentioned "target version number" may include but is not limited to a version identifier associated with a specific data format, which is used to track changes in the data format as the application is updated, including but not limited to the release version number of the application, the internal build number, or the version number of the data format structure. For example, the target data format "001" may correspond to version 1.0 of the application. When the application is updated to version 2.0, the data format may change, so the target version number is updated to 2.0. The update of this version number allows the system to identify and maintain data formats that are compatible with the latest application version, ensuring the accuracy and effectiveness of data reporting.

[0068] Optionally, in an embodiment of the present application, the above-mentioned "target comparison result" may include but is not limited to the conclusion drawn after comparing the target version number and the current version number, which is used to determine whether the data format needs to be updated or retained, including but not limited to the case of version matching, version lagging or version leading. For example, if the target version number is 2.0 and the current application version number is 2.1, the target comparison result may indicate that the version is lagging, which means that the data format needs to be updated to match the latest application version.

[0069] Optionally, in the embodiment of the present application, the above decision of "retaining the target data format" may include but is not limited to further processing based on the target comparison result, including but not limited to deciding whether to continue to use the current data format or whether to switch to a new data format. For example, if the target comparison result shows that the currently used format is compatible with the latest version of the application, the target data format is retained; if it is not compatible, the target data format may need to be updated or replaced to ensure the validity and accuracy of the data reporting.

[0070] It should be noted that, in the case where the first statistical result indicates that the number of reports of data in the target data format is greater than the first threshold, the decision to retain the target data format can be made based on multiple dimensions, and this application does not limit this. For example, this decision may be based on three dimensions: reporting frequency, data importance, and user feedback. The reporting frequency dimension may involve the frequency of use of the data format. If a data format is frequently reported, it indicates that it is critical to the current business process. The importance dimension of data may be based on business logic. For example, some key transaction data is retained due to its sensitivity and importance even if it is not reported many times. The user feedback dimension may involve user feedback on application performance. If users report problems related to certain data formats, this may affect the decision of whether to retain the data format.

[0071] In addition, in the above-mentioned case where the first statistical result indicates that the number of reports of data in the target data format is less than or equal to the first threshold, the process of determining the target version number corresponding to the target data format can also be considered from multiple dimensions, and this application does not limit this. For example, this may involve three dimensions: version compatibility, historical data consistency, and expected business development. The version compatibility dimension ensures that the data format is consistent with the latest version of the application to avoid data parsing errors. The historical data consistency dimension takes into account the impact that data format changes may have on historical data analysis, and it is necessary to ensure the compatibility of new and old data. The expected business development dimension is based on predictions of future business needs, and it may be necessary to plan and update the data format in advance to adapt to new business scenarios.

[0072] Furthermore, the above process of generating the target comparison result based on the comparison between the target version number and the current version number of the target application can also be analyzed from multiple dimensions, which is not limited in this application. This may include three dimensions: the size of the version difference, changes in business requirements, and technological evolution. The dimension of the size of the version difference focuses on the specific differences between the version numbers, such as changes in the major or minor version numbers. The dimension of changes in business requirements involves whether the data format needs to be updated to meet new business needs as the business develops. The dimension of technological evolution focuses on the impact of technological development on the data format, such as new data compression algorithms or encryption technologies that may require updates to the data format.

[0073] Finally, the above-mentioned decision on whether to retain the target data format based on the target comparison result can also be made from multiple dimensions, which is not limited in this application. This may include three dimensions: efficiency, security, and scalability of the data format. The efficiency dimension of the data format focuses on the performance of data reporting and processing. If the current data format causes processing delays or waste of resources, it may need to be updated. The security dimension involves the protection of data. If there are security vulnerabilities in the current data format, it needs to be improved. The scalability dimension takes into account the adaptability of the data format during future business expansion. If the business is expected to grow rapidly, the current data format may need to be optimized in advance to adapt to the future data volume.

[0074] As an optional solution, determining whether to retain the target data format is based on the target comparison result, including: deleting the target data format when the target comparison result determines that the target version number is different from the current version number; retaining the target data format when the target comparison result determines that the target version number is the same as the current version number.

[0075] Optionally, in an embodiment of the present application, the above-mentioned "target version number" may include, but is not limited to, a version identifier associated with a specific data format, which is used to track changes in the data format as the application is updated. When the target version number is different from the current version number, it means that the application has been updated, and the original data format may no longer be compatible or applicable to the new version of the application. For example, if an e-commerce application is upgraded from version 1.0 to version 2.0, and the data reporting format is also changed to adapt to the new user interface and functions, then the old data format associated with version 1.0 will be deleted to ensure that all reported data meets the requirements of the new version. This helps to maintain the consistency and accuracy of the data, while reducing errors and confusion caused by version incompatibility.

[0076] Optionally, in an embodiment of the present application, the above-mentioned "current version number" may include, but is not limited to, an identifier indicating the version of the application that is currently installed or running. When the target version number is the same as the current version number, it indicates that the version of the application has not changed, so the corresponding data format is still valid and can continue to be used. For example, if a social media application is always maintained at version 3.5 and no updates are made, the data format corresponding to version 3.5 will continue to be retained and used because it is compatible with the current state of the application. Retaining the target data format helps maintain the stability of the data processing process, avoids unnecessary changes and reconfigurations, and also reduces the complexity and maintenance costs of the system. In addition, this also means that existing data analysis and processing processes can continue to be used without additional adjustments or optimizations.

[0077] It should be noted that, in the case where the target comparison result determines that the target version number is different from the current version number, the operation of deleting the target data format can be decided based on multiple dimensions, and this application does not limit this. For example, this decision may be based on three dimensions: the scope of impact of version differences, the compatibility of data formats, and business continuity. The dimension of the scope of impact of version differences involves the extent of the impact of version updates on existing data formats. If the update results in fundamental changes, such as the reconstruction of an API, the old data format may need to be deleted. The data format compatibility dimension considers the compatibility of data formats between the old and new versions. If the new version does not support the old data format at all, then in order to maintain system consistency, the old format must be deleted. The business continuity dimension focuses on the impact of version updates on business processes. If the old data format is critical to the business process, a transition period may be required to delete the old format after the new format is completely stable and widely adopted.

[0078] In addition, in the above-mentioned case where the target comparison result determines that the target version number is the same as the current version number, the decision to retain the target data format can also be considered from multiple dimensions, and this application does not limit this. For example, this decision may be based on three dimensions: stability of the data format, consistency of business requirements, and convenience of technical maintenance. The stability dimension of the data format focuses on whether the data format can continue to meet business needs without frequent changes. If the current data format is already stable and widely adopted by business processes, then it is reasonable to retain it. The consistency dimension of business requirements involves whether the data format can meet current and expected business needs. If the business needs have not changed, then it is appropriate to retain the existing data format. The convenience dimension of technical maintenance considers the difficulty of maintaining the existing data format. If the existing data format is easy to maintain and familiar to the technical team, then retaining it can reduce the technical burden and potential risks.

[0079] As an optional scheme, when the embedding point type is a preset embedding point type and the target data format is found based on the preset embedding point type, the data to be transmitted is converted into target data based on the target data format for reporting, including: when the embedding point type is a preset embedding point type and the target data format is found based on the preset embedding point type, obtaining the first key field in the initial data format; replacing the second key field in the target data format with the first key field, and filling it with the data to be transmitted to obtain the target data, wherein the second key field is different from the first key field; and reporting the target data.

[0080] Optionally, in an embodiment of the present application, the above-mentioned "initial data format" may include but is not limited to the original recording method of user behavior data before any optimization is performed. The initial data format may include a series of fields, among which the "first key field" may include but is not limited to the fields that are most important in the data reporting process, such as user ID, event ID or timestamp. These fields are crucial for data analysis because they provide the basic context of user behavior. For example, in e-commerce applications, the first key field may be the product ID, because it is directly related to the user's specific behavior, such as purchasing or browsing, and is very important for subsequent data analysis and user behavior tracking.

[0081] Optionally, in an embodiment of the present application, the "second key field" may include, but is not limited to, a field that is less important than the first key field in the target data format, or a field that requires special attention during the data reporting process. For example, in the data reporting of the user registration process, the second key field may be the registration source, which is crucial for analyzing the effectiveness of the user registration channel. In the process of replacing the first key field with the second key field, the structure of the data reporting is actually optimized, making the data more concise and focused. For example, if the first key field is the user ID and the second key field is the registration time, then when reporting the registration event, only the user ID and registration time can be reported instead of the complete user information. This can reduce the amount of data and improve reporting efficiency.

[0082] Optionally, in an embodiment of the present application, "reporting target data" may include, but is not limited to, a process of sending processed data to a server. This process involves the transmission and reception of data, wherein "target data" refers to data that has been processed according to specific rules, and these data have been optimized to adapt to specific business needs and network environments. For example, in a mobile application, reporting target data may involve sending user behavior data, such as click events, page visit duration, etc., to a back-end server. The reporting process may include data compression, encryption, and formatting to ensure the security and integrity of the data. The purpose of reporting target data is to conduct data analysis, user behavior tracking, and product optimization, which is crucial to improving user experience and business decision-making.

[0083] It should be noted that when the tracking point type is a preset tracking point type and the target data format is found based on the preset tracking point type, the process of obtaining the first key field in the initial data format can be performed according to multiple dimensions, and this application does not limit this. For example, this process may involve three dimensions: the importance of the field, the data type of the field, and the frequency of use of the field. In terms of importance, the first key field may be information that is critical to business decisions, such as a user's unique identifier or the identifier of a key event. In terms of data type dimension, the first key field may include different types of data such as strings, numbers, or timestamps, depending on the purpose and storage requirements of the data. In terms of frequency of use dimension, the first key fields may be those fields that are most frequently referenced in data reporting, and therefore need to be acquired and processed first.

[0084] In addition, the above-mentioned process of replacing the second key field in the target data format with the first key field and filling it with the data to be transmitted to obtain the target data can also be diversified from multiple dimensions, and this application does not limit this. For example, this process may involve three dimensions: the business logic of the field, the data sensitivity of the field, and the update frequency of the field. In the business logic dimension, the replacement of the second key field may be based on specific business rules or process optimization. In the data sensitivity dimension, the replacement operation may need to take into account the privacy protection and security of the data. In the update frequency dimension, the second key field may be updated more frequently than the first key field, so the replacement operation needs to adapt to this change to ensure the timeliness of the data.

[0085] On the other hand, the above-mentioned process of reporting target data can also be diversified according to different dimensions, which is not limited in this application. For example, this process may involve three dimensions: the timing of data reporting, the reporting method, and the amount of data reported. In terms of the timing of reporting, the target data may be reported immediately after certain conditions are met, such as after the user completes a transaction. In terms of the reporting method, the target data may be reported through different network protocols or data transmission technologies, such as HTTP, WebSocket, or MQTT. In terms of the amount of data reported, the reporting operation may be adjusted according to network conditions or server load to optimize data transmission efficiency and cost. The comprehensive consideration of these dimensions helps to achieve an efficient, secure and reliable data reporting mechanism.

[0086] As an optional solution, after obtaining the burying point type of the data to be transmitted in the target application, the above method also includes: when the burying point type is a preset burying point type and the target data format is not found based on the preset burying point type, reporting the data to be transmitted according to the initial data format; performing burying point data analysis on the data to be transmitted to obtain a second statistical result, wherein the second statistical result includes the number of reports of data with the data format being the initial data format; when the second statistical result indicates that the number of reports of data with the data format being the initial data format is greater than a second threshold, generating a target data format, and establishing a mapping relationship between the target data format and the preset burying point type.

[0087] Optionally, in an embodiment of the present application, the above-mentioned "initial data format" may include but is not limited to the original recording method of user behavior data before any optimization or specific processing is performed. The initial data format usually contains comprehensive data fields, which are not filtered or streamlined to ensure the integrity of the data. For example, in a fitness application, the initial data format may include detailed information such as the user's exercise type, exercise duration, calorie consumption, exercise date and time. When the system fails to find a target data format that matches a specific preset embedding type, in order to ensure the continuity and availability of the data, the system will choose to report the data to be transmitted in this initial data format to ensure that the data is not lost due to format problems.

[0088] Optionally, in an embodiment of the present application, the above-mentioned "second statistical result" may include but is not limited to statistical information obtained after analyzing the data reported in the initial data format. These statistical information include not only the number of reports, but may also include the reporting time distribution of the data, user group characteristics, behavior patterns, etc. For example, the second statistical result may show that within a week, the user behavior data reported using the initial data format reached 1,500 times, and these data covered the user's login, browsing, purchase and other behaviors. By analyzing these data, it can help understand the overall trend and specific patterns of user behavior, and provide a basis for further optimizing data reporting strategies and improving user experience.

[0089] Optionally, in an embodiment of the present application, the above-mentioned "second threshold" may include but is not limited to a preset numerical value, which is used to determine whether the initial data format needs to be optimized and simplified. When the number of reports exceeds this threshold, it indicates that the initial data format is used very frequently, and further optimization may be required to reduce the load of data reporting and improve efficiency. For example, if the second statistical result shows that the number of reports of the initial data format exceeds the set second threshold of 2000 times, the system will generate a new target data format based on these frequently reported data features. This new target data format will be more streamlined and only contain the most critical information, such as user ID and behavior type. At the same time, the system will establish a mapping relationship between this new target data format and the preset tracking point type, so that it can automatically identify and use this optimized data format in future data reports, thereby improving data processing efficiency and reducing resource consumption.

[0090] It should be noted that when the burying point type is a preset burying point type and the target data format is not found based on the preset burying point type, the operation of reporting the data to be transmitted in the initial data format can be adjusted according to multiple dimensions, and this application does not limit this. For example, this operation may involve three dimensions: data integrity, timeliness of reporting, and data security. In the dimension of data integrity, the initial data format may contain all the necessary information to ensure the comprehensiveness of data analysis. In the dimension of timeliness of reporting, even if the target data format is not found, reporting in the initial format can ensure that the data will not be delayed due to format issues. In the dimension of data security, the initial data format may contain sensitive information, so it is necessary to ensure that appropriate encryption and security measures are taken during the reporting process.

[0091] Moreover, the above-mentioned process of performing point-of-use data analysis on the data to be transmitted and obtaining the second statistical result can also be considered from multiple dimensions, which is not limited in this application. For example, the second statistical result may involve three dimensions: the frequency of data reporting, the pattern of user behavior, and the distribution of data reporting. In the dimension of data reporting frequency, the statistical results may show that the reporting frequency of certain behaviors is abnormally high, which may indicate the need to optimize the data format of these behaviors. In the dimension of user behavior patterns, the statistical results may reveal specific trends in user behavior, such as peaks of activity within a specific time period. In the dimension of data reporting distribution, the statistical results may show differences in data reporting in different regions or for different user groups, which helps to understand the geographical characteristics of data reporting.

[0092] In addition, when the second statistical result indicates that the number of reports of data in the initial data format is greater than the second threshold, the operation of generating the target data format and establishing a mapping relationship between the target data format and the preset tracking point type can also be processed in a diversified manner according to different dimensions, and the present application does not limit this. For example, this operation may involve three dimensions: optimization of data format, improvement of data reporting efficiency, and reasonable allocation of system resources. In the dimension of data format optimization, the generated target data format may be more streamlined to reduce the burden of network transmission. In the dimension of improving data reporting efficiency, the new target data format may help to speed up data processing and improve reporting efficiency. In the dimension of reasonable allocation of system resources, by optimizing the data format, the burden on the server can be reduced, so that system resources can be more reasonably allocated to different data processing tasks.

[0093] The following is a further explanation of this application with reference to specific examples:

[0094] Device: refers to a device (such as Android, Windows, and other applications). Environmental judgment content includes but is not limited to: bandwidth, device performance (CPU processing power), etc.

[0095] Platform: A service platform that includes an interface scheduling engine, tracking point statistics service, data format template service, and tracking point data storage service.

[0096] Template degradation engine: It is a way to optimize the format of reported data. With the upgrade of the client version, the data corresponding to the tracking type may increase or decrease fields, so the original tracking method template may be compatible. The template degradation engine is a data template degradation operation based on the version number and tracking level. That is, it retains the current latest version of the tracking data format and manages the tracking data format generated by the previous version number in an orderly manner. If the version is relatively old and the tracking level is below a certain threshold, the tracking data format is deleted without affecting the upload of the old version of the tracking data, which improves the compatibility of the system.

[0097] Data format template (integrated key filling), such as:

[0098] Original data format:

[0099] {"btnType":"loginButton","time":"2917616789","eveId":'buttonClick'};

[0100] Template structure: {"TemplateNo":001,data:["btnType","time","eveId"]};

[0101] The data after the template is filled in: {"No":"001",data:"["loginButton","2917616789","buttonClick"}.

[0102] Figure 3 is a schematic diagram of an optional method for transmitting buried point data according to an embodiment of the present application, such as Figure 3 The implementation steps include but are not limited to the following:

[0103] S1, the device triggers the collection of information, which includes data that needs to be collected, such as page jumps and clicks.

[0104] S2, environmental judgment includes but is not limited to: bandwidth, device performance, etc. In a weak network environment, the amount of data reported is reduced due to the reduction of fields.

[0105] S3, based on the tracking point type ("No": "001" and eveID are symmetrical, first determine eveID, then determine btnType, if they are the same, find one, first use eveid), check whether there is a data format corresponding to the tracking point type locally, if so, process the data to generate format data, otherwise report it according to the general format field.

[0106] S4, returns the data generated according to the embedding data format.

[0107] S5, returns the normal field mapping data format (such as: the value corresponding to the Key).

[0108] S6 and S7, data format preparation and reporting of client tracking data to the service (data is compressed).

[0109] S8, send the data to the statistical engine for data analysis. If the current data has been processed by the data embedding format, restore the data through steps S10 and S11. If it has not been processed, do not process it. Then the data embedding type analysis engine performs the magnitude statistics of the embedding category. If the magnitude exceeds the threshold, the embedding format is automatically generated, and the template data format is updated through step S12 to perform the storage operation. If the data magnitude is less than a certain magnitude and the version is not the latest version (based on the version number comparison), continue the embedding data format degradation engine processing, and update the template data format through step S12 to delete the embedding format.

[0110] S9, the buried point data is stored in the database.

[0111] S13 and S14 return the corresponding embedding template based on the embedding data type to the client.

[0112] S15: The device updates the local tracking point format to prepare for the next tracking point report.

[0113] Through the embodiments of the present application, by utilizing the arrangement of the burying point format, devices in different regions can use the burying point data format, and the amount of data reported by different devices is reduced, which increases the service life of the device and the server while improving the reporting efficiency. The service dynamically generates the burying point format template based on the burying point magnitude, which improves the efficiency of generating the burying point format template relative to the manual entry of the template version. The degradation mechanism added by the service to the burying point format, with the iteration of the application version, etc., the burying point format has dynamic changes, and it is inevitable that the burying point format template is not applicable. Therefore, the present application can automatically be compatible with the reporting of subsequent burying point format data, improve the service's use efficiency of the burying point format, reduce the amount of data transmission, and improve the client's bandwidth usage efficiency in weak networks and poor performance. Through the platform's statistical dynamic burying point type magnitude analysis, the data burying point format template is dynamically generated, which realizes the unified magnitude management of the platform according to different burying point formats, and improves the burying point management efficiency of the service. By automatically managing data templates on the platform, dynamically generating a combination of tracking point format templates and tracking point template degradation strategies, the service life and efficiency of the service are improved. At the same time, as the client's tracking point data is upgraded, new tracking point templates can be dynamically generated and old tracking point templates can be discarded, improving the compatibility of the service.

[0114] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0115] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0116] According to another aspect of the embodiment of the present application, a device for transmitting buried point data for implementing the above-mentioned method for transmitting buried point data is also provided. Figure 4 As shown, the device comprises:

[0117] An acquisition module 402 is used to acquire the type of tracking point of the data to be transmitted in the target application;

[0118] The processing module 404 is used to convert the data to be transmitted into the target data for reporting based on the target data format when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, wherein the target data format represents a data format automatically generated when the number of reports of the reported data meets the preset conditions, the burying point type of the reported data is the preset burying point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format;

[0119] The analysis module 406 is used to perform buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data in the target data format.

[0120] As an optional scheme, the device is also used to: when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, before converting the data to be transmitted into the target data based on the target data format for reporting, obtain the network environment in which the target application is located; when the network environment is a preset network environment and the burying point type is a preset burying point type, determine the target data format based on the preset burying point type.

[0121] As an optional solution, the device is used to determine the target data format based on the preset burying point type in the following manner when the network environment is a preset network environment and the burying point type is a preset burying point type: determine whether the target terminal is in a weak network environment based on the bandwidth information of the target terminal where the target application is located and the device status of the target terminal, wherein the preset network environment includes a weak network environment; when the network environment is a weak network environment and the burying point type is a preset burying point type, determine the target data format based on the preset burying point type.

[0122] As an optional scheme, the device is also used to: perform buried data analysis on the target data, and after obtaining a first statistical result, retain the target data format when the first statistical result indicates that the number of reports of data in the target data format is greater than a first threshold; determine the target version number corresponding to the target data format when the first statistical result indicates that the number of reports of data in the target data format is less than or equal to the first threshold, wherein the version number of the target data format is allowed to be updated as the target application is updated; compare the target version number with the current version number of the target application to generate a target comparison result; and determine whether to retain the target data format based on the target comparison result.

[0123] As an optional solution, the device is used to determine whether to retain the target data format based on the target comparison result in the following manner: when the target comparison result determines that the target version number is different from the current version number, the target data format is deleted; when the target comparison result determines that the target version number is the same as the current version number, the target data format is retained.

[0124] As an optional scheme, the device is used to convert the data to be transmitted into target data based on the target data format for reporting in the following manner when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type: when the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, obtain the first key field in the initial data format; replace the second key field in the target data format with the first key field, and fill it with the data to be transmitted to obtain the target data, wherein the second key field is different from the first key field; and report the target data.

[0125] As an optional scheme, the device is also used to: after obtaining the burying point type of the data to be transmitted in the target application, when the burying point type is a preset burying point type and the target data format is not found based on the preset burying point type, report the data to be transmitted according to the initial data format; perform burying point data analysis on the data to be transmitted to obtain a second statistical result, wherein the second statistical result includes the number of reports of data with the data format being the initial data format; when the second statistical result indicates that the number of reports of data with the data format being the initial data format is greater than a second threshold, generate the target data format, and establish a mapping relationship between the target data format and the preset burying point type.

[0126] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0127] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0128] According to one aspect of the present application, a computer program product is provided. The computer program product includes a computer program.

[0129] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0130] Figure 5 The structure block diagram of a computer system for implementing an electronic device according to an embodiment of the present application is schematically shown.

[0131] It should be noted that Figure 5 The computer system 500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0132] like Figure 5 As shown, the computer system 500 includes a central processing unit 501 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 502 (ROM) or the program loaded from the storage part 508 to the random access memory 503 (RAM). Various programs and data required for system operation are also stored in the random access memory 503. The central processing unit 501, the read-only memory 502 and the random access memory 503 are connected to each other through a bus 504. The input / output interface 505 (Input / Output interface, i.e., I / O interface) is also connected to the bus 504.

[0133] The following components are connected to the input / output interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a local area network card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the input / output interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

[0134] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processor 501, various functions defined in the system of the present application are executed.

[0135] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the central processor 501, various functions provided by the embodiment of the present application are performed.

[0136] According to another aspect of the embodiment of the present application, an electronic device for implementing the above-mentioned method for transmitting buried data is also provided. The electronic device may be Figure 1 The terminal device or server shown in the figure. This embodiment is described by taking the electronic device as a terminal device as an example. Figure 6 As shown, the electronic device includes a memory 602 and a processor 604. The memory 602 stores a computer program, and the processor 604 is configured to execute the steps in any of the above method embodiments through the computer program.

[0137] Optionally, in this embodiment, the electronic device may be located in at least one network device among a plurality of network devices of a computer network.

[0138] Optionally, in this embodiment, the above-mentioned processor can be configured to execute the methods in each embodiment of the present application through a computer program.

[0139] Alternatively, a person skilled in the art may understand that: Figure 6 The structure shown is for illustration only. Figure 6 The structure of the electronic device is not limited. Figure 6 More or fewer components (such as network interfaces, etc.) as shown in, or with Figure 6 Different configurations are shown.

[0140] Among them, the memory 602 can be used to store software programs and modules, such as the program instructions / modules corresponding to the method and device for transmitting buried data in the embodiments of the present application. The processor 604 executes various functional applications and data processing by running the software programs and modules stored in the memory 602, that is, realizing the above-mentioned method for transmitting buried data. The memory 602 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 602 may further include a memory remotely located relative to the processor 604, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Among them, the memory 602 can be specifically, but not limited to, used for information such as buried data. As an example, such as Figure 6 As shown, the memory 602 may include but is not limited to the acquisition module 402, the processing module 404 and the analysis module 406 in the transmission device of the buried data. In addition, it may also include but is not limited to other module units in the transmission device of the buried data, which will not be repeated in this example.

[0141] Optionally, the transmission device 606 is used to receive or send data via a network. Specific examples of the network may include a wired network and a wireless network. In one example, the transmission device 606 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 606 is a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0142] In addition, the above-mentioned electronic device also includes: a display 608 for displaying the above-mentioned buried point data; and a connection bus 610 for connecting various module components in the above-mentioned electronic device.

[0143] In other embodiments, the terminal device or server may be a node in a distributed system, wherein the distributed system may be a blockchain system, and the blockchain system may be a distributed system formed by connecting the multiple nodes through network communication. The nodes may form a peer-to-peer network, and any form of computing device, such as a server, terminal or other electronic device, may become a node in the blockchain system by joining the peer-to-peer network.

[0144] According to one aspect of the present application, a computer-readable storage medium is provided, and a processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the method for transmitting buried point data provided in various optional implementations of the above-mentioned transmission of buried point data.

[0145] Optionally, in this embodiment, the above-mentioned computer-readable storage medium can be configured to store data for executing the methods in various embodiments of the present application.

[0146] Optionally, in this embodiment, a person of ordinary skill in the art may understand that all or part of the steps in the various methods of the above embodiments may be completed by instructing hardware related to the terminal device through a program, and the program may be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0147] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0148] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for one or more electronic devices to execute all or part of the steps of the methods described in each embodiment of the present application.

[0149] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0150] In the several embodiments provided in the present application, it should be understood that the disclosed application can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0151] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0152] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0153] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for transmitting buried point data, characterized in that: include: Get the tracking point type of the data to be transmitted in the target application; In the case where the burying point type is a preset burying point type and the target data format is found based on the preset burying point type, the data to be transmitted is converted into target data based on the target data format for reporting, wherein the target data format represents a data format automatically generated when the number of reports of the reported data meets a preset condition, the burying point type of the reported data is the preset burying point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format; Performing buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data in the target data format.

2. The method according to claim 1, characterized in that In the case where the burying point type is a preset burying point type and a target data format is found based on the preset burying point type, before converting the data to be transmitted into target data based on the target data format for reporting, the method further includes: Acquire the network environment where the target application is located; When the network environment is a preset network environment and the burying point type is the preset burying point type, the target data format is determined based on the preset burying point type.

3. The method according to claim 2, characterized in that When the network environment is a preset network environment and the burying point type is the preset burying point type, determining the target data format based on the preset burying point type includes: Determining whether the target terminal is in a weak network environment based on bandwidth information of the target terminal where the target application is located and a device state of the target terminal, wherein the preset network environment includes the weak network environment; When the network environment is the weak network environment and the burying point type is the preset burying point type, the target data format is determined based on the preset burying point type.

4. The method according to claim 1, characterized in that After performing buried point data analysis on the target data to obtain a first statistical result, the method further includes: When the first statistical result indicates that the number of reports of data in the target data format is greater than a first threshold, retaining the target data format; When the first statistical result indicates that the number of reports of data in the target data format is less than or equal to the first threshold, determining a target version number corresponding to the target data format, wherein the version number of the target data format is allowed to be updated along with the update of the target application; Comparing the target version number with the current version number of the target application to generate a target comparison result; Determine whether to retain the target data format based on the target comparison result.

5. The method according to claim 4, characterized in that The determining whether to retain the target data format based on the target comparison result includes: If the target comparison result determines that the target version number is different from the current version number, deleting the target data format; When the target comparison result determines that the target version number is the same as the current version number, the target data format is retained.

6. The method according to claim 1, characterized in that The method of converting the data to be transmitted into target data based on the target data format for reporting when the burying point type is a preset burying point type and a target data format is found based on the preset burying point type includes: When the embedding point type is a preset embedding point type and a target data format is found based on the preset embedding point type, obtaining a first key field in the initial data format; Replacing a second key field in the target data format with the first key field and filling it with the data to be transmitted to obtain the target data, wherein the second key field is different from the first key field; Report the target data.

7. The method according to claim 1, characterized in that After obtaining the tracking point type of the data to be transmitted in the target application, the method further includes: When the burying point type is the preset burying point type and the target data format is not found based on the preset burying point type, reporting the data to be transmitted according to the initial data format; Performing a buried point data analysis on the data to be transmitted to obtain a second statistical result, wherein the second statistical result includes the number of reports of data in the data format of the initial data format; When the second statistical result indicates that the number of reports of data in the initial data format is greater than a second threshold, the target data format is generated, and a mapping relationship between the target data format and the preset burial point type is established.

8. A device for transmitting buried point data, characterized in that: include: The acquisition module is used to obtain the tracking point type of the data to be transmitted in the target application; A processing module, used for, when the burying point type is a preset burying point type and a target data format is found based on the preset burying point type, converting the data to be transmitted into target data based on the target data format for reporting, wherein the target data format represents a data format automatically generated when the number of reports of the reported data meets a preset condition, the burying point type of the reported data is the preset burying point type, the data formats of the reported data and the data to be transmitted are both initial data formats, the fields of the target data format are less than the fields of the initial data format, the fields of the target data format are allowed to be updated as the target application is updated, and the data format of the target data is the target data format; The analysis module is used to perform buried point data analysis on the target data to obtain a first statistical result, wherein the first statistical result includes the number of reports of data in the target data format.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein the computer program can be executed by an electronic device to perform the method described in any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 7 are implemented.

11. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images