A method and device for collecting behavior logs

Abstract

The embodiments of the present specification provide a method and device for collecting behavior logs, the method comprising: when a target business is executed, monitoring whether a target operation event that needs to be monitored and is pre-set in the target business is triggered; if so, obtaining structured operation behavior log information corresponding to the target operation event through the SPM tracking point corresponding to the target operation event, and reporting it to a log collection server; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a method and device for collecting behavior logs. Background Art

[0002] With the rapid development of computer and Internet technology, Internet products that can handle business emerge in an endless stream. The emergence of these products has brought great convenience to people and avoided users queuing on site to handle business. Therefore, more and more users handle business online, such as online purchase of commercial insurance, online shopping, online payment, etc. When users handle business online, it is necessary to record the user's operation behavior when handling business, so that the user's operation behavior can be restored, analyzed, or the business handling process can be optimized later. Therefore, there is an urgent need for a solution to collect user operation behavior data during the user's business handling process. Summary of the invention

[0003] An embodiment of this specification provides a method for collecting behavior logs, the method comprising: when a target business is executed, monitoring whether a target operation event that needs to be monitored and is pre-set in the target business is triggered. If so, the structured operation behavior log information corresponding to the target operation event is obtained through the super location model SPM tracking point corresponding to the target operation event. The operation behavior log information is reported to the log collection server. Among them, the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business.

[0004] The embodiments of this specification provide a device for collecting behavior logs, which includes: a monitoring module, which monitors whether a target operation event that needs to be monitored and is pre-set in the target business is triggered when the target business is executed. An acquisition module, if the target operation event is triggered, obtains the structured operation behavior log information corresponding to the target operation event through the super location model SPM tracking point corresponding to the target operation event. A reporting module reports the operation behavior log information to the log collection server. Among them, the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business.

[0005] The embodiments of this specification also provide a behavior log collection device. The device includes a processor; and a memory arranged to store computer executable instructions, and when the executable instructions are executed, the processor: when the target business is executed, monitor whether the target operation event that needs to be monitored and is pre-set in the target business is triggered. If so, the structured operation behavior log information corresponding to the target operation event is obtained through the super location model SPM tracking point corresponding to the target operation event. The operation behavior log information is reported to the log collection server. Among them, the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business.

[0006] The embodiments of this specification also provide a storage medium for storing computer executable instructions, which implement the following process when executed: when the target business is executed, monitor whether the target operation event that needs to be monitored and is pre-set in the target business is triggered. If so, the structured operation behavior log information corresponding to the target operation event is obtained through the super location model SPM tracking point corresponding to the target operation event. The operation behavior log information is reported to the log collection server. Among them, the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0008] Figure 1 A schematic diagram of an application scenario of the behavior log collection method provided in the embodiments of this specification;

[0009] Figure 2 A method flow chart of a method for collecting behavior logs provided in an embodiment of this specification;

[0010] Figure 3 A schematic diagram of the interactive process of the behavior log collection method provided in the embodiment of this specification;

[0011] Figure 4 A schematic diagram of the module composition of a behavior log collection device provided in an embodiment of this specification;

[0012] Figure 5A schematic diagram of the structure of a behavior log collection device provided in an embodiment of this specification. DETAILED DESCRIPTION

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

[0014] Figure 1 A schematic diagram of an application scenario of the behavior log collection method provided in the embodiment of this specification, such as Figure 1 As shown, the application scenario includes a terminal device and a log collection server. The terminal device is a smart device used by the user to handle the target service, specifically, a mobile phone, a tablet computer, a computer, etc., and an application corresponding to the target service is installed on the terminal device, wherein the application can be an independent application (application, APP) installed on the terminal device, or a small program embedded in some independent applications, etc. The log collection server is an analysis server used for behavioral data analysis.

[0015] Specifically, for the target business, if it is necessary to monitor certain operation events of the target business, it is necessary to set the corresponding target operation event, that is, the corresponding super position model (SPM) tracking point in the application corresponding to the target business. In this way, when the user uses the application to execute the target business, if the target operation event is triggered, the structured operation behavior log information corresponding to the target operation event is collected and reported to the log collection server.

[0016] Figure 2 This is a flow chart of the first method of the behavior log collection method provided in the embodiment of this specification, Figure 2 The method shown is applied to a business client, that is, the method is executed by the business client. Figure 2 As shown, the method comprises at least the following steps:

[0017] Step 202, when the target service is executed, monitor whether the target operation event that needs to be monitored and is preset in the target service is triggered; if so, execute step 204; otherwise, end.

[0018] Among them, the above-mentioned target business can be any business that needs to be executed, such as purchasing commercial insurance, commercial insurance claims, payments, etc. For different businesses, the target operation event and the SPM tracking point corresponding to the target operation event can be set in advance in the application corresponding to the business according to actual needs. Specifically, the target operation event can be a click event, a page access event, an element (such as a page, a control, a module, etc.) exposure event, and so on. In the specific implementation, the target operation event that needs to be monitored can be set according to actual needs. The embodiments of this specification do not limit the specific event content of the above-mentioned target operation events.

[0019] Optionally, in a specific implementation, when it is detected that a user opens an application corresponding to a target service and executes the target service, an operation of monitoring whether a target operation event is triggered is triggered.

[0020] Step 204: Acquire structured operation behavior log information corresponding to the target operation event through the SPM tracking point corresponding to the target operation event.

[0021] The above-mentioned operation behavior log information includes the event type of the target operation event and the position information of the target operation event in the execution link of the target business.

[0022] Optionally, in an embodiment of the present application, the event type of the above-mentioned target operation event may include any one or more of a click event, an element exposure event or a page operation event, etc. Of course, the above-mentioned event type may also be other. Specifically, the specific content of the above-mentioned event type can be set according to actual needs, and the embodiments of this specification do not limit this.

[0023] In the specific implementation, when the target operation event pre-set in the target business is triggered, the SPM tracking point corresponding to the target operation event is called, and the structured operation behavior log information corresponding to the triggered target operation event can be obtained through the SPM tracking point.

[0024] Optionally, in the embodiments of the present specification, the acquired user operation behavior log information is directly structured into data by using the SPM technology, thereby avoiding the need to perform data structuring operations after acquiring the user operation behavior data.

[0025] Step 206: Report the above operation behavior log information to the log collection server.

[0026] The behavior log collection method provided in the embodiment of this specification pre-sets the target operation event that needs to be monitored and the SPM tracking point corresponding to the target operation event in the application of the target business according to actual needs. In this way, when the user executes the target business through the application, if the pre-set target operation event is detected to be triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point. In the embodiment of this specification, by adopting the SPM tracking point method, structured operation behavior log information can be directly obtained in the process of collecting operation behavior logs, avoiding the operation of structuring after obtaining the information, saving the cost and time of obtaining structured data, and improving the efficiency of obtaining structured data.

[0027] Optionally, in a specific implementation, in the above step 204, obtaining structured operation behavior log information corresponding to the target operation event through the SPM tracking point corresponding to the target operation event specifically includes the following process:

[0028] The event type and location information of the target operation event are obtained through SPM tracking, and the event type and location information are represented according to the set format as the structured operation behavior log information corresponding to the target operation event.

[0029] That is, in the embodiments of the present specification, by setting the SPM tracking point method, the event type of the triggered target operation event and its corresponding location information can be directly extracted from the user's operation behavior information, and the event type and location information can be expressed according to the set format, thereby achieving structured operation behavior log information.

[0030] Optionally, in a specific implementation, a possible form of the structured operation behavior log information obtained is event type-location information, that is, first list the field information of the event type representing the target operation event, and then list the location information field representing the location information of the target operation event in the execution link of the target business.

[0031] For example, suppose a user purchases commercial insurance in application A, and the target operation event is set as a click event of "confirm insurance". When the target operation event is triggered, the operation behavior log information obtained through the SPM tracking point can be: click to confirm insurance event-SPM code. Among them, the SPM code represents the location information corresponding to the operation event.

[0032] Optionally, in a specific implementation, the obtained operation behavior log information may include other required extended parameters in addition to the event type and location information of the target operation event, such as the application version number corresponding to the target business, the operating system version of the terminal device used, the current page flow, the previous page identifier, the length of time stayed on the page, and other parameters; the specific parameters that need to be obtained can be set according to actual needs. In this way, when executing the method provided in the embodiment of this specification, the corresponding data can be directly obtained through the pre-set SPM tracking points.

[0033] The method provided in the embodiments of this specification adopts the SPM tracking method, so that when collecting the operation behavior log information corresponding to the target operation event, structured operation behavior log information can be directly obtained, thereby avoiding the subsequent structured processing of the collected operation behavior log information and simplifying the process of obtaining structured operation behavior log information.

[0034] Optionally, in a specific embodiment, the location information of the target operation event obtained through SPM tracking in the execution link of the target business can be represented in the form of SPM coding; wherein, the SPM coding can include the site identification information of the site to which the target operation event belongs, the page identification information of the site page, the area identification information of the page area to which it belongs, and the module identification information of the area module.

[0035] That is, in the embodiment of the present specification, the location information of the target operation event obtained through the SPM tracking includes information such as the site and page to which the target operation event belongs and the specific location information on the page.

[0036] For ease of understanding, the following examples are given to illustrate.

[0037] For example, in a specific implementation, assume that a user performs an operation of purchasing commercial insurance in application A, and the target operation event set is a click event of "confirming insurance". When the target operation event is triggered, the location information of the target operation event in the link of purchasing commercial insurance obtained through the SPM embedding point can be represented as [spm1; spm2; spm3; spm4]; wherein spm1 is the identification information of application A, spm2 is the identification information of the insurance page, spm3 is the identification information of the insurance area, and spm4 is the identification information of the insurance confirmation module.

[0038] Specifically, in the embodiment of this specification, the operation behavior log information reported to the log collection server includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business. Therefore, the event type corresponding to the target operation event can also be obtained through the SPM tracking point. Continuing with the above example, the operation behavior log information corresponding to the target operation event obtained through the SPM tracking point can be represented as [click event; spm1; spm2; spm3; spm4].

[0039] In addition, it should be noted that in the embodiments of this specification, since an element can be uniquely identified by SPM coding, in the process of executing the target business, the SPM coding corresponding to a target operation event can be carried to the next page, thereby facilitating the tracking of the user's behavior path.

[0040] Optionally, in a specific implementation, an SDK (Software Development Kit) is provided in the application corresponding to the target service;

[0041] Correspondingly, in the above step 202, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered includes:

[0042] Use SDK to monitor whether the target operation event is triggered;

[0043] In the above step 204, the structured operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point corresponding to the target operation event, including:

[0044] The SPM tracking point corresponding to the target operation event is retrieved through the SDK, and the above operation behavior log information is obtained through the retrieved SPM tracking point;

[0045] In the above step 206, reporting the operation behavior log information to the log collection server includes:

[0046] The above operation behavior log information is reported to the log collection server through the SDK.

[0047] That is, in the embodiments of the present specification, an SDK is provided in the application corresponding to the target business. When the user executes the target business through the application, the SDK is triggered to perform the operation of monitoring whether the target operation event is triggered. If the SDK monitors that the target operation event is triggered, the SDK calls the SPM tracking point corresponding to the target operation event to trigger the SPM tracking point to obtain the structured operation behavior log information corresponding to the target operation event, and the SDK executes the operation of reporting the obtained operation behavior log information to the log collection server.

[0048] Specifically, the target operation event mentioned in the embodiments of this specification may be any one, two or more of a click event, a page access event, and an exposure event.

[0049] Optionally, in a specific implementation, the target operation event includes a click event;

[0050] Correspondingly, in the above step 202, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered specifically includes:

[0051] Monitor whether a target control in the execution link of the target business is clicked; if so, determine that a target operation event is triggered.

[0052] Generally, in specific implementation, for the target business, it may be necessary to only collect the operation conditions of certain key controls. Therefore, the target controls that need to be monitored can be pre-set as target operation events. In this way, when the user clicks the target control, that is, when the target control is detected to be clicked, it is determined that the target operation event is triggered.

[0053] For ease of understanding, the following examples are given to illustrate.

[0054] For example, in a specific implementation, the target business is a commercial insurance business, and the target operation events that need to be monitored include "clicking on the insurance confirmation control". When the user executes the commercial insurance business, the SDK pre-set in the application will monitor whether the user clicks on the "confirm insurance control". If it is detected that the "confirm insurance control" is clicked, the SPM tracking point corresponding to the "click on the insurance confirmation control" event is retrieved through the SDK, and the structured operation behavior information corresponding to the "click on the insurance confirmation control" is obtained through the SPM tracking point, and reported to the log collection server.

[0055] Optionally, in a specific implementation, the target operation event includes a page access event; accordingly, in the step 202, monitoring whether a target operation event that needs to be monitored and is preset in the target business is triggered specifically includes:

[0056] Monitor whether a target page in the execution link of the target business is executed with a set operation; if so, determine that a target operation event is triggered;

[0057] The above setting operation includes any one of the following operations: a loading operation, a closing operation or a jumping operation.

[0058] Optionally, in a specific implementation, the target operation event is determined to be triggered when the user loads (or understands to open) the target page; or, the target operation event is determined to be triggered when the user loads (or opens) the target page and then performs an operation to close the target page; or, the target operation event is determined to be triggered when the user loads (or opens) the target page and then performs an operation to jump from the target page to other pages.

[0059] Specifically, in the embodiments of this specification, it can be determined that the target operation event is triggered when the target page is opened, or it can be determined that the target operation event corresponding to the target page is triggered when the target page is closed. The triggering method corresponding to the target operation event can be set according to actual needs, and the embodiments of this specification do not limit this. For example, if it is necessary to report the length of time the user stays on the target page, the closing of the target page can be selected as the triggering method of the target operation event corresponding to the target page.

[0060] Optionally, in a specific implementation, the target operation event includes an exposure event;

[0061] Correspondingly, in the above step 202, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered specifically includes:

[0062] Monitor whether the target element in the execution link of the target business is exposed in the current interface; if so, determine that the target operation event is triggered;

[0063] The target element includes any one of the following: a page, a module or a control.

[0064] Optionally, in a specific implementation, each time a target operation event is triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point corresponding to the target operation event, and the operation behavior log information corresponding to the target operation event is reported to the log collection server. That is, the operation behavior log information is reported in real time to ensure the timeliness of the operation behavior log information.

[0065] However, for some specific businesses, there may be more target operation events that need to be monitored, and multiple target operation events may be pre-set on a page. In this way, if the operation behavior log information corresponding to each target operation event is still reported once, frequent event reporting is required. In this case, in order to reduce the number of data reports to the log collection server (which can also be understood as throttling), the operation behavior log information collected during this period of time can be reported at intervals.

[0066] Accordingly, in the embodiment of the present specification, before executing the above step 206, that is, before reporting the operation behavior log information to the log collection server, the method provided in the embodiment of the present specification further includes the following steps:

[0067] Collecting operation behavior log information corresponding to at least one target operation event acquired within a set time length;

[0068] Correspondingly, in the above step 206, reporting the above operation behavior log information to the log collection server specifically includes:

[0069] Report the operation behavior log information collected within the set time length to the log collection server.

[0070] Among them, the specific value of the above-mentioned set time length can be any value such as 1 second, 2 seconds, etc. The specific value of the above-mentioned set time length can be set according to actual needs. For example, when setting the specific value of the set time length, timeliness and reporting frequency can be taken into account.

[0071] For example, in a specific implementation, the above-mentioned set time length is set to a value of 5 seconds, that is, the reporting operation of the operation behavior log information is performed once every 5 seconds, and the reported operation behavior log information is the operation behavior log information collected from the previous reporting to the current reporting, that is, the reported operation behavior log information is the operation behavior log information collected within these 5 seconds.

[0072] In addition, it should be noted that the target operation events and SPM tracking points in the embodiments of this specification are all set in the application corresponding to the target business. In some application scenarios, after the developer sets some target operation events in the application corresponding to the target business, in the later actual operation, it may be found that the set target operation events are unreasonable or cannot meet the actual needs. At this time, the developer can change the target operation events set in the application corresponding to the target business, or add new target operation events in the application or delete existing target operation events. After completing the modification of the application corresponding to the target business, send an indication of the application update to the business client to instruct the user to upgrade the application corresponding to the target business.

[0073] Therefore, the method provided in the embodiment of this specification also includes the following process:

[0074] When there is an event update for the target operation event corresponding to the target business, the operation of updating the application corresponding to the target business is executed according to the instruction of the business server; wherein the updated target operation event and the corresponding SPM tracking point are set in the application to be updated.

[0075] Thus, in the embodiment of the present specification, the target operation events and SPM tracking points corresponding to the target business can be updated by updating the application corresponding to the target business.

[0076] To facilitate understanding of the method provided in the embodiments of this specification, the method provided in the embodiments of this specification will be introduced below by taking the target business as commercial insurance business and the target operation event as "click to confirm insurance" as an example. Figure 3 The interactive schematic diagram of the method provided in the embodiment of this specification is as follows: Figure 3 As shown, the method comprises the following steps:

[0077] Step 302, when the user executes the target service through the target service client, the SDK set in the target service client is triggered to monitor whether the "click to confirm insurance control" event is triggered; if so, step 304 is executed;

[0078] Step 304, call the SPM tracking point corresponding to the "click to confirm insurance control" event through SDK.

[0079] Step 306, obtain the structured operation behavior log information corresponding to the "click to confirm insurance control" event through the called SPM tracking point.

[0080] Step 308: Report the acquired operation behavior log information to the log collection server through the SDK.

[0081] The behavior log collection method provided in the embodiment of this specification pre-sets the target operation event that needs to be monitored and the SPM tracking point corresponding to the target operation event in the application of the target business according to actual needs. In this way, when the user executes the target business through the application, if the pre-set target operation event is detected to be triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point. In the embodiment of this specification, by adopting the SPM tracking point method, structured operation behavior log information can be directly obtained in the process of collecting operation behavior logs, avoiding the operation of structuring after obtaining the information, saving the cost and time of obtaining structured data, and improving the efficiency of obtaining structured data.

[0082] Corresponding to the behavior log collection method provided in the embodiment of this specification, based on the same idea, the embodiment of this specification also provides a behavior log collection device for executing the method provided in the embodiment of this specification. Figure 4 A schematic diagram of the module composition of the behavior log collection device provided in the embodiment of this specification, such as Figure 4 As shown, the device comprises:

[0083] A monitoring module 402 monitors whether a target operation event that needs to be monitored and is preset in the target business is triggered when the target business is executed;

[0084] The acquisition module 404, if the target operation event is triggered, obtains the structured operation behavior log information corresponding to the target operation event through the super position model SPM tracking point corresponding to the target operation event; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business;

[0085] The reporting module 406 reports the operation behavior log information to the log collection server.

[0086] Among them, the device provided in the embodiments of this specification can realize Figure 2-3 All the method steps in the embodiment shown in the figure, therefore, the specific implementation process of each function corresponding to the device can be referred to. Figure 2-3 The embodiments shown will not be described in detail here.

[0087] The behavior log collection device provided in the embodiment of the present specification pre-sets the target operation event to be monitored and the SPM tracking point corresponding to the target operation event in the application of the target business according to actual needs. In this way, when the user executes the target business through the application, if the pre-set target operation event is detected to be triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point. In the embodiment of the present specification, by adopting the SPM tracking point method, structured operation behavior log information can be directly obtained in the process of collecting operation behavior logs, avoiding the operation of structuring after obtaining the information, saving the cost and time of obtaining structured data, and improving the efficiency of obtaining structured data.

[0088] Furthermore, based on the above Figures 2 to 3 The method shown in the embodiment of the present specification also provides a device for collecting behavior logs, such as Figure 5 shown.

[0089] The behavior log collection device may have different configurations or performances, and may include one or more processors 501 and memory 502. The memory 502 may store one or more storage applications or data. The memory 502 may be a temporary storage or a permanent storage. The application stored in the memory 502 may include one or more modules (not shown in the figure), each of which may include a series of computer executable instruction information in the behavior log collection device.

[0090] Furthermore, the processor 501 can be configured to communicate with the memory 502, and execute a series of computer executable instruction information in the memory 502 on the behavior log collection device. The behavior log collection device can also include one or more power supplies 503, one or more wired or wireless network interfaces 504, one or more input and output interfaces 505, one or more keyboards 506, etc.

[0091] In a specific embodiment, the behavior log collection device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instruction information in the behavior log collection device, and the one or more programs are configured to be executed by one or more processors, including computer executable instruction information for performing the following:

[0092] When the target service is executed, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered;

[0093] If so, the structured operation behavior log information corresponding to the target operation event is obtained through the super location model SPM tracking point corresponding to the target operation event; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business;

[0094] The operation behavior log information is reported to the log collection server.

[0095] Among them, the device provided in the embodiments of this specification can realize Figure 2-Figure 3 All the method steps in the embodiment shown in the figure, therefore, the specific implementation process of each function corresponding to the device can be referred to. Figure 2-Figure 3 The embodiments shown will not be described in detail here.

[0096] The behavior log collection device provided in the embodiment of the present specification pre-sets the target operation event that needs to be monitored and the SPM tracking point corresponding to the target operation event in the application of the target business according to actual needs. In this way, when the user executes the target business through the application, if the pre-set target operation event is detected to be triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point. In the embodiment of the present specification, by adopting the SPM tracking point method, structured operation behavior log information can be directly obtained in the process of collecting operation behavior logs, avoiding the operation of structuring after obtaining the information, saving the cost and time of obtaining structured data, and improving the efficiency of obtaining structured data.

[0097] Furthermore, based on the above Figures 2 to 3 The method shown in the specification also provides a storage medium for storing computer executable instruction information. In a specific embodiment, the storage medium can be a USB flash drive, an optical disk, a hard disk, etc. When the computer executable instruction information stored in the storage medium is executed by the processor, the following process can be implemented:

[0098] Obtaining from the application server the relevant data required to upload the target file to the object storage OSS server, and verification information generated based on the relevant data for authenticating the file upload end; wherein the relevant data includes the public key of the OSS server and the storage path of the target file in the OSS server;

[0099] When the target service is executed, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered;

[0100] If so, the structured operation behavior log information corresponding to the target operation event is obtained through the super location model SPM tracking point corresponding to the target operation event; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business;

[0101] The operation behavior log information is reported to the log collection server.

[0102] The computer executable instruction information stored in the storage medium provided in the embodiments of this specification can be implemented when executed. Figure 2-Figure 3 All method steps in the embodiment shown, therefore, the specific implementation process of each function corresponding to the computer executable instruction information stored in the storage medium when being executed can refer to Figure 2-Figure 3 The embodiments shown will not be described in detail here.

[0103] When the computer executable instruction information stored in the storage medium provided in the embodiment of this specification is executed, the target operation event that needs to be monitored and the SPM tracking point corresponding to the target operation event are pre-set in the application of the target business according to actual needs. In this way, when the user executes the target business through the application, if the pre-set target operation event is detected to be triggered, the operation behavior log information corresponding to the target operation event is obtained through the SPM tracking point; in the embodiment of this specification, by adopting the SPM tracking point method, structured operation behavior log information can be directly obtained in the process of collecting operation behavior logs, avoiding the operation of structuring after obtaining the information, saving the cost and time of obtaining structured data, and improving the efficiency of obtaining structured data.

[0104] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0105] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0106] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0107] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0108] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0109] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instruction information. These computer program instruction information can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instruction information executed by the processor of the computer or other programmable data processing device generates a method for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0110] These computer program instruction information can also be stored in a computer readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instruction information stored in the computer readable memory produces a manufactured product including an instruction information device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0111] These computer program instruction information can also be loaded into a computer or other programmable data processing device so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instruction information executed on the computer or other programmable device for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0112] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0113] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0114] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instruction information, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0115] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0116] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0117] The present application may be described in the general context of computer-executable instruction information executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0118] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0119] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for collecting behavior logs, the method comprising: When the target service is executed, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered is monitored through a software development kit SDK, wherein the SDK is set in the application corresponding to the target service; If so, the super location model SPM tracking point corresponding to the target operation event is retrieved through the SDK; the structured operation behavior log information corresponding to the target operation event is obtained through the retrieved SPM tracking point; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business, the location information is represented in the form of SPM coding, and the SPM coding includes the site identification information of the site to which the target operation event belongs, the page identification information of the site page to which it belongs, the area identification information of the page area to which it belongs, and the module identification information of the area module to which it belongs; The operation behavior log information is reported to the log collection server through the SDK.

2. The method according to claim 1, wherein the step of retrieving the super location model (SPM) tracking point corresponding to the target operation event through the SDK; and obtaining the structured operation behavior log information corresponding to the target operation event through the retrieved SPM tracking point comprises: The event type and location information of the target operation event are obtained through the SPM tracking point, and the event type and the location information are characterized according to a set format to serve as structured operation behavior log information corresponding to the target operation event.

3. The method according to claim 1, wherein the target operation event and the corresponding SPM tracking point are set in an application corresponding to the target business; Accordingly, the method further includes: When there is an event update for the target operation event corresponding to the target business, the operation of updating the application corresponding to the target business is executed according to the instruction of the business server; wherein the updated target operation event and the corresponding SPM tracking point are set in the application to be updated.

4. The method according to any one of claims 1 to 3, wherein the target operation event comprises a click event; Correspondingly, the monitoring of whether a target operation event preset in the target service and requiring to be monitored is triggered includes: Monitoring whether a target control in the execution link of the target service is clicked; If so, it is determined that the target operation event is triggered.

5. The method according to any one of claims 1 to 3, wherein the target operation event comprises a page access event; Correspondingly, the monitoring of whether a target operation event that is preset in the target service and needs to be monitored is triggered includes: monitoring whether a target page in the execution link of the target service is subjected to a set operation; if so, determining that the target operation event is triggered; The setting operation includes any one of the following operations: a loading operation, a closing operation or a jumping operation.

6. The method according to any one of claims 1 to 3, wherein the target operation event comprises an exposure event; Correspondingly, the monitoring of whether a target operation event that is preset in the target service and needs to be monitored is triggered includes: Monitoring whether a target element in the execution link of the target service is displayed in the currently displayed interface; if so, determining that the target operation event is triggered; The target element includes any one of the following: a page, a module or a control.

7. The method according to claim 1, before reporting the operation behavior log information to the log collection server, the method further comprises: Collecting operation behavior log information corresponding to at least one of the target operation events acquired within a set time length; Correspondingly, reporting the operation behavior log information to the log collection server includes: The operation behavior log information collected within the set time length is reported to the log collection server.

8. A device for collecting behavior logs, the device comprising: A monitoring module, when the target service is executed, monitors whether a target operation event that needs to be monitored and is preset in the target service is triggered through a software development kit SDK, wherein the SDK is set in the application corresponding to the target service; The acquisition module, if the target operation event is triggered, calls the super location model SPM tracking point corresponding to the target operation event through the SDK; obtains the structured operation behavior log information corresponding to the target operation event through the called SPM tracking point; wherein the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business, and the location information is represented in the form of SPM coding; wherein the SPM coding includes the site identification information of the site to which the target operation event belongs, the page identification information of the site page to which it belongs, the area identification information of the page area to which it belongs, and the module identification information of the area module to which it belongs; The reporting module reports the operation behavior log information to the log collection server through the SDK.

9. The device according to claim 8, wherein the acquisition module is specifically configured to: The event type and location information of the target operation event are obtained through the SPM tracking point, and the event type and the location information are characterized according to a set format to serve as structured operation behavior log information corresponding to the target operation event.

10. The device according to claim 8, wherein the target operation event and the corresponding SPM tracking point are set in an application corresponding to the target service; The device also includes: The update module executes the operation of updating the application corresponding to the target business according to the instruction of the business server when there is an event update in the target operation event corresponding to the target business; wherein the updated target operation event and the corresponding SPM tracking point are set in the application to be updated.

11. The device according to any one of claims 8 to 10, wherein the target operation event comprises a click event; Accordingly, the monitoring module is specifically used for: Monitor whether a target control in the execution link of the target service is clicked; if so, determine that the target operation event is triggered.

12. The device according to any one of claims 8 to 10, wherein the target operation event comprises a page access event; Accordingly, the monitoring module is specifically used for: monitoring whether a target page in the execution link of the target service is subjected to a set operation; if so, determining that the target operation event is triggered; in, The setting operation includes any one of the following operations: a loading operation, a closing operation or a jumping operation.

13. The apparatus according to any one of claims 8 to 10, wherein the target operation event comprises an exposure event; Accordingly, the monitoring module is specifically used for: Monitoring whether a target element in the execution link of the target service is displayed in the currently displayed interface; if so, determining that the target operation event is triggered; in, The target element includes any one of the following: a page, a module or a control.

14. A device for collecting behavior logs, comprising: processor; as well as a memory arranged to store computer executable instructions which, when executed, cause the processor to: When the target service is executed, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered is monitored through a software development kit SDK, wherein the SDK is set in the application corresponding to the target service; If so, the super location model SPM tracking point corresponding to the target operation event is retrieved through the SDK; the structured operation behavior log information corresponding to the target operation event is obtained through the retrieved SPM tracking point; wherein, the operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business, and the location information is represented in the form of SPM coding; wherein, the SPM coding includes the site identification information of the site to which the target operation event belongs, the page identification information of the site page to which it belongs, the area identification information of the page area to which it belongs, and the module identification information of the area module to which it belongs; The operation behavior log information is reported to the log collection server through the SDK.

15. A storage medium for storing computer executable instructions, wherein the executable instructions implement the following process when executed: When the target service is executed, monitoring whether a target operation event that needs to be monitored and is preset in the target service is triggered is monitored through a software development kit SDK, wherein the SDK is set in the application corresponding to the target service; If yes, the super location model SPM tracking point corresponding to the target operation event is retrieved through the SDK; the structured operation behavior log information corresponding to the target operation event is obtained through the retrieved SPM tracking point; wherein, The operation behavior log information includes the event type of the target operation event and the location information of the target operation event in the execution link of the target business, and the location information is represented in the form of SPM coding; wherein the SPM coding includes the site identification information of the site to which the target operation event belongs, the page identification information of the site page to which it belongs, the area identification information of the page area to which it belongs, and the module identification information of the area module to which it belongs; The operation behavior log information is reported to the log collection server through the SDK.

Images