Business-scene-based burying point method and device, electronic equipment and storage medium

Abstract

The application discloses a business-scene-based burying point method and device, electronic equipment and storage medium. The method comprises the following steps: firstly, acquiring a burying point configuration file corresponding to a business scene, and extracting initial burying point configuration information from the burying point configuration file; secondly, acquiring recombination keywords, recombining the initial burying point configuration information according to the recombination keywords, and obtaining recombination burying point configuration information; thirdly, performing normalization processing on the recombination burying point configuration information, and obtaining normalized burying point configuration information; fourthly, generating a burying point plug-in according to the normalized burying point configuration information; and finally, setting the burying point plug-in on an application interface corresponding to the business scene, and the burying point plug-in is used for collecting and transmitting event information generated on the application interface. The application recombines and normalizes burying point configuration information of different types, formats the burying point information uniformly, and developers only need to pay attention to keywords of the burying point and places where the burying point is added, so that the burying point process is simplified, burying point time is shortened, and burying point efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and more specifically, to a method, apparatus, electronic device, and storage medium for data tracking based on business scenarios. Background Technology

[0002] Event tracking, also known as data collection tracking, involves capturing, processing, and transmitting data related to specific user behaviors or events. It records user behavior processes and outcomes to enable fast, efficient, and comprehensive data applications. Data tracking is a commonly used data collection method. Event tracking is the source of data; the collected data can be used to analyze website / app usage, user behavior habits, etc., forming the foundation for building user profiles, user behavior paths, and other data products.

[0003] Currently, during the process of tracking data encoding, developers need to manually input the tracking data provided by business personnel, which is inefficient, prone to errors, and requires a lot of time to adapt to the data format of the tracking SDK (Software Development Kit), thus reducing development efficiency. Summary of the Invention

[0004] To overcome the above problems and defects, the present invention provides a method, apparatus, electronic device and storage medium for tracking data based on business scenarios, which can improve the efficiency of tracking data development.

[0005] To achieve the above objectives, the first aspect of the present invention provides a data tracking method based on business scenarios, comprising:

[0006] Obtain the event tracking configuration file corresponding to the business scenario, and extract different types of initial event tracking configuration information from the event tracking configuration file;

[0007] Obtain the reorganization keywords, and reorganize the initial tracking point configuration information based on the reorganization keywords to obtain the reorganized tracking point configuration information;

[0008] The recombined tracking point configuration information is normalized to obtain normalized tracking point configuration information;

[0009] Generate a tracking plugin based on the normalized tracking configuration information;

[0010] The event tracking plugin is set on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface.

[0011] A second aspect of the present invention provides a data tracking device based on a business scenario, comprising:

[0012] The acquisition unit is used to acquire the event tracking configuration file corresponding to the business scenario and extract the initial event tracking configuration information from the event tracking configuration file.

[0013] The reorganization unit is used to obtain reorganization keywords and reorganize the initial tracking point configuration information based on the reorganization keywords to obtain reorganized tracking point configuration information.

[0014] The normalization unit is used to normalize the recombined embedding configuration information to obtain normalized embedding configuration information.

[0015] The generation unit is used to generate a tracking plugin based on the normalized tracking configuration information.

[0016] The setting unit is used to set the event tracking plugin on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface.

[0017] A third aspect of the present invention provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, the above-described data collection method based on business scenarios is implemented.

[0018] The fourth invention provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the above-described business scenario-based data collection method.

[0019] Compared with existing technologies, the beneficial effects of this invention include: First, this invention obtains the event tracking configuration file corresponding to the business scenario and extracts initial event tracking configuration information from the configuration file; then, it obtains recombining keywords and recombines the initial event tracking configuration information according to the recombining keywords to obtain recombined event tracking configuration information; then, it normalizes the recombined event tracking configuration information to obtain normalized event tracking configuration information; subsequently, it generates an event tracking plugin based on the normalized event tracking configuration information; finally, it sets the event tracking plugin on the application interface corresponding to the business scenario, and the event tracking plugin is used to collect and transmit event information generated on the application interface. This invention, by recombining and normalizing different types of event tracking configuration information, makes the event tracking information uniformly formatted. Developers only need to focus on the event tracking keywords and where the event tracking is added, without needing to pay additional attention to the type of event tracking, thus simplifying the event tracking process, shortening event tracking time, reducing the risk of event tracking errors, and improving event tracking efficiency. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention. It is obvious that the drawings described below are merely some embodiments of the invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0021] Figure 1This is a schematic diagram of an exemplary system architecture for the technical solution of an embodiment of the present invention;

[0022] Figure 2 The flowchart of the data collection method based on business scenarios in this embodiment of the invention. Figure 1 ;

[0023] Figure 3 This is a schematic diagram of the architecture of the tracking plugin in an embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of the data acquisition module in an embodiment of the present invention;

[0025] Figure 5 The flowchart of the data collection method based on business scenarios in this embodiment of the invention. Figure 2 ;

[0026] Figure 6 The flowchart of the data collection method based on business scenarios in this embodiment of the invention. Figure 3 ;

[0027] Figure 7 This is a schematic diagram of the architecture of the data tracking device based on a business scenario according to an embodiment of the present invention;

[0028] Figure 8 This is a schematic diagram of the computer system architecture of the electronic device according to an embodiment of the present invention. Detailed Implementation

[0029] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that the invention will be more thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art.

[0030] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a full understanding of embodiments of the invention. However, those skilled in the art will recognize that the technical solutions of the invention can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of the invention.

[0031] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0032] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0033] Figure 1 A schematic diagram of an exemplary system architecture to which the technical solutions of embodiments of the present invention can be applied is shown.

[0034] like Figure 1 As shown, the system architecture may include terminal devices (such as...) Figure 1 The device shown includes one or more of a smartphone 101, tablet 102, and portable computer 103 (which could also be a desktop computer, etc.), a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the terminal device and the server 105. The network 104 can include various connection types, such as wired communication links, wireless communication links, etc.

[0035] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, there can be any number of terminal devices, networks, and servers. For example, server 105 could be a server cluster composed of multiple servers.

[0036] It should be noted that the business scenario-based event tracking method provided in this embodiment of the invention is generally executed by server 105, and correspondingly, the business scenario-based event tracking device is generally located in server 105. However, in other embodiments of the invention, the terminal device may also have similar functions to the server, thereby executing the business scenario-based event tracking technical solution provided in this embodiment of the invention.

[0037] The implementation details of the technical solutions in the embodiments of the present invention will be described in detail below.

[0038] This invention provides a unified method for event tracking based on business scenarios, such as... Figure 2 As shown, this includes steps 201, 202, 203, 204, and 205. Specifically:

[0039] Step 201: Obtain the event tracking configuration file corresponding to the business scenario, and extract different types of initial event tracking configuration information from the configuration file. Business scenarios can include user account login on a webpage or app, news browsing, money transfer / payment, chat conversations, system settings, and other similar operations. The event tracking configuration file can be prepared by business personnel, who can organize the necessary event tracking data (such as user information, click / browse information, and behavior occurrence time) into an XLSX format table file.

[0040] Specifically, scripts can be used to parse the event tracking configuration file to obtain initial event tracking configuration information, avoiding the risk of human error. Event tracking configuration information can include event ID, event name (English name, Chinese explanation), event attributes (English name, Chinese explanation, attribute type), event tracking method (frontend / backend), event triggering timing, etc.

[0041] Step 202: Obtain the reorganization keywords. Reorganize the initial event tracking configuration information based on these keywords to obtain reorganized event tracking configuration information. The reorganization keywords can include the interface name. The initial event tracking configuration information can be categorized and reorganized. For example, event IDs, event names, and event attributes can be reorganized according to different interfaces. Specifically, the reorganization of event tracking configuration information can be accomplished using scripts, avoiding the risk of human error.

[0042] Step 203 involves normalizing the recombined tracking point configuration information to obtain normalized tracking point configuration information. Normalization ensures that recombined tracking point configuration information with different dimensions has a unified format. Normalized tracking point configuration information facilitates automated processing.

[0043] Step 204: Generate the event tracking plugin 400 based on the normalized event tracking configuration information. In this embodiment, the event tracking plugin 400 can adopt either a visual event tracking method or a full event tracking method. The visual event tracking method allows configuration of collection nodes through a visual tool, specifying the elements and attributes to be monitored, enabling precise tracking of event points. Full event tracking, also known as no-code tracking, automatically collects all events from the front end and reports the event tracking data. Useful data is filtered out during backend data calculation. Full event tracking can collect all user on-device behaviors, providing very comprehensive data.

[0044] Step 205: Set the event tracking plugin on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface.

[0045] In this embodiment, as Figure 3As shown, the event tracking plugin 400 includes a data acquisition module 410 and a transmission module 420. The data acquisition module 410 is used to collect event information from the application interface, and the transmission module 420 is used to transmit the event information to the database 500. Because the event tracking configuration information was normalized in step 204, the original code sending methods provided by the SDK can be merged into one, that is, the transmission module 420 can send various event information to the database 500 using only one method from the SDK.

[0046] The event information includes button click information and interface exposure information. Button click information refers to which function buttons the user clicked on the application interface, such as the send button, confirm button, pay button, exit button, and close button. Interface exposure information refers to which areas of the webpage or app were displayed and seen by the user.

[0047] like Figure 4 As shown, the acquisition module 410 includes a click information acquisition module 411 and an exposure information acquisition module 412. The click information acquisition module 411 is used to acquire button click information, and the exposure information acquisition module 412 is used to acquire interface exposure information.

[0048] Specifically, the click information collection module 411 can delegate event tracking information to the root element through a bubbling mechanism. The bubbling mechanism means that when an event is triggered on an element, such as a button triggering its onclick event, the same event will be triggered in all ancestor elements of that element. This process is called event bubbling. And this event will bubble up from the original element to the top of the DOM tree. In this way, the tracking and listening of event tracking can be completed through the final root element. The DOM stands for Document Object Model.

[0049] The exposure information acquisition module 412 can use MutationObserver at the root node to observe changes in DOM nodes, thereby tracking and listening to light exposure information. MutationObserver is a class in the native API used to listen for changes in node nodes.

[0050] In this embodiment, the event information also includes interface browsing information, which refers to information such as the number of page views, page viewing time, and page type viewed by the user on a webpage or APP interface. The collection module 410 also includes a browsing information collection module 413, which is used to collect interface browsing information.

[0051] In this embodiment, the event tracking plugin also includes a storage module 430. The acquisition module 410 stores the acquired event information in the storage module 430, and the transmission module 420 transmits the event information in the storage module 430 to the database 500.

[0052] In this embodiment, as Figure 5 As shown, after step 205, the following steps are also included:

[0053] Step 206: Based on the set transmission period, trigger the transmission module to send event information to the database. By setting the transmission period, the transmission module periodically sends time information to the database.

[0054] Or / and, in step 207, according to the set information volume threshold, the transmission module 420 is triggered to send event information to the database. Specifically, when the amount of event information stored on the storage module 430 reaches the information volume threshold (e.g., 1000 data entries), the transmission module 420 transmits all of these event information entries to the database 500, and at the same time, the storage module 430 clears its memory to facilitate the subsequent storage of new event information.

[0055] By following the steps above, we can ensure data timeliness and facilitate smooth data processing.

[0056] In this embodiment, as Figure 6 As shown, after step 205, the following steps are also included:

[0057] Step 208: Using the event tracking plugin, acquire test event information generated on the application interface based on test operation information. For example, the test operation information can be set to include the following: stay on page A for 5 seconds, click the confirmation button on page B, and enter search keywords on page C. Testers perform the corresponding operations according to the above test operation information, and at the same time, the event tracking plugin starts tracking the above events and generating test event information.

[0058] Step 209: Verify whether the test event information matches the test operation information. Specifically, the corresponding test event information can be exported from the event tracking plugin, and then the test event information is compared with the test operation information mentioned above. If the error is large and they do not match (for example, the dwell time on page A in the test event information is 2 seconds, or the clicked button on page B is a cancel button), then the event tracking configuration file needs to be checked, and steps 201 to 205 should be repeated.

[0059] The data tracking method based on business scenarios in this invention can produce the following technical effects in practical applications:

[0060] 1) Improve channel conversion rates by identifying user drop-off points through user action sequences;

[0061] 2) Improve the product by analyzing user behavior to identify problems, such as whether excessive buttons cause user behavior to be ineffective, thereby discovering functional design flaws.

[0062] 3) Precise user operation: Group users (e.g., some prefer to buy at a discount, some prefer to buy directly) to achieve precise marketing, such as issuing coupons;

[0063] 4) Improve user profiles, including basic attributes (gender, age, region, etc.) and behavioral attributes (device operating habits, etc.);

[0064] 5) Data analysis: Tracking data is stored in a data warehouse as raw material. This provides insights into channel conversion, personalized recommendations, and more.

[0065] This embodiment is a data tracking method based on business scenarios. Through the above steps, different types of data tracking configuration information are reorganized and normalized to make the data tracking information uniformly formatted. Developers only need to focus on the keywords of the data tracking and where the data tracking is added, without having to pay extra attention to the type of data tracking. Therefore, the data tracking process is simplified, the data tracking time is shortened, the risk of data tracking errors is reduced, and the data tracking efficiency is improved.

[0066] This invention also provides a business scenario-based event tracking device for use with the business scenario-based event tracking method provided in the above embodiments, such as... Figure 7 As shown, it includes an acquisition unit 301, a recombination unit 302, a normalization unit 303, a generation unit 304, and a setting unit 305. Wherein:

[0067] The acquisition unit 301 is used to acquire the tracking configuration file corresponding to the business scenario and extract different types of initial tracking configuration information from the tracking configuration file.

[0068] The recombination unit 302 is used to obtain recombination keywords and reorganize the initial tracking point configuration information based on the recombination keywords to obtain reorganized tracking point configuration information.

[0069] The normalization unit 303 is used to normalize the recombined embedding configuration information to obtain normalized embedding configuration information;

[0070] The generation unit 304 is used to generate a tracking point plugin based on the normalized tracking point configuration information;

[0071] The setting unit 305 is used to set the event tracking plugin on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface.

[0072] The event tracking device based on business scenarios in this embodiment reorganizes and normalizes different types of event tracking configuration information, making the event tracking information uniformly formatted. Developers only need to focus on the keywords of the event tracking and where the event tracking is added, without having to pay extra attention to the type of event tracking. This simplifies the event tracking process, shortens the event tracking time, reduces the risk of event tracking errors, and improves event tracking efficiency.

[0073] This invention also provides an electronic device, including a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, it implements the business scenario-based data collection method provided in the above embodiments.

[0074] Figure 8 A schematic diagram of a computer system suitable for implementing embodiments of the present invention is shown.

[0075] It should be noted that, Figure 8 The computer system of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0076] like Figure 8 As shown, the computer system includes a Central Processing Unit (CPU) 1801, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 1802 or programs loaded from storage portion 1808 into Random Access Memory (RAM) 1803, such as performing the methods described in the above embodiments. The RAM 1803 also stores various programs and data required for system operation. The CPU 1801, ROM 1802, and RAM 1803 are interconnected via a bus 1804. An Input / Output (I / O) interface 1805 is also connected to the bus 1804.

[0077] The following components are connected to I / O interface 1805: an input section 1806 including a keyboard, mouse, etc.; an output section 1807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1808 including a hard disk, etc.; and a communication section 1809 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1809 performs communication processing via a network such as the Internet. A drive 1810 is also connected to I / O interface 1805 as needed. Removable media 1811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1810 as needed so that computer programs read from them can be installed into storage section 1808 as needed.

[0078] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing computer programs for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1809, and / or installed from removable medium 1811. When the computer program is executed by central processing unit (CPU) 1801, it performs various functions defined in the system of the present invention.

[0079] It should be noted that the computer-readable medium shown in the embodiments of the present invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, wherein a computer-readable computer program is carried. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0080] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0081] The units described in the embodiments of the present invention can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0082] Specifically, using the electronic device in this embodiment, the following steps are taken: First, the tracking configuration file corresponding to the business scenario is obtained, and initial tracking configuration information is extracted from the tracking configuration file. Then, recombining keywords are obtained, and the initial tracking configuration information is recombined according to the recombining keywords to obtain recombined tracking configuration information. Next, the recombined tracking configuration information is normalized to obtain normalized tracking configuration information. Then, a tracking plugin is generated based on the normalized tracking configuration information. Finally, the tracking plugin is set on the application interface corresponding to the business scenario. The tracking plugin is used to collect and transmit event information generated on the application interface. This invention recombines and normalizes different types of tracking configuration information, making the tracking information uniformly formatted. Developers only need to focus on the keywords and where the tracking is added, without needing to pay extra attention to the type of tracking, thus simplifying the tracking process, shortening tracking time, reducing the risk of tracking errors, and improving tracking efficiency.

[0083] In another aspect, the present invention also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The storage medium carries one or more programs that, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0084] It should be noted that although several modules or units of the device for performing actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0085] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, portable hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, touch terminal, or network device, etc.) to execute the method according to the embodiments of the present invention.

[0086] Specifically, using the storage medium in this embodiment, the tracking configuration file corresponding to the business scenario can be obtained first, and initial tracking configuration information can be extracted from the tracking configuration file. Then, recombination keywords are obtained, and the initial tracking configuration information is recombined based on the recombination keywords to obtain recombined tracking configuration information. Next, the recombined tracking configuration information is normalized to obtain normalized tracking configuration information. Then, a tracking plugin is generated based on the normalized tracking configuration information. Finally, the tracking plugin is set on the application interface corresponding to the business scenario. The tracking plugin is used to collect and transmit event information generated on the application interface. This invention recombines and normalizes different types of tracking configuration information, making the tracking information uniformly formatted. Developers only need to focus on the keywords and where the tracking is added, without needing to pay extra attention to the type of tracking, thus simplifying the tracking process, shortening tracking time, reducing the risk of tracking errors, and improving tracking efficiency.

[0087] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein.

[0088] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A data tracking method based on business scenarios, characterized in that, include: Obtain the event tracking configuration file corresponding to the business scenario, and parse the event tracking configuration file through a script to extract different types of initial event tracking configuration information from the event tracking configuration file; Obtain recombination keywords, and use a script to recombine the initial tracking point configuration information based on the recombination keywords to obtain recombined tracking point configuration information. The recombination keywords include the interface name, and the recombined tracking point configuration information is obtained by recombining the initial tracking point configuration information based on the interface name. The recombined embedding configuration information is normalized to obtain normalized embedding configuration information; An event tracking plugin is generated based on the normalized event tracking configuration information, wherein the event tracking plugin includes visual event tracking or full event tracking; The event tracking plugin is set on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface. The event tracking plugin is used to obtain test event information generated on the application interface based on test operation information. Verify whether the test event information matches the test operation information.

2. The data tracking method based on business scenarios according to claim 1, characterized in that, The event tracking plugin includes a data acquisition module and a data transmission module; the data acquisition module is used to acquire the event information on the application interface, and the data transmission module is used to transmit the event information to the database.

3. The data collection method based on business scenarios according to claim 2, characterized in that, The event information includes button click information and interface exposure information. The acquisition module includes a click information acquisition module and an exposure information acquisition module. The click information acquisition module is used to acquire the button click information, and the exposure information acquisition module is used to acquire the interface exposure information.

4. The data collection method based on business scenarios according to claim 3, characterized in that, The event information also includes interface browsing information, and the acquisition module further includes a browsing information acquisition module, which is used to acquire the interface browsing information.

5. The data collection method based on business scenarios according to claim 2, characterized in that, The event tracking plugin also includes a storage module. The acquisition module stores the acquired event information in the storage module, and the transmission module transmits the event information in the storage module to the database.

6. The data collection method based on business scenarios according to claim 2, characterized in that, After the step of setting the tracking plugin on the application interface corresponding to the business scenario, the method further includes: According to the set transmission period, the transmission module is triggered to send the event information to the database; Or / and, based on a set information threshold, the transmission module is triggered to send the event information to the database.

7. A data tracking device based on business scenarios, characterized in that, include: The acquisition unit is used to acquire the event tracking configuration file corresponding to the business scenario, and parse the event tracking configuration file through a script to extract different types of initial event tracking configuration information from the event tracking configuration file; A reorganization unit is used to obtain reorganization keywords and reorganize the initial tracking point configuration information according to the reorganization keywords using a script to obtain reorganized tracking point configuration information. The reorganization keywords include the interface name, and the reorganized tracking point configuration information is obtained by reorganizing the initial tracking point configuration information based on the interface name. The normalization unit is used to normalize the recombined embedding configuration information to obtain normalized embedding configuration information. A generation unit is used to generate a tracking plugin based on the normalized tracking configuration information, wherein the tracking plugin includes visual tracking or full tracking. The setting unit is used to set the event tracking plugin on the application interface corresponding to the business scenario. The event tracking plugin is used to collect and transmit event information generated on the application interface; obtain test event information generated on the application interface based on test operation information through the event tracking plugin; and verify whether the test event information matches the test operation information.

8. An electronic device, characterized in that, It includes a processor and a memory, wherein a computer program is stored in the memory, and when the computer program is executed by the processor, it implements the data collection method based on any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the data tracking method based on any one of claims 1 to 6.

Images