CN111552620A

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

Info

Publication number: CN111552620A
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: 2020-08-18
Anticipated expiration: 2040-04-03
Also published as: CN111552620B

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 a target object in a 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; by the method and the device, the complexity of layer-by-layer transmission in the buried point data acquisition process can be reduced, the development of middle-layer storage controls is reduced, and the storage space is increased.

Description

Data acquisition method, device, terminal and storage medium

Technical Field

The present disclosure relates to software development technologies, and in particular, to a data acquisition method, an apparatus, a terminal, and a storage medium.

Background

In order to realize user behavior collection of the client at the mobile terminal, a lot of buried point data need to be acquired, and the transmission process of acquiring the buried point data spans a lot of page and view levels. In the related art, the data is obtained by sequentially transmitting the buried point data in each level of page and view, for example, a page includes 5 view levels ABCDE included in sequence, when a user action occurs on the view E, the data of the buried point at a needs to be obtained, and a needs to transmit the data of the buried point to B, B to C, C to D, and D to E. Therefore, the process of data transmission is complex and error-prone, and a storage area needs to be opened up for storing the data of the embedded point in each middle view, 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 obtaining method, including:

presenting a target object in a 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 foregoing 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;

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

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

In the above solution, the determining a source page corresponding to the view based on the current page 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 that the searched page positioned at the first page level in the pages is the source page corresponding to the view.

In the above scheme, the obtaining of the buried point data corresponding to the trigger event from the data source object includes:

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

acquiring 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 obtaining of the buried point data corresponding to the trigger event from the data source object includes:

acquiring 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 foregoing 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, with the target object as a starting point, finding a target transfer object positioned at the end point of the data transfer path;

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 delivery object;

and determining that the fourth identifier is 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 that the second content data is buried point data corresponding to the trigger event.

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

analyzing the buried point 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 and presenting a 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 for presenting the target object in the client;

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

a first obtaining unit, configured to obtain an event response chain corresponding to the trigger event, where the event response chain is used 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, 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;

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

In the foregoing solution, 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;

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

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;

acquiring 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 included in the current page;

acquiring a third identifier for identifying each target page;

In the foregoing solution, 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 starting point;

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

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

In the above scheme, the apparatus further comprises:

and the analysis unit is used for analyzing the buried point 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 the click operation of a user and presenting a function entry corresponding to the target object, and the function entry is used for triggering the 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 the executable instruction is executed.

In a fourth aspect, the present disclosure provides a storage medium storing executable instructions, where the executable instructions are executed to implement the data acquisition method provided by the embodiments of the present disclosure.

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

by applying the embodiment of the disclosure, when it is detected that the trigger event is executed for the target object presented by the client, the event response chain corresponding to the trigger event is obtained, and because the event response chain is used for indicating the data transmission path corresponding to the trigger event and the data transmission path includes the transmission object with the 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; in the whole process, the data of the buried point is not required to be transmitted layer by layer, namely, the data storage space is not required to be developed in the middle layer, so that the complexity of layer by layer transmission in the process of acquiring the data of the buried point can be reduced, the development of the storage control in the middle layer is reduced, and the storage space is increased.

Drawings

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

Fig. 1 is a schematic view 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 first flowchart of a data acquisition method provided in 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 embodiments 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 schematic flowchart of a data acquisition method according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a data acquisition apparatus 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 are shown in the 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 rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the 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. Moreover, 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 "include" and variations thereof as used herein are 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". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

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

Before further detailed description of the embodiments of the present disclosure, terms and expressions referred to in the embodiments of the present disclosure are explained, and the terms and expressions referred to in the embodiments of the present disclosure are applied to the following explanations.

1) In response to the condition or state on which the performed operation depends, one or more of the performed operations may be in real-time or may have a set delay when the dependent condition or state is satisfied; there is no restriction on the order of execution of the operations performed unless otherwise specified.

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

3) The system comprises a page and a view (view layer), wherein the page of a client can be independently presented or embedded into other pages, and the view needs to be presented by depending on the page.

Based on the above explanations of terms and terms involved in the embodiments of the present disclosure, a data acquisition system provided in the embodiments of the present disclosure is described below, referring to fig. 1, fig. 1 is a schematic view of an implementation scenario of a data acquisition method provided in the embodiments of the present disclosure, in order to support 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 and is provided with an application client such as news information, and the terminal 200-2 is a test developer-side terminal and is provided with a test client) is connected to the server 100 through a network 300, and the network 300 may be a wide area network or a local area network, or a combination of the two networks, and data transmission is implemented using a wireless or wired link.

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

the server 100 is used for responding to a user behavior analysis instruction aiming at the client and sending a buried point data acquisition instruction to the terminal;

and the terminal (such as the terminal 200-2) is used for responding to the test instruction and sending a user behavior analysis instruction aiming at the client.

In practical applications, the server 100 may be a server configured independently to support various services, or may be a server cluster; the terminal (e.g., terminal 200-1) may be any type of user terminal such as a smartphone, tablet, laptop, etc., and may also be 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 present disclosure. The electronic device may be various terminals including a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a Personal Digital Assistant (PDA), a tablet computer (PAD), a Portable Multimedia Player (PMP), a vehicle mounted terminal (e.g., a car navigation terminal), etc., and a fixed terminal such as a digital Television (TV), a desktop computer, etc. The electronic device shown in fig. 2 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 2, the electronic device may include a processing device (e.g., central processing unit, 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 device 280 into a Random Access Memory (RAM) 230. In the RAM 230, various programs and data necessary for the operation of the electronic apparatus are also stored. The processing device 210, the ROM 220, and the RAM 230 are connected to each other through a bus 240. An Input/Output (I/O) interface 250 is also connected to bus 240.

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

In particular, the processes described by the provided flowcharts may be implemented as computer software programs according to embodiments of the present disclosure. For example, the disclosed embodiments 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 flow chart. In such embodiments, the computer program may be downloaded and installed from a network through communication device 290, or installed from storage device 280, or installed from ROM 220. The functions in the data acquisition method of the embodiments 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. A computer readable storage medium may include, 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 RAM, a ROM, an erasable programmable Read-Only Memory (EPROM), 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, a computer readable signal medium may comprise 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 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 over electrical wiring, fiber optics, Radio Frequency (RF), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may be present alone without being incorporated into the 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 for embodiments of the present disclosure may be written in any combination of 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 a remote computer, the remote computer may be connected to the user's computer through any type of Network, including a Local Area Network (LAN) and a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart 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 described in the embodiments of the present disclosure may be implemented by software or hardware. The name of a unit does not in some cases form a definition of the unit itself, for example, the determining unit may be further described as "a unit for determining a data source object corresponding to the trigger event in the at least two delivery 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), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Part (ASSP)), a System On Chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.

In the context of embodiments of the present disclosure, 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. A 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 according to the embodiments of the present disclosure is described below. Referring to fig. 3, fig. 3 is a first schematic flow chart of a data acquisition method provided in the embodiment of the present disclosure, in some embodiments, the data acquisition method may be implemented by a server or a terminal alone, or implemented by the server and the terminal in a cooperative manner, taking the terminal as an example, 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 a target object in the client, wherein the target object can be a page or a view of the client and the like.

Here, the page of the client can be presented alone or embedded in other pages, and the view needs to be presented depending on the page. Taking a terminal to operate an instant messaging client as an example, referring to fig. 4, fig. 4 is a schematic view of a page and a view of the client provided by the embodiment of the present disclosure; here, in response to an open instruction of a user for an instant messaging client, a page containing four function items ("information", "address list", "find", and "i") is presented, each of which can present a corresponding separate page when a click operation by the user is received; the page contains four functional items of 'information', 'address list', 'discovery' and 'me' and a message list which can be views.

In order to realize the user behavior collection of the mobile terminal, the user behavior collection specifically includes a user behavior process and a behavior result, 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 the user behavior analysis, and the buried point data for the terminal client is obtained 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 obtained.

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 detailed contents through a client, the user can trigger through clicking operation, so that the terminal collects a trigger event of the user for the client. Here, the trigger event executed by the user for the target object may be referred to as behavior information of the user, and when analyzing and tracking the behavior of the user for the client, the analysis may be performed according to the trigger event executed by the user for the client. In practical application, user behaviors of a client are analyzed and tracked, and the user behaviors can be analyzed and tracked according to the occurrence condition of a trigger event of a certain service function, a presented page, a view and the like included in the client, for example, if the client is a news information client, the user behaviors can be analyzed and tracked according to a news recommendation page, a news collection page, a my attention page and the like included in the news information client. Therefore, there is a need to monitor in real time the occurrence of trigger events for target objects presented by a user to a client.

When the trigger event executed aiming at the target object is detected, user behavior data aiming at the trigger event at this time is collected, namely the buried point data is 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 having a hierarchical relationship, and the hierarchical relationship includes relationships between view layers, between view layers and pages, and between pages and pages.

When acquiring the buried point data, an event response chain corresponding to the trigger 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 a news information client as an example, refer to fig. 5, and fig. 5 is a schematic diagram of a presentation target object provided by the embodiment of the present disclosure; here, the target object may be an "author name view", and then the user definitely clicks other pages or views before clicking the "author name view", so as to enter the "author name view", and thus, in the process of jumping to the target object, the sequence of pages or views that are sequentially passed by when data transmission corresponding to a trigger event is triggered (i.e. a data transmission path corresponding to the trigger event) is recorded as an event response chain, such as a graph, and the event response chain (i.e. a 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 the like are transfer objects.

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

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

In practical applications, 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 that the current page and the source page are 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 included, 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 (a) in fig. 6, a level above the view D is the current page where the view D is located; or referring to (b) in fig. 6, the upper level of view D is view C, and the upper level of view C is the current page.

After determining the current page where the view is currently located, the original page corresponding to the trigger event for the target object at this time, that is, the source page corresponding to the view, needs to be tracked. Here, the user is accessing 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 in which the view D is located can be entered through both page a and page a1, for example, when page a is "news recommendation page" and page a1 is "news collection page", page a and page a1 can be clicked to enter "news detail page B". At this time, it is necessary to determine whether the user enters the current page B through the page a or the page a1, and when it is determined that the user enters the current page B through the page a, the page a is considered as an original page corresponding to the target object trigger event of this time, that is, 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 the page stack; and determining that the page positioned at the first page level in the searched pages is the source page corresponding to the view.

In actual practice, the UINavigationontroller controls the "pop-up and disappear" of the client page. Specifically, a page stack corresponding to the client is maintained through the uinnavigationsontroller, and various pages included in the current client are stored in the page stack and are placed in the order of "pop-up and disappearance". Therefore, when the source page of the view is determined, 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, here, the current page where the view D is located is a page B, and only a page a of the page located above the page level of the page B is found through the page stack corresponding to the page B, that is, the page a is located at the first page level, and then the page a is the source page of the view.

Of course, in practical applications, besides finding a source page through a page stack, the determination may also be made according to an event response chain. The event response chain records a data transmission path corresponding to the trigger event, and the data transmission path comprises a transmission object with a hierarchical relationship. Taking the target object as a starting point, 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 a current page where the view is located and a corresponding source page, determining the current page and the source page as data source objects corresponding to the trigger event.

In some other embodiments, when the target object is a view, the terminal may further 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 positioned above the page level of the current page from the page stack; and determining the current page and each searched target page as a data source object corresponding to the trigger event.

Here, in an actual application, in addition to the current page where the target object is located and the corresponding source page as the data source object of the trigger event, all pages (i.e. target pages) whose page levels are above the page level of the current page may be used as the data source object 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, the target object is used as a starting point, and the target transmission object positioned at the end point of the data transmission path is found; and determining the searched target transmission object as a data source object corresponding to the trigger event.

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

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

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, the buried point data is acquired from the data source object.

In some embodiments, when the target object is a view, the terminal may obtain 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; acquiring a second identifier for identifying the source page; and determining the first identifier, the first content data and the second identifier as 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 identifier for identifying the current page and first content data included 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 business function "current affairs news" and the like can be acquired to identify a first identifier of the current page, and media information content included in the page, such as a column ID, a column name, a topic ID, a topic name and the like, can also be acquired.

A second identifier for identifying the source page, such as a page name of the source page, such as "news recommendation page", "my interest page", and "my favorite page", may also be obtained.

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

In some embodiments, when the target object is a view, the terminal may further obtain the 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; acquiring 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 the current page where the target object is located, and all pages (i.e. target pages) whose page levels are above the page level of the current page; based on this, 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 identifier as buried point data corresponding to the trigger event.

When the target object is a page, acquiring a fourth identifier of a source page of the page, namely a fourth identifier for identifying a target transfer object; and determining the fourth identification as the 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 recommendation page", "my interest page", and "my favorite page", and the like.

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 the buried point data is acquired, 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 obtain the buried point data of the target object itself in addition to the data obtained from 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 trigger event.

When the user behavior analysis is performed on the trigger event of the target object, the buried point data of the target object may also be obtained, where the buried point data may also be content data, an identifier, and the like 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 included in the target object may also be obtained to be used as the buried point data corresponding to the trigger event.

In some embodiments, after the terminal obtains the buried point data corresponding to the trigger event, the buried point data may be analyzed 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 and 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 obtained, 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 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 of the user, such that the target object is presented when the user clicks the function entry. Therefore, by analyzing the obtained buried point data of the trigger event, the page or the target function item from which the user jumps to the target object display page is obtained, and the analysis and tracking of the user behavior are realized.

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

Next, taking an example that a terminal runs an application client, the data acquisition method provided by the embodiment of the present disclosure is continuously described. Referring to fig. 8, fig. 8 is a second schematic flowchart of a data acquisition method provided in the embodiment of the present disclosure, where the data acquisition method provided in the embodiment of the present disclosure includes:

step 801: the terminal runs an 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 view may be an "author information view", "author name view", and "author avatar view", etc.

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

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

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

Here, when analyzing and tracking the behavior of the user with respect to the client, the analysis may be performed according to a trigger event executed by the user with respect to the client. In practical application, user behaviors of a client are analyzed and tracked, and click conditions of a certain service function, a presented page, a view and the like included in the client can be analyzed, for example, if the client is a news information client, user behaviors can be analyzed and tracked according to a news recommendation page, a news collection page, a my attention page and the like included in the news information client. Therefore, there is a need to monitor in real time the occurrence of trigger events for target objects presented by a user to a client.

Step 805: when a trigger event aiming at the 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 then the user definitely clicks other pages or views before clicking the "author name view", so as to enter the "author name view", so that in the process of jumping to the target object, the sequence of pages or views that pass through in sequence when data transmission corresponding to a trigger event occurs (i.e., a data transmission path corresponding to the trigger event) is recorded as an event response chain, as shown in the figure, which may be "news recommendation page a-news detail page B-author information view C-author name view D", where "news recommendation page a, news detail page B" are transfer objects.

Step 806: based on the chain of event responses, the current page where 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 included, see (a) in fig. 6, where the upper level of the view D is the current page; or referring to (b) in fig. 6, the upper level of view D is view C, and the upper level of view C is the current page.

Step 807: the method comprises the steps of obtaining a first identifier used for identifying a current page and first content data contained in the current page.

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 business function "current affairs news" and the like can be acquired to identify a first identifier of the current page, and media information content included in the page, such as a column ID, a column name, a topic ID, a topic name and the like, can also be acquired.

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

In actual practice, the UINavigationontroller controls the "pop-up" and "disappear" of the client page. Specifically, a page stack corresponding to the client is maintained through the uinnavigationsontroller, and various pages included in the current client are stored in the page stack and are placed in the order of "pop-up and disappearance". Therefore, when the source page of the view is determined, the determination can be performed according to the page stack corresponding to the current page of the view.

Step 809: and acquiring a second identifier for identifying the source page.

Here, a second identifier for identifying the source page, such as a page name of the source page, such as "news recommendation page", "my focus page", and "my favorite page", is acquired.

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

When the user behavior analysis is performed on the trigger event of the target object, the buried point data of the target object may also be obtained, where the buried point data may 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 the buried point data.

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

Here, the terminal may directly analyze the buried point data.

The following describes units and/or modules in a data acquisition device provided by implementing the embodiments of the present disclosure. It is understood that the units or modules in the data acquisition device can be implemented in the electronic device shown in fig. 2 by using software (for example, a computer program stored in the computer software program) and can also be implemented in the electronic device shown in fig. 2 by using the hardware logic components (for example, FPGA, ASIC, SOC, and CPLD) described above.

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

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

It should be further noted that the names of the above units do not form 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 a data source object corresponding to a trigger event in at least two delivery objects based on an event response chain".

For the same reason, units and/or modules in the electronic device, which are not described in detail, do not represent defaults of the corresponding units and/or modules, and all operations performed by the electronic device may be implemented by the corresponding units and/or modules in the electronic device.

With continued reference to fig. 9, fig. 9 is a schematic structural diagram of a data acquisition apparatus provided in the embodiment of the present disclosure, where the apparatus includes:

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

a detecting unit 920, configured to detect 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 used to indicate a data transmission path corresponding to the trigger event, and the data transmission path includes at least two transmission objects having a hierarchical relationship;

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

a second obtaining unit 950, 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 where 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 the current page and first content data included in the current page;

acquiring a second identifier for identifying the source page;

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

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 included in the current page;

acquiring a third identifier for identifying each target page;

In some embodiments, the determining unit 940 is further configured to, when a target object is a page, find, based on the event response chain, a target transfer object located at the 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 identifier as buried point data corresponding to the trigger event.

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

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

In some embodiments, the apparatus further comprises:

and the analysis unit is used for analyzing the buried point 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 the click operation of the user and presenting a function entry corresponding to the target object, and the function entry is used for triggering the display of the target object.

Here, it should be noted that: similar to the above description of the method, the beneficial effects of the method are described, and no further description is given, for the technical details not disclosed in the embodiment of the data acquisition apparatus in the embodiment of the present disclosure, please refer to the description of the embodiment of the method in the present disclosure.

An embodiment of the present disclosure further provides a terminal, where the terminal includes:

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 present disclosure also provides a storage medium, which stores executable instructions, and when the executable instructions are executed, the storage medium is used for implementing the data acquisition method provided by the embodiment of the present disclosure.

According to one or more embodiments of the present disclosure, an embodiment of the present disclosure provides a data acquisition method, including:

presenting a target object in a client;

detecting a trigger event for a target object;

acquiring an event response chain corresponding to a 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 a trigger event in at least two transfer objects based on the event response chain;

According to one or more embodiments of the present disclosure, an embodiment of the present disclosure provides a data obtaining method, further including:

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

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

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

acquiring a page stack corresponding to a current page;

acquiring buried point data corresponding to a trigger event from a data source object, wherein the buried point data comprises the following steps:

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

acquiring 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;

acquiring a third identifier for identifying each target page;

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

acquiring a fourth identifier for identifying the target delivery object;

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

and analyzing the buried point 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 the click operation of the user and presenting a function entry corresponding to the target object, and the function entry is used for triggering the display of the target object.

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

a presentation unit for presenting the target object in the client;

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

the device comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring an event response chain corresponding to a trigger event, 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 a trigger event in at least two transfer objects based on the event response chain;

The above description is only an example of the present disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while 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. Under 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 limitations on the scope of the 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 disclosed as example forms of implementing the claims.

Claims

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

presenting a target object in a client;

detecting a trigger event for the target object;

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

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

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

acquiring a page stack corresponding to the current page;

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

acquiring a second identifier for identifying the source page;

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

acquiring a page stack corresponding to the current page;

acquiring a third identifier for identifying each target page;

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

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

acquiring a fourth identifier for identifying the target delivery object;

8. 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;

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

10. A data acquisition apparatus, characterized in that the apparatus comprises:

a presentation unit for presenting the target object in the client;

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

11. A terminal, characterized in that the terminal comprises:

a memory for storing executable instructions;

a processor, configured to implement the data acquisition method according to any one of claims 1 to 9 when executing the executable instructions.

12. A storage medium having stored thereon executable instructions for implementing a data acquisition method as claimed in any one of claims 1 to 9 when executed.