CN111552620B

CN111552620B - Data acquisition method, device, terminal and storage medium

Info

Publication number: CN111552620B
Application number: CN202010260606.4A
Authority: CN
Inventors: 郝学智
Original assignee: Beijing ByteDance Network Technology Co Ltd
Current assignee: Beijing ByteDance Network Technology Co Ltd
Priority date: 2020-04-03
Filing date: 2020-04-03
Publication date: 2023-07-11
Anticipated expiration: 2040-04-03
Also published as: CN111552620A

Abstract

The embodiment of the disclosure provides a data acquisition method, a data acquisition device, a terminal and a storage medium; the method comprises the following steps: presenting the target object in the client; detecting a trigger event for the target object; acquiring an event response chain corresponding to the trigger event, wherein the event response chain is used for indicating a data transmission path corresponding to the trigger event, and the data transmission path comprises at least two transmission objects with a hierarchical relationship; determining a data source object corresponding to the trigger event in the at least two transfer objects based on the event response chain; acquiring buried point data corresponding to the trigger event from the data source object; through the method and the device, the complexity of layer-by-layer transfer in the buried point data acquisition process can be reduced, development of middle-layer storage controls is reduced, and storage space is increased.

Description

Data acquisition method, device, terminal and storage medium

Technical Field

The embodiment of the disclosure relates to a software development technology, in particular to a data acquisition method, a data acquisition device, a terminal and a storage medium.

Background

In order to realize the user behavior acquisition of the client at the mobile terminal, a lot of embedded point data needs to be acquired, and a lot of pages and view levels can be crossed in the transmission process of acquiring the embedded point data. In the related art, the embedded point data is acquired by sequentially transmitting the embedded point data in each level page and view, for example, a page comprises 5 view levels ABCDE sequentially included in the page, when user behavior occurs in an E view, the embedded point data at a position a needs to be acquired, and the embedded point data needs to be transmitted to B from B to C, and transmitted to D from C to E. Thus, the data transmission process is complex and error-prone, and each middle view needs to open up a storage area to store buried point data, so that the storage space is occupied.

BRIEF SUMMARY OF THE PRESENT DISCLOSURE

In view of this, the embodiments of the present disclosure provide a data acquisition method, apparatus, terminal, and storage medium.

In a first aspect, an embodiment of the present disclosure provides a data acquisition method, including:

presenting the target object in the client;

detecting a trigger event for the target object;

acquiring an event response chain corresponding to the trigger event, wherein the event response chain is used for indicating a data transmission path corresponding to the trigger event, and the data transmission path comprises at least two transmission objects with a hierarchical relationship;

determining a data source object corresponding to the trigger event in the at least two transfer objects based on the event response chain;

and acquiring buried point data corresponding to the trigger event from the data source object.

In the above solution, when the target object is a view, the determining, based on the event response chain, a data source object corresponding to the trigger event in the at least two transfer objects includes:

determining a current page where the view is located based on the event response chain;

and determining a source page corresponding to the view based on the current page;

and determining the current page and the source page as data source objects corresponding to the trigger event.

In the above solution, the determining, based on the current page, a source page corresponding to the view includes:

acquiring a page stack corresponding to the current page;

searching a page with a page level above the page level of the current page from the page stack;

and determining the searched page positioned at the first page level in the pages as a source page corresponding to the view.

In the above solution, the acquiring, from the data source object, buried point data corresponding to the trigger event includes:

acquiring a first identifier for identifying the current page and first content data contained in the current page;

and obtaining a second identifier for identifying the source page;

and determining the first identifier, the first content data and the second identifier as the buried point data.

acquiring a page stack corresponding to the current page;

Searching a target page with a page level above the page level of the current page from the page stack;

determining the current page and each searched target page as a data source object corresponding to the trigger event;

correspondingly, the acquiring the buried point data corresponding to the triggering event from the data source object includes:

and obtaining a third identifier for identifying each target page;

and determining the first identifier, the first content data and the third identifier as the buried point data.

In the above solution, when the target object is a page, the determining, based on the event response chain, a data source object corresponding to the trigger event in the at least two transfer objects includes:

based on the event response chain, searching a target transfer object positioned at the end point of the data transfer path by taking the target object as a starting point;

and determining the searched target transfer object as a data source object corresponding to the trigger event.

Acquiring a fourth identifier for identifying the target transfer object;

and determining the fourth mark as buried point data corresponding to the trigger event.

In the above solution, when the target object is a view, the method further includes:

acquiring second content data corresponding to the target object;

and determining the second content data as buried point data corresponding to the triggering event.

In the above solution, after the obtaining the buried data corresponding to the trigger event from the data source object, the method further includes:

analyzing the embedded data to obtain a user entry corresponding to the target object, wherein the user entry corresponds to a target function item of the client, the target function item is used for responding to clicking operation of a user, presenting the function entry corresponding to the target object, and the function entry is used for triggering display of the target object.

In a second aspect, an embodiment of the present disclosure provides a data acquisition apparatus, including:

a presentation unit configured to present a target object in a client;

a detection unit configured to detect a trigger event for the target object;

the first acquisition unit is used for acquiring an event response chain corresponding to the trigger event, wherein the event response chain is used for indicating a data transmission path corresponding to the trigger event, and the data transmission path comprises at least two transmission objects with a hierarchical relationship;

The determining unit is used for determining a data source object corresponding to the trigger event in the at least two transfer objects based on the event response chain;

the second acquisition unit is used for acquiring the buried point data corresponding to the trigger event from the data source object.

In the above scheme, the determining unit is further configured to determine, when the target object is a view, a current page where the view is located based on the event response chain;

In the above scheme, the determining unit is further configured to obtain a page stack corresponding to the current page;

In the above solution, the second obtaining unit is further configured to obtain a first identifier for identifying the current page and first content data included in the current page;

And obtaining a second identifier for identifying the source page;

acquiring a page stack corresponding to the current page;

correspondingly, the second obtaining unit is further configured to obtain a first identifier for identifying the current page and first content data contained in the current page;

and obtaining a third identifier for identifying each target page;

In the above scheme, the determining unit is further configured to, when the target object is a page, find, based on the event response chain, a target transfer object located at an end point of the data transfer path with the target object as a start point;

In the above solution, the second obtaining unit is further configured to obtain a fourth identifier for identifying the target delivery object;

In the above solution, the second obtaining unit is further configured to obtain second content data corresponding to the target object when the target object is a view;

In the above scheme, the device further includes:

the analysis unit is used for analyzing the embedded data to obtain a user entry corresponding to the target object, the user entry corresponds to a target function item of the client, the target function item is used for responding to clicking operation of a user, the function entry corresponding to the target object is presented, and the function entry is used for triggering display of the target object.

In a third aspect, an embodiment of the present disclosure provides a terminal, including:

a memory for storing executable instructions;

and the processor is used for realizing the data acquisition method provided by the embodiment of the disclosure when executing the executable instructions.

In a fourth aspect, an embodiment of the present disclosure provides a storage medium storing executable instructions that, when executed, are configured to implement the above-described data acquisition method provided by the embodiment of the present disclosure.

The application of the embodiment of the present disclosure has the following beneficial effects:

by applying the embodiment of the present disclosure, when the trigger event is detected to be executed for the target object presented by the client, an event response chain corresponding to the trigger event is obtained, and because the event response chain is used for indicating a data transmission path corresponding to the trigger event and the data transmission path includes the transmission objects with a hierarchical relationship, the data source object corresponding to the trigger event can be determined according to the event response chain, so as to directly obtain the buried point data corresponding to the trigger event from the data source object; the embedded point data is not required to be transferred layer by layer in the whole process, namely, the middle layer development data storage space is not required, so that the complexity of layer by layer transfer in the embedded point data acquisition process can be reduced, the development of the middle layer storage control is reduced, and the storage space is increased through the embedded point data storage method and device.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

Fig. 1 is a schematic diagram of an implementation scenario of a data acquisition method provided in an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating a method for acquiring data according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a page and view of a client provided by an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a target object provided by an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a current page provided by an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a source page provided by an embodiment of the present disclosure;

fig. 8 is a second flowchart of a data acquisition method according to an embodiment of the disclosure;

fig. 9 is a schematic structural diagram of a data acquisition device according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure have been shown in the accompanying drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Furthermore, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

Before explaining the embodiments of the present disclosure in further detail, terms and terminology involved in the embodiments of the present disclosure are explained, and the terms and terminology involved in the embodiments of the present disclosure are applicable to the following explanation.

1) In response to a condition or state that is used to represent the condition or state upon which the performed operation depends, the performed operation or operations may be in real-time or with a set delay when the condition or state upon which it depends is satisfied; without being specifically described, there is no limitation in the execution sequence of the plurality of operations performed.

2) Buried point data is obtained through buried point analysis, and the buried point analysis is a common data acquisition method for realizing client user behavior analysis.

3) Pages and views (view layers), pages of clients can be presented alone or embedded in other pages, and views need to be presented by means of the pages.

Based on the above explanation of terms and terminology involved in the embodiments of the present disclosure, the data acquisition system provided in the embodiments of the present disclosure is described below, referring to fig. 1, fig. 1 is a schematic diagram of an implementation scenario of a data acquisition method provided in the embodiments of the present disclosure, for supporting an exemplary application, a terminal (including a terminal 200-1 and a terminal 200-2, where the terminal 200-1 is a user-side terminal, provided with an application client such as news information, and the terminal 200-2 is a test developer-side terminal, provided with a test client) is connected to a server 100 through a network 300, where the network 300 may be a wide area network or a local area network, or a combination of both, and data transmission is implemented using a wireless or wired link.

A terminal (e.g., terminal 200-1) for presenting the target object in the client; detecting a trigger event for a target object; when receiving a buried data acquisition instruction sent by a server, acquiring an event response chain corresponding to a trigger event; determining a data source object corresponding to a triggering event in at least two transfer objects based on an event response chain; acquiring buried point data corresponding to a trigger event from a data source object;

a server 100 for transmitting a buried data acquisition instruction to a terminal in response to a user behavior analysis instruction for a client;

a terminal (e.g., terminal 200-2) for sending a user behavior analysis instruction for the client in response to the test instruction.

In practical application, the server 100 may be a separately configured server supporting various services, or may be configured as a server cluster; the terminal (e.g., terminal 200-1) may be a smart phone, tablet, notebook, etc., various types of user terminals, as well as a wearable computing device, a Personal Digital Assistant (PDA), a desktop computer, a cellular phone, a media player, a navigation device, a game console, a television, or a combination of any two or more of these or other data processing devices.

Referring to fig. 2, fig. 2 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure. The electronic device may be various terminals including mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, personal digital assistants (PDA, personal Digital Assistant), tablet computers (PAD), portable multimedia players (PMP, portable Media Player), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital Televisions (TVs), desktop computers, and the like. The electronic device shown in fig. 2 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 2, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 210 that may perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 220 or a program loaded from a storage means 280 into a random access Memory (RAM, random Access Memory) 230. In the RAM 230, various programs and data required for the operation of the electronic device are also stored. The processing device 210, the ROM 220, and the RAM 230 are connected to each other by a bus 240. An Input/Output (I/O) interface 250 is also connected to bus 240.

In general, the following devices may be connected to the I/O interface 250: input devices 260 including, for example, a touch screen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 270 including, for example, a liquid crystal display (LCD, liquid Crystal Display), a speaker, a vibrator, and the like; storage 280 including, for example, magnetic tape, hard disk, etc.; and a communication device 290. The communication means 290 may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data.

In particular, according to embodiments of the present disclosure, the processes described by the provided flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure 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 shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 290, or from the storage device 280, or from the ROM 220. The functions in the data acquisition method of the embodiment of the present disclosure are performed when the computer program is executed by the processing device 220.

It should be noted that, the computer readable medium described above in the embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium may include, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 RAM, a ROM, an erasable programmable read-only memory (EPROM, erasable Programmable Read Only Memory), a 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 disclosed embodiments, 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 contrast, in the disclosed embodiments, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may 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 electrical wiring, optical fiber cable, radio Frequency (RF), the like, or any suitable combination of the foregoing.

The computer readable medium may be contained in the electronic device; or may exist alone without being assembled into an electronic device.

The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the data acquisition method provided by the embodiments of the present disclosure.

Computer program code for carrying out operations in embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of remote computers, the remote computers may be connected to the user computer through any kind of network, including a local area network (LAN, local Area Network)) and a wide area network (WAN, wide Area Network), or may be connected to external computers (e.g., connected through the internet using an internet service provider).

The flowcharts and block diagrams provided by the embodiments of the present disclosure illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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 units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the name of the unit does not constitute a limitation of the unit itself in some cases, for example, the determining unit may also be described as "a unit for determining a data source object corresponding to the trigger event in the at least two transfer objects based on the event response chain".

The functions described in the embodiments of the present disclosure may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field programmable gate array (FPGA, field-Programmable Gate Array), an application specific integrated circuit (ASIC, application Specific Integrated Circuit), a special standard product (ASSP, application Specific Standard Parts)), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of the disclosed embodiments, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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.

Based on the above description of the data acquisition system and the electronic device according to the embodiments of the present disclosure, the data acquisition method provided by the embodiments of the present disclosure is described below. Referring to fig. 3, fig. 3 is a flowchart of a data acquisition method provided in an embodiment of the present disclosure, and in some embodiments, the data acquisition method may be implemented by a server or a terminal alone or in conjunction with the server and the terminal, and in an embodiment of the present disclosure, the data acquisition method provided in the embodiment of the present disclosure includes:

step 301: the terminal presents the target object in the client.

Here, in practical applications, the terminal is provided with an application client, such as a social application client, a news information client, and the like. The terminal presents the running application client through the view interface, and presents the target object in the client, wherein the target object can be a page or view of the client.

Here, the pages of the client may be presented separately or embedded in other pages, and the view needs to be presented by means of the pages. Taking an example of a terminal running an instant messaging client, referring to fig. 4, fig. 4 is a schematic diagram of a page and a view of the client provided in an embodiment of the disclosure; here, in response to an opening instruction of a user for the instant messaging client, presenting a page containing four functional items ("information", "address book", "find" and "me"), each of which can present a corresponding separate page when receiving a click operation of the user; the four functional items of "information", "address book", "find" and "me" contained in the page can be views.

In order to realize the acquisition of the user behavior of the mobile terminal, the acquisition of the user behavior process and the behavior result can be specifically included, and a large amount of data needs to be acquired. In practical application, the buried point analysis is a common data acquisition method for user behavior analysis, is a very important link in user behavior analysis, and obtains buried point data aiming at a terminal client through the buried point analysis. When the user behavior of the client needs to be analyzed and tracked, the buried point data needs to be acquired.

Step 302: a trigger event for the target object is detected.

Here, the trigger event may be a click operation or the like performed by the user with respect to the target object.

When a user browses or wants to view the detail content through the client, the user can trigger through clicking operation, so that the terminal acquires a triggering event aiming at the client by the user. Here, the trigger event executed by the user for the target object may be referred to as behavior information of the user, and when the user performs behavior analysis and tracking for the client, the analysis may be performed according to the trigger event executed by the user for the client. In practical application, the analysis and tracking of the user behavior of the client can be performed according to the occurrence of a triggering event including a certain service function, a presented page, a view and the like of the client, for example, the client is a news information client, and then the analysis and tracking of the user behavior can be performed according to a news recommendation page, a news collection page, a my attention page and the like included in the news information client. Thus, there is a need to monitor the occurrence of trigger events by a user for a target object presented by a client in real time.

When the trigger event is detected to be executed for the target object, the user behavior data for the trigger event is collected, namely buried point data obtained according to buried point analysis.

Step 303: and acquiring an event response chain corresponding to the trigger event.

Here, the event response chain is used to indicate a data transfer path corresponding to the trigger event, where the data transfer path includes at least two transfer objects with a hierarchical relationship, where the hierarchical relationship includes relationships between view layers, between view layers and pages, and between pages.

When the buried point data is acquired, an event response chain corresponding to the triggering event needs to be acquired first. Here, the event response chain indicates a data transfer path corresponding to the trigger event, and the data transfer path includes at least two transfer objects having a hierarchical relationship. Specifically, taking a terminal running news information client as an example, referring to fig. 5, fig. 5 is a schematic diagram of a presentation target object provided by an embodiment of the disclosure; here, the target object may be an "author name view", and the user must click on other pages or views before clicking on the "author name view", so that the user jumps to the target object, and the sequence of pages or views sequentially passed by when the data corresponding to the trigger event is transmitted (i.e., the data transmission path corresponding to the trigger event) is recorded as an event response chain, where the event response chain (i.e., the data transmission path corresponding to the trigger event) may be "news recommendation page a-news detail page B-author information view C-author name view D", where "news recommendation page, news detail page" and so on are the transmission objects.

Step 304: and determining the data source object corresponding to the triggering event in the at least two transfer objects based on the event response chain.

Based on the event response chain obtained in the above embodiment, the data source object corresponding to the triggering event in the at least two transfer objects, that is, the obtaining position of the buried point data, is determined. Continuing with the example of a terminal running a news information client, where the target object may be an "author name view," the data source object may be a "news recommendation page, a news detail page" in the event response chain, and so on.

In practical application, the target object may be a page of the client or a view of the client. When the target object is a view, in some embodiments, the terminal may determine the data source object by: determining a current page where the view is located based on the event response chain; determining a source page corresponding to the view based on the current page; and determining the current page and the source page as data source objects corresponding to the trigger event.

In practical application, when the target object is a view, the current page where the target object is currently located may be determined according to the event response chain. Here, the view and the current page may be directly or indirectly involved, see fig. 6, where fig. 6 is a schematic diagram of the current page provided by the embodiment of the present disclosure, and here, see fig. 6 (a), where the previous level of view D is the current page where the current page is located; or referring to fig. 6 (b), the upper level of view D is view C, which is the current page at which it is located.

After determining the current page where the view is currently located, the original page corresponding to the triggering event aiming at the target object at the time, namely the source page corresponding to the view, needs to be tracked. Here, the user enters the current page where the target object is located through the source page. Illustratively, referring to FIG. 7, FIG. 7 is a schematic diagram of a source page provided by an embodiment of the present disclosure; here, the current page B where the view D is located may be entered through both the page a and the page A1, and, for example, when the page a is "news recommended page" and the page A1 is "news collecting page", the "news detail page B" may be entered by clicking both the page a and the page A1. At this time, whether the user enters the current page B through the page a or the page A1 needs to be judged, and when the user is determined to enter the current page B through the page a, the page a is considered as an original page corresponding to the triggering event of the target object at this time, namely, a source page of the view.

In some embodiments, the terminal may determine the source page of the view by: acquiring a page stack corresponding to a current page; searching a page with a page level above the page level of the current page from a page stack; and determining the page positioned at the first page level in the searched pages as a source page corresponding to the view.

In practical applications, uinatingcontrol controls the "pop-up and disappearance" of client pages. Specifically, a page stack corresponding to the client is maintained by the uinvationcontroller, and various pages contained in the current client are stored in the page stack and are placed in the order of "pop-up and disappearance". Therefore, when determining the source page of the view, the determination can be performed according to the page stack corresponding to the current page where the view is located.

Firstly, acquiring a page stack corresponding to a current page; then, searching a page with a page level above the page level of the current page in the page stack; and finally, taking the searched page positioned at the first page level as a source page corresponding to the view, wherein the first page level is the highest level. For example, referring to fig. 7, where the current page in which view D is located is page B, through the page stack corresponding to page B, it is found that only page a is located above the page level of page B, that is, page a is located at the first page level, and then page a is the source page of this view.

Of course, in practical application, the determination may be based on an event response chain, in addition to searching for the source page through the page stack. The event response chain records a data transmission path corresponding to the trigger event, wherein the data transmission path comprises a transfer object with a hierarchical relationship. And taking the target object as a starting point, and taking a transfer object (namely a page) positioned at the end point of the data transmission path as a source page corresponding to the view.

After determining the current page where the view is currently located and the corresponding source page, determining the current page and the source page as the data source object corresponding to the trigger event.

In other embodiments, when the target object is a view, the terminal may also determine the data source object by: determining a current page where the view is located based on the event response chain; acquiring a page stack corresponding to a current page; searching a target page with a page level above the page level of the current page from a page stack; and determining the current page and each searched target page as a data source object corresponding to the trigger event.

Here, in practical application, besides the current page where the target object is located and the corresponding source page are taken as the data source objects of the trigger event, all pages with page levels above the page level of the current page (i.e. the target page) are taken as the data source objects corresponding to the trigger event, so as to analyze and track the user behavior more accurately.

When the target object is a page, in some embodiments, the terminal may determine the data source object by: based on the event response chain, searching a target transfer object positioned at the end point of the data transfer path by taking the target object as a starting point; and determining the searched target transfer object as a data source object corresponding to the trigger event.

When the target object is a page, the terminal may directly determine according to a page stack corresponding to the target object (page) when determining the data source object, and the specific determination method is the same as the above method for determining the source page according to the page stack of the current page, which is not described herein again.

In practical application, when the target object is a page, the determination may also be performed according to an event response chain, that is, in this event response chain, the target object is taken as a starting point, the target transfer object located at the end point of the data transfer path is searched, and the target transfer object located at the end point of the data transfer path is taken as a data source object of the target object (page). Of course, in other embodiments, any delivery object that is on the data delivery path may be the data source object of the target object (page), starting with the target object.

Step 305: and acquiring buried point data corresponding to the trigger event from the data source object.

Here, after determining the data source object corresponding to the trigger event, buried point data is acquired from the data source object.

In some embodiments, when the target object is a view, the terminal may acquire the buried point data corresponding to the trigger event by: acquiring a first identifier for identifying a current page and first content data contained in the current page; and obtaining a second identifier for identifying the source page; the first identifier, the first content data and the second identifier are determined to be buried point data.

In practical application, when the target object is a view, the data source object is a current page and a source page. At this time, a first identification for identifying the current page and first content data contained in the current page may be acquired. Illustratively, when the client is a news information client, the current page where the "author information view" is located is a "news detail page", where a page name "detail page" of the "news detail page", a page service function "temporal news" and the like may be obtained to identify a first identifier of the current page, and media information content contained in the page, such as a column ID, a column name, a topic ID, a topic name and the like, may also be obtained.

A second identification may also be obtained for identifying the source page, such as the page name of the source page, such as "news recommended page", "my attention page", and "my collection page", among others.

Thereby determining the first identifier, the first content data and the second identifier as buried point data corresponding to the view.

In some embodiments, when the target object is a view, the terminal may further obtain buried point data corresponding to the trigger event by: acquiring a first identifier for identifying the current page and first content data contained in the current page; and obtaining a third identifier for identifying each target page; and determining the first identifier, the first content data and the third identifier as the buried point data.

Here, the data source object includes a current page where the target object is located, and all pages whose page hierarchy is located above the page hierarchy of the current page (i.e., target pages); based on the above, when the terminal acquires the buried point data corresponding to the trigger event, the terminal may acquire the first identifier of the current page, the first content data included in the current page, and the third identifier of each target page.

In some embodiments, when the target object is a page, the terminal may obtain the buried point data corresponding to the trigger event by: acquiring a fourth identifier for identifying the target transfer object; and determining the fourth mark as buried point data corresponding to the triggering event.

When the target object is a page, a fourth identification of a source page of the page is obtained, namely, a fourth identification for identifying the target transfer object; and determining the fourth identifier as buried point data corresponding to the target object (page). Here, the third identifier may also be a page name of the source page, such as "news recommended page", "my attention page", and "my collection page", etc.

In practical application, if the data source object corresponding to the trigger event of the target object (page) includes each transfer object in the data transfer path, when acquiring the buried data, information such as the identifier of each transfer object may also be acquired.

In some embodiments, when the target object is a view, the terminal may acquire the embedded point data of the target object itself in addition to acquiring the embedded point data at the data source object: acquiring second content data corresponding to the target object; and determining the second content data as buried point data corresponding to the triggering event.

When user behavior analysis is performed on the triggering event of the target object, buried point data of the target object can be obtained, where the buried point data may also be content data, identification, etc. of the target object (view), such as media information content displayed by the view: author name, author avatar, etc.

Similarly, if the target object is a page, the content and the identifier contained in the target object may be obtained as buried point data corresponding to the trigger event.

In some embodiments, after the terminal acquires the buried data corresponding to the trigger event, the terminal may further analyze the buried data to obtain a user entry corresponding to the target object. Here, the user entry corresponds to a target function item of the client, the target function item is used for responding to a click operation of the user, presenting a function entry corresponding to the target object, and the function entry is used for triggering display of the target object.

After the buried point data corresponding to the target event is acquired, the buried point data can be analyzed, so that a user entry corresponding to the target object is obtained, namely, a target function item clicked by a user when the user jumps to the target object, such as 'my collection', 'news recommendation', and the like. Here, the target function item may present a function entry of the target object in response to a click operation by the user such that the target object is presented when the user clicks on the function entry. Therefore, by analyzing the obtained buried data of the trigger event, the user can jump to the target object display page from which page or which target function item, thereby realizing analysis and tracking of user behaviors.

By applying the embodiment of the present disclosure, when the triggering event is detected to be executed for the target object presented by the client, an event response chain corresponding to the triggering event is obtained, and because the event response chain is used for indicating a data transmission path corresponding to the triggering event and the data transmission path includes the transmission objects with a hierarchical relationship, the data source object corresponding to the triggering event can be determined according to the event response chain, so that buried point data corresponding to the triggering event can be directly obtained from the data source object; the embedded point data is not required to be transferred layer by layer in the whole process, namely, the middle layer development data storage space is not required, so that the complexity of layer by layer transfer in the embedded point data acquisition process can be reduced, the development of the middle layer storage control is reduced, and the storage space is increased through the embedded point data storage method and device.

The data acquisition method provided by the embodiment of the present disclosure is further described below by taking a terminal running an application client as an example. Referring to fig. 8, fig. 8 is a second flowchart of a data acquisition method according to an embodiment of the present disclosure, where the data acquisition method according to the embodiment of the present disclosure includes:

step 801: the terminal runs the application client.

Here, the application client may be a news information client.

Step 802: the target object is presented at the client.

Here, the target object may be a page or a view. When the application client is a news information client, the page can be a news recommendation page, a news detail page and the like; the views may be an "author information view", "author name view", an "author avatar view", and the like.

Step 803: and the server responds to the user behavior analysis instruction aiming at the client and sends a buried data acquisition instruction to the terminal.

Here, when a developer of the client needs to analyze and track the user behavior of the client, buried point data for the client is acquired, and at this time, a buried point data acquisition instruction is sent to the terminal.

Step 804: and the terminal responds to the buried data acquisition instruction and detects a trigger event aiming at the target object.

Here, when the behavior analysis and tracking are performed on the client by the user, the analysis may be performed according to a trigger event performed on the client by the user. In practical application, the analysis and tracking of the user behavior of the client can be performed with respect to a click condition of a certain service function, a presented page, a view and the like contained in the client, for example, the client is a news information client, and then the analysis and tracking of the user behavior can be performed with respect to a "news recommendation page", "news collection page", a "my attention page" and the like contained in the news information client. Thus, there is a need to monitor the occurrence of trigger events by a user for a target object presented by a client in real time.

Step 805: when a trigger event aiming at a target object is detected, an event response chain corresponding to the trigger event is obtained.

Here, the event response chain indicates a data transfer path corresponding to the trigger event, and the data transfer path includes at least two transfer objects having a hierarchical relationship. Specifically, referring to fig. 5, here, the target object may be an "author name view", and the user must click on other pages or views before clicking on the "author name view", so that the user enters the "author name view", and in the process of jumping to the target object, the sequence of pages or views sequentially passed by when the data corresponding to the trigger event is transmitted (i.e., the data transmission path corresponding to the trigger event) is recorded as an event response chain, where the "news recommendation page a-news detail page B-author information view C-author name view D" may be the "news recommendation page a, news detail page B" is the delivery object.

Step 806: based on the event response chain, the current page on which the view is located is determined.

Here, when the target object is a view, the current page where the target object is currently located may be determined according to the event response chain. Here, the view and the current page may be directly or indirectly involved, referring to fig. 6 (a), where the previous level of view D is the current page; or referring to fig. 6 (b), the upper level of view D is view C, which is the current page at which it is located.

Step 807: a first identification for identifying a current page and first content data contained in the current page are acquired.

Illustratively, when the client is a news information client, the current page where the "author information view" is located is a "news detail page", where a page name "detail page" of the "news detail page", a page service function "temporal news" and the like may be obtained to identify a first identifier of the current page, and media information content contained in the page, such as a column ID, a column name, a topic ID, a topic name and the like, may also be obtained.

Step 808: acquiring a page stack corresponding to the current page, and searching a source page corresponding to the view from the page stack.

In practical applications, uinating control controls the "pop-up" and "disappearance" of client pages. Specifically, a page stack corresponding to the client is maintained by the uinvationcontroller, and various pages contained in the current client are stored in the page stack and are placed in the order of "pop-up and disappearance". Therefore, when determining the source page of the view, the determination can be performed according to the page stack corresponding to the page where the view is currently located.

Step 809: a second identification is obtained for identifying the source page.

Here, a second identification for identifying the source page, such as a page name of the source page, such as "news recommendation page", "my attention page", and "my collection page", etc., is acquired.

Step 810: and acquiring second content data corresponding to the target object.

When user behavior analysis is performed on the triggering event of the target object, buried point data of the target object can be obtained, and the buried point data can also be content data and identification of the target object (view or page), such as media information content displayed by the view: author name, author ID, etc.

Step 811: and determining the first identifier, the second identifier and the first content data and the second content data as buried point data.

Step 812: and sending the embedded data to a server so that the server analyzes the embedded data.

Here, the terminal may directly analyze the buried data.

The following describes units and/or modules in a data acquisition device implementing embodiments of the present disclosure. It will be appreciated that the units or modules in the data acquisition device may be implemented in the electronic device shown in fig. 2 in the form of software (e.g. a computer program stored in a computer software program as described above), or in the electronic device shown in fig. 2 in the form of hardware logic components (e.g. FPGA, ASIC, SOC and CPLD) as described above.

Referring to fig. 9, fig. 9 is a schematic diagram of an alternative configuration of a data acquisition device implementing an embodiment of the present disclosure, showing the following elements: the functions of the presentation unit 910, the detection unit 920, the first acquisition unit 930, the determination unit 940, and the second acquisition unit 950 will be described below.

It should be noted that the above classification of units does not constitute a limitation on the electronic device itself, for example, some units may be split into two or more sub-units, or some units may be combined into one new unit.

It should also be noted that the names of the above units do not constitute a limitation on the units themselves in some cases, for example, the above "determining unit 940" may also be described as "a unit for determining, based on an event response chain, a data source object corresponding to a trigger event in at least two transfer objects".

For the same reason, elements and/or modules not described in detail in the electronic device do not represent defaults of corresponding elements and/or modules, and any operations performed by the electronic device may be performed by corresponding elements and/or modules in the electronic device.

With continued reference to fig. 9, fig. 9 is a schematic structural diagram of a data acquisition device according to an embodiment of the disclosure, where the device includes:

a presenting unit 910, configured to present the target object in the client;

a detection unit 920 for detecting a trigger event for a target object;

a first obtaining unit 930, configured to obtain an event response chain corresponding to a trigger event, where the event response chain is configured to indicate a data transfer path corresponding to the trigger event, and the data transfer path includes at least two transfer objects having a hierarchical relationship;

a determining unit 940, configured to determine, based on the event response chain, a data source object corresponding to the trigger event in the at least two transfer objects;

The second obtaining unit 950 is configured to obtain buried point data corresponding to the trigger event from the data source object.

In some embodiments, the determining unit 940 is further configured to determine, when the target object is a view, a current page on which the view is located based on the event response chain;

determining a source page corresponding to the view based on the current page;

In some embodiments, the determining unit 940 is further configured to obtain a page stack corresponding to the current page;

In some embodiments, the second obtaining unit 950 is further configured to obtain a first identifier for identifying a current page, and first content data contained in the current page;

and obtaining a second identifier for identifying the source page;

the first identifier, the first content data and the second identifier are determined to be buried point data.

In some embodiments, the determining unit 940 is further configured to determine, when the target object is a view, a current page in which the view is located based on the event response chain;

Acquiring a page stack corresponding to the current page;

correspondingly, the second obtaining unit 950 is further configured to obtain a first identifier for identifying the current page and first content data contained in the current page;

and obtaining a third identifier for identifying each target page;

In some embodiments, the determining unit 940 is further configured to, when the target object is a page, find, based on the event response chain, a target transfer object located at an end point of the data transfer path with the target object as a starting point;

In some embodiments, the second obtaining unit 950 is further configured to obtain a fourth identifier for identifying the target delivery object;

and determining the fourth mark as buried point data corresponding to the triggering event.

In some embodiments, the second obtaining unit 950 is further configured to obtain, when the target object is a view, second content data corresponding to the target object;

In some embodiments, the apparatus further comprises:

It should be noted here that: the description of the data acquisition device is similar to the description of the method, and the description of the beneficial effects of the method is omitted herein for details of the technology not disclosed in the embodiments of the data acquisition device, please refer to the description of the embodiments of the method of the present disclosure.

The embodiment of the disclosure also provides a terminal, which comprises:

a memory for storing an executable program;

and the processor is used for realizing the data acquisition method provided by the embodiment of the disclosure when executing the executable program.

The embodiment of the disclosure also provides a storage medium, which stores executable instructions that, when executed, are used to implement the data acquisition method provided by the embodiment of the disclosure.

According to one or more embodiments of the present disclosure, there is provided a data acquisition method including:

presenting the target object in the client;

detecting a trigger event for a target object;

determining a data source object corresponding to a triggering event in at least two transfer objects based on an event response chain;

According to one or more embodiments of the present disclosure, there is provided a data acquisition method, further including:

when the target object is a view, determining a data source object corresponding to a triggering event in at least two transfer objects based on an event response chain, wherein the data source object comprises:

determining a source page corresponding to the view based on the current page;

determining a source page corresponding to the view based on the current page, including:

acquiring a page stack corresponding to a current page;

acquiring buried point data corresponding to a trigger event from a data source object, including:

acquiring a first identifier for identifying a current page and first content data contained in the current page;

and obtaining a second identifier for identifying the source page;

When the target object is a view, the determining, based on the event response chain, a data source object corresponding to the trigger event in the at least two transfer objects includes:

acquiring a page stack corresponding to the current page;

and obtaining a third identifier for identifying each target page;

when the target object is a page, determining a data source object corresponding to a triggering event in at least two transfer objects based on an event response chain, wherein the data source object comprises:

acquiring a fourth identifier for identifying the target transfer object;

when the target object is a view, second content data corresponding to the target object is acquired;

and analyzing the embedded data to obtain a user entry corresponding to the target object, wherein the user entry corresponds to a target function item of the client, the target function item is used for responding to clicking operation of a user, the function entry corresponding to the target object is presented, and the function entry is used for triggering display of the target object.

According to one or more embodiments of the present disclosure, there is further provided a data acquisition apparatus including:

a presentation unit configured to present a target object in a client;

the detection unit is used for detecting a trigger event aiming at the target object;

the determining unit is used for determining a data source object corresponding to the triggering event in the at least two transfer objects based on the event response chain;

and the second acquisition unit is used for acquiring the buried point data corresponding to the trigger event from the data source object.

The foregoing description is only illustrative of the embodiments of the present disclosure and the technical principles employed. It will be appreciated by persons skilled in the art that the scope of the disclosure referred to in this disclosure is not limited to the specific combinations of features described above, but also covers other embodiments which may be formed by any combination of features described above or equivalents thereof without departing from the spirit of the disclosure. Such as those described above, are mutually substituted with the technical features having similar functions disclosed in the present disclosure (but not limited thereto).

Moreover, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are example forms of implementing the claims.

Claims

1. A method of data acquisition, the method comprising:

presenting the target object in the client;

Detecting a trigger event for the target object;

acquiring buried point data corresponding to the trigger event from the data source object;

acquiring a page stack corresponding to the current page;

and obtaining a third identifier for identifying each target page;

2. The method of claim 1, wherein when the target object is a view, the determining, based on the event response chain, a data source object corresponding to the trigger event in the at least two delivery objects comprises:

3. The method of claim 2, wherein the determining, based on the current page, a source page to which the view corresponds comprises:

acquiring a page stack corresponding to the current page;

4. The method of claim 2, wherein the obtaining buried point data corresponding to the trigger event from the data source object comprises:

and obtaining a second identifier for identifying the source page;

5. The method of claim 1, wherein when the target object is a page, the determining, based on the event response chain, a data source object corresponding to the trigger event in the at least two transfer objects comprises:

6. The method of claim 5, wherein the obtaining buried point data corresponding to the trigger event from the data source object comprises:

acquiring a fourth identifier for identifying the target transfer object;

7. The method of claim 1, wherein when the target object is a view, the method further comprises:

acquiring second content data corresponding to the target object;

8. The method of claim 1, wherein after the obtaining the buried data corresponding to the trigger event from the data source object, the method further comprises:

9. A data acquisition device, the device comprising:

a presentation unit configured to present a target object in a client;

a detection unit configured to detect a trigger event for the target object;

the second acquisition unit is used for acquiring buried point data corresponding to the trigger event from the data source object;

the determining unit is further configured to determine, when the target object is a view, a current page where the view is located based on the event response chain;

acquiring a page stack corresponding to the current page;

and obtaining a third identifier for identifying each target page;

10. A terminal, the terminal comprising:

A memory for storing executable instructions;

a processor for implementing a data acquisition method as claimed in any one of claims 1 to 8 when executing said executable instructions.

11. A storage medium storing executable instructions which, when executed, are adapted to carry out a data acquisition method according to any one of claims 1 to 8.