Event point burying method and device based on abstract thinking design, medium and equipment

Abstract

The invention provides an event point burying method and device based on abstract thinking design, a medium and equipment, and relates to the technical field of event point burying and the financial science and technology field, and the method comprises the steps: obtaining point burying data information, and reporting the point burying data information to a point burying abstraction layer; the burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information; determining a target data reporting platform corresponding to the target reporting component; and calling an SDK (Software Development Kit) of the target data reporting platform by utilizing the target reporting component, and reporting the burying point data information to the target data reporting platform based on the SDK of the target data reporting platform so as to complete an event burying point operation of the trigger operation. According to the embodiment of the invention, the event burying point abstraction layer is provided, so that direct interaction between an application layer and an underlying data reporting platform is isolated, the flexibility and expandability of event burying points are improved, and an efficient and convenient solution is provided for event tracking and data analysis in the field of financial science and technology.

Description

Technical Field

[0001] The present disclosure relates to the field of event tracking technology and the field of financial technology, and specifically, to an event tracking method, device, medium and equipment designed based on abstract thinking. Background Art

[0002] In the financial sector, with the acceleration of digital transformation, the project tracking system has become a key tool for financial institutions to collect and analyze data. The system aims to capture various behavioral events of users in the process of using financial products, such as transactions, logins, browsing, etc., so as to conduct subsequent user behavior analysis, product optimization and personalized recommendations. Since financial institutions usually cooperate with multiple third-party platforms to achieve multiple functions such as payment, risk control, and marketing, the project tracking system will face a complex reality: different platforms have different requirements for event reporting. Some platforms only need to receive specific events, while others require comprehensive reception and processing of large amounts of data. In addition, there are significant differences in the reporting interfaces and data processing specifications of these platforms, which undoubtedly increases the complexity of the design and implementation of the tracking system.

[0003] At present, the tracking point systems of financial projects generally face the problem of strong dependence on the application layer. The business layer directly calls the tracking point SDK interface, which simplifies the operation but brings many disadvantages. First, changes in the tracking point SDK directly affect the business logic and reduce the stability of the system; second, when updating or replacing the tracking point product, the call point needs to be fully modified, which increases the cost and risk of change; third, the lack of a unified public reference processing mechanism leads to the need for each platform to be processed separately, which is inefficient; finally, the inconsistency of the interfaces of different tracking point products increases the learning and maintenance costs of developers. These disadvantages limit the flexibility and scalability of the tracking point system, which is not conducive to the long-term stable operation and continuous optimization of the system. Summary of the invention

[0004] The embodiments of the present disclosure at least provide an event tracking method, device, medium and equipment designed based on abstract thinking. By proposing an event tracking abstract layer, the direct interaction between the application layer and the underlying data reporting platform is isolated, so that the application layer does not need to pay attention to the implementation details of the underlying data reporting platform, and only needs to use the event tracking abstract layer to achieve data interaction with the data reporting platform, thereby improving the flexibility and scalability of event tracking, and providing an efficient and convenient solution for event tracking and data analysis in the field of financial technology.

[0005] The present disclosure provides an event tracking method based on abstract thinking design, including:

[0006] Acquire the buried point data information, and report the buried point data information to the buried point abstraction layer; wherein the buried point data information includes a buried point event reporting channel;

[0007] The burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information;

[0008] Determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

[0009] The present disclosure provides an event tracking device designed based on abstract thinking, including:

[0010] An information collection module obtains the buried point data information and reports the buried point data information to the buried point abstraction layer; wherein the buried point data information includes a buried point event reporting channel;

[0011] A component determination module, used for the burying point abstraction layer to determine at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information;

[0012] An information reporting module is used to determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

[0013] An embodiment of the present disclosure provides a computer device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, an event tracking method based on abstract thinking design as described in any possible implementation manner described above is performed.

[0014] An embodiment of the present disclosure provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the event tracking method based on abstract thinking design as described in any possible implementation manner described above is implemented.

[0015] The event tracking method, device, medium and equipment provided in the embodiments of the present disclosure based on the design of abstract thinking, first, obtain the tracking data information, and report the tracking data information to the tracking abstract layer; then, the tracking abstract layer determines at least one target reporting component corresponding to the tracking event reporting channel based on the tracking data information; and then determines the target data reporting platform corresponding to the target reporting component; finally, the target reporting component is used to call the SDK of the target data reporting platform, and the tracking data information is reported to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation of the triggering operation. In this way, the present disclosure isolates the direct interaction between the application layer and the underlying data reporting platform by proposing a tracking abstract layer, so that the application layer does not need to pay attention to the implementation details of the underlying data reporting platform, and only needs to realize data interaction with the data reporting platform through the tracking abstract layer, thereby improving the flexibility and scalability of event tracking, and providing an efficient and convenient solution for event tracking and data analysis in the field of financial technology.

[0016] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required to be cited in the embodiments. The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and are used together with the specification to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without creative work.

[0018] Figure 1 A schematic diagram of an application environment of an event tracking method based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0019] Figure 2 A flow chart of an event tracking method based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0020] Figure 3 A flow chart of a first tracking plug-in preprocessing method in an event tracking method based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0021] Figure 4 A flowchart of a second tracking plug-in post-processing method in an event tracking method based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0022] Figure 5 A schematic diagram of the structure of an event tracking device based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0023] Figure 6 A schematic diagram of the structure of another event tracking device based on abstract thinking design provided by an embodiment of the present disclosure is shown;

[0024] Figure 7 A schematic diagram of the structure of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, the technical scheme in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the present disclosure for protection, but merely represents the selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present disclosure.

[0026] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0027] The term "and / or" herein only describes an association relationship, indicating that three relationships may exist. For example, A and / or B may represent the following three situations: A exists alone, A and B exist at the same time, and B exists alone. In addition, the term "at least one" herein represents any combination of at least two of any one or more of a plurality of. For example, including at least one of A, B, and C may represent including any one or more elements selected from the set consisting of A, B, and C.

[0028] To facilitate understanding of this embodiment, the execution subject of the event tracking method based on abstract thinking design provided by the embodiment of the present disclosure is first introduced in detail. The event tracking method based on abstract thinking design provided by the embodiment of the present invention can be applied to Figure 1In an application environment, the client communicates with the server through a network. The client can be a mobile device, a user terminal, a terminal, a handheld device, a computing device, etc. The server can be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud storage, big data and artificial intelligence platforms.

[0029] The event tracking method based on abstract thinking design provided by the embodiment of the present application is described in detail below in conjunction with the accompanying drawings. Figure 2 As shown, it is a flow chart of an event tracking method based on abstract thinking design provided by an embodiment of the present disclosure, and the method includes the following S201-S203:

[0030] S201, obtaining buried point data information, and reporting the buried point data information to the buried point abstraction layer.

[0031] It is understandable that event tracking refers to a data collection mechanism pre-set in an application to record user behavior, application status or system events. Event tracking requires first obtaining tracking data information, that is, collecting data related to user behavior, event triggering or system status in the application. This process is usually completed by embedding tracking code in different locations of the application. For example, a user's actions such as clicking a button, browsing a page, and completing a purchase can all be considered an event, and the corresponding data can be collected by triggering specific tracking code when these actions occur.

[0032] Specifically, in order to ensure the consistency and standardization of the buried data, a preset interface specification can be designed for the acquisition method corresponding to each buried data. The interface specification is a convention to ensure that the event attributes of each event are unified. Here, the event attributes include event name, event id, event triggering method, and event reporting channel. The event name is expressed as a brief description related to the event, which is used to identify the event; the event id is a unique identifier for each event, usually a string or a number, to ensure that each event has a unique mark in the entire system; the event triggering method is to describe the cause or condition of the event. Common triggering methods include user operations (clicks, slides, etc.) or system triggers (page loading, network request completion, etc.); the event reporting channel is expressed as the platform to which the buried data is reported after the event is triggered. Correspondingly, the collected buried data information includes the buried event name, buried event id, buried event triggering method, and buried event reporting channel.

[0033] For example, in the financial field, embedding code is embedded in different locations of financial applications to obtain embedding data information. For example, event embedding can be set in the process of user login, browsing financial product pages, and performing transaction operations (such as purchasing funds and transferring money). These embedding codes are triggered when users perform corresponding operations, and collect information such as event name, event id, triggering method (such as user click, system trigger), and reporting channel (such as third-party financial data analysis platform).

[0034] In some other embodiments, the event type, data structure, and attribute type (such as string, number, Boolean value, etc.) of each event may also be defined in the interface specification. In this way, when implementing event tracking, developers can obtain and report data according to the standard interface to avoid data inconsistency or loss due to differences in their respective implementations.

[0035] In the present disclosure, by designing a preset interface specification for the acquisition method corresponding to each buried point data, it is ensured that the event attributes of each event are unified, thereby effectively avoiding data inconsistency or missing problems caused by implementation differences and improving data quality.

[0036] It can be understood that abstract thinking refers to the extraction of common features and laws from specific things through in-depth analysis and summary, and then forming a generalized and generalized way of thinking. In the present disclosure, the application of abstract thinking is reflected in the design of the point-burying abstract layer. Specifically, the point-burying abstract layer abstracts the reporting channels of different point-burying events, that is, in the point-burying abstract layer, multiple reporting components are pre-registered, and each reporting component corresponds to a different data reporting platform (such as a server-side data collection platform, a third-party data analysis platform, a log analysis platform, etc.). For example, assuming that the point-burying of an application needs to support sending data to two different analysis platforms at the same time (such as platform A and platform B), then two reporting components can be pre-registered in the point-burying abstract layer, corresponding to the two platforms respectively, so that the point-burying abstract layer will select the corresponding reporting component according to the point-burying data information reported each time (including the point-burying reporting channel). In this way, the present invention simplifies the relationship between specific data information and various data reporting platforms into a universal abstract layer, smoothing the differences between data reporting platforms and data point applications. It only needs to focus on data collection and transmission without worrying about specific platform implementation details. This allows the system to flexibly adapt and accurately select corresponding reporting components when faced with different point-of-care data information reporting tasks.

[0037] Exemplarily, when defining the event attributes of the acquisition method corresponding to the buried point data information, it is also necessary to determine whether there is a reporting component corresponding to the event reporting channel related to the event attributes of the acquisition method in the buried point abstract layer, so as to check whether the existing resources can meet the requirements of the new event attributes. When there is no reporting component corresponding to the event reporting channel related to the event attributes of the acquisition method in the buried point abstract layer, it is necessary to determine the specific data reporting platform indicated by the event reporting channel and build a reporting component corresponding to the data reporting platform. This reporting component can implement the logic required to communicate with the data reporting platform, and may include protocol conversion, etc. After building a new reporting component, the newly built reporting component can be registered in the buried point abstract layer, which usually involves adding new component information in the configuration of the buried point abstract layer, and updating related dependencies to ensure the smooth operation of the entire data collection process.

[0038] For example, when defining the event attributes of the acquisition method corresponding to the burial point data information, if there is a reporting component corresponding to the event reporting channel related to the event attributes of the acquisition method in the burial point abstract layer, the burial point data information obtained from the acquisition method can be directly sent to the burial point abstract layer for processing according to the established process, without the need for additional construction and registration steps.

[0039] In the present disclosure, by dynamically registering reporting components, the system can build and register new reporting components in the tracking point abstraction layer as needed to adapt to different data reporting platforms. This not only reduces the cost and risk of changes, but also improves the maintainability and scalability of the system.

[0040] S202: The burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information.

[0041] It can be understood that the burying point abstraction layer includes a first burying point plug-in and a second burying point plug-in, which are pluggable plug-ins for the burying point abstraction layer, and are used to pre-process and post-process the burying point data information during the event burying process to meet the needs of different platforms and businesses.

[0042] Specifically, refer to Figure 3 After the tracking point data information is reported to the tracking point abstraction layer, the following steps S301 to S303 may be included:

[0043] S301, obtaining the burying point event information corresponding to the burying point data information, and sending the burying point data information and the burying point event information to the first burying point plug-in.

[0044] Here, the burying point event information includes burying point event user information, which may include: user device information (such as device model, operating system version), geographic location (such as the city or specific coordinates of the user), user identity information (such as login status, user ID), etc. After the burying point event information corresponding to the burying point data information is obtained, it is sent to the first burying point plug-in.

[0045] S302: pre-process the burying point event information and the burying point data information based on the first burying point plug-in to combine the burying point event information and the burying point data information.

[0046] It is understandable that after receiving the burial point data, the first burial point plug-in will pre-process the data with the aim of integrating the collected burial point event information and data information to meet specific reporting requirements. This process may include data merging (combining the burial point event information and the burial point data information to generate a complete event data packet).

[0047] S303, updating the tracking point data information based on the preprocessing result; the first tracking point plug-in determines at least one target reporting component corresponding to the tracking point event reporting channel based on the updated tracking point data information.

[0048] Specifically, after the preprocessing is completed, the first tracking plug-in will further update the tracking data information based on the preprocessing results, and then determine the tracking event reporting channel according to the updated tracking data information, and select its corresponding target reporting component to complete the data reporting. Here, the tracking event reporting channel can correspond to multiple target reporting components.

[0049] In the present disclosure, by acquiring and combining the burial point data information and the burial point event information (such as user device information, geographic location and identity information, etc.), the integrity of the reported burial point data information and the richness of the contextual information are ensured; then, the first burial point plug-in pre-processes the data, including data merging, so that the reported burial point data information can have user information, thereby improving the integrity of the data.

[0050] S203, determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

[0051] It is understandable that since the reporting component and the data reporting platform have a one-to-one correspondence, that is, after determining the target reporting component, the target data reporting platform to which the buried point data information needs to be reported can be determined. Then, the target reporting component is used to call the SDK (software development kit) provided by the platform. The SDK of the target data reporting platform provides some predefined functions or APIs, which interact with the platform through these interfaces. The SDK usually has packaged functions to handle network requests, data formatting, retry mechanisms, error reports, etc., to help technicians efficiently complete the task of uploading data.

[0052] Specifically, after the target reporting component calls the SDK of the target data reporting platform, the system will perform a data upload operation to transfer the tracking data information to the target data reporting platform. This process usually includes: data is processed and formatted according to the requirements of the target platform. For example, tracking data may need to be converted to a specific JSON format, or the field naming method may need to be adjusted to ensure that the uploaded data meets the platform specifications.

[0053] For example, refer to Figure 4 As shown, after the tracking point data information is reported to the target data reporting platform, the following S401 to S402 may also be included:

[0054] S401, obtain the reporting result about the burying point data information, and send the reporting result to the second burying point plug-in.

[0055] It is understandable that the method of obtaining the reporting result of the buried data information may include a receipt of a network request, an identifier of the reporting status, or a response information returned by the platform.

[0056] S402, post-processing the reporting result based on the second tracking plug-in, the post-processing includes recording logs, counting reporting success rate, analyzing reporting exceptions, and executing other business logic related to the reporting result.

[0057] Specifically, by obtaining the reporting results about the tracking data information, the second tracking plug-in can understand the status of data transmission according to the reporting results, that is, whether the reported tracking data information has successfully reached the target data reporting platform, and then perform post-processing.

[0058] Here, post-processing can include logging. By recording detailed logs for each report, it can provide strong support for subsequent troubleshooting and data analysis. Secondly, statistical reporting success rate can help operation and maintenance personnel find possible problems in data reporting. If the success rate is lower than expected, it may indicate that the system has performance bottlenecks or network transmission anomalies. At the same time, post-processing can also include analyzing reporting anomalies, the purpose of which is to fundamentally identify and solve problems that arise in the data reporting process. For example, the reasons for some reporting failures may be related to factors such as network instability, long server response time, and interface return anomalies. Through detailed analysis of these anomalies, the system can perform targeted optimization to avoid the recurrence of similar problems. In addition, post-processing can also include executing other business logic related to the reporting results. Business logic may include automatically retrying reporting, notifying relevant personnel to handle, triggering alarm mechanisms, or adjusting data upload strategies, etc., which will help further improve the robustness and automation of the system and reduce the need for manual intervention.

[0059] For example, in practical applications in the financial field, the user behavior analysis of the bank APP is taken as an example to specifically explain the above-mentioned point-of-sale data reporting and post-processing process, including: when the user completes a transfer operation in the bank APP, it is reported to the point-of-sale abstract layer, and then the point-of-sale abstract layer reports the relevant point-of-sale data information (such as transfer amount, transfer time, payee information, etc.) to the bank's data analysis platform through the reporting component corresponding to the bank's data analysis platform. The bank system will obtain the reporting result of this point-of-sale data information and send the result to the second point-of-sale plug-in. Here, the reporting result may be presented in the form of a receipt of a successful network request, a status code 200 (representing success), or a confirmation JSON message returned by the platform. Then, the second tracking plug-in will perform in-depth post-processing on the reported results: the second tracking plug-in can record key information such as the time, content, and results of each transfer behavior data report, and provide data support for possible compliance reviews, troubleshooting, or user behavior pattern analysis in the future; or, the second tracking plug-in counts the reporting success rate and calculates the proportion of successfully reported tracking data to the total number of attempts within a period of time, which helps to evaluate the data transmission efficiency of the bank APP and monitor potential system or network problems; or, the second tracking plug-in can also analyze anomalies that occur during the reporting process, such as network timeouts, data format errors, or server response abnormalities.

[0060] In the present disclosure, the smooth progress of the reporting process is ensured by acquiring and post-processing the reporting results. At the same time, it also provides support for system optimization, troubleshooting and business logic execution, and improves the stability and reliability of the data reporting platform.

[0061] The event tracking method, device, medium and equipment provided in the embodiments of the present invention, which are designed based on abstract thinking, isolate the direct interaction between the application layer and the underlying data reporting platform by proposing an event tracking abstract layer, so that the application layer does not need to pay attention to the implementation details of the underlying data reporting platform, and only needs to use the event tracking abstract layer to achieve data interaction with the data reporting platform, thereby improving the flexibility and scalability of event tracking and providing an efficient and convenient solution for event tracking and data analysis in the field of financial technology.

[0062] Those skilled in the art will appreciate that, in the above method of specific implementation, the order in which the steps are written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of the steps should be determined by their functions and possible internal logic.

[0063] Based on the same inventive concept, the embodiment of the present disclosure also provides an event burying device based on abstract thinking design corresponding to the event burying method based on abstract thinking design. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the event burying method based on abstract thinking design mentioned above in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0064] Reference Figure 5 FIG. 5 is a schematic diagram of an event tracking device 500 based on abstract thinking design provided by an embodiment of the present disclosure, wherein the device includes:

[0065] The information collection module 501 obtains the buried point data information and reports the buried point data information to the buried point abstraction layer; wherein the buried point data information includes the buried point event reporting channel;

[0066] A component determination module 502, configured for the tracking point abstraction layer to determine at least one target reporting component corresponding to the tracking point event reporting channel based on the tracking point data information;

[0067] The information reporting module 503 is used to determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

[0068] In some possible embodiments, the information collection module 501 is further used for:

[0069] Define the event attributes of the acquisition method corresponding to the buried data information based on the preset interface specification; wherein the event attributes include event name, event id, event triggering method and event reporting channel;

[0070] The buried point data information also includes the buried point event name, buried point event id and buried point event triggering method.

[0071] In some possible embodiments, reference Figure 6 , the device further comprises:

[0072] A component judgment module 504 is used to judge whether there is a reporting component corresponding to the event reporting channel related to the event attribute in the burying point abstract layer when defining the event attribute of the acquisition method corresponding to the burying point data information;

[0073] The component construction module 505 is used to determine the data reporting platform indicated by the event reporting channel when there is no reporting component corresponding to the event reporting channel related to the event attribute in the burying point abstract layer, and to construct a reporting component corresponding to the data reporting platform, and to register the reporting component in the burying point abstract layer.

[0074] In some possible embodiments, the component determination module 502 is further configured to:

[0075] Construct multiple reporting components, each reporting component corresponds to a different data reporting platform, and register the multiple reporting components in the tracking point abstraction layer.

[0076] In some possible embodiments, the burying point abstraction layer includes a first burying point plug-in; the component determination module 502 is specifically used to:

[0077] Acquire the burying point event information corresponding to the burying point data information, and send the burying point data information and the burying point event information to the first burying point plug-in; wherein the burying point event information includes burying point event user information;

[0078] Preprocessing the burying point event information and the burying point data information based on the first burying point plug-in to combine the burying point event information and the burying point data information;

[0079] The tracking point data information is updated based on the preprocessing result; the first tracking point plug-in determines at least one target reporting component corresponding to the tracking point event reporting channel based on the updated tracking point data information.

[0080] In some possible embodiments, the burying point abstraction layer further includes a second burying point plug-in; the information reporting module 503 is further used to:

[0081] Obtaining a reporting result about the burying point data information, and sending the reporting result to the second burying point plug-in;

[0082] The reporting result is post-processed based on the second tracking plug-in, and the post-processing includes recording logs, counting reporting success rate, analyzing reporting exceptions, and executing other business logic related to the reporting result.

[0083] In some possible embodiments, the first burying point plug-in and the second burying point plug-in are both pluggable plug-ins for the burying point abstraction layer, which are used to pre-process and post-process the burying point data information during the event burying process to meet the needs of different platforms and businesses.

[0084] Based on the same technical concept, the embodiment of the present disclosure also provides a computer device. Figure 7 , which is a schematic diagram of the structure of a computer device 700 provided in an embodiment of the present disclosure, including a processor 701, a memory 702, and a bus 703. The memory 702 is used to store execution instructions, including a memory 7021 and an external memory 7022; the memory 7021 is also called an internal memory, which is used to temporarily store the operation data in the processor 701 and the data exchanged with the external memory 7022 such as a hard disk. The processor 701 exchanges data with the external memory 7022 through the memory 7021.

[0085] In the embodiment of the present application, the memory 702 is specifically used to store the application code for executing the solution of the present application, and the execution is controlled by the processor 701. That is, when the computer device 700 is running, the processor 701 communicates with the memory 702 through the bus 703, so that the processor 701 executes the application code stored in the memory 702, and then executes the method described in any of the above embodiments.

[0086] Among them, the memory 702 can be, but is not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable read-only memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.

[0087] Processor 701 may be an integrated circuit chip with signal processing capabilities. The above-mentioned processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present invention may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0088] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the computer device 700. In other embodiments of the present application, the computer device 700 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0089] The present disclosure also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the event tracking method based on abstract thinking design described in the above method embodiment are executed. The storage medium can be a volatile or non-volatile computer-readable storage medium.

[0090] The embodiments of the present disclosure also provide a computer program product, which carries a program code. The instructions included in the program code can be used to execute the steps of the event tracking method based on abstract thinking design described in the above method embodiment. Please refer to the above method embodiment for details, which will not be repeated here.

[0091] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0092] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, the specific working process of the system and device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed system and method can be implemented in other ways. The device embodiments described above are merely 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 communication interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0093] 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.

[0094] In addition, each functional unit in each embodiment of the present disclosure 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.

[0095] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the 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 a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0096] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The protection scope of the present disclosure is not limited thereto. Although the present disclosure is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present disclosure, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. An event tracking method based on abstract thinking design, characterized in that: include: Acquire the buried point data information, and report the buried point data information to the buried point abstraction layer; wherein the buried point data information includes a buried point event reporting channel; The burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information; Determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

2. The method according to claim 1, characterized in that Before obtaining the buried point data information, the following steps are included: Define the event attributes of the acquisition method corresponding to the buried data information based on the preset interface specification; wherein the event attributes include event name, event id, event triggering method and event reporting channel; The buried point data information also includes the buried point event name, buried point event id and buried point event triggering method.

3. The method according to claim 2, characterized in that The method further comprises: When defining the event attribute of the acquisition method corresponding to the tracking data information, it is determined whether there is a reporting component corresponding to the event reporting channel related to the event attribute in the tracking abstract layer; When there is no reporting component corresponding to the event reporting channel related to the event attribute in the burying point abstract layer, determine the data reporting platform indicated by the event reporting channel, construct a reporting component corresponding to the data reporting platform, and register the reporting component in the burying point abstract layer.

4. The method according to claim 1, characterized in that: Before the burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information, the method includes: Construct multiple reporting components, each reporting component corresponds to a different data reporting platform, and register the multiple reporting components in the tracking point abstraction layer.

5. The method according to claim 4, characterized in that The burying point abstraction layer includes a first burying point plug-in; the burying point abstraction layer determines at least one target reporting component corresponding to the burying point event reporting channel based on the burying point data information, including: Acquire the burying point event information corresponding to the burying point data information, and send the burying point data information and the burying point event information to the first burying point plug-in; wherein the burying point event information includes burying point event user information; Preprocessing the burying point event information and the burying point data information based on the first burying point plug-in to combine the burying point event information and the burying point data information; The tracking point data information is updated based on the preprocessing result; the first tracking point plug-in determines at least one target reporting component corresponding to the tracking point event reporting channel based on the updated tracking point data information.

6. The method according to claim 1, characterized in that The burying point abstraction layer also includes a second burying point plug-in; after the SDK based on the target data reporting platform reports the burying point data information to the target data reporting platform, it includes: Obtaining a reporting result about the burying point data information, and sending the reporting result to the second burying point plug-in; The reporting result is post-processed based on the second tracking plug-in, and the post-processing includes recording logs, counting reporting success rate, analyzing reporting exceptions, and executing other business logic related to the reporting result.

7. The method according to claim 6, characterized in that The first burying point plug-in and the second burying point plug-in are both pluggable plug-ins for the burying point abstraction layer, which are used to pre-process and post-process the burying point data information during the event burying process to meet the needs of different platforms and businesses.

8. An event tracking device designed based on abstract thinking, characterized in that: include: An information collection module obtains the buried point data information and reports the buried point data information to the buried point abstraction layer; wherein the buried point data information includes a buried point event reporting channel; A component determination module, used for the tracking point abstraction layer to determine at least one target reporting component corresponding to the tracking point event reporting channel based on the tracking point data information; An information reporting module is used to determine the target data reporting platform corresponding to the target reporting component; use the target reporting component to call the SDK of the target data reporting platform, and report the tracking data information to the target data reporting platform based on the SDK of the target data reporting platform to complete the event tracking operation.

9. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer device comprising a storage medium, a processor, and a computer program stored in the storage medium and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

Images