CN110069463B

CN110069463B - User behavior processing method, device electronic equipment and storage medium

Info

Publication number: CN110069463B
Application number: CN201910191097.1A
Authority: CN
Inventors: 周天; 高思宇; 题华龙; 何宇航; 王伟
Original assignee: Beijing QIYI Century Science and Technology Co Ltd
Current assignee: Beijing QIYI Century Science and Technology Co Ltd
Priority date: 2019-03-12
Filing date: 2019-03-12
Publication date: 2021-07-16
Anticipated expiration: 2039-03-12
Also published as: CN110069463A

Abstract

The invention provides a user behavior processing method and device, electronic equipment and a storage medium. The method comprises the following steps: monitoring an operation event triggered by user behavior, acquiring an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to the operation event, and generating an operation log; receiving a path query request sent by a terminal, and acquiring a first target operation log corresponding to the path query request from the operation log; selecting an operation log with the same operation cycle identifier and operation tracking identifier from the first target operation log; and according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, taking the operation log with the level of the affiliated level below one level, and determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the affiliated level to obtain the tree-shaped user behavior path. The invention can obtain more accurate and more real user behavior path.

Description

User behavior processing method, device electronic equipment and storage medium

Technical Field

The present invention relates to the field of internet technologies, and in particular, to a user behavior processing method, an electronic device, and a storage medium.

Background

With the rapid development of mobile internet and intelligent terminals, mobile terminals are becoming an indispensable part of people's lives. With this, various APPs (applications) applied to mobile terminals are also emerging.

In order to solve the problem of the APP in use of a user, a product close to the user requirement is designed, and the operation information of the user is usually obtained, so that the use habit of the user is analyzed. Due to the huge amount of APP users, a mode of reporting user operation logs is generally adopted in the industry, and then the user behaviors are analyzed by using the operation logs.

The traditional operation logs are usually discrete, and the operation logs are simply correlated by time, so that the user can only know what behavior is executed by the user at what time, but the accurate logical relationship of the user behavior cannot be known, and the real behavior path of the user cannot be accurately known.

Disclosure of Invention

The embodiment of the invention provides a user behavior processing method, electronic equipment and a storage medium, and aims to solve the problem of inaccurate user behavior analysis.

In a first aspect, an embodiment of the present invention provides a user behavior processing method, where the method includes: after an operation event triggered by user behavior is monitored, acquiring an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to the operation event; the operational cycle identifying a lifecycle characterizing the operational event, the operational trace identifying an initial operation characterizing the operational event trace, the operational hierarchy identifying a level characterizing a hierarchy to which the operational event belongs, an upper level hierarchy identification of the hierarchy to which the operational event belongs, and a location in the hierarchy to which the operational event belongs; generating an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier and the operation level identifier; after receiving a path query request sent by a terminal, acquiring a first target operation log corresponding to the path query request from the operation log; selecting an operation log with the same operation cycle identifier and operation tracking identifier from the first target operation log; and according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, taking the operation log with the level of the affiliated level below one level, and determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the affiliated level to obtain the tree-shaped user behavior path.

Optionally, the obtaining of the operation name, the operation timestamp, the operation type, the operation cycle identifier, the operation tracking identifier, and the operation level identifier corresponding to the operation event includes: reading an operation name, an operation timestamp and an operation period identifier corresponding to the operation event; searching an operation type corresponding to the operation name from a preset mapping relation between the name and the type, and taking the operation type as an operation type corresponding to the operation event; and determining an operation tracking identifier and an operation level identifier corresponding to the operation event according to the operation name, the operation timestamp and the operation period identifier.

Optionally, the operation type comprises a behavior operation and a result operation; determining an operation tracking identifier and an operation level identifier corresponding to the operation event according to the operation name, the operation timestamp and the operation period identifier, including: when the operation name is a name representing a starting operation or a name representing an initial operation after starting, generating a unique operation tracking identifier as an operation tracking identifier corresponding to the operation event, and generating a unique primary operation level identifier as an operation level identifier corresponding to the operation event; when the operation name is not the name for representing the starting operation and the name for representing the initial operation after the starting, searching a first operation log from the stored operation logs; the operation cycle identifier of the first operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is behavior operation, and the operation timestamp is closest to the operation timestamp corresponding to the operation event; and acquiring an operation tracking identifier corresponding to the first operation log as an operation tracking identifier corresponding to the operation event, and generating a lower-level operation level identifier of the operation level identifier corresponding to the first operation log as an operation level identifier corresponding to the operation event.

Optionally, the generating a lower operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event includes: searching a second operation log from the stored operation logs; the operation cycle identifier of the second operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is result operation, the operation timestamp is positioned behind the operation timestamp corresponding to the first operation log, and the operation timestamp is closest to the operation timestamp corresponding to the operation event; when the second operation log is not found, generating a first lower-level operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event; and when the second operation log is found, generating lower operation level identifications which are arranged in an ascending order of the operation level identifications corresponding to the second operation log as the operation level identifications corresponding to the operation events.

Optionally, the method further comprises: and pushing the user behavior path to the terminal so as to display the user behavior path in the terminal.

Optionally, the method further comprises: after receiving an information query request sent by the terminal, acquiring a second target operation log corresponding to the information query request from the operation log; determining query result information corresponding to the information query request by using the second target operation log; and pushing the query result information to the terminal so as to display the query result information in the terminal.

Optionally, the method further comprises: detecting whether the operation log carries error information or not; when the operation log carries error information, counting the occurrence frequency of the error information within a set time; when the occurrence frequency of the error information exceeds a set threshold value, generating alarm information; and pushing the alarm information to a user subscribing the error information.

In a second aspect, an embodiment of the present invention provides a user behavior processing apparatus, where the apparatus includes: the first acquisition module is used for acquiring an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to an operation event after the operation event triggered by a user behavior is monitored; the operation cycle identification characterizes a life cycle to which the operation event belongs, the operation track identification characterizes an initial operation of the operation event track, and the operation hierarchy identification characterizes a level of a hierarchy to which the operation event belongs, an upper operation hierarchy identification of the hierarchy to which the operation event belongs, and a position in the hierarchy to which the operation event belongs; a log generating module, configured to generate an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier, and the operation level identifier; the second acquisition module is used for acquiring a first target operation log corresponding to a path query request from the operation log after receiving the path query request sent by a terminal; the selection module is used for selecting the operation logs with the same operation cycle identification and operation tracking identification from the first target operation logs; and the path generation module is used for determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the selected operation log to obtain the tree-shaped user behavior path by taking the operation log with the level of the selected operation log as a root node and the operation log with the level of the selected operation log below one level as a root node.

Optionally, the first obtaining module includes: the reading unit is used for reading an operation name, an operation timestamp and an operation cycle identifier corresponding to the operation event; the type determining unit is used for searching an operation type corresponding to the operation name from a preset mapping relation between the name and the type, and the operation type is used as an operation type corresponding to the operation event; and the identification determining unit is used for determining an operation tracking identification and an operation level identification corresponding to the operation event according to the operation name, the operation timestamp and the operation period identification.

Optionally, the operation type comprises a behavior operation and a result operation; the identification determination unit includes: the first identification determining subunit is configured to generate a unique operation tracking identification as an operation tracking identification corresponding to the operation event and a unique primary operation level identification as an operation level identification corresponding to the operation event when the operation name is a name characterizing a start operation or a name characterizing an initial operation after start; the second identification determining subunit is used for searching the first operation log from the stored operation logs when the operation name is not the name for representing the starting operation and the name for representing the initial operation after the starting; the operation cycle identifier of the first operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is behavior operation, and the operation timestamp is closest to the operation timestamp corresponding to the operation event; and acquiring an operation tracking identifier corresponding to the first operation log as an operation tracking identifier corresponding to the operation event, and generating a lower-level operation level identifier of the operation level identifier corresponding to the first operation log as an operation level identifier corresponding to the operation event.

Optionally, the second identity-determining subunit comprises: the log searching submodule is used for searching a second operation log from the stored operation logs; the operation cycle identifier of the second operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is result operation, the operation timestamp is positioned behind the operation timestamp corresponding to the first operation log, and the operation timestamp is closest to the operation timestamp corresponding to the operation event; the identifier generation sub-module is configured to generate a first lower-level operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event when the second operation log is not found; and when the second operation log is found, generating lower operation level identifications which are arranged in an ascending order of the operation level identifications corresponding to the second operation log as the operation level identifications corresponding to the operation events.

Optionally, the apparatus further comprises: the first pushing module is used for pushing the user behavior path to the terminal so as to display the user behavior path in the terminal.

Optionally, the apparatus further comprises: the third obtaining module is used for obtaining a second target operation log corresponding to the information query request from the operation logs after receiving the information query request sent by the terminal; the determining module is used for determining query result information corresponding to the information query request by using the second target operation log; and the second pushing module is used for pushing the query result information to the terminal so as to facilitate the query result information in the terminal.

Optionally, the apparatus further comprises: the detection module is used for detecting whether the operation log carries error information or not; the counting module is used for counting the occurrence frequency of the error information when the error information is carried in the operation log; the alarm generation module is used for generating alarm information when the occurrence frequency of the error information exceeds a set threshold value; and the third pushing module is used for pushing the alarm information to a user subscribing the error information.

In a third aspect, an embodiment of the present invention provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to perform any of the user behavior processing methods described above.

In a fourth aspect, an embodiment of the present invention provides a non-transitory computer-readable storage medium, where instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform any one of the user behavior processing methods described above.

In the embodiment of the invention, after monitoring an operation event triggered by user behavior, a client acquires an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to the operation event; generating an operation log carrying an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier, wherein the client can report the operation log to the server; after receiving a path query request sent by a terminal, a server acquires a first target operation log corresponding to the path query request from the operation logs; selecting an operation log with the same operation period identifier and operation tracking identifier from the first target operation log; and according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, taking the operation log with the level of the affiliated level below one level, and determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the affiliated level to obtain the tree-shaped user behavior path. Therefore, the operation log in the embodiment of the invention not only comprises the operation name and the operation timestamp, but also comprises the operation type, the operation period identifier, the operation tracking identifier and the operation level identifier. The operation event can be known as the operation in which life cycle according to the operation cycle identifier, the operation after which initial operation is performed can be known according to the operation tracking identifier, and the level of the hierarchy to which the operation event belongs, the upper hierarchy identifier of the hierarchy to which the operation event belongs and the position in the hierarchy to which the operation event belongs can be known according to the operation hierarchy identifier. Therefore, the operation after the same initial operation in the same life cycle can be associated through the operation cycle identifier and the operation tracking identifier, and each operation can be associated according to the actual hierarchical relationship through the operation hierarchical identifier, so that a more accurate and more real user behavior path can be obtained according to the operation log.

Drawings

FIG. 1 is a flow chart of steps of a method for user behavior processing according to an embodiment of the present invention;

FIG. 2 is a flow chart of steps in another method of user behavior processing according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating steps of a method for handling user behavior according to another embodiment of the present invention;

FIG. 4 is a diagram illustrating a tree-shaped user behavior path according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an interface showing a user behavior path according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of an interface for displaying core behavior information of a user according to an embodiment of the present invention;

FIG. 7 is an interface schematic of an alarm setting of an embodiment of the present invention;

fig. 8 is a block diagram of a user behavior processing apparatus according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Referring to fig. 1, a flowchart illustrating steps of a user behavior processing method according to an embodiment of the present invention is shown.

The user behavior processing method of the embodiment of the invention comprises the following steps:

step 101, after monitoring an operation event triggered by a user behavior, a client acquires an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to the operation event.

The client can be various APPs with the requirement of analyzing user behaviors, such as various reading APPs, video APPs, social APPs and the like.

When a user performs certain actions on the client, corresponding operational events may be triggered. For example, a user may trigger a start operation event when starting the client, a click operation event when clicking an interface of the client, a slide operation event when sliding the interface of the client, and the like.

The client monitors the operation event, and after the operation event triggered by the user behavior is monitored, operation information corresponding to the operation event can be acquired, wherein the operation information can include an operation name, an operation timestamp and the like. For example, the operation name of the start operation event may be a start operation, the operation name of the click operation event may be a click operation, the operation name of the slide operation event may be a slide operation, and the like. The operation time stamp indicates a time point at which the operation event occurs.

The client can also monitor whether the client is started in real time, generate a unique operation period identifier for the start after the client is started, and record the operation period identifier. After an operation event triggered by a user behavior is monitored, an operation period identifier recorded currently can be acquired as an operation period identifier corresponding to the operation event.

According to the operation name, the operation timestamp and the period identifier, the operation type, the tracking identifier and the hierarchy identifier corresponding to the operation event can be determined. The operation types may include behavioral operations and resultant operations. The behavior operation means an operation actively triggered by the user, such as start, click, slide, and the like. The result operation represents an operation resulting from a behavior operation, such as an interface request, page reveal, or the like.

And the operation event can be known as the operation in which life cycle according to the operation cycle identifier. A client is started once for a lifecycle.

According to the operation tracking identifier, the initial operation of the operation event tracking can be known, that is, the operation event is the operation after which initial operation. The initial operation may be an operation initially performed in a series of consecutive operations. For example, a start operation, a click operation, or the like may be used as the initial operation.

The level of the hierarchy to which the operation event belongs, the upper level hierarchy identification of the hierarchy to which the operation event belongs and the position in the hierarchy to which the operation event belongs can be known according to the operation hierarchy identification.

And 102, generating an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier and the operation level identifier by the client.

When the client generates the operation log, the operation log may carry information such as an operation name, an operation timestamp, an operation type, an operation cycle identifier, an operation tracking identifier, and an operation level identifier, and may also carry basic information such as an equipment type, an operating system version number, and a client version number.

The client can also report the operation log to the server. When using a client, the user behavior may include many, and thus, a plurality of operation logs will be generated. Considering that the number of the operation logs is large, if one operation log is generated and reported to the server every time, the number of interaction times is large, so that the operation log can be temporarily stored without reporting after the client generates the operation log.

In the embodiment of the invention, the reporting condition can be preset. And after detecting that the preset reporting condition is met, the client reports the stored operation logs to the server in batches.

For example, the reporting condition may be set such that the number of the stored operation logs reaches a set number. For the specific values of the set quantity, those skilled in the art can select any suitable value according to practical experience, for example, the number can be 50, 100, etc.

For another example, the reporting condition may be set to a set operation event. The set operation event may be a start operation event, a log out operation event, and the like.

Step 103, after receiving a path query request sent by a terminal, a server acquires a first target operation log corresponding to the path query request from the operation logs.

And after receiving the operation log reported by the client, the server stores the operation log. The operation log comprises information such as operation name, operation timestamp, operation type, operation period identification, operation tracking identification and operation level identification.

When a user behavior path corresponding to a certain user is desired to be viewed, corresponding operation can be executed in the terminal to trigger the terminal to send a path query request to the server. For example, a user may input one or more of information such as a user ID to be queried, a time range, an operating system version number, a client version number, and the like in a terminal, so as to trigger a path query request carrying information input by the user. The terminal may be a PC (personal computer) or the like.

The server can obtain a first target operation log corresponding to the path query request from the stored operation logs according to the user input information carried in the path query request. The first target oplog includes a plurality of oplogs that satisfy the path query request.

And 104, selecting the operation log with the same operation cycle identifier and operation tracking identifier from the first target operation log by the server.

And 105, the server uses the operation log with the level of the subordinate level as a root node according to the level identification corresponding to the selected operation log, determines the father-son relationship and the brother relationship according to the operation log with the level of the subordinate level below one level and the position of the superior level identification in the subordinate level, and obtains the tree-shaped user behavior path.

The server may determine, by using the first target operation log, a user behavior path according to an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier, and an operation level identifier of the first target operation log.

Firstly, an operation log with the same operation cycle identifier and operation tracking identifier is selected from a first target operation log. For a user, a series of behavior paths after the user executes an initial operation after starting the client once can be determined by using the operation log with the same operation cycle identifier and operation tracking identifier. And then, according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, determining a parent-child relationship and a brother relationship according to the level identification of the superior level and the position in the affiliated level of the operation log with the level of the affiliated level as the operation log with the level of one level or less, and obtaining the tree-shaped user behavior path.

The operation log in the embodiment of the invention not only comprises an operation name and an operation timestamp, but also comprises an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier. The operation after the same initial operation in the same life cycle can be associated through the operation cycle identifier and the operation tracking identifier, and each operation can be associated according to the actual hierarchical relationship through the operation hierarchical identifier, so that a more accurate and more real user behavior path can be obtained according to the operation log.

Referring to fig. 2, a flowchart illustrating steps of a user behavior processing method according to an embodiment of the present invention is shown. The user behavior processing method of the embodiment can be applied to the client.

step 201, after monitoring an operation event triggered by a user behavior, a client reads an operation name, an operation timestamp and an operation cycle identifier corresponding to the operation event.

The client monitors an operation event, the operation event has corresponding operation information, and the operation information may include an operation name, an operation timestamp, and the like. Therefore, after monitoring the operation event triggered by the user behavior, the client can read the operation name and the operation timestamp from the operation information.

The client can also automatically generate and record the operation cycle identifier after starting. After monitoring an operation event triggered by a user behavior, the client may read the currently recorded operation cycle identifier as the operation cycle identifier corresponding to the operation event.

Taking reading APP as an example, the operation names may include start operation start, click operation, swipe operation, foreground cut operation enterforego, background cut operation enterBackground, domain name switch operation domainChange, page turn operation pageturn, page block display operation blockpv, product page display operation detailspg, purchase operation purchase, bookshelf add operation addShelf, interface request operation API, desktop add operation icon, download operation download, read information operation readInfo, login operation login, log-out operation login, search operation search, and the like. Wherein the click operation click may include specific contents of a click, such as clicking a bookshelf, clicking a book city, and the like.

Step 202, the client searches an operation type corresponding to the operation name from a preset mapping relationship between the name and the type, and uses the operation type as an operation type corresponding to the operation event.

The operation types may include behavioral operations and resultant operations.

In this embodiment, the mapping relationship between the name and the type may be preset. For example, for the above 18 operation names, the setting behavior operation includes: starting operation start, clicking operation click, sliding operation swap, foreground switching operation enterForeground, background switching operation enterBackground and network domain name switching operation domainChange. The set result operation includes: page turning operation pageTurning, page block showing operation blockpv, page showing operation detailspg, purchase operation purchase, bookshelf adding operation addShelf, interface request operation API, desktop adding operation icon, download operation download, information reading operation readInfo, login operation login, log-out operation logout and search operation search. And finding the operation type corresponding to the operation name from the mapping relation between the preset name and the type, and taking the found operation type as the operation type corresponding to the operation event.

Step 203, the client determines an operation tracking identifier and an operation level identifier corresponding to the operation event according to the operation name, the operation timestamp and the operation period identifier.

The operation trace identification may characterize an initial operation of the operation event trace. The operation level identification characterizes the level of the level to which the operation event belongs, the upper level identification of the level to which the operation event belongs and the position in the level to which the operation event belongs.

In an alternative embodiment, step 203 may comprise:

and A1, when the operation name is a name representing a starting operation or a name representing an initial operation after starting, generating a unique operation tracking identifier as an operation tracking identifier corresponding to the operation event, and generating a unique primary operation level identifier as an operation level identifier corresponding to the operation event.

The name for representing the starting operation can be starting operation start, and the name for representing the initial operation after starting can be click operation and the like. And the name of the characterization starting operation and the operation type corresponding to the name of the initial operation after the characterization starting are behavior operations.

And when the operation name is the name representing the starting operation or the name representing the initial operation after the starting, indicating that the operation event is an initial operation. Therefore, a unique operation tracking identifier can be generated as the operation tracking identifier corresponding to the current operation event, and a unique primary operation level identifier can be generated as the operation level identifier corresponding to the current operation event.

And A2, when the operation name is not the name for representing the starting operation and the name for representing the initial operation after the starting, searching a first operation log in which the operation cycle identifier is the same as the operation cycle identifier corresponding to the operation event, the operation type is behavior operation, and the operation timestamp is the closest to the operation timestamp corresponding to the operation event from the stored operation log.

And when the operation name is not the name representing the starting operation and the name representing the initial operation after the starting, indicating that the current operation event is the operation after the previous initial operation. The operation of the upper level of the behavior operation and the result operation should be behavior operations. Therefore, the operation log corresponding to the latest behavior operation before the current operation event can be searched. In the implementation, a first operation log in which the operation cycle identifier is the same as the operation cycle identifier corresponding to the current operation event, the operation type is behavior operation, and the operation timestamp is closest to the operation timestamp corresponding to the current operation event can be searched from the stored operation log.

A3, obtaining the operation tracking identifier corresponding to the first operation log as the operation tracking identifier corresponding to the operation event, and generating a lower operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event.

The current operation event belongs to a next-level operation event of the operation event corresponding to the first operation log, so that the operation tracking identifier corresponding to the first operation log can be used as the operation tracking identifier corresponding to the current operation event, and a next-level operation level identifier of the operation level identifier corresponding to the first operation log is generated and used as the operation level identifier corresponding to the current operation event.

Since the next operation event of an operation event may include a plurality of operation events, the operation level identifiers of the next operation level identifier may include a plurality of operation level identifiers, and in order to more accurately indicate the association between user behaviors, the operation level identifiers of the next operation level identifier may be sorted in time. Therefore, the step of generating a lower operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the current operation event may include:

b1, searching a second operation log with an operation cycle identifier identical to the operation cycle identifier corresponding to the operation event and an operation type of the second operation log being a result operation, wherein the operation time stamp is located after the operation time stamp corresponding to the first operation log and closest to the operation time stamp corresponding to the operation event from the stored operation log.

Both the behavior operation and the last peer operation of the result operation should be the result operation. Therefore, the operation log corresponding to the latest result operation after the operation event corresponding to the first operation log before the current operation event can be searched. In the implementation, a second operation log, in which the operation cycle identifier is the same as the operation cycle identifier corresponding to the current operation event and the operation type is the result operation, and the operation timestamp is located after the operation timestamp corresponding to the first operation log and is closest to the operation timestamp corresponding to the current operation event, may be searched from the stored operation logs.

B2, when the second operation log is not found, generating a first lower operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event.

If the second operation log is not found, it indicates that the current operation event is the first subordinate operation event after the previous operation event (i.e. the operation event corresponding to the first operation log). Therefore, the first lower operation level identifier of the operation level identifier corresponding to the first operation log may be generated as the operation level identifier corresponding to the current operation event.

B3, when the second operation log is found, generating lower operation level identifiers arranged in ascending order of the operation level identifiers corresponding to the second operation log as the operation level identifiers corresponding to the operation events.

If the second operation log is found, the fact that the lower-level operation event after the upper-level operation event exists before the current operation is shown, and the operation event corresponding to the second operation log is closest to the current operation event. Therefore, the lower operation level identifiers arranged in ascending order of the operation level identifiers corresponding to the second operation log can be generated as the operation level identifiers corresponding to the current operation event.

And 204, generating an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier and the operation level identifier by the client, and storing the operation log.

And the client generates an operation log corresponding to the operation event. The oplog may include both basic delivery data and behavioral delivery data.

The basic delivery data may include: device type, operating system version number systemVersion, client version number QRVersion, network status netStatus, operator name, screen resolution, channel number AppKey, user device number QYID, user number UID, date, reader kernel version number kernelVersion, delivery rule version number pingbackRuleVersion, and the like.

The behavioral delivery data may include: the operation system comprises an operation name, an operation timeStamp, an operation type, an operation period identification life ID, an operation tracking identification traceID, an operation hierarchy identification span ID, a view stack versionStack (the hierarchical relationship of views, such as a plus-sign-click expansion view, and the like), an event parameter eventsParams (specific parameters corresponding to operations, such as service parameters and the like), and the like.

Thus, the format of the oplog can be expressed as follows:

obj＝{

“publicParam”:“xx”,

“events”:“xx”}

wherein, publicParam represents basic delivery data, and events represents behavior delivery data.

public param can be expressed as follows:

publicParam＝{

“deviceType”:”xx”,

“systemVersion”:”xx”,

“QRVersion”:”xx”…}

a complete publicParam may include the 12 basic delivery data described above.

events may be an array structure, each array element including one of the 18 behavior posting data described above, and the format of each array element may be expressed as follows:

events＝[{

"type": xx ", action or result

Name, xx, one of the delivery data of 18 behaviors

"traceID": xx ", operation tracking identification

"spanID": xx ", operation level identification, e.g., 0.1, 0.1.0, 0.1.1

"life ID": xx ", operation cycle identifier for starting APP once

"timeStamp", operation timeStamp, time point of each operation event

"VersionStack" "xxx/xxx/xxx/… …", view Stack information

"eventsParams": xx "and the parameters of each operation are different according to the name

}]

In step 205, the client reports the stored operation log to the server after meeting the preset reporting condition.

After the client generates the operation log, the client temporarily stores the operation log. And after meeting the preset reporting condition, reporting the stored operation log to a server.

After receiving the operation log reported by the client, the server can analyze the user behavior according to the operation log, so as to obtain an accurate user behavior path.

Referring to fig. 3, a flowchart illustrating steps of a user behavior processing method according to an embodiment of the present invention is shown. The user behavior processing method of the embodiment can be applied to a server.

step 301, a server receives an operation log reported by a client and stores the operation log.

Step 302, after receiving a path query request sent by a terminal, a server acquires a first target operation log corresponding to the path query request from the operation logs.

The server can obtain a first target operation log corresponding to the path query request according to the user input information carried in the path query request. The first target oplog includes a plurality of oplogs that satisfy the path query request.

Step 303, the server determines a user behavior path according to the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier, and the operation level identifier corresponding to the first target operation log by using the first target operation log.

The step of determining the user behavior path comprises the following steps: selecting an operation log with the same operation period identifier and operation tracking identifier from the first target operation log; and according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, taking the operation log with the level of the affiliated level below one level, and determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the affiliated level to obtain the tree-shaped user behavior path. .

Next, an example of clicking the book cover drawing and the subsequent operation will be described. Assume that the click book cover figure click operation is an initial operation after startup. The parts of the operation time stamp and the operation cycle identification are omitted in this example.

Fig. 4 is a schematic diagram of a tree-shaped user behavior path according to an embodiment of the present invention.

1. The user clicking on the book cover image triggers an operation event named click operation on the book cover image. Click book cover operation click is an action type operation. The current operation event is an initial operation after starting, so that a unique traceID is generated for the current operation event, and the value is assumed to be 123 abc. The current operation event is a first-level hierarchy, so that a unique spanID is generated for the current operation event, the value is assumed to be 0, the span ID is 0, the level of the hierarchy to which the spanID belongs is represented as a first-level hierarchy, and the hierarchy to which the spanID belongs does not have a higher-level hierarchy. The client generates an operation log corresponding to the operation event, where the operation log is a root node in the user behavior path, as shown in fig. 4.

2. The book detail page interface is called after the book cover image is clicked, so that an operation event with an operation name of the book detail page interface request operation API is triggered. The book detail page interface request operation API is a result type operation. Since the current operation event is a result triggered by an operation event of clicking a book cover image before, the value of traceID of the current operation event is also 123 abc. The current operation event is a second-level and belongs to a first operation event in the second-level, so that the value of the spanID of the current operation event is 0.0, the spanID of 0.0 represents that the level of the current operation event is the second-level, the position in the current operation event is 1, and the spanID of the upper-level of the current operation event is 0. The client generates an operation log corresponding to the current operation event, where the operation log is a first child node of the root node in the user behavior path, as shown in fig. 4.

3. The book detail page is also displayed after the book cover drawing is clicked, so that the operation name is triggered to be the book detail page display operation detailspg. The book detail page reveal operation detailspg is a result type operation. Since the current operation event is a result triggered by an operation event of clicking a book cover image before, the value of traceID of the current operation event is also 123 abc. The current operation event is a second-level, belongs to the same-level operation of the API operation requested by the book detail page interface, and belongs to a second operation event in the second-level, so that the value of the spanID of the current operation event is 0.1, the spanID of 0.1 represents that the level of the current operation event is the second-level, the position in the current operation event is 2, and the spanID of the upper-level of the current operation event is 0. The client generates an operation log corresponding to the current operation event, where the operation log is a second child node of the root node in the user behavior path, as shown in fig. 4.

4. On the detail page of the book, when a user wants to read the book after finishing reading the content of the detail page, the user continues to click the immediate reading button, and an operation event with an operation name of clicking the immediate reading operation click is triggered. Click immediate read operation click is an action type operation. Since the current operation event is the result of click operation on the book cover image, the value of traceID of the current operation event is also 123 abc. The current operation event is a second-level, belongs to the same-level operation of a detailspg operation displayed on the book detail page, and belongs to a third operation event in the second-level, so that the value of the spanID of the current operation event is 0.2, the spanID of 0.0 represents that the level of the current operation event is the second-level, the position in the current operation event is 3, and the spanID of the upper-level of the current operation event is 0. The client generates an operation log corresponding to the current operation event, where the operation log is a third child node of the root node in the user behavior path, as shown in fig. 4.

5. After clicking the immediate reading button, three operation events with operation names of a reader directory interface request operation API, a chapter information interface request operation API and a reader page display operation detailspg are sequentially triggered. These three operation events are all result type operations, and are all the results triggered by the operation event that is clicked and read immediately before, so their traceID values are all 123 abc. The three operation events are all three levels and belong to the first operation event, the second operation event and the third operation event in the three levels, so that the tedious values of the spanID are 0.2.0, 0.2.1 and 0.2.2 respectively. The span id of 0.2.0 characterizes the hierarchy level as three levels, the position in the hierarchy level is 1, and the span id of the upper level of the hierarchy level is 0.2. The span id of 0.2.1 characterizes the hierarchy level as three levels, the position in the hierarchy level is 2, and the span id of the upper level of the hierarchy level is 0.2. The span id of 0.2.2 characterizes the hierarchy level as three levels, the position in the hierarchy level is 3, and the span id of the upper level of the hierarchy level is 0.2. The client generates operation logs corresponding to the three operation events, and the operation logs are three child nodes of the click immediate reading operation in turn in the user behavior path, as shown in fig. 4.

6. When reading, the user can use the sliding operation to realize the page turning effect, so that an operation event called sliding page turning operation swipe is triggered. The slide page flip operation swipe is an action type operation. The current operation event is the result of clicking to read immediately the operation click, so the traceID value of the current operation event is also 123 abc. The current operation event is a third-level hierarchy and belongs to a fourth operation event in the third-level hierarchy, so that the value of the spanID of the current operation event is 0.2.3, the spanID is 0.2.3, the hierarchy of the current operation event is characterized as the third-level hierarchy, the position in the current hierarchy is 4, and the spanID of the upper-level hierarchy of the current hierarchy is 0.2. The client generates an operation log corresponding to the operation event, and the operation log is a fourth child node of the click to read immediately in the user behavior path, as shown in fig. 4.

7. When a user reads a book and turns pages to a new chapter, the new chapter request is triggered by sliding page turning, so that an operation event with the operation name of a chapter information interface request operation API is triggered, the chapter information interface request operation API is a result type operation and is a result triggered by the operation event of the previous sliding page turning, and therefore the traceID value of the operation event is also 123 abc. The current operation event is of a four-level hierarchy and belongs to the first operation event in the four-level hierarchy, so that the value of the spanID of the current operation event is 0.2.3.0, the spanID is 0.2.3.0, the hierarchy of the current operation event is represented as the four-level hierarchy, the position in the current operation event is 1, and the spanID of the upper level hierarchy of the current operation event is 0.2.3. The client generates an operation log corresponding to the operation event, where the operation log is a first child node of the slide page-turning operation swap in the user behavior path, as shown in fig. 4.

In the embodiment of the invention, the data of the operation logs are clearly and comprehensively classified before the operation logs are reported, the association attribute among the data is defined, the operation logs are reported to the server in time without omission, the server generates the user behavior path according to the operation logs, the operation logs are comprehensive and highly associated, the user behavior can be accurately analyzed, the real behavior path of the user is restored, and the user behavior path is indicated through the interactive tree structure.

Step 304, the server pushes the user behavior path to the terminal so as to display the user behavior path in the terminal.

After the server determines the user behavior path, the server pushes the user behavior path to the terminal, and the terminal can visually display the user behavior path.

Fig. 5 is a schematic interface diagram showing a user behavior path according to an embodiment of the present invention.

Fig. 5 shows the user's interaction behavior once in 9 months and 21 days, and starting APP once is a life cycle, with a plus sign indicating clickable deployment. Partial interception of the user behavior path after the 1 st lifecycle is expanded is shown in fig. 5, and the user behavior path includes two behaviors of startAction (start delivery) and clickAction (click on bottom tab-bookshelf), each behavior has a corresponding actionParams parameter, and the display can be expanded. After clicking plus sign and expanding, the clickAction can display next-level result behavior display, including detailspgResult (product page display delivery) and two apiResults (interface delivery).

By displaying the user behavior path in the tree structure diagram, the real logic relationship and the time relationship of the user behavior can be more clearly known. The user behavior path can be applied to monitoring user behaviors, assisting users in finding problems, intelligently recommending and the like.

Step 305, after receiving the information query request sent by the terminal, the server obtains a second target operation log corresponding to the information query request, and determines query result information corresponding to the information query request by using the second target operation log.

Step 306, the server pushes the query result information to the terminal so as to display the query result information in the terminal.

In an alternative embodiment, the information query request may be a core query request, and the query result information may be core behavior information.

When the core behavior information corresponding to a certain user is desired to be viewed, corresponding operation can be executed in the terminal to trigger the terminal to send a core query request to the server. For example, the user may input one or more of information such as a user ID to be queried, a time range, and the like in the terminal, thereby triggering a core query request carrying information input by the user.

And the server can acquire a second target operation log corresponding to the core query request according to the user input information carried in the core query request. The second target oplog includes a plurality of oplogs that satisfy the core query request.

Core behaviors can be included in the oplog, such as core behaviors can include APP open, chapter purchase, consumption, reading chapters, reading books, and so forth. The server may determine core behavior information corresponding to the core query request using the second target operation log. The core behavior information may include APP turn-on number, chapter purchase number, consumption number, reading chapter number, reading book number, and the like.

The server pushes the core behavior information to the terminal, and the terminal can visually display the core behavior information.

Fig. 6 is a schematic interface diagram showing user core behavior information according to an embodiment of the present invention. Fig. 6 shows the number of times APP is turned on, chapter purchases, consumption, reading chapters, and reading books with user ID 1169533258, and information of today, the last seven days, and the last thirty days can be shown. Of course, the information shown in fig. 6 can also be displayed through a curve trend chart, so as to obtain the behavior trend of the user.

By displaying the core behavior information of the user, the core behavior of the user in the set time can be visually checked, and the core behavior index is focused. The core behavior information of the user can be applied to intelligent recommendation, health degree measurement of APP products and the like.

In an alternative embodiment, the information query request may be an error query request, and the query result information may be error information.

When the error information is required to be checked, corresponding operation can be executed in the terminal so as to trigger the terminal to send an error query request to the server. For example, the user may input one or more of information such as a time range to be queried, an operating system version number, and the like in the terminal, so as to trigger an error query request carrying information input by the user.

And the server can acquire a third target operation log corresponding to the error query request according to the user input information carried in the error query request. The third target oplog includes a plurality of oplogs that satisfy the core query request.

The server may determine error information corresponding to the error query request using the third target oplog. When an error operation event occurs in the client, the operation log may carry error information. The error information may include In App Purchase payment (IAP In) payment issues, reader issues, network issues, Purchase issues, real name verification, kernel errors, reader blank pages, retry to failure, TTS errors, apikey acquisition failure, and so on.

The server pushes the error information to the terminal, and the terminal can visually display the error information.

Step 307, the server detects whether the operation log carries error information.

When the operation of the client has an error, the operation log generated by the client may also carry error information, such as an error name, an error time, and the like. When the server receives the operation log, the server can detect the operation log so as to determine whether the operation log carries error information.

And 308, when the operation log carries error information, the server counts the occurrence frequency of the error information within a set time, and generates alarm information when the occurrence frequency of the error information exceeds a set threshold value.

When the operation log carries error information, the server can also count the times of the error information occurring in the set time. For example, each time the same error information occurs, the number of times the error information occurs may be increased by 1.

The server judges whether the number of times of occurrence of the error information in the set time exceeds a set threshold value or not, and if so, alarm information is generated aiming at the error information. The alarm information may include error information, set time, number of occurrences, and the like.

The user can carry out alarm setting aiming at the concerned error information and subscribe the error information. FIG. 7 is an interface schematic of an alarm setting according to an embodiment of the invention. Fig. 7 shows alarm settings for the payment problem of the monthly IAP (In App Purchase, In-App payment), the reader problem, the network problem, the Purchase problem, the real-name verification, the kernel error, the reader blank page, the retry of failure, the TTS error, the failure of apikey acquisition, and other error information. Whether to alarm, whether to subscribe, add error information, delete error information, edit frequency (i.e., the above-described set time) and threshold (i.e., the above-described set threshold), and the like may be set.

And 309, the server pushes the alarm information to a user subscribing the error information.

And if the user subscribes to the error information, the server pushes the generated alarm information to the user subscribing to the error information. For example, the error message may be pushed to the user who subscribes to the error message by using a mail, a short message, or the like. The user who subscribes to the error information can be a user of multiple positions of development, test, product, operation and the like.

Through the error alarm mechanism, the occurrence frequency of certain type of error information in set time can be monitored, alarm information is sent out in time, and related personnel are informed to process in time.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

Referring to fig. 8, a block diagram of a user behavior processing apparatus according to an embodiment of the present invention is shown.

The user behavior processing device of the embodiment of the invention comprises: a first obtaining module 801, a log generating module 802, a second obtaining module 803, a selecting module 804 and a path generating module 805. The first obtaining module 801 and the log generating module 802 may be applied to a client, and the second obtaining module 803, the selecting module 804, and the path generating module 805 may be applied to a server.

The first obtaining module 801 is configured to obtain, after an operation event triggered by a user behavior is monitored, an operation name, an operation timestamp, an operation type, an operation cycle identifier, an operation tracking identifier, and an operation level identifier corresponding to the operation event. The operation cycle identification characterizes a life cycle to which the operation event belongs, the operation track identification characterizes an initial operation of the operation event track, and the operation level identification characterizes a level of a level to which the operation event belongs, an upper operation level identification of the level, and a position in the level.

A log generating module 802, configured to generate an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier, and the operation level identifier.

A second obtaining module 803, configured to obtain, after receiving a path query request sent by a terminal, a first target operation log corresponding to the path query request from the operation log;

a selecting module 804, configured to select an operation log with the same operation cycle identifier and operation tracking identifier from the first target operation log;

the path generating module 805 is configured to, according to the level identifier corresponding to the selected operation log, use the operation log whose level belongs to one level as a root node, determine a parent-child relationship and a sibling relationship according to the upper level identifier and a position in the level to which the operation log belongs, and determine a parent-child relationship and a sibling relationship according to the level identifier and the position in the level to which the operation log belongs.

Optionally, the first obtaining module 801 includes: the reading unit is used for reading an operation name, an operation timestamp and an operation cycle identifier corresponding to the operation event; the type determining unit is used for searching an operation type corresponding to the operation name from a preset mapping relation between the name and the type, and the operation type is used as an operation type corresponding to the operation event; and the identification determining unit is used for determining an operation tracking identification and an operation level identification corresponding to the operation event according to the operation name, the operation timestamp and the operation period identification.

Optionally, the operation type comprises a behavior operation and a result operation; the identification determination unit includes: the first identification determining subunit is configured to generate a unique operation tracking identification as an operation tracking identification corresponding to the operation event and a unique primary operation level identification as an operation level identification corresponding to the operation event when the operation name is a name characterizing a start operation or a name characterizing an initial operation after start; the second identification determining subunit is configured to, when the operation name is not a name representing a start operation and a name representing an initial operation after start, search, from a stored operation log, a first operation log in which an operation cycle identification is the same as an operation cycle identification corresponding to the operation event, an operation type is a behavior operation, and an operation timestamp is closest to the operation timestamp corresponding to the operation event; and acquiring an operation tracking identifier corresponding to the first operation log as an operation tracking identifier corresponding to the operation event, and generating a lower-level operation level identifier of the operation level identifier corresponding to the first operation log as an operation level identifier corresponding to the operation event.

Optionally, the second identity-determining subunit comprises: the log searching submodule is used for searching a second operation log which has the same operation cycle identifier as the operation cycle identifier corresponding to the operation event and the operation type of the second operation log is result operation, and the operation time stamp is positioned behind the operation time stamp corresponding to the first operation log and is closest to the operation time stamp corresponding to the operation event from the stored operation log; the identifier generation sub-module is configured to generate a first lower-level operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event when the second operation log is not found; and when the second operation log is found, generating lower operation level identifications which are arranged in an ascending order of the operation level identifications corresponding to the second operation log as the operation level identifications corresponding to the operation events.

Optionally, the apparatus further comprises: the third obtaining module is used for obtaining a second target operation log corresponding to the information query request after receiving the information query request sent by the terminal; the determining module is used for determining query result information corresponding to the information query request by using the second target operation log; and the second pushing module is used for pushing the query result information to a terminal so as to display the query result information in the terminal.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

In an embodiment of the invention, an electronic device for user behavior processing is also provided. For example, the electronic device may be provided as a client. The electronic device may include one or more processors and memory for storing processor-executable instructions, such as application programs. The processor is configured to execute a part of the client processing in the user behavior processing method.

In an embodiment of the invention, an electronic device for user behavior processing is also provided. For example, the electronic device may be provided as a server. The electronic device may include one or more processors and memory for storing processor-executable instructions, such as application programs. The processor is configured to execute a part of the server processing in the user behavior processing method.

In an embodiment of the present invention, there is also provided a non-transitory computer-readable storage medium, such as a memory, including instructions executable by a processor of an electronic device to perform the user behavior processing method shown above. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The user behavior processing method, the device electronic device and the storage medium provided by the present invention are introduced in detail, and a specific example is applied in the present document to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A user behavior processing method, characterized in that the method comprises:

after an operation event triggered by user behavior is monitored, acquiring an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to the operation event; the operational cycle identifying a lifecycle characterizing the operational event, the operational trace identifying an initial operation characterizing the operational event trace, the operational hierarchy identifying a level characterizing a hierarchy to which the operational event belongs, an upper level hierarchy identification of the hierarchy to which the operational event belongs, and a location in the hierarchy to which the operational event belongs;

generating an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier and the operation level identifier;

after receiving a path query request sent by a terminal, acquiring a first target operation log corresponding to the path query request from the operation log;

selecting an operation log with the same operation cycle identifier and operation tracking identifier from the first target operation log;

and according to the level identification corresponding to the selected operation log, taking the operation log with the level of the affiliated level as a root node, taking the operation log with the level of the affiliated level below one level, and determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the affiliated level to obtain the tree-shaped user behavior path.

2. The method of claim 1, wherein the obtaining of the operation name, the operation timestamp, the operation type, the operation cycle identifier, the operation tracking identifier, and the operation level identifier corresponding to the operation event comprises:

reading an operation name, an operation timestamp and an operation period identifier corresponding to the operation event;

searching an operation type corresponding to the operation name from a preset mapping relation between the name and the type, and taking the operation type as an operation type corresponding to the operation event;

and determining an operation tracking identifier and an operation level identifier corresponding to the operation event according to the operation name, the operation timestamp and the operation period identifier.

3. The method of claim 2, wherein the operation types include behavior operations and result operations; determining an operation tracking identifier and an operation level identifier corresponding to the operation event according to the operation name, the operation timestamp and the operation period identifier, including:

when the operation name is a name representing a starting operation or a name representing an initial operation after starting, generating a unique operation tracking identifier as an operation tracking identifier corresponding to the operation event, and generating a unique primary operation level identifier as an operation level identifier corresponding to the operation event;

when the operation name is not the name for representing the starting operation and the name for representing the initial operation after the starting, searching a first operation log from the stored operation logs; the operation cycle identifier of the first operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is behavior operation, and the operation timestamp is closest to the operation timestamp corresponding to the operation event;

and acquiring an operation tracking identifier corresponding to the first operation log as an operation tracking identifier corresponding to the operation event, and generating a lower-level operation level identifier of the operation level identifier corresponding to the first operation log as an operation level identifier corresponding to the operation event.

4. The method according to claim 3, wherein the generating, as the operation level identifier corresponding to the operation event, an operation level identifier lower than the operation level identifier corresponding to the first operation log comprises:

searching a second operation log from the stored operation logs; the operation cycle identifier of the second operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is result operation, the operation timestamp is positioned behind the operation timestamp corresponding to the first operation log, and the operation timestamp is closest to the operation timestamp corresponding to the operation event;

when the second operation log is not found, generating a first lower-level operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event;

and when the second operation log is found, generating lower operation level identifications which are arranged in an ascending order of the operation level identifications corresponding to the second operation log as the operation level identifications corresponding to the operation events.

5. The method of claim 1, further comprising:

and pushing the user behavior path to the terminal so as to display the user behavior path in the terminal.

6. The method of claim 1, further comprising:

after receiving an information query request sent by the terminal, acquiring a second target operation log corresponding to the information query request from the operation log;

determining query result information corresponding to the information query request by using the second target operation log;

and pushing the query result information to the terminal so as to display the query result information in the terminal.

7. The method of claim 1, further comprising:

detecting whether the operation log carries error information or not;

when the operation log carries error information, counting the occurrence frequency of the error information within a set time;

when the occurrence frequency of the error information exceeds a set threshold value, generating alarm information;

and pushing the alarm information to a user subscribing the error information.

8. A user behavior processing apparatus, characterized in that the apparatus comprises:

the first acquisition module is used for acquiring an operation name, an operation timestamp, an operation type, an operation period identifier, an operation tracking identifier and an operation level identifier corresponding to an operation event after the operation event triggered by a user behavior is monitored; the operation cycle identification characterizes a life cycle to which the operation event belongs, the operation track identification characterizes an initial operation of the operation event track, and the operation hierarchy identification characterizes a level of a hierarchy to which the operation event belongs, an upper operation hierarchy identification of the hierarchy to which the operation event belongs, and a position in the hierarchy to which the operation event belongs;

a log generating module, configured to generate an operation log carrying the operation name, the operation timestamp, the operation type, the operation period identifier, the operation tracking identifier, and the operation level identifier;

the second acquisition module is used for acquiring a first target operation log corresponding to a path query request from the operation log after receiving the path query request sent by a terminal;

the selection module is used for selecting the operation logs with the same operation cycle identification and operation tracking identification from the first target operation logs;

and the path generation module is used for determining a parent-child relationship and a brother relationship according to the upper level identification and the position in the selected operation log to obtain the tree-shaped user behavior path by taking the operation log with the level of the selected operation log as a root node and the operation log with the level of the selected operation log below one level as a root node.

9. The apparatus of claim 8, wherein the first obtaining module comprises:

the reading unit is used for reading an operation name, an operation timestamp and an operation cycle identifier corresponding to the operation event;

the type determining unit is used for searching an operation type corresponding to the operation name from a preset mapping relation between the name and the type, and the operation type is used as an operation type corresponding to the operation event;

and the identification determining unit is used for determining an operation tracking identification and an operation level identification corresponding to the operation event according to the operation name, the operation timestamp and the operation period identification.

10. The apparatus of claim 9, wherein the operation types comprise behavior operations and result operations; the identification determination unit includes:

the first identification determining subunit is configured to generate a unique operation tracking identification as an operation tracking identification corresponding to the operation event and a unique primary operation level identification as an operation level identification corresponding to the operation event when the operation name is a name characterizing a start operation or a name characterizing an initial operation after start;

the second identification determining subunit is used for searching the first operation log from the stored operation logs when the operation name is not the name for representing the starting operation and the name for representing the initial operation after the starting; the operation cycle identifier of the first operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is behavior operation, and the operation timestamp is closest to the operation timestamp corresponding to the operation event; and acquiring an operation tracking identifier corresponding to the first operation log as an operation tracking identifier corresponding to the operation event, and generating a lower-level operation level identifier of the operation level identifier corresponding to the first operation log as an operation level identifier corresponding to the operation event.

11. The apparatus of claim 10, wherein the second identity determination subunit comprises:

the log searching submodule is used for searching a second operation log from the stored operation logs; the operation cycle identifier of the second operation log is the same as the operation cycle identifier corresponding to the operation event, the operation type is result operation, the operation timestamp is positioned behind the operation timestamp corresponding to the first operation log, and the operation timestamp is closest to the operation timestamp corresponding to the operation event;

the identifier generation sub-module is configured to generate a first lower-level operation level identifier of the operation level identifier corresponding to the first operation log as the operation level identifier corresponding to the operation event when the second operation log is not found; and when the second operation log is found, generating lower operation level identifications which are arranged in an ascending order of the operation level identifications corresponding to the second operation log as the operation level identifications corresponding to the operation events.

12. The apparatus of claim 8, further comprising:

the first pushing module is used for pushing the user behavior path to the terminal so as to display the user behavior path in the terminal.

13. The apparatus of claim 8, further comprising:

the third obtaining module is used for obtaining a second target operation log corresponding to the information query request from the operation logs after receiving the information query request sent by the terminal;

the determining module is used for determining query result information corresponding to the information query request by using the second target operation log;

and the second pushing module is used for pushing the query result information to the terminal so as to facilitate the query result information in the terminal.

14. The apparatus of claim 8, further comprising:

the detection module is used for detecting whether the operation log carries error information or not;

the counting module is used for counting the occurrence frequency of the error information when the error information is carried in the operation log;

the alarm generation module is used for generating alarm information when the occurrence frequency of the error information exceeds a set threshold value;

and the third pushing module is used for pushing the alarm information to a user subscribing the error information.

15. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to perform the user behavior processing method of any of claims 1-7.

16. A non-transitory computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the user behavior processing method of any of claims 1-7.