CN109587197B

CN109587197B - Method, device and system for associating reported data

Info

Publication number: CN109587197B
Application number: CN201710909032.7A
Authority: CN
Inventors: 吴凯; 王海旭
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Priority date: 2017-09-29
Filing date: 2017-09-29
Publication date: 2022-02-22
Anticipated expiration: 2037-09-29
Also published as: CN109587197A

Abstract

The invention discloses a method, a device and a system for associating reported data, and relates to the technical field of computers. One embodiment of the method comprises: receiving reporting requests sent by various clients; the reporting request carries reporting data and an associated identifier, wherein the associated identifier is pre-stored by any one of the plurality of clients; and associating the reported data by using the association identifier. The implementation method can pre-store the association identifier at various clients, and realize accurate association of the reported data of the same user by using the association identifier.

Description

Method, device and system for associating reported data

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, and a system for associating reported data.

Background

With the rapid development of smart terminals such as mobile phones and tablet computers, a large amount of user behavior data is gradually transferred from a Personal Computer (PC) terminal to a mobile terminal accessing the internet through a wireless network technology. At the mobile terminal, if a certain website is provided with both a browser-based page and an APP application, the user may browse through the page, may browse through the APP, and may also call up the APP in the page to browse. Because the mechanism of collecting user behavior data of the page and the APP is different, and the data collected by the page and the APP are also stored independently, in practical application, the user behavior data are analyzed and associated accurately with certain difficulty.

In specific application, for a logged-in user, the page and the data acquired by the APP can be associated through the user identifier of the logged-in user. For a user who does not log in, the prior art determines whether user behavior data corresponds to the same user through an Internet Protocol (IP) address, geographical location information, and access time carried in the user behavior data, thereby implementing association.

In the process of implementing the invention, the inventor finds that the prior art has at least the following problems:

1. during browsing, if the network type of the user is switched, for example, from a Wi-Fi (Wi-Fi is a technology that allows the electronic device to connect to a wireless local area network) network to a mobile 3G network, the IP address changes, so that the association of the user behavior data cannot be realized.

2. In the browsing process of the user who does not log in, if the reporting of the geographic position information is forbidden, the correlation of the user behavior data can not be realized.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, and a system for associating reported data, which can store association identifiers in advance at multiple clients, and implement accurate association of the reported data of the same user by using the association identifiers.

To achieve the above object, according to an aspect of the present invention, a method for associating reported data is provided.

The method for associating the reported data comprises the following steps: receiving reporting requests sent by various clients; the reporting request carries reporting data and an associated identifier, wherein the associated identifier is pre-stored by any one of the plurality of clients; and associating the reported data by using the association identifier.

Optionally, the plurality of clients includes: a first client and a second client both in an unregistered state.

Optionally, the association identifier is stored at the first client and the second client according to the following steps: after the first client sends an access request and receives a response aiming at the access request, establishing an association identifier and storing the association identifier; the first client sends a call request carrying the associated identifier to the second client; and the second client receives the call request and stores the associated identifier carried in the call request.

Optionally, the association identification is established based on a timestamp included in the response.

Optionally, the sending, by the first client, the call initiation request carrying the association identifier to the second client includes: and after monitoring a trigger event comprising the link identifier of the second client, the first client sends the call request to the second client.

Optionally, the report request sent by the first client further carries: the reporting sequence number currently stored by the first client; the report request sent by the second client further carries: the reporting sequence number currently stored by the second client; and the associating the reported data by using the association identifier comprises: and associating the reported data carried in the reporting requests sent by the first client and the second client by using the association identifier and the reporting sequence number carried in the reporting requests.

Optionally, the reporting sequence number is stored in the first client and the second client according to the following steps: when establishing the association identifier, the first client establishes and stores an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to the currently stored reporting serial number, and removing the currently stored reporting serial number; the first client sends the call request to the second client; the call request carries a reporting serial number currently stored by a first client; the second client receives the call request and stores the reporting sequence number carried in the call request; when sending the report request, generating and storing a new report serial number according to the currently stored report serial number, and removing the currently stored report serial number.

Optionally, the generating a new reporting sequence number according to the currently stored reporting sequence number includes: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

Optionally, the reporting data carried in the reporting requests sent by the first client and the second client includes user behavior log data; and the associating the report data carried in the report requests sent by the first client and the second client by using the association identifier and the report sequence number carried in the report request comprises: determining the reported data corresponding to the same associated identifier in the reported data as the reported data of the same user; and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

Optionally, the first client is a browser end, the second client is an APP application, and the link identifier is a uniform resource locator plan URL Scheme; the first client stores the association identifier and the reporting serial number in a local storage localStorage; or the first client is an APP, the second client is a browser, and the link identifier is a Uniform Resource Locator (URL); the second client stores the association identifier and the reporting serial number in a local storage localStorage; or both the first client and the second client are APP applications, and the link identifier is a uniform resource locator plan URL Scheme.

To achieve the above object, according to another aspect of the present invention, an apparatus for associating report data is provided.

The device for associating the reported data of the embodiment of the invention can comprise: the receiving module can be used for receiving the reporting requests sent by various clients; the reporting request carries reporting data and an associated identifier, wherein the associated identifier is pre-stored by any one of the plurality of clients; and the association module can be used for associating the reported data by utilizing the association identifier.

Optionally, the association identifier is stored at the first client and the second client according to the following steps: after the first client sends an access request and receives a response aiming at the access request, establishing an association identifier and storing the association identifier; after monitoring a trigger event comprising a link identifier of a second client, a first client sends a call-up request carrying the association identifier to the second client; and the second client receives the call request and stores the associated identifier carried in the call request.

Optionally, the report request sent by the first client further carries: the reporting sequence number currently stored by the first client; the report request sent by the second client further carries: the reporting sequence number currently stored by the second client; and the association module may be further operable to: and associating the reported data carried in the reporting requests sent by the first client and the second client by using the association identifier and the reporting sequence number carried in the reporting requests.

Optionally, the reporting sequence number is stored in the first client and the second client according to the following steps: when establishing the association identifier, the first client establishes and stores an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to a currently stored reporting serial number and a preset rule, and removing the currently stored reporting serial number; the first client sends the call request to the second client; the call request carries a reporting serial number currently stored by a first client; the second client receives the call request and stores the reporting sequence number carried in the call request; when a report request is sent, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

Optionally, the preset rule includes: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

Optionally, the reporting data carried in the reporting requests sent by the first client and the second client includes user behavior log data; and the association module may be further operable to: determining the reported data corresponding to the same associated identifier in the reported data as the reported data of the same user; and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

To achieve the above object, according to another aspect of the present invention, a terminal for associating reporting data is provided.

The terminal of the embodiment of the invention comprises a plurality of clients; the various clients can be used for sending reporting requests carrying reporting data and associated identifiers; the association identifier is pre-stored by any one of the plurality of clients and is used for associating the reported data.

Optionally, the first client may be further configured to: after sending an access request and receiving a response to the access request, establishing and storing an association identifier; sending a call starting request carrying the associated identifier to a second client; the second client may be further operable to: and receiving the call request, and storing the associated identifier carried in the call request.

Optionally, the first client may be further configured to: and after a trigger event comprising the link identifier of the second client is monitored, sending the call-starting request to the second client.

Optionally, the report request sent by the first client may further carry: the reporting sequence number currently stored by the first client; the report request sent by the second client may further carry: the reporting sequence number currently stored by the second client; and the reporting sequence numbers carried in the reporting requests sent by the first client and the second client can be used for: and associating the reported data carried in the reporting requests sent by the first client and the second client.

Optionally, the first client may be further configured to: when the association identifier is established, establishing and storing an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to a currently stored reporting serial number and a preset rule, and removing the currently stored reporting serial number; sending the call initiation request to a second client; the call request carries a reporting serial number currently stored by a first client; the second client may be further operable to: receiving the call request, and storing a reporting sequence number carried in the call request; when a report request is sent, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

Optionally, the preset rule may include: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

Optionally, the reporting data carried in the reporting requests sent by the first client and the second client may include user behavior log data; the association identifiers carried in the reporting requests sent by the first client and the second client may be further configured to: determining the reported data of the same user in the reported data; and the reporting sequence numbers carried in the reporting requests sent by the first client and the second client can be further used for: and sequencing the reported data of the same user to correlate the user behaviors.

To achieve the above object, according to still another aspect of the present invention, a system for associating report data is provided.

The system for associating the reported data of the embodiment of the invention can comprise: a server and various clients; the multiple clients can be used for sending reporting requests carrying reporting data and associated identifiers to the server, wherein the associated identifiers are pre-stored by any one of the multiple clients; the server can be used for receiving the report request and associating the report data by using the association identifier.

Optionally, the first client may be further configured to: after an access request is sent to a server and a response of the server to the access request is received, establishing and storing an association identifier; sending a call starting request carrying the associated identifier to a second client; the second client may be further operable to: and receiving the call request, and storing the associated identifier carried in the call request.

Optionally, the report request sent by the first client may further carry: the reporting sequence number currently stored by the first client; the report request sent by the second client may further carry: the reporting sequence number currently stored by the second client; and the server may be further configured to: and associating the reported data carried in the reporting requests sent by the first client and the second client by using the association identifier and the reporting sequence number carried in the reporting requests.

Optionally, the first client may be further configured to: when the association identifier is established, establishing and storing an initial reporting serial number; when a report request is sent to a server, generating and storing a new report serial number according to a currently stored report serial number and a preset rule, and removing the currently stored report serial number; sending the call initiation request to a second client; the call request carries a reporting serial number currently stored by a first client; the second client may be further operable to: receiving the call request, and storing a reporting sequence number carried in the call request; when a report request is sent to a server, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

Optionally, the reporting data carried in the reporting requests sent by the first client and the second client includes user behavior log data; and the server may be further configured to: determining the reported data corresponding to the same associated identifier in the reported data as the reported data of the same user; and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

To achieve the above object, according to still another aspect of the present invention, an electronic apparatus is provided.

An electronic device of the present invention includes: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the method for associating the reported data provided by the invention.

To achieve the above object, according to still another aspect of the present invention, there is provided a computer-readable storage medium.

The invention relates to a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the method for associating reporting data according to the invention.

According to the technical scheme of the invention, one embodiment of the invention has the following advantages or beneficial effects: the association identifier is pre-stored in the first client and the second client which are not logged in, and is carried in the report request, so that the report data of the same user from the first client to the second client can be accurately associated by using the association identifier, the processing of the report data in the prior art is avoided, and the defects that the association effect of the report data in the prior art is easily influenced by factors such as network type switching, geographic position information forbidding and the like are overcome; the reporting sequence numbers are stored in advance in the first client and the second client which are not logged in, and are carried in the reporting request, so that the reporting data can be further sequenced by using the reporting sequence numbers, and the subsequent user behavior analysis is facilitated; the method comprises the steps that a triggering event of a second client is called by a first client, and an association identifier and a reporting serial number stored by the first client are carried in a calling request and sent to the second client, so that the second client can synchronously store the association identifier and the reporting serial number, and complete association of reported data is facilitated; in addition, the present invention can be applied to various environments associated with reporting data, such as: from a browser side to an APP application, from an APP application to a browser side, from one APP to another APP application.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram illustrating main steps of a method for associating reported data according to an embodiment of the present invention;

fig. 2 is a schematic main flowchart of a method for associating reported data according to a first embodiment of the present invention;

fig. 3 is a schematic diagram of a main portion of an apparatus for associating report data according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a main portion of a system for associating report data according to an embodiment of the present invention;

FIG. 5 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 6 is a schematic structural diagram of an electronic device for implementing the method for associating reported data according to the embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

According to the technical scheme of the embodiment of the invention, the association identifier is pre-stored in the first client and the second client which are not logged in, and the association identifier is carried in the report request, so that the report data of the same user from the first client to the second client can be accurately associated by using the association identifier, the processing of the report data in the prior art is avoided, and the defects that the association effect of the report data in the prior art is easily influenced by factors such as network type switching, geographic position information forbidding and the like are overcome; the reporting sequence numbers are stored in advance in the first client and the second client which are not logged in, and are carried in the reporting request, so that the reporting data can be further sequenced by using the reporting sequence numbers, and the subsequent user behavior analysis is facilitated; the method comprises the steps that a triggering event of a second client is called by a first client, and an association identifier and a reporting serial number stored by the first client are carried in a calling request and sent to the second client, so that the second client can synchronously store the association identifier and the reporting serial number, and complete association of reported data is facilitated; in addition, the present invention can be applied to various environments associated with reporting data, such as: from a browser side to an APP application, from an APP application to a browser side, from one APP to another APP application.

It should be noted that the embodiments of the present invention and the technical features of the embodiments may be combined with each other without conflict.

Fig. 1 is a schematic diagram illustrating main steps of a method for associating reported data according to an embodiment of the present invention.

As shown in fig. 1, the method for associating reported data according to the embodiment of the present invention may be performed according to the following steps:

step S101: the server receives reporting requests sent by various clients.

In this step, the client may be a physical device such as a computer, a mobile phone, or any other computer program. In particular, the multiple clients are multiple computer programs corresponding to the same server. In practical applications, the plurality of clients may include a first client and a second client corresponding to the same server. For example: for XXX service: the first client is a mobile terminal webpage corresponding to XXX, and the second client is a mobile terminal APP application corresponding to XXX; or the first client is a mobile terminal APP corresponding to XXX, and the second client is another mobile terminal APP corresponding to XXX.

In particular, in the embodiment of the present invention, both the first client and the second client are in the unregistered state, that is, the current users of the first client and the second client are unregistered users.

In a specific application, the first client and the second client may be any one of the following situations:

1. the first client is a browser end arranged on equipment such as a mobile phone, and the second client is an APP application arranged on the equipment such as the mobile phone. The browser end refers to a page based on a browser, and the APP refers to an application program installed and running on an intelligent terminal such as a mobile phone and a tablet computer.

2. The first client is an APP, and the second client is a browser.

3. The first client is an APP, and the second client is another APP.

It is to be understood that the terms "first", "second", and the like, used in the embodiments of the present invention, are used herein to describe various objects, but the objects are not limited by the above terms. The above terms are used only to distinguish one object from another. For example, without departing from the technical solution of the present invention, the first client may be referred to as a second client, or the second client may be referred to as a first client, where the first client and the second client are both clients, but they are not the same client.

In this step, the reporting request refers to a request sent by the first client and the second client when reporting data to the server. The report request may carry report data and an association identifier pre-stored by the first client or the second client. The reported data may include user behavior log data, such as user browsing log data and user clicking log data. It can be understood that the user behavior log can be collected at the browser end by means of JavaScript (JavaScript is a programming language widely used for the client), script, and the like, and collected at the APP application by means of SDK (Software Development Kit, and the like).

In particular, in the embodiment of the present invention, the association identifier is established for associating the reported data. Specifically, the first client and the second client may establish and store the association identifier by the following steps:

1. the first client sends an access request to the server, and establishes and stores the association identifier after receiving a response of the server to the access request.

In practical application, the access request may be a first web page access request sent to the server after the first client is started. In the embodiment of the present invention, if the first client is a browser, after receiving a response returned by the server, the first client may establish an association identifier according to a JavaScript script previously sent by the server, and store the association identifier in a local storage localStorage (localStorage is a browser storage mechanism) in a domain corresponding to the server. In a specific application, the association identifier may be a character string obtained according to a preset association identifier generation rule.

For example: and obtaining 13-bit timestamp digits in milliseconds according to the timestamps included in the responses, and adding random numbers of 8 to 12 bits after the 13-bit timestamp digits to obtain the associated identification.

It can be understood that, after the first client stores the association identifier, each time a report request is sent to the server, the report request carries the association identifier, and the server can associate the report data accordingly.

2. And the first client sends a call-starting request carrying the associated identifier to the second client.

In a specific application, after monitoring a trigger event including a link identifier of a second client, a first client adds an association identifier to a call request and sends the call request to the second client.

The trigger event refers to an event capable of triggering a behavior in a browser page or an APP application page, for example, a click event of a browser in a PC, a double click event, a touch event in an intelligent terminal, and the like. The link identifiers are used to indicate address information in the network, on the basis of which the corresponding computer programs can be located. For an APP application, its link identification is the uniform resource locator plan URL Scheme of the APP application. It is understood that the URL Scheme is data bound with the target application for launching the target application from a browser or an application. For a web page on a browser side, the link is identified as the URL of the web page. It is understood that when a certain link identifier is included in the trigger event, it indicates that the trigger event points to the address indicated by the link identifier.

In the embodiment of the present invention, the origination request refers to a request for triggering the start of an application program. In practical applications, the call request may be sent from the browser to the APP, from the APP to the browser, or from one APP to another APP.

3. And the second client receives the call request and stores the associated identifier carried in the call request.

Preferably, the second client is started after receiving the call-initiating request, and parses the call-initiating request, and obtains and stores the association identifier therefrom. If the second client is a browser end, it stores the association identifier in localStorage. It can be understood that, after storing the association identifier, the reporting request sent by the second client to the server each time includes the association identifier, and the server can associate the reported data based on the association identifier.

In practical applications, after the first client sends the call initiation request, if the second client is not installed, the first client may present a download page of the second client to the user.

It will be appreciated that in particular applications, the first client and the second client, which store the same association identifier in the manner described above, are typically installed to run on the same physical device. For example: the same association identifier can be stored in the above manner by the browser end and the APP application installed in one mobile phone.

In practical application, on the basis of realizing the association of the reported data through the association identifier, the reported serial number can be established to perform more refined association on the reported data.

Specifically, the reporting sequence number is established, stored and updated through the following steps, and is used for association of the reported data:

1. and when the first client establishes the association identifier, establishing and storing an initial reporting serial number.

Preferably, the initial reporting sequence number may be a number. If the first client is a browser, the first client stores the initial reporting sequence number and the subsequently updated reporting sequence number in localStorage.

2. When sending a reporting request to a server, a first client generates and stores a new reporting serial number according to a currently stored reporting serial number, and removes the currently stored reporting serial number.

It can be understood that the report request sent by the first client carries the report sequence number currently stored by the first client. In practical application, the first client may add the currently stored reporting sequence number to a preset value to generate a new reporting sequence number. The preset value is generally a positive number.

For example: the initial reporting serial number established by the first client is 1, when a reporting request is sent to the server for the first time later, the reporting serial number carried in the reporting request is the currently stored reporting serial number 1, meanwhile, the first client generates a new reporting serial number 2 according to the currently stored reporting serial number 1 and a preset rule, and removes the currently stored reporting serial number 1; and then, when the first client sends a reporting request to the server for the second time, the reporting sequence number carried in the reporting request is 2, and meanwhile, the first client generates a new reporting sequence number 3 according to the currently stored reporting sequence number 2 and a preset rule, and removes the currently stored reporting sequence number 2.

3. The first client sends a call-up request carrying the reporting sequence number currently stored by the first client to the second client.

Specifically, after monitoring a trigger event including a link identifier of the second client, the first client adds the currently stored reporting sequence number to the call request and sends the call request to the second client. Meanwhile, the first client can remove the stored reporting serial number so as to associate the reporting data of the next period.

4. And the second client receives and analyzes the call request and stores the reporting sequence number carried by the call request.

It can be understood that, if the second client is a browser, it stores the reporting sequence number and the reporting sequence number of the subsequent update in localStorage.

Through the step, the reporting sequence number currently stored by the first client can be synchronized to the second client, and the updating is continuously carried out on the second client, so that the server can realize the accurate series connection of the reported data of the first client and the second client based on the reporting sequence number.

5. And when the second client sends a reporting request to the server, generating and storing a new reporting serial number according to the currently stored reporting serial number, and removing the currently stored reporting serial number.

It can be understood that the report request sent by the second client to the server carries the report sequence number currently stored by the second client. In practical application, the second client may add the currently stored reporting sequence number to a preset value to generate a new reporting sequence number. In addition, when the second client is closed, the stored reporting sequence number can be cleared, so that the reported data in the next period can be associated.

Through the setting, each piece of reported data received by the server side comprises the association identifier and the reported sequence number, so that the reported data association based on the association identifier and the reported sequence number can be realized.

Step S102: and the server associates the reported data by using the association identifier.

In this step, the association refers to a process of extracting partial data having a high correlation among a large amount of data. In an embodiment of the present invention, the association may be: determining the reported data of the same user in a large amount of reported data, and judging the processing process of the user behavior by analyzing the reported data of the same user. In particular, in this step, the association may be performed only for the reported data of the first client, only for the reported data of the second client, and also for the reported data of the first client and the second client.

In the embodiment of the present invention, the server may determine the reported data corresponding to the same association identifier as the reported data of the same user. In an optional implementation manner, the server may also sort the reported data of the same user according to the reporting sequence number, so as to implement more refined reported data association.

In practical applications, if the first client and the second client add the currently stored reporting sequence number to the preset value greater than zero to generate a new reporting sequence number, the reporting sequence number corresponding to the reported data may reflect the time sequence of the reported data. The server can sort the reported data of the same user in the sequence from small to large according to the reported sequence number, so as to serially connect the sequence behaviors of the users.

In addition, as a preferred scheme, after the first client and the second client store the association identifier, if the user who does not log in browses the page at the first client or the second client alone, the server may associate the current reported data with the previous reported data.

It can be understood that, based on a similar principle, the method for associating reported data according to the embodiment of the present invention may be used for associating reported data of more than two clients corresponding to the same server; for the first client and the second client, the reported data association can be carried out on the condition that one or both of the first client and the second client are in a login state.

Fig. 2 is a schematic main flowchart of a method for associating reported data according to a first embodiment of the present invention.

In this embodiment, the first client and the second client are a browser end and an APP application corresponding to the same service end, respectively.

As shown in fig. 2, the method for associating reported data in this embodiment is specifically executed according to the following steps:

step S201: the user who is not logged on starts browsing the page at the browser end.

Step S202: the browser side sends an access request to the server side for the first time, and after a response returned by the server side is received, a corresponding 13-bit timestamp, such as '1506000686000', is obtained according to the timestamp included in the response, and then an 8-bit random number is added to establish an association identifier '150600068600085625632'. Meanwhile, an initial reporting serial number '1' is established, and the initial reporting serial number are stored in a localStorage at a browser end.

Step S203: and each time the browser sends a reporting request to the server, the stored reporting sequence number is increased by 1. Meanwhile, each report request carries the associated identifier and the currently stored report sequence number.

Step S204: when a user starts an APP in the same device at a browser end, the browser end monitors a touch event including a URL Scheme of the APP.

Step S205: the browser end adds the association identifier '150600068600085625632' and the currently stored reporting sequence number to the call-starting request, and sends the call-starting request to the APP.

Step S206: the APP application is started after receiving the call request, analyzes the call request to obtain the associated identification and the report sequence number carried in the call request, and stores the associated identification and the report sequence number.

Step S207: the APP sends a report request to the server every time, and the stored report sequence number is increased by 1. Meanwhile, each report request carries the associated identifier and the report sequence number currently stored by the APP application.

Step S208: the server associates the browser with the reported data of the APP: and determining the reported data with the association identifier of '150600068600085625632' as the reported data of the same user, and sequencing the reported data in the order with the sequence numbers of 1, 2 and 3 …, thereby realizing accurate association of the behavior data of the user.

The main process of the method for associating reported data according to the second embodiment of the present invention is described below.

In this embodiment, the first client and the second client are an APP application and a browser corresponding to the same server, respectively.

Specifically, the method for associating reported data according to this embodiment is executed according to the following steps:

1: the unregistered user starts browsing the page at the APP.

2: the APP sends an access request to the server for the first time, and after a response returned by the server is received, a corresponding 13-bit timestamp, for example, "1506000686000", is obtained according to the timestamp included in the response, and then an 8-bit random number is added to establish an association identifier "150600068600085625632". Meanwhile, an initial reporting serial number '1' is established, and the initial reporting serial number '1' are stored.

3: the APP sends a report request to the server every time, and the stored report sequence number is increased by 1. Meanwhile, each report request carries the associated identifier and the currently stored report sequence number.

4: when a user starts a browser end in the same device, the APP monitors a touch event including a URL of the browser end.

5: the APP adds the association identifier '150600068600085625632' and the currently stored reporting sequence number to the call request, and sends the call request to the browser.

6: and the browser end is started after receiving the call-up request, analyzes the call-up request to acquire the associated identification and the reported serial number carried in the call-up request, and stores the associated identification and the reported serial number.

7: and each time the browser sends a reporting request to the server, the stored reporting sequence number is increased by 1. Meanwhile, each report request carries the associated identifier and the report sequence number currently stored by the APP application.

8: the server associates the browser with the reported data of the APP: and determining the reported data with the association identifier of '150600068600085625632' as the reported data of the same user, and sequencing the reported data in the order with the sequence numbers of 1, 2 and 3 …, thereby realizing accurate association of the behavior data of the user.

The main process of the method for associating reported data according to the third embodiment of the present invention is described below.

In this embodiment, the first client and the second client are two APP applications corresponding to the same server, respectively: a first APP application and a second APP application.

1: the unregistered user starts browsing the page at the first APP application.

2: the first APP application sends an access request to the server for the first time, and after a response returned by the server is received, a corresponding 13-bit timestamp, such as "1506000686000", is obtained according to the timestamp included in the response, and then an 8-bit random number is added to establish an association identifier "150600068600085625632". Meanwhile, an initial reporting serial number '1' is established, and the initial reporting serial number '1' are stored.

3: and the first APP application sends a reporting request to the server every time, and the stored reporting sequence number is increased by 1. Meanwhile, each report request carries the associated identifier and the currently stored report sequence number.

4: when a user starts a second APP of the same device at a first APP, the first APP monitors a touch event including a URL Scheme of the second APP.

5: the first APP application adds the association identifier '150600068600085625632' and the currently stored reporting sequence number to the call-starting request, and sends the call-starting request to the second APP application.

6: and the second APP application is started after receiving the call request, analyzes the call request, acquires the associated identifier and the report sequence number carried in the call request and stores the associated identifier and the report sequence number.

7: and the second APP application sends a reporting request to the server every time, and the stored reporting sequence number is increased by 1. Meanwhile, each report request carries the association identifier and a report sequence number currently stored by the second APP application.

8: the server associates the reported data of the first APP application and the second APP application of different users: and determining the reported data with the association identifier of '150600068600085625632' as the reported data of the same user, and sequencing the reported data in the order with the sequence numbers of 1, 2 and 3 …, thereby realizing accurate association of the behavior data of the user.

In the technical scheme of the embodiment of the invention, the association identifier is pre-stored in the first client and the second client which are not logged in, and the association identifier is carried in the report request, so that the report data of the same user from the first client to the second client can be accurately associated by using the association identifier, the processing of the report data in the prior art is avoided, and the defect that the association effect of the report data in the prior art is easily influenced by factors such as network type switching, geographic position information forbidding and the like is overcome; the reporting sequence numbers are stored in advance in the first client and the second client which are not logged in, and are carried in the reporting request, so that the reporting data can be further sequenced by using the reporting sequence numbers, and the subsequent user behavior analysis is facilitated; the method comprises the steps that a triggering event of a second client is called by a first client, and an association identifier and a reporting serial number stored by the first client are carried in a calling request and sent to the second client, so that the second client can synchronously store the association identifier and the reporting serial number, and complete association of reported data is facilitated; in addition, the present invention can be applied to various environments associated with reporting data, such as: from a browser side to an APP application, from an APP application to a browser side, from one APP to another APP application.

Fig. 3 is a schematic diagram of a main portion of an apparatus for associating report data according to an embodiment of the present invention.

As shown in fig. 3, an apparatus 300 for associating reporting data according to an embodiment of the present invention may include: a receiving module 301 and an associating module 302. Wherein:

the receiving module 301 may be configured to receive reporting requests sent by various clients; the reporting request carries reporting data and an associated identifier, wherein the associated identifier is pre-stored by any one of the plurality of clients;

the association module 302 may be configured to associate the reported data with the association identifier.

Preferably, the plurality of clients may include: a first client and a second client both in an unregistered state.

In an embodiment of the present invention, the association identifier is stored at the first client and the second client according to the following steps: after the first client sends an access request and receives a response aiming at the access request, establishing an association identifier and storing the association identifier; after monitoring a trigger event comprising a link identifier of a second client, a first client sends a call-up request carrying the association identifier to the second client; and the second client receives the call request and stores the associated identifier carried in the call request.

Preferably, the association identification is established based on a timestamp included in the response.

In an optional implementation manner, the report request sent by the first client may further carry: the reporting sequence number currently stored by the first client; the report request sent by the second client may further carry: and the reporting sequence number currently stored by the second client. Accordingly, the association module 302 may be further configured to: and associating the reported data by using the association identifier and the reporting sequence number carried in the reporting request.

In the embodiment of the present invention, the reporting sequence number may be stored in the first client and the second client according to the following steps: when establishing the association identifier, the first client establishes and stores an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to a currently stored reporting serial number and a preset rule, and removing the currently stored reporting serial number; the first client sends the call request to the second client; the call request carries a reporting serial number currently stored by a first client; the second client receives the call request and stores the reporting sequence number carried in the call request; when a report request is sent, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

As a preferred scheme, the preset rule may include: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

In a specific application, the reported data may include user behavior log data. Accordingly, the association module 302 may be further configured to: determining the reported data corresponding to the same association identifier as the reported data of the same user; and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

In addition, in the embodiment of the present invention, the first client is a browser end, the second client is an APP application, and the link identifier is a uniform resource locator plan URL Scheme; the first client stores the association identifier and the reporting serial number in a local storage localStorage; or the first client is an APP, the second client is a browser, and the link identifier is a Uniform Resource Locator (URL); the second client stores the association identifier and the reporting serial number in a local storage localStorage; or the first client and the second client are both APP, and the link identifier is a uniform resource locator plan URL Scheme.

It should be noted that the method for associating reported data according to the embodiment described in fig. 3 may be executed in a server.

The following describes main components of the terminal that facilitates associating reported data according to the embodiment of the present invention. It will be appreciated that the terminal may be a physical device or may be a computer program.

Specifically, the terminal of the embodiment of the present invention may include various clients; the various clients can be used for sending reporting requests carrying reporting data and associated identifiers; the association identifier is pre-stored by any one of the plurality of clients and is used for associating the reported data.

Preferably, the plurality of clients includes a first client and a second client both in an unregistered state.

In practical applications, the first client and the second client may be two computer programs installed on the terminal. For example: the first client and the second client are respectively a browser end and an APP application installed in a mobile phone (terminal).

In an optional implementation, the first client may be further configured to: after sending an access request and receiving a response to the access request, establishing and storing an association identifier; sending a call starting request carrying the associated identifier to a second client; the second client may be further operable to: and receiving the call request, and storing the associated identifier carried in the call request.

As a preferred aspect, the first client may be further configured to: and after a trigger event comprising the link identifier of the second client is monitored, sending the call-starting request to the second client.

In practical application, the report request sent by the first client may further carry: the reporting sequence number currently stored by the first client; the report request sent by the second client may further carry: the reporting sequence number currently stored by the second client; and the reporting sequence numbers carried in the reporting requests sent by the first client and the second client can be used for: and associating the reported data.

In a specific application, the first client may be further configured to: when the association identifier is established, establishing and storing an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to a currently stored reporting serial number and a preset rule, and removing the currently stored reporting serial number; sending the call initiation request to a second client; the call request carries a reporting serial number currently stored by a first client; the second client may be further operable to: receiving the call request, and storing a reporting sequence number carried in the call request; when a report request is sent, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

Preferably, the preset rules include: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

In the embodiment of the invention, the reported data comprises user behavior log data; the association identifiers carried in the report requests sent by the first client and the second client are further used for: determining reported data of the same user; and the reporting sequence numbers carried in the reporting requests sent by the first client and the second client are further used for: and sequencing the reported data in the reported data of the same user to correlate the user behaviors.

In addition, in the embodiment of the present invention, the first client is a browser end, the second client is an APP application, and the link identifier is a uniform resource locator plan URL Scheme; the first client stores the association identifier and the reporting serial number in a local storage localStorage; or the first client is an APP, the second client is a browser, and the link identifier is a Uniform Resource Locator (URL); the second client stores the association identifier and the reporting serial number in a local storage localStorage; or both the first client and the second client are APP applications, and the link identifier is a uniform resource locator plan URL Scheme.

Fig. 4 is a schematic diagram of a main portion of a system for associating report data according to an embodiment of the present invention.

As shown in fig. 4, the system for associating reported data according to the embodiment of the present invention may include a server 401 and a plurality of clients; the multiple clients are used for sending reporting requests carrying reporting data and associated identifiers to the server 401, wherein the associated identifiers are pre-stored by any one of the multiple clients; the server 401 is configured to receive the report request, and associate the report data with the association identifier.

Preferably, the plurality of clients includes: a first client 402 and a second client 403 both in an unregistered state.

In this embodiment of the present invention, the first client 402 may further be configured to: after an access request is sent to the server 401 and a response of the server 401 to the access request is received, establishing and storing an association identifier; sending a call-starting request carrying the association identifier to a second client 403; the second client 403 may further be configured to: and receiving the call request, and storing the associated identifier carried in the call request.

In a specific application, the first client 402 may further be configured to: after monitoring a trigger event including the link identifier of the second client 403, the call initiation request is sent to the second client 403.

As a preferred scheme, the report request sent by the first client 402 may further carry: the reporting sequence number currently stored by the first client 402; the report request sent by the second client 403 may further include: the reporting sequence number currently stored by the second client 403; and the server 401 may be further configured to: and associating the reported data by using the association identifier and the reporting sequence number carried in the reporting request.

Preferably, in the embodiment of the present invention, the first client 402 is further configured to: when the association identifier is established, establishing and storing an initial reporting serial number; when a reporting request is sent to the server 401, a new reporting sequence number is generated and stored according to the currently stored reporting sequence number and a preset rule, and the currently stored reporting sequence number is removed; sending the call initiation request to the second client 403; wherein, the call-starting request carries a reporting sequence number currently stored by the first client 402; the second client 403 may further be configured to: receiving the call request, and storing a reporting sequence number carried in the call request; when a report request is sent to the server 401, a new report sequence number is generated and stored according to the currently stored report sequence number and a preset rule, and the currently stored report sequence number is removed.

Specifically, the preset rule may include: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

In an optional implementation manner, the report data includes user behavior log data. Accordingly, the server 401 may further be configured to: determining the reported data corresponding to the same association identifier as the reported data of the same user; and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

Furthermore, in the embodiment of the present invention, the first client 402 is a browser end, the second client 403 is an APP application, and the link identifier is a uniform resource locator plan URL Scheme; the first client 402 stores the association identifier and the reporting sequence number in a local storage localStorage; or, the first client 402 is an APP application, the second client 403 is a browser, and the link identifier is a uniform resource locator URL; the second client 403 stores the association identifier and the reporting sequence number in a local storage localStorage; alternatively, the first client 402 and the second client 403 are both APP applications, and the link identifier is a uniform resource locator plan URL Scheme.

Fig. 5 illustrates an exemplary system architecture 500 to which a method for associating reporting data or an apparatus for associating reporting data according to an embodiment of the present invention may be applied.

As shown in fig. 5, the system architecture 500 may include

terminal devices

501, 502, 503, a network 504, and a server 505 (this architecture is merely an example, and the components included in a particular architecture may be adapted according to application specific circumstances). The network 504 serves to provide a medium for communication links between the

terminal devices

501, 502, 503 and the server 505. Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

501, 502, 503 to interact with a server 505 over a network 504 to receive or send messages or the like. The

terminal devices

501, 502, 503 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

501, 502, 503 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 505 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the

terminal devices

501, 502, 503. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.

It should be noted that the method for associating reported data provided by the embodiment of the present invention is generally executed by the server 505, and accordingly, the apparatus for associating reported data is generally disposed in the server 505.

It should be understood that the number of terminal devices, networks, and servers in fig. 5 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The invention also provides the electronic equipment.

The electronic device of the embodiment of the invention comprises: one or more processors; the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors realize the method for associating the reported data provided by the invention.

Referring now to fig. 6, a block diagram of a computer system 600 of an electronic device suitable for implementing a method for associating reported data in accordance with an embodiment of the present invention is shown. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 6, the computer system 600 includes a Central Processing Unit (CPU)601 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM603, various programs and data necessary for the operation of the computer system 600 are also stored. The CPU601, ROM 602, and RAM603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted in the storage section 608 as necessary.

In particular, the processes described in the main step diagrams above may be implemented as computer software programs, according to embodiments of the present disclosure. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the main step diagram. In the above-described embodiment, the computer program can be downloaded and installed from the network through the communication section 609, and/or installed from the removable medium 611. The computer program performs the above-described functions defined in the system of the present invention when executed by the central processing unit 601.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a receiving module and an associating module, where the names of these modules do not in some cases constitute a limitation on the module itself, e.g., the receiving module may also be described as a "module that sends reporting data to the associating module".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by the apparatus, cause the apparatus to perform steps comprising: receiving reporting requests sent by various clients; the reporting request carries reporting data and an associated identifier, wherein the associated identifier is pre-stored by any one of the plurality of clients; and associating the reported data by using the association identifier.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for associating reported data, comprising:

receiving reporting requests sent by various clients; wherein the plurality of clients includes: the system comprises a first client and a second client, wherein the first client and the second client are installed and run in the same physical device and are in a non-login state; reporting requests sent by a first client and a second client carry reporting data and the same associated identifier, wherein the associated identifier is pre-stored by any one of the first client and the second client;

the association identity is stored at the first client and the second client according to the following steps: after the first client sends an access request and receives a response aiming at the access request, establishing an association identifier and storing the association identifier;

the first client sends a call request carrying the associated identifier to the second client;

the second client receives the call request and stores the associated identification carried in the call request;

associating the reported data by using the association identifier; the associating the reported data by using the association identifier comprises: and determining the reported data corresponding to the same association identifier in the reported data as the reported data of the same user.

2. The method of claim 1, wherein the association identification is established based on a timestamp included in the response.

3. The method of claim 1, wherein sending, by the first client, the origination request carrying the association identifier to the second client comprises:

and after monitoring a trigger event comprising the link identifier of the second client, the first client sends the call request to the second client.

4. The method of claim 3,

the report request sent by the first client further carries: the reporting sequence number currently stored by the first client; the report request sent by the second client further carries: the reporting sequence number currently stored by the second client; and

the associating the reported data by using the association identifier comprises: and associating the reported data carried in the reporting requests sent by the first client and the second client by using the association identifier and the reporting sequence number carried in the reporting requests.

5. The method of claim 4, wherein the reporting sequence number is stored at the first client and the second client according to the following steps:

when establishing the association identifier, the first client establishes and stores an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to the currently stored reporting serial number, and removing the currently stored reporting serial number;

the first client sends the call request to the second client; the call request carries a reporting serial number currently stored by a first client;

the second client receives the call request and stores the reporting sequence number carried in the call request; when sending the report request, generating and storing a new report serial number according to the currently stored report serial number, and removing the currently stored report serial number.

6. The method of claim 5, wherein the generating a new reporting sequence number according to the currently stored reporting sequence number comprises:

and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

7. The method according to claim 6, wherein the reporting data carried in the reporting requests sent by the first client and the second client comprises user behavior log data; and the associating the report data carried in the report requests sent by the first client and the second client by using the association identifier and the report sequence number carried in the report request comprises:

and sequencing the reported data of the same user according to the reported sequence number so as to correlate the user behavior.

8. The method according to any one of claims 3 to 7,

the first client is a browser end, the second client is an APP, and the link identifier is a uniform resource locator plan URL Scheme; the first client stores the association identifier and the reporting serial number in a local storage localStorage; or

The first client is an APP, the second client is a browser, and the link identifier is a Uniform Resource Locator (URL); the second client stores the association identifier and the reporting serial number in a local storage localStorage; or

The first client and the second client are both APP applications, and the link identifier is a uniform resource locator plan URL Scheme.

9. An apparatus for associating reported data, comprising:

the receiving module is used for receiving the reporting requests sent by various clients; wherein the plurality of clients includes: the system comprises a first client and a second client, wherein the first client and the second client are installed and run in the same physical device and are in a non-login state; reporting requests sent by a first client and a second client carry reporting data and the same associated identifier, wherein the associated identifier is pre-stored by any one of the first client and the second client;

the association identity is stored at the first client and the second client according to the following steps:

after the first client sends an access request and receives a response aiming at the access request, establishing an association identifier and storing the association identifier;

after monitoring a trigger event comprising a link identifier of a second client, a first client sends a call-up request carrying the association identifier to the second client;

and the association module is used for determining the reported data corresponding to the same association identifier in the reported data as the reported data of the same user.

10. The apparatus of claim 9, wherein the association identification is established based on a timestamp included in the response.

11. A terminal, comprising: a plurality of clients; wherein,

the multiple clients are used for sending reporting requests carrying reporting data and the same associated identifier; wherein the plurality of clients includes: the system comprises a first client and a second client, wherein the first client and the second client are installed and run in the same physical device and are in a non-login state; the association identifier is pre-stored by any one of the first client and the second client;

the first client is further configured to: after sending an access request and receiving a response to the access request, establishing and storing an association identifier; sending a call starting request carrying the associated identifier to a second client;

the second client is further to: receiving the call request, and storing the associated identifier carried in the call request;

the association identification is used for executing: and determining the reported data corresponding to the same association identifier in the reported data as the reported data of the same user.

12. The terminal of claim 11, wherein the association identifier is established based on a timestamp included in the response.

13. The terminal of claim 11, wherein the first client is further configured to:

and after a trigger event comprising the link identifier of the second client is monitored, sending the call-starting request to the second client.

14. The terminal of claim 13,

the report request sent by the first client further carries: the reporting sequence number currently stored by the first client;

the report request sent by the second client further carries: the reporting sequence number currently stored by the second client; and

the reporting sequence numbers carried in the reporting requests sent by the first client and the second client are used for: and associating the reported data carried in the reporting requests sent by the first client and the second client.

15. The terminal of claim 14,

the first client is further configured to: when the association identifier is established, establishing and storing an initial reporting serial number; when a reporting request is sent, generating and storing a new reporting serial number according to a currently stored reporting serial number and a preset rule, and removing the currently stored reporting serial number; sending the call initiation request to a second client; the call request carries a reporting serial number currently stored by a first client;

the second client is further to: receiving the call request, and storing a reporting sequence number carried in the call request; when a report request is sent, a new report serial number is generated and stored according to the currently stored report serial number and a preset rule, and the currently stored report serial number is removed.

16. The terminal of claim 15, wherein the preset rule comprises: and adding the currently stored reporting sequence number with a preset numerical value to obtain a new reporting sequence number.

17. The terminal of claim 16,

the reporting data carried in the reporting requests sent by the first client and the second client comprises user behavior log data;

the association identifiers carried in the report requests sent by the first client and the second client are further used for: determining the reported data of the same user in the reported data; and

the reporting sequence numbers carried in the reporting requests sent by the first client and the second client are further used for: and sequencing the reported data of the same user to correlate the user behaviors.

18. The terminal according to any of the claims 13 to 17,

19. A system for associating reported data, comprising: a server and various clients; wherein,

the various clients are used for sending reporting requests carrying the reporting data and the same associated identifier to the server; the plurality of clients include: the system comprises a first client and a second client, wherein the first client and the second client are installed and run in the same physical device and are in a non-login state; the association identifier is pre-stored by any one of the first client and the second client;

the first client is further configured to: after an access request is sent to a server and a response of the server to the access request is received, establishing and storing an association identifier; sending a call starting request carrying the associated identifier to a second client;

the server is used for receiving the report request and determining the report data corresponding to the same association identifier in the report data as the report data of the same user.

20. The system of claim 19, wherein the association identifier is established based on a timestamp included in the response.

21. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.

22. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-8.