CN110704270A - Zero-buried point data acquisition method and device, electronic equipment and storage medium - Google Patents

Zero-buried point data acquisition method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN110704270A
CN110704270A CN201910770304.9A CN201910770304A CN110704270A CN 110704270 A CN110704270 A CN 110704270A CN 201910770304 A CN201910770304 A CN 201910770304A CN 110704270 A CN110704270 A CN 110704270A
Authority
CN
China
Prior art keywords
event
page
preset event
view
preset
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201910770304.9A
Other languages
Chinese (zh)
Inventor
范兴华
吴宪
张韩
邹鑫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing QIYI Century Science and Technology Co Ltd
Original Assignee
Beijing QIYI Century Science and Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing QIYI Century Science and Technology Co Ltd filed Critical Beijing QIYI Century Science and Technology Co Ltd
Priority to CN201910770304.9A priority Critical patent/CN110704270A/en
Publication of CN110704270A publication Critical patent/CN110704270A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3051Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3476Data logging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3604Software analysis for verifying properties of programs
    • G06F11/3612Software analysis for verifying properties of programs by runtime analysis

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention relates to a zero-buried point data acquisition method, a zero-buried point data acquisition device, electronic equipment and a storage medium, wherein the method comprises the following steps: detecting whether an event occurs on a target application program; if the event is detected to occur, judging whether the event is a preset event or not according to a preset event name of the preset event contained in a configuration file acquired from a server; and if the event is the preset event, acquiring first acquisition data information of the preset event. According to the technical scheme provided by the invention, the first acquisition data information corresponding to the preset event is acquired according to the configuration file issued by the server, and the data information of the event needing to be acquired is determined through the server, so that the frequency and times of releasing the application program version increased by modifying the buried point are reduced, the development time and cost are saved, and the data acquisition efficiency is improved.

Description

Zero-buried point data acquisition method and device, electronic equipment and storage medium
Technical Field
The embodiment of the invention relates to the field of data acquisition, in particular to a zero-buried-point data acquisition method and device, electronic equipment and a storage medium.
Background
The buried point analysis is a common data acquisition method for website analysis. Monitoring points of monitoring events preset in a website or an application program can be monitored through buried point analysis. The preset monitoring event is an event triggered by operation when a user uses a website or an application program, for example, when the user clicks a thumbs-up button, a click event is triggered. These events may generate data, such as praise numbers, which may be obtained by monitoring the point code.
Wherein, the process of implanting the monitoring point code into the monitoring point can become a buried point. The concrete process of embedding points is as follows: the web page engineer (or application program developer) implants a special monitoring point code into each monitoring point needing statistical data, and also needs to ensure that the monitoring point codes correspond to the monitoring points one by one (because the monitoring points are different, the implanted monitoring point codes are different in naming and attribute setting, and each monitoring point needs to implant a point monitoring point code special for the monitoring point), and the monitoring point codes cannot be added by mistake or neglected when implanted into the monitoring points.
Based on the scheme, the process of embedding the points is complex, and when a certain webpage or a certain application program has new statistical requirements, the embedded points must be modified or added by releasing a new version of the application program, but the development period of the new version of the application program is long, so that the efficiency of collecting data by modifying or adding the embedded points is low.
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, embodiments of the present invention provide a zero-buried point data acquisition method and apparatus, an electronic device, and a storage medium.
In view of this, an embodiment of the present invention provides a zero-buried point data acquisition method, including:
detecting whether an event occurs on a target application program;
if the event is detected to occur, judging whether the event is a preset event or not according to a preset event name of the preset event contained in a configuration file acquired from a server;
if the event is the preset event, acquiring first acquisition data information of the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
Further, before detecting whether an event occurs on the target application, the method further comprises:
when a target application program is initialized, sending an initialization request to a server;
and receiving a configuration file sent by a server in response to the initialization request, wherein the configuration file comprises a preset event name of a preset event and an acquisition path of service data corresponding to the preset event.
Further, the detecting whether an event occurs on the target application includes:
configuring monitoring code on the target application;
and detecting whether an event on the target application program occurs or not according to the monitoring code.
Further, when the first collected data information includes page access path information, acquiring the first collected data information of the preset event, including:
in the state that the target application program displays the multi-level pages, the current displayed page of the target application program traverses the pages to the root page;
acquiring the class name of each page and the identification of each page in a parent page;
combining the class name of each page with the identification of the page in a parent page to obtain the path information of each page;
and combining the path information of each page according to the sequence from the root page to the currently displayed page to obtain the page access path information of the preset event.
Further, the first collected data information further includes: and the view accesses the path information and the service data corresponding to the preset event.
Further, when the first collected data information further includes view access path information, acquiring the first collected data information of the preset event, including:
traversing the view from the currently displayed view of the target application program to the root view of the page in the state that the target application program receives the multi-level operation;
acquiring the class name of each view and the identifier of each view in a parent view;
combining the class name of each view with the identifier of the view in the parent view to obtain the path information of each view;
and combining the path information of each view according to the sequence from the root view to the currently displayed view to obtain view access path information of the preset event.
Further, when the first collected data information further includes service data corresponding to a preset event, acquiring the first collected data information of the preset event, including:
extracting an acquisition path of service data corresponding to a preset event from a configuration file;
and acquiring the service data corresponding to the preset event through the acquisition path of the service data corresponding to the preset event.
Further, the method further comprises:
if the event is not the preset event, second acquisition data information of the event is acquired; the second collected data information includes page access path information.
The embodiment of the present invention further provides a zero-buried point data acquisition apparatus, including:
the detection module is used for detecting whether an event occurs on the target application program;
the judging module is used for judging whether the event is a preset event or not according to a preset event name of the preset event contained in the configuration file acquired from the server if the event is detected to occur;
the acquisition module is used for acquiring first acquisition data information of the preset event if the event is the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
The embodiment of the invention also provides electronic equipment which comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the steps of any one of the zero-buried point data acquisition methods when executing the program stored in the memory.
The embodiment of the invention also provides a storage medium, wherein the storage medium is stored with a zero-buried point data acquisition method program, and the zero-buried point data acquisition method program is executed by a processor to realize the steps of any one of the zero-buried point data acquisition methods.
The method includes the steps of firstly detecting whether an event occurs on a target application program, judging whether the event is a preset event according to a preset event name of the preset event contained in a configuration file acquired from a server if the event occurs, and acquiring first acquired data information of the preset event if the event is the preset event. According to the scheme, the first acquisition data information corresponding to the preset event is acquired according to the configuration file issued by the server, the data information of the event needing to be acquired is determined through the server, and compared with the prior art that the data information of the event is acquired through a point burying mode, when the data information of the new event needing to be acquired is acquired through a mode that the new point is modified or added through a mode of issuing a new version of the application program, the frequency and times of issuing the version of the application program increased due to modification of the point are reduced, so that the development time and cost are saved, and the data acquisition efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a schematic view of an application scenario of a zero-buried point data acquisition method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a zero-buried point data collection method according to an embodiment of the present invention;
fig. 3 is a flowchart of a method for obtaining a configuration file from a server according to an embodiment of the present invention;
fig. 4 is a flowchart of a method for detecting whether an event occurs on a target application according to an embodiment of the present invention;
fig. 5 is a flowchart of a method for acquiring first collected data information of a preset event according to an embodiment of the present invention;
fig. 6 is a flowchart of another method for acquiring first collected data information of a preset event according to an embodiment of the present invention;
fig. 7 is a flowchart of another method for acquiring first collected data information of a preset event according to an embodiment of the present invention;
FIG. 8 is a flowchart of another zero-buried point data collection method according to an embodiment of the present invention;
FIG. 9 is a flowchart of another zero-buried point data collection method according to an embodiment of the present invention;
fig. 10 is a flowchart of a method for sending collected data information to a server according to an embodiment of the present invention;
FIG. 11 is a flowchart illustrating an overall method for collecting zero-buried data according to an embodiment of the present invention;
fig. 12 is a schematic structural diagram of a zero-buried point data acquisition apparatus according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
The main body of execution of each step of the present invention is a terminal. The terminal may be a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palm top computer, a PAD (Personal Digital Assistant), a PMP (Portable media player), a navigation device, etc., and a fixed terminal such as a Digital TV, a desktop computer, etc.
Fig. 1 is a schematic view of an application scenario of a zero-buried point data acquisition method according to an exemplary embodiment of the present invention, where the application scenario includes a terminal 1 and a server 2. The method comprises the steps that an application program is installed on a terminal 1, when the application program is initialized, a server 2 sends a configuration file to the terminal 1, and the terminal 1 acquires data information when an event occurs on the application program according to the configuration file.
It should be noted that fig. 1 is only a schematic diagram of the present invention, and only one terminal 1 is shown in the diagram, in an actual situation, the server 2 may issue a plurality of configuration files to one or more terminals, and the one or more terminals collect data information corresponding to the configuration files by using the zero-buried data collection method provided in the present application, and send the collected data information to the server 2.
FIG. 2 is a flowchart of a zero-buried point data collection method provided by the present invention. As shown in fig. 2, the method is applied to a terminal.
In the embodiment of the invention, due to different attention degrees of various events, the data required to be collected when an event occurs is different. In particular, more data needs to be collected for some events with higher attention, and conversely, less data needs to be collected for events with lower attention. The server sets the event with higher attention as a preset event, puts the preset event and the path of the information required to be acquired from the preset event into a configuration file, and then sends the configuration file to the terminal. For example, in some embodiments of the present invention, the first collected data information needs to be acquired for a preset event, and the second collected data information is acquired for a non-preset event, and specifically, the acquiring manner is described in detail in the following embodiments, and is not described herein again.
In step S201, it is detected whether an event occurs on the target application.
Specifically, the event is an operation that can be identified by a target application program, and the target application program may include a plurality of application programs that can be installed on the terminal; the events may include: starting an application program, entering a background, entering a foreground, displaying and disappearing a page, operating a control (such as clicking and sliding), and the like.
In a possible embodiment of the present invention, whether an event occurs on the target program is detected, which may be detected by setting a monitoring code on the target application program, and if the event is detected, it indicates that an event occurs. The event detection is described in detail in the following embodiments, and is not described herein.
In step S202, if an event is detected to occur, whether the event is a preset event is determined according to a preset event name of the preset event included in the configuration file acquired from the server.
Specifically, when the monitoring code detects that an event occurs, it determines whether the detected event is a preset event according to a preset event name of the preset event included in a configuration file acquired from the server when the target application is initialized.
The preset event is an event carried in a configuration file acquired by the terminal from the server when the application program is initialized, and the configuration file carries a preset event name of the preset event and an acquisition path of service data corresponding to the preset event. When data corresponding to different events need to be acquired, corresponding data can be acquired through different configuration files issued by the server, and compared with the prior art that data is acquired by releasing a new version of an application program and modifying or increasing a buried point, the development times of the new version of the application program are reduced, so that the development time and cost are saved, and the data acquisition efficiency is improved.
Further, it is determined whether the detected event is a preset event by comparing a preset event name of the preset event in the configuration file with the detected event name. If the names are the same, the detected event is a preset event; if the names are different, the detected event is not a preset event.
In step 203, if the event is the preset event, acquiring first collected data information of the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
Specifically, the terminal determines that the event in step S202 is the preset event according to the preset event name of the preset event carried in the configuration file acquired from the server, and acquires first collected data information of the preset event.
The first collected data information at least includes page access path information, and may also include other data information, such as view access path information and service data corresponding to the preset event.
The page access path is formed by connecting the path information of each page.
The connection order of the path information of each page is connected according to the order from the root page to the currently displayed page. The path information of the page refers to character string information consisting of the class name of the page and the identification of the page in a parent page.
When a preset event occurs and the application program displays a multi-level page, according to the sequence of the user operation page, connecting the path information of the root page of the page currently displayed by the target application program to the path information of the page currently displayed by the target application program to form a character string, and using the character string as the page access path of the currently displayed page. The target application program where the currently displayed page is located may be a state in which a multi-level page is displayed, or may be a state in which a one-level page is displayed. That is, the currently displayed page may be a page displayed after clicking a plurality of controls, or may be a page displayed when the target application program is just opened.
In this embodiment, first, whether an event occurs on a target application is detected, if the event occurs, whether the event is a preset event is determined according to a preset event name of the preset event included in a configuration file acquired from a server, and if the event is the preset event, first acquisition data information of the preset event is acquired. According to the scheme, the data information of the preset event carried by the configuration file is acquired according to the configuration file acquired from the server, when the preset event is detected, the data information corresponding to the preset event can be acquired, and compared with the method that the data information of the event is acquired in a point burying mode in the prior art, and when the data information of a new event needs to be acquired, the data information corresponding to the new event needs to be acquired in a mode that a new version of the application program is released, the frequency and times of releasing the version of the application program increased due to the fact that the point is modified are reduced, development time and cost are saved, and data acquisition efficiency is improved.
In another embodiment of the present invention, as shown in fig. 3, before detecting whether an event occurs on the target application program, the zero-buried-point data collecting method further includes:
in step S301, upon initialization of the target application, an initialization request is sent to the server.
Specifically, when the target application is initialized, an initialization request is sent to the server, and the initialization request includes some information related to the target application, such as a name of the target application, version information, and the like. For example, the target Application is a video APP (Application), and when the video APP is initialized, an initialization request including an APP name, version information of the APP, and some other information of the APP is sent to the server.
In step S302, a configuration file sent by the server in response to the initialization request is received, where the configuration file includes a preset event name of a preset event and an acquisition path of service data corresponding to the preset event.
Specifically, the server may send a configuration file corresponding to the target application program to the terminal according to some information related to the target application program, such as a name and version information of the target application program in the initialization request, where the configuration file includes a preset event name of a preset event and an acquisition path of service data corresponding to the preset event.
For example, when receiving an initialization request of a video APP, a server may query, according to an APP name, APP version information, and some other information of the APP carried in the initialization request, a configuration file corresponding to the APP name and APP version information in a preset file, and send the queried configuration file to a terminal, where the configuration file includes a path for obtaining a click volume of a movie and a click rate of the movie.
A more specific method of detecting the occurrence of an event on a target program is given below.
Fig. 4 is a flowchart of a method for detecting whether an event occurs on a target application according to the present invention.
In step S401, monitoring code is configured on the target application.
In the embodiment of the invention, the monitoring code can be various codes, and the type of the monitoring code is set according to the type of the event.
Specifically, the monitoring code may be a javascript code, and the javascript code may be customized according to actual needs. For example, the javascript code for monitoring an application start event, the javascript code for monitoring an APP entering a background event, the javascript code for monitoring an APP entering a foreground event, the javascript code for monitoring a page reveal event and the javascript code for monitoring a page disappear event, the javascript code for monitoring a click operation event on a control, the javascript code for monitoring a slide operation event on a control, and the like. The method for configuring the monitoring code on the application program is to embed JavaScript code into the application program in advance.
For example, monitoring the application for a start event by calling uiapplicationdirofrnishlaunchingnotification; monitoring the application program entering a background event by calling UIApplicationDidEnterBackGroundNotification; the application is monitored for entering a foreground event by calling uiapplicationwillenterforegrounndnotification. Monitoring a page display event by calling viewDidAppear; the page disappearance event is monitored by calling viewdiddispear. Click events to a space are monitored by calling SendAction (SEL) action to (nullable id) target from (nullable id) sensor for event, and so on.
In step S402, whether an event occurs on the target application is detected according to the monitoring code.
In the embodiment of the present invention, if any of the above events is detected, it indicates that an event occurs on the target application.
A method for acquiring the first collected data information of the preset event more specifically is given below.
In the embodiment of the invention, the first acquired data information at least comprises page access path information, the page access path is an access path of a page currently displayed by the target application program when a preset event occurs, and the page access path information is information which can uniquely identify the page and is generated according to a layer where the currently displayed page is located.
The first collected data information may further include view access path information and service data corresponding to the preset event.
The view access path information is formed by connecting the view path information of the view in which each operated control is positioned.
Wherein, the connection order of the view path information of each view is connected according to the order from the root view to the currently displayed view. The view path information of the view refers to the character string information composed of the class name of the view and the identification of the view in the parent view.
When a preset event occurs and the application program shows the multi-level views, according to the sequence of the user operating the control, connecting view path information of all operated controls between the view in which the operated control is located and the root page view of the page in which the view is located to form a character string, and using the character string as a view access path of the current view. The character string is information that uniquely identifies the location of the view.
The service data is data obtained according to an obtaining path of the service data corresponding to the preset event obtained from the server.
As shown in fig. 5, a method for acquiring first collected data information of a preset event is provided in the present invention. The method is applied to the condition that the first collected data information is the page access path information.
In step S501, in a state where the target application shows a multi-level page, the page is traversed from the page currently shown by the target application to the root page.
In step S502, the class name of each page and the identifier of each page in the parent page are obtained.
In step S503, the class name of each page is combined with the identifier of the page in the parent page to obtain the path information of each page.
In step S504, the path information of each page is combined according to the sequence from the root page to the currently displayed page, so as to obtain the page access path information of the preset event.
Specifically, in a state that a target application program displays a multi-level page, the page is traversed from a currently displayed page to a root page of the target application program, and a class name of each page and an identifier of the page in a parent page are recorded as path information of one page, wherein the root page does not have the identifier in the parent page because the root page does not have the parent page.
For example, the path information of a certain page is UIViewController [1], where UIViewController represents the class name and 1 represents the identification of the page in the parent page. And connecting the path information of each page by using a negative character string according to the sequence from the root page to the currently displayed page to form a character string as page access path information. For example: QIYIPAOPAOBASE NAVIIGONCONTROLLER-QYPPCardSquareViewController [0] represents the page access path of the currently displayed page when a certain application program shows a two-level state, wherein the QYPPCardSquareViewController [0] represents the path information of the currently displayed page, the QYPPCardSquareViewController represents the class name of the currently displayed page, and 0 represents the identification of the currently displayed page in the root page; the qiyipaopobasenavigationcontroller indicates path information of a root page of a currently-presented page.
As shown in fig. 6, another method for acquiring first collected data information of a preset event is provided in the present invention. The method is applied to the condition that the first acquisition data information is the view access path information.
In step S601, in a state where the target application receives the multi-level operation, the view is traversed from the view currently presented by the target application up to the root view of the page.
In step S602, the class name of each view and the identifier of each view in the parent view are obtained.
In step S603, the class name of each view is combined with the identifier of the view in the parent view to obtain the path information of each view.
In step S604, the path information of each view is combined in the order from the root view to the currently displayed view, so as to obtain view access path information of a preset event.
Specifically, in a state that the target application program receives multi-level operation, traversing from the currently displayed view to the root view of the page, recording the class name of each view and the identification of the view in the parent view as the path information of one view, wherein the path information of the view represents the position information of the control in the current page, and the root view has no identification in the parent view because the root view has no parent view.
For example, the path information of a view is UIView [1], where UIView represents the class name and numeral 1 represents the identification of the view in the parent view. The identification of the list item view refers to the sequence of the view in the list, and the format of the identification of the list item view is [ row: section ], wherein the section represents the fourth block, and the row represents the fourth block. And connecting the path information of each view by using a character string in the sequence from the root view to the currently displayed view to form the character string as view access path information. For example: QYPPUIMessageBox-UIView [0] -UIButton [3] represents a view access path of a currently displayed view when an application program displays a state of a three-level operation, wherein UIButton [3] represents the view path of the currently displayed view, UIButton represents a class name of the currently displayed view, namely the name of a current control, and 3 represents an identifier of the currently displayed view in a parent view; UIView [0] represents the path information of the parent view of the currently displayed view, UIView represents the class name of the parent view of the currently displayed view, and 0 represents the identifier of the parent view of the currently displayed view in the root view; QYPPUIMessageBox represents path information for the root view of the currently presented view.
Fig. 7 shows another method for acquiring first collected data information of a preset event according to the present invention. The method is applied to the condition that the first collected data information is the service data corresponding to the preset event.
In step S701, an acquisition path of service data corresponding to a preset event is extracted from the configuration file.
In step S702, the service data corresponding to the preset event is acquired through the acquisition path of the service data corresponding to the preset event.
Specifically, when the first collected data information is service data corresponding to a preset event, an acquisition path of the service data corresponding to the preset event is extracted from a configuration file issued by the server, and then the service data corresponding to the preset event is acquired according to the acquisition path of the service data.
Based on the foregoing embodiment, in another embodiment of the present invention, as shown in fig. 8, after determining whether an event is a preset event according to a preset event name of the preset event included in a configuration file acquired from a server if the event is detected to occur, the zero-buried-point data collecting method may further include:
in step S204, if the event is not the preset event, acquiring second collected data information of the event; the second collected data information includes page access path information.
Specifically, when the second collected data information is the page access path information, the steps of the method for obtaining the second collected data information are the same as the steps of the method for obtaining the first collected data information when the first collected data information is the page access path information, and are not described herein again.
Based on the above embodiment, in another embodiment of the present invention, as shown in fig. 9, the zero-buried point data collecting method may further include:
in step S205, the acquired first collected data information and/or second collected data information is sent to a server.
In a possible embodiment of the present invention, the first collected data information and/or the second collected data information acquired in the above embodiment may be stored in a preset storage space, and when the size of the data information stored in the preset storage space is greater than or equal to a storage threshold or the time length for operating the target application program is greater than or equal to a time length threshold, the first collected data information and/or the second collected data information may be sent to the server.
Specifically, as shown in fig. 10, sending the acquired first collected data information and/or second collected data information to the server specifically includes:
in step S1001, storing the first collected data information and/or the second collected data information in a preset storage space;
in step S1002, when the stored data information satisfies a preset condition, the first collected data information and/or the second collected data information stored in a preset storage space is sent to a server.
When the stored data information meets the preset condition, the first collected data information and/or the second collected data information stored in the preset storage space are/is sent to the server, and the method specifically comprises the following steps:
judging whether the residual space of the preset storage space is smaller than a preset storage value or not;
and if the residual space of the preset storage space is smaller than the preset storage value, sending the first acquired data information and/or the second acquired data information stored in the preset storage space to a server.
In another specific embodiment, when the time length for operating the target application program by the user is greater than or equal to the time length threshold, the first collected data information and/or the second collected data information stored in the preset storage space are/is sent to the server.
As shown in fig. 11, it is an overall flowchart of the zero-buried point data collection method provided by the present invention.
Firstly, judging whether an event occurs on a target application program; if an event occurs, judging whether the event is a preset event or not according to a preset event name of the preset event contained in a configuration file acquired from a server; if the event is a preset event, acquiring first acquired data information of the preset event, wherein the first acquired data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs; if the event is not a preset event, second acquisition data information of the event is acquired, wherein the second acquisition data information comprises page access path information; the acquired first collected data information and/or second collected data information are/is stored in a preset storage space, and when the stored data information meets preset conditions, the first collected data information and/or the second collected data information stored in the preset storage space are/is sent to a server.
Whether the event occurring on the target application program is the preset event can be judged through the name of the preset event carried by the configuration file, and when the event occurring on the target application program is the preset event, first acquisition data information corresponding to the preset event is acquired. Compared with the prior art that data is acquired in a point burying mode, and when data information of a new event needs to be acquired, the data information corresponding to the new event needs to be acquired in a mode of modifying or increasing a buried point by releasing a new version of an application program, frequency and times of releasing the version of the application program increased by modifying the buried point are reduced, development time and cost are saved, and data acquisition efficiency is improved.
Based on the same inventive concept as the above method, in another embodiment of the present invention, as shown in fig. 12, a zero-buried point data acquisition apparatus is further disclosed, the apparatus comprising: a detection module 101, a judgment module 102 and an acquisition module 103.
The detection module 101 is configured to detect whether an event has occurred on the target application.
The determining module 102 is configured to determine whether the event is a preset event according to a preset event name of the preset event included in the configuration file acquired from the server if the event is detected to occur.
The obtaining module 103 is configured to obtain first collected data information of the preset event if the event is the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
Therefore, whether an event occurs on the target application program is detected, if the event occurs, whether the event is a preset event is judged according to a preset event name of the preset event contained in the configuration file acquired from the server, and if the event is the preset event, first acquisition data information of the preset event is acquired. According to the scheme, the data information of the preset event carried by the configuration file is acquired according to the configuration file acquired from the server, when the preset event is detected, the data information corresponding to the preset event can be acquired, and compared with the method that the data information of the event is acquired in a point burying mode in the prior art, and when the data information of a new event needs to be acquired, the data information corresponding to the new event needs to be acquired in a mode that a new version of the application program is released, the frequency and times of releasing the version of the application program increased due to the fact that the point is modified are reduced, development time and cost are saved, and data acquisition efficiency is improved.
In a possible embodiment of the present invention, the zero-buried point data collecting apparatus may further include: a requesting module 104 and a receiving module 105.
The request module 104 is configured to send an initialization request to the server upon initialization of the target application.
The receiving module 105 is configured to receive a configuration file sent by the server in response to the initialization request, where the configuration file includes a preset event name of a preset event and an acquisition path of service data corresponding to the preset event.
In a possible embodiment of the present invention, the detection module 101 is specifically configured to:
configuring monitoring code on the target application;
and detecting whether an event on the target application program occurs or not according to the monitoring code.
In a possible implementation manner of the present invention, when the first collected data information includes page access path information, the obtaining module 103 is specifically configured to:
in the state that the target application program displays the multi-level pages, the current displayed page of the target application program traverses the pages to the root page;
acquiring the class name of each page and the identification of each page in a parent page;
combining the class name of each page with the identification of the page in a parent page to obtain the path information of each page;
and combining the path information of each page according to the sequence from the root page to the currently displayed page to obtain the page access path information of the preset event.
In a possible implementation manner of the present invention, when the first collected data information further includes view access path information, the obtaining module 103 is specifically configured to:
traversing the view from the currently displayed view of the target application program to the root view of the page in the state that the target application program receives the multi-level operation;
acquiring the class name of each view and the identifier of each view in a parent view;
combining the class name of each view with the identifier of the view in the parent view to obtain the path information of each view;
and combining the path information of each view according to the sequence from the root view to the currently displayed view to obtain view access path information of the preset event.
In a possible implementation manner of the present invention, when the first collected data information further includes service data corresponding to a preset event, the obtaining module 103 is specifically configured to:
extracting an acquisition path of service data corresponding to a preset event from a configuration file;
and acquiring the service data corresponding to the preset event through the acquisition path of the service data corresponding to the preset event.
In a possible embodiment of the present invention, the zero-buried point data collecting apparatus may further include: a second obtaining module 106.
The second obtaining module 106 is specifically configured to:
if the event is not the preset event, second acquisition data information of the event is acquired; the second collected data information includes page access path information.
The zero-buried point data acquisition device corresponds to the zero-buried point data acquisition method one to one, and the specific principle and process thereof are the same as those of the method described in the above embodiment, and are not described again here.
In another embodiment of the present application, there is also provided an electronic device, as shown in fig. 13, including a processor 501, a communication interface 502, a memory 503 and a communication bus 504, where the processor 501, the communication interface 502 and the memory 503 complete communication with each other through the communication bus 504;
a memory 503 for storing a computer program;
the processor 501, when executing the program stored in the memory 503, implements the following steps:
detecting whether an event occurs on a target application program;
if the event is detected to occur, judging whether the event is a preset event or not according to a preset event name of the preset event contained in a configuration file acquired from a server;
if the event is the preset event, acquiring first acquisition data information of the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
In this embodiment, first, whether an event occurs on a target application is detected, if the event occurs, whether the event is a preset event is determined according to a preset event name of the preset event included in a configuration file acquired from a server, and if the event is the preset event, first acquisition data information of the preset event is acquired. According to the scheme, the data information of the preset event carried by the configuration file is acquired according to the configuration file acquired from the server, when the preset event is detected, the data information corresponding to the preset event can be acquired, and compared with the method that the data information of the event is acquired in a point burying mode in the prior art, and when the data information of a new event needs to be acquired, the data information corresponding to the new event needs to be acquired in a mode that a new version of the application program is released, the frequency and times of releasing the version of the application program increased due to the fact that the point is modified are reduced, development time and cost are saved, and data acquisition efficiency is improved.
The communication bus 504 mentioned above for the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 504 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 13, but this is not intended to represent only one bus or type of bus.
The communication interface 502 is used for communication between the above-described electronic apparatus and other apparatuses.
The Memory 503 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor 501 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment of the present application, a storage medium is further provided, where the storage medium stores a zero-buried point data acquisition method program, and the zero-buried point data acquisition method program, when executed by a processor, implements any of the steps of the zero-buried point data acquisition method described above.
When the embodiment of the invention is specifically implemented, reference can be made to the above embodiments, and corresponding technical effects are achieved.
It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described herein may be implemented by means of units performing the functions described herein. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or make a contribution to the prior art, or may be implemented in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
Through the above description of the embodiments, those skilled in the art will clearly understand that the methods described in the embodiments of the present invention can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention or the method according to some parts of the embodiments.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (11)

1. A zero-buried point data acquisition method is characterized by comprising the following steps:
detecting whether an event occurs on a target application program;
if the event is detected to occur, judging whether the event is a preset event or not according to a preset event name of the preset event contained in a configuration file acquired from a server;
if the event is the preset event, acquiring first acquisition data information of the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
2. The method of claim 1, wherein before detecting whether an event occurs on the target application, the method further comprises:
when a target application program is initialized, sending an initialization request to a server;
and receiving a configuration file sent by a server in response to the initialization request, wherein the configuration file comprises a preset event name of a preset event and an acquisition path of service data corresponding to the preset event.
3. The method as claimed in claim 2, wherein the detecting whether an event occurs on the target application program comprises:
configuring monitoring code on the target application;
and detecting whether an event on the target application program occurs or not according to the monitoring code.
4. The method as claimed in claim 2, wherein when the first collected data information includes page access path information, acquiring the first collected data information of the preset event includes:
in the state that the target application program displays the multi-level pages, the current displayed page of the target application program traverses the pages to the root page;
acquiring the class name of each page and the identification of each page in a parent page;
combining the class name of each page with the identification of the page in a parent page to obtain the path information of each page;
and combining the path information of each page according to the sequence from the root page to the currently displayed page to obtain the page access path information of the preset event.
5. The method as claimed in claim 2, wherein the first collected data information further comprises: and the view accesses the path information and the service data corresponding to the preset event.
6. The method as claimed in claim 5, wherein when the first collected data information further includes view access path information, acquiring the first collected data information of the preset event includes:
traversing the view from the currently displayed view of the target application program to the root view of the page in the state that the target application program receives the multi-level operation;
acquiring the class name of each view and the identifier of each view in a parent view;
combining the class name of each view with the identifier of the view in the parent view to obtain the path information of each view;
and combining the path information of each view according to the sequence from the root view to the currently displayed view to obtain view access path information of the preset event.
7. The method as claimed in claim 5, wherein when the first collected data information further includes service data corresponding to a preset event, acquiring the first collected data information of the preset event includes:
extracting an acquisition path of service data corresponding to a preset event from a configuration file;
and acquiring the service data corresponding to the preset event through the acquisition path of the service data corresponding to the preset event.
8. The zero-buried point data acquisition method according to claim 1, further comprising:
if the event is not the preset event, second acquisition data information of the event is acquired; the second collected data information includes page access path information.
9. The utility model provides a zero buried point data acquisition device which characterized in that includes:
the detection module is used for detecting whether an event occurs on the target application program;
the judging module is used for judging whether the event is a preset event or not according to a preset event name of the preset event contained in the configuration file acquired from the server if the event is detected to occur;
the acquisition module is used for acquiring first acquisition data information of the preset event if the event is the preset event; the first collected data information at least comprises page access path information, and the page access path is an access path of a page currently displayed by the target application program when the preset event occurs.
10. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the steps of the zero buried point data collection method according to any one of claims 1 to 8 when executing the program stored in the memory.
11. A storage medium having stored thereon a zero-buried point data acquisition method program, the zero-buried point data acquisition method program realizing the steps of the zero-buried point data acquisition method according to any one of claims 1 to 8 when executed by a processor.
CN201910770304.9A 2019-08-20 2019-08-20 Zero-buried point data acquisition method and device, electronic equipment and storage medium Pending CN110704270A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910770304.9A CN110704270A (en) 2019-08-20 2019-08-20 Zero-buried point data acquisition method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910770304.9A CN110704270A (en) 2019-08-20 2019-08-20 Zero-buried point data acquisition method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN110704270A true CN110704270A (en) 2020-01-17

Family

ID=69193600

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910770304.9A Pending CN110704270A (en) 2019-08-20 2019-08-20 Zero-buried point data acquisition method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110704270A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111552620A (en) * 2020-04-03 2020-08-18 北京字节跳动网络技术有限公司 Data acquisition method, device, terminal and storage medium
CN111639007A (en) * 2020-05-29 2020-09-08 北京金山云网络技术有限公司 Data processing method, device, terminal and computer readable storage medium
CN112214378A (en) * 2020-10-23 2021-01-12 珠海格力电器股份有限公司 Data collection method and device, electronic equipment and storage medium
CN114385478A (en) * 2020-10-22 2022-04-22 腾讯科技(深圳)有限公司 Data acquisition reporting method and device, electronic equipment and storage medium

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107391538A (en) * 2017-04-26 2017-11-24 阿里巴巴集团控股有限公司 Click data collection, processing and methods of exhibiting, device, equipment and storage medium
CN107818162A (en) * 2017-11-01 2018-03-20 平安科技(深圳)有限公司 Bury a processing method, device, computer equipment and storage medium
CN108153641A (en) * 2016-12-05 2018-06-12 北京国双科技有限公司 A kind of nothing buries deployment monitoring method and a relevant apparatus
CN108536594A (en) * 2018-04-02 2018-09-14 腾讯科技(武汉)有限公司 Page test method, device and storage device
US20180336171A1 (en) * 2017-05-17 2018-11-22 American Megatrends, Inc. System and method for constructing extensible event log with javascript object notation (json) encoded payload data
CN109150641A (en) * 2017-06-15 2019-01-04 北京国双科技有限公司 A kind of data acquisition, querying method, device, storage medium and processor
CN109561117A (en) * 2017-09-26 2019-04-02 北京国双科技有限公司 Collecting method and device

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108153641A (en) * 2016-12-05 2018-06-12 北京国双科技有限公司 A kind of nothing buries deployment monitoring method and a relevant apparatus
CN107391538A (en) * 2017-04-26 2017-11-24 阿里巴巴集团控股有限公司 Click data collection, processing and methods of exhibiting, device, equipment and storage medium
US20180336171A1 (en) * 2017-05-17 2018-11-22 American Megatrends, Inc. System and method for constructing extensible event log with javascript object notation (json) encoded payload data
CN109150641A (en) * 2017-06-15 2019-01-04 北京国双科技有限公司 A kind of data acquisition, querying method, device, storage medium and processor
CN109561117A (en) * 2017-09-26 2019-04-02 北京国双科技有限公司 Collecting method and device
CN107818162A (en) * 2017-11-01 2018-03-20 平安科技(深圳)有限公司 Bury a processing method, device, computer equipment and storage medium
CN108536594A (en) * 2018-04-02 2018-09-14 腾讯科技(武汉)有限公司 Page test method, device and storage device

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111552620A (en) * 2020-04-03 2020-08-18 北京字节跳动网络技术有限公司 Data acquisition method, device, terminal and storage medium
CN111552620B (en) * 2020-04-03 2023-07-11 北京字节跳动网络技术有限公司 Data acquisition method, device, terminal and storage medium
CN111639007A (en) * 2020-05-29 2020-09-08 北京金山云网络技术有限公司 Data processing method, device, terminal and computer readable storage medium
CN111639007B (en) * 2020-05-29 2024-05-03 北京金山云网络技术有限公司 Data processing method, device, terminal and computer readable storage medium
CN114385478A (en) * 2020-10-22 2022-04-22 腾讯科技(深圳)有限公司 Data acquisition reporting method and device, electronic equipment and storage medium
CN112214378A (en) * 2020-10-23 2021-01-12 珠海格力电器股份有限公司 Data collection method and device, electronic equipment and storage medium
CN112214378B (en) * 2020-10-23 2023-03-24 珠海格力电器股份有限公司 Data collection method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
CN110704270A (en) Zero-buried point data acquisition method and device, electronic equipment and storage medium
CN113892087B (en) Third party application performance improvement toolkit
US20150082242A1 (en) Providing Context Menu Based on Predicted Commands
US20160224207A1 (en) Method and system for freezing and unfreezing applications
CN113939792A (en) User interface for machine language model creation
CN107181858B (en) Method and terminal for displaying notification message
CN103092604A (en) Application program classification method and device
CN105453106A (en) Display privacy with dynamic configuration
CN106681587B (en) A kind of the footmark processing method and terminal of application icon
CN103324892A (en) File display method and device of Android system
CN109710571B (en) File analysis method, device and storage medium
CN108595965B (en) Method and device for preventing attribute information of interface control from being stolen
US20160125727A1 (en) Communication device and emergency help method
KR102439786B1 (en) Method for sharing content information and electronic device thereof
CN103677517A (en) Method and device for searching pictures
CN108388616B (en) Data collection device, method, system and computer readable storage medium
US9201576B2 (en) Display method and portable device
CN107819944A (en) Delet method, device, equipment and the storage medium of short message
CN111124627B (en) Method and device for determining call initiator of application program, terminal and storage medium
CN111756618A (en) Group chat processing method and device, electronic equipment and readable storage medium
CN106657316B (en) Message withdrawing method and device
CN109104481B (en) File integrity detection method, file integrity detection device and terminal equipment
CN107743151B (en) Content pushing method and device, mobile terminal and server
KR20180007792A (en) Apparatus and method for providing data based on cloud service
CN111198830B (en) Identification method and device of mobile storage equipment, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20200117

RJ01 Rejection of invention patent application after publication