CN111338960A - Buried point data acquisition method and device - Google Patents
Buried point data acquisition method and device Download PDFInfo
- Publication number
- CN111338960A CN111338960A CN202010128119.2A CN202010128119A CN111338960A CN 111338960 A CN111338960 A CN 111338960A CN 202010128119 A CN202010128119 A CN 202010128119A CN 111338960 A CN111338960 A CN 111338960A
- Authority
- CN
- China
- Prior art keywords
- page
- native
- preset
- implementation class
- buried point
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 230000009191 jumping Effects 0.000 claims abstract description 6
- 238000012545 processing Methods 0.000 claims description 10
- 238000013480 data collection Methods 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012827 research and development Methods 0.000 abstract 1
- 230000000694 effects Effects 0.000 description 20
- 239000012634 fragment Substances 0.000 description 14
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006399 behavior Effects 0.000 description 3
- 238000009933 burial Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 3
- 238000007405 data analysis Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000010845 search algorithm Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
Abstract
The embodiment of the invention discloses a buried point data acquisition method and a device thereof, wherein the method is applied to terminal equipment, can be applied to the research and development field, and comprises the following steps: detecting whether page jumping occurs in a native page; when detecting that the native page jumps, determining page component information of the native page; if the page component information comprises a component realized based on a preset page realization class, acquiring buried point data of a non-native page through an interceptor corresponding to the preset page realization class, wherein the non-native page is a page realized based on the preset page realization class. By implementing the embodiment of the invention, the buried point data of the non-native page can be obtained.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a buried point data acquisition method and a buried point data acquisition device.
Background
The embedded point is used for recording the use behavior data of the user by adding a section of code in the page and returning the use behavior data to the server side for visual recording. At present, a page embedded point frame monitors the opening of a native page by a native page switching lifecycle monitoring method, and further collects embedded point data of the native page. However, when the non-native page is opened, the system will not trigger the native page switch lifecycle listening method.
In this case, the system cannot monitor the opening of the non-native page, so that the data of the embedded point of the non-native page cannot be collected.
Disclosure of Invention
The embodiment of the invention discloses a buried point data acquisition method and a buried point data acquisition device, which can acquire buried point data of a non-native page.
In a first aspect, an embodiment of the present invention discloses a buried point data acquisition method, where the method is applied to a terminal device, and the method may include: detecting whether page jumping occurs in a native page; when detecting that the native page jumps, determining page component information of the native page; if the page component information comprises a component realized based on a preset page realization class, acquiring buried point data of a non-native page through an interceptor corresponding to the preset page realization class, wherein the non-native page is a page realized based on the preset page realization class.
In one implementation manner, the preset page implementation class may include a first preset page implementation class and/or a second preset page implementation class; the first preset page implementation class may include a fifth generation hypertext markup language page implementation class and/or a subclass of the fifth generation hypertext markup language page implementation class, and the second preset page implementation class may include a nested page implementation class and/or a subclass of the nested page implementation class.
In an implementation manner, a specific implementation manner of obtaining the embedded point data of the non-native page through the interceptor corresponding to the preset page implementation class may be as follows: and under the condition that the preset page implementation class comprises a first preset page implementation class, acquiring the data of the embedded point of the non-native page through a first interceptor corresponding to the first preset page implementation class.
In an implementation manner, a specific implementation manner of obtaining the embedded point data of the non-native page through the interceptor corresponding to the preset page implementation class may be as follows: and under the condition that the preset page implementation class comprises the second preset page implementation class, acquiring the data of the embedded point of the non-native page through a second interceptor corresponding to the second preset page implementation class.
In one implementation, the native page may be a page of an application running in the terminal device; the specific implementation method for obtaining the buried point data of the non-native page through the interceptor corresponding to the preset page implementation class may be as follows: acquiring page information of a non-native page through an interceptor corresponding to a preset page implementation class; and if the non-native page is determined not to be the internal page of the application according to the page information of the non-native page, using the uniform resource locator of the non-native page as the buried point data of the non-native page.
In one implementation, the method may further include: if the page information of the non-native page does not include the preset page element, determining that the non-native page is not the internal page of the application, and the page information of each internal page of the application may include the preset page element.
In an implementation manner, after obtaining the buried point data of the non-native page by the interceptor corresponding to the preset page implementation class, the method may further include: and processing the data of the buried point data.
In a second aspect, an embodiment of the present invention discloses a buried point data collecting apparatus, which includes a unit for executing the method of the first aspect.
In a third aspect, an embodiment of the present invention discloses a terminal device, where the terminal device includes a memory and a processor, the memory is used for storing a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect.
In the embodiment of the invention, the non-native page can be determined to be opened through the native page by determining the page component information of the native page and determining that the page component information comprises the components realized based on the preset page implementation class. And the non-native page is realized based on the preset page realization class, so that the buried point data of the non-native page can be obtained.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a buried point data collection method according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of another buried point data collection method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a buried point data acquisition device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic flow chart of a buried point data collection method according to an embodiment of the present invention. The method is applied to a terminal device, and specifically, as shown in fig. 1, the method for acquiring buried point data according to the embodiment of the present invention may include, but is not limited to, the following steps:
s101, the terminal device detects whether page jumping occurs in the original page.
Among them, native pages may refer to Activity objects and Fragment objects in Android (Android). Activity is one of four large components of Android, and provides an interface for a user to interact with the system, and each application has one or more activities. An Activity is an application component that provides a screen through which a user can interact in order to complete a task. Such as dialing numbers, taking pictures, sending emails, looking at maps. Specifically, one user interaction interface may correspond to one Activity.
Fragment, which can also be called Fragment, is Activity dependent and cannot exist independently. There may be multiple fragments in an Activity.
The native page may be a page in the terminal device that is in an open state.
In one implementation, the specific implementation manner of detecting whether the page jump occurs in the native page may be: it is detected whether the Activity object or Fragment object calls a preset function, which may be a start () function. For example, an object corresponding to page 1 calls the start () function to jump from page 1 to page 2. It should be noted that the preset function may be set by default in the terminal device or may be customized by the user, and the terminal device may change the preset function according to the user operation, which is not limited in the embodiment of the present invention.
In one implementation, a native page may include many links that can be clicked to jump to other pages. When the terminal device detects that the user clicks the link a in the native page and can open a new page through the link a, it can be determined that the page jump is detected in the native page.
In this embodiment of the present invention, the terminal device may be a smart phone, a tablet Computer, a Personal Computer (PC), a smart television, a smart watch, a vehicle-mounted device, a wearable device, a terminal device in the future fifth Generation mobile communication technology (5G) network, and the like, which is not limited in this embodiment of the present invention.
S102, when the terminal device detects that the primary page jumps, determining page component information of the primary page.
Where a native page may include a variety of components, each component may be implemented based on a respective page implementation class. For example, the button in the native page may be implemented based on page implementation class 1, and the selection box in the native page may be implemented based on page implementation class 2.
The page component information of the native page may include information of page implementation classes corresponding to all components currently displayed by the native page. For example, when all elements in a native page are displayed, the page component information of the native page may include information of 30 page implementation classes, but the native page may display only some of the aforementioned elements at a certain time, and at this time, the page component information of the native page may include information of less than 30 page implementation classes. The element may be a button, a selection box, a picture, a link corresponding to a non-native page, or an element that can be displayed in other native pages. The non-native page may be displayed by clicking on a link corresponding to the non-native page.
Therefore, the terminal device can determine whether a non-native page opened by the native page exists according to the page component information of the native page.
In one implementation, the page component information may be a view tree. View is a rectangular area that can be used for drawing and can process input events for interaction, and Viewgroup is a rectangular container that can hold the View. All views in an Activity can form a tree with a root (i.e. a View tree), and the views in the Activity can be obtained by traversing the View tree. That is, through the page component information of the native page, it can be determined on which page implementation classes the elements currently displayed in the native page are implemented. In embodiments of the present application, the non-native pages may include multiple types, and each type of non-native page may be implemented based on a corresponding page implementation class. For example, the non-native pages include a first type of non-native pages implemented based on page implementation class 1 and a second type of non-native pages implemented based on page implementation class 2. At this time, the terminal device may determine whether the first type of non-native page is opened through the native page by determining whether the page component information of the native page includes a component implemented based on the page implementation class 1, and the first type of non-native page is currently in an opened state. The View tree may include a View and a subclass of an inheritance View, such as a subclass of a View, for example, TextView, ImageView, surfaview, and the like.
S103, if the page component information comprises a component realized based on a preset page realization class, the terminal equipment obtains the buried point data of a non-native page through an interceptor corresponding to the preset page realization class, wherein the non-native page is a page realized based on the preset page realization class.
Specifically, after determining the page component information of the native page, the terminal device may determine whether the page component information includes a component implemented based on a preset page implementation class. The preset page implementation class may include a first preset page implementation class and/or a second preset page implementation class; the first preset page implementation class may include a fifth generation Hypertext Markup Language (HTML) page implementation class (H5 for short) and/or a subclass of the H5page implementation class, and the second preset page implementation class may include a nested page implementation class and/or a subclass of the nested page implementation class.
In one implementation, the component implemented based on the H5page implementation class may be a WebView rendering-based H5page, and the component implemented based on the nested page implementation class may be a nested page implemented based on a ViewPager. If a component implemented based on the H5page implementation class exists in the view tree (i.e., the page component information) corresponding to the native page, it may indicate that the H5page is opened through the native page. If the component realized based on the nested page implementation class exists in the view tree (i.e., the page component information) corresponding to the native page, it may be indicated that the nested page is opened through the native page.
It should be noted that, at present, the nested page implemented based on ViewPager is not recognized as a page by the system, in other words, the nested page does not belong to a page from a technical aspect, but is a part of a page composition. The nested pages can be switched by clicking a tab (tab key) key on the keyboard or by a slide switch operation in general. These switching behaviors are also page switching in the aspect of business, but the switching of the nested page cannot be monitored technically, and the data of the embedded page cannot be obtained. In the embodiment of the application, through the page component information of the native page, it can be determined that the nested page is opened through the native page, and the nested page is currently in an opened state. Further, buried point data in the nested page can be obtained.
In one implementation, the terminal device may traverse a view tree (i.e., page component information) of the native page through a depth-first search algorithm to determine whether a component implemented based on a preset page implementation class exists in the view tree. Because the components realized based on the preset page implementation classes are generally positioned in a deeper layer in the view tree, the search efficiency can be improved by adopting a depth-first search algorithm.
In the embodiment of the present application, the native page can be regarded as a container. The container information may be collected by a system native burial point frame, for example, the burial point data of the native page may be collected by the system native burial point frame. However, the native embedded point frame of the system cannot go deep into the container, and the embedded point data of the non-native page is collected. For example, the native site-embedding framework of the system cannot collect site data of H5page rendered based on WebView, and the native site-embedding framework of the system cannot collect site data of nested page implemented based on ViewPager, where WebView may be a browser.
The native nexus framework may refer to the nexus framework that is set by the operating system of the terminal device by default. The embodiment of the application designs a special interceptor for the non-native page, and the special interceptor is used for collecting the buried point data of the corresponding non-native page.
In an implementation manner, a specific implementation manner in which the terminal device obtains the embedded point data of the non-native page through the interceptor corresponding to the preset page implementation class may be: and under the condition that the preset page implementation class comprises a first preset page implementation class, acquiring the data of the embedded point of the non-native page through a first interceptor corresponding to the first preset page implementation class. Since the first preset page implementation class may include the H5page implementation class and/or the H5page implementation class, the page-embedded data of the page type H5page is obtained by the first interceptor. I.e., the non-native page at this time has a page type of H5 page.
In an implementation manner, a specific implementation manner in which the terminal device obtains the embedded point data of the non-native page through the interceptor corresponding to the preset page implementation class may be: and under the condition that the preset page implementation class comprises a second preset page implementation class, acquiring the data of the embedded point of the non-native page through a second interceptor corresponding to the second preset page implementation class. Since the second preset page implementation class may include the nested page implementation class and/or the subclass of the nested page implementation class, the page embedded data of which the page type is the nested page is obtained by the second interceptor. That is, the page type of the non-native page is a nested page at this time.
In an implementation manner, a specific implementation manner in which the terminal device obtains the embedded point data of the non-native page through the interceptor corresponding to the preset page implementation class may be: under the condition that the preset page implementation class comprises a first preset page implementation class and a second preset page implementation class, acquiring the data of the embedded point of the non-native page implemented on the basis of the first preset page implementation class through a first interceptor, and acquiring the data of the embedded point of the non-native page implemented on the basis of the second preset page implementation class through a second interceptor. The page type of the non-native page realized based on the first preset page realization class is an H5page, and the page type of the non-native page realized based on the second preset page realization class is a nested page.
By the method, different interceptors can be adopted to obtain the buried point data of different types of non-native pages, so that the acquisition efficiency of the buried point data can be improved. In one implementation, the data type of the buried point data for different types of non-native pages may be different. For example, when the non-native page is the H5page, the data type of the collected buried point data may be a data type corresponding to the web address. When the non-native page is a nested page, the data type of the collected buried point data can be a data type corresponding to a page title. Therefore, for different types of non-native pages, different interceptors are adopted to collect the data of the buried point, and the required data can be collected in a targeted manner, so that the collection efficiency of the data of the buried point is improved.
In this embodiment of the application, if the page component information includes a component implemented based on a preset page implementation class, the terminal device may enter an interception flow corresponding to the preset page implementation class, and then call a corresponding interceptor to collect the buried point data. When the page component information is a view tree, specifically, when a component realized based on WebView or a WebView subclass exists in the view tree, a WebView interception process can be entered, and a WebView interceptor is called to collect buried point data. When the view tree has a component realized based on the ViewPager or the subclass of the ViewPager, the ViewPager interception process can be entered, and the ViewPager interceptor is called to collect the data of the buried point.
1) WebView interception process:
the WebView interceptor can call a loading start event and a loading end event of the current WebView by a hook when a page realized based on the WebView or subclasses thereof is opened, and call the loading end event when the page realized based on the WebView or the subclasses thereof is closed. And if the loading end event is detected to be called, the WebView finishes loading the H5page, and when the WebView finishes loading the H5page, the WebView interceptor can start to collect the buried point data. When the next H5page loads or the current H5page closes, the collection of the buried point data for that H5page may stop. The buried point data may include, but is not limited to, a buried point Identification (ID), itemId, and itemType, among others. hook (also known as a hook or hook) is a system mechanism provided in Windows to replace "interrupts" under DOS. After a hook event has occurred for a particular system event, the program that made the hook event will be notified by the system upon the occurrence of the hook event, and can then respond to the event at a first time.
In one implementation, the collection process of the buried point ID may be as follows: when the WebView finishes loading the H5page, a pageView object in the window objects of the H5page is accessed by calling js (JavaScript) code. If the returned result is not null, the page 5page contains the pageView object, and then the H5page embedded point flow of the first application can be entered; if the returned result is null, that is, the H5page does not contain the pageView object, then the H5page node-embedding flow of the non-third-party application can be entered.
The pageView object may be an object held by each page of the first application, so if the pageView object exists in the H5page, the H5page may be considered as an internal page of the first application; if the H5page does not have a pageView object, the H5page may be considered a page that is not the first application (i.e., the third-party application). In one implementation, the first application may be an application internal to an enterprise.
A. H5page landed flow for first application: and acquiring the page ID from the pageView object as the embedded point ID. The buried point ID can be used to identify the page so that it can be known from which page the buried point data was collected in the later data analysis. Optionally, the itemId object and the itemType object in the pageView object may be obtained, the itemId object and the itemType object are used as extension parameters of the buried point, and the H5page type is marked as the first type. The itemId can be used for uniquely identifying the page belonging to the itemType type, the pages belonging to the same type can be rendered by the same page module, but the itemId is different, the specific data of the corresponding pages are different, and therefore the pages rendered through the same page are possibly different.
B. H5page landed flow for third party applications: the Page ID is marked as the thepirdh 5Page and the Page type is marked as the second type. Wherein the first type and the second type may be used to distinguish between pages of the first application and pages of the third party application. The mark is a first type, which can indicate that the source of the H5page is an internal page of a first application; the flag is of the second type, which may indicate that the source of the H5page is a page of a third party application.
2) ViewPager interception process:
the ViewPager interceptor may hook the load start event and the load end event of the current ViewPager. And if the loading end event is detected to be called, indicating that the ViewPager has loaded the nested page, and when the ViewPager has loaded the nested page, the ViewPager interceptor can start to collect the data of the buried point. When the native page exit event is monitored, the data collection of the nested page can be stopped.
In one implementation, the ViewPager is a container, and the ViewPager may include 1 or more nested pages, the type of each nested page may be different, a nested page may include a plurality of child nodes, and the type of each child node in the same nested page is the same. The type of child node may include Fragment or a common child node.
Specifically, the ViewPager interceptor may determine whether the type of the current ViewPager child node is Fragment or normal child node, and if the type of the current ViewPager child node is Fragment, the view pager interceptor may use an acquisition policy of the Fragment child node to acquire the buried point data, and if the type of the current ViewPager child node is normal child node, the view pager interceptor may use an acquisition policy of the normal child node to acquire the buried point data. When the types of the ViewPager child nodes are different, developers/testers can more conveniently analyze data sources when checking buried point data by adopting different acquisition strategies. For example, when the developer checks the buried point data, it can quickly locate in which Fragment of which Activity the buried point data was captured.
The collection strategy of Fragment child node may be: and acquiring the class name of the host Activity and the class name of the current Fragment as the embedded point ID, wherein the embedded point ID is in the format of the Activity class name # Fragment class name. Wherein, the host Activity is the Activity depended by the Fragment child node.
The collection strategy of the common child node may be: and acquiring the Activity class name of the host and a character string returned by the getTitle function as a buried point ID, wherein the format of the buried point ID is the Activity class name # Title. Wherein, the Title after the # number is the character string returned by the getTitle function. Wherein, the character string returned by the getTitle function is: the title of the nested page is directly returned, so that the nested page can be quickly known through the title, and the data analysis efficiency is improved. It should be noted that the titles of different nested pages in the ViewPager may be different, and a page title may uniquely identify one nested page.
Optionally, if the current nested page does not include a title, that is, the getTitle function returns to null, the terminal device may obtain the Activity of the host and the page serial number displayed by the current ViewPager as the embedded point ID, and the format may be an Activity class name # serial number. Wherein the page sequence number can uniquely identify one nested page in the ViewPager. In one implementation, when the ViewPager includes a plurality of nested pages and the types of the nested pages are different, if the user switches the nested pages, a ViewPager child node change event may be triggered. When the ViewPager child node change event is detected, a corresponding acquisition strategy can be adopted according to the type of the current nested page.
In one implementation, after the terminal device obtains the buried point data of the non-native page, the terminal device may perform data processing on the buried point data. In one implementation, the terminal device may use the page identifier of the non-native page as a buried point identifier (i.e., a buried point ID); the specific implementation of the terminal device performing data processing on the buried point data may be as follows: and storing the embedded point identification and the embedded point data in an associated manner. In this way, when the buried point data is checked later, the source of the buried point data can be determined through the buried point identifier (namely, the page identifier).
In an implementation manner, the specific implementation manner of the terminal device performing data processing on the buried point data may be: and adding a session identification (namely a session ID), a page serial number, access time, a user telephone number or a network access mode of equipment to the buried point data, and the like. In this way, the buried point data can be divided by the session ID, which facilitates management of the buried point data. The session ID may be a session ID of a Protocol Data Unit (PDU) session.
In the embodiment of the invention, the non-native page can be determined to be opened through the native page by determining the page component information of the native page and determining that the page component information comprises the components realized based on the preset page implementation class. And the non-native page is realized based on the preset page realization class, so that the buried point data of the non-native page can be obtained.
Referring to fig. 2, fig. 2 is a schematic flow chart of another buried point data collection method according to an embodiment of the present invention. The method is applied to a terminal device, and specifically, as shown in fig. 2, the method for acquiring buried point data according to the embodiment of the present invention may include, but is not limited to, the following steps:
s201, the terminal device detects whether page jumping occurs in a native page, wherein the native page is a page of an application running in the terminal device.
S202, when the terminal device detects that the primary page jumps, determining page component information of the primary page.
It should be noted that, the execution processes of step S201 to step S202 may refer to the specific descriptions in step S101 to step S102 in fig. 1, which are not described herein again.
And S203, if the page component information includes a component realized based on a preset page realization class, the terminal device obtains the page information of the non-native page through an interceptor corresponding to the preset page realization class.
The page information may include all page elements displayed in the non-native page, wherein the page elements may include, but are not limited to, one or more of buttons, icons, text boxes, characters, links, pictures, and other page elements. In one implementation, the page information may include the buried point data of the non-native page and may also include attribute information of the non-native page.
And S204, if the non-native page is determined not to be the internal page of the application according to the page information of the non-native page, the terminal equipment takes the uniform resource locator of the non-native page as the buried point data of the non-native page.
Specifically, the terminal device determines that the non-native page is not an internal page of the application, and may use a Uniform Resource Locator (URL) of the non-native page as the buried point data of the non-native page. Because the non-native page is not an internal page of the application, namely the non-native page is from a third-party application, the URL of the non-native page is used as the data of the embedded point of the non-native page, so that the non-native page can be obtained through the URL when the data of the embedded point is analyzed at a later stage, and the data of the embedded point can be better analyzed. For example, when the buried point data is analyzed subsequently, it is possible to confirm that a certain buried point data is in question, or to confirm which page is a specific page corresponding to the buried point data by url.
In one implementation, if the page information of the non-native page does not include the preset page element, it may be determined that the non-native page is not an internal page of the application, and the page information of each internal page of the application includes the preset page element. The preset page element may be any one or more of the aforementioned page elements. For example, the preset page may be an identifier of the application, such as a trademark (logo) of the application. The preset page elements can be set by default by the terminal device or can be customized by a user, and the preset page elements are not limited in the embodiment of the application.
In one implementation, the terminal device may determine whether the non-native page is an internal page of the application according to attribute information in the page information. The attribute information may indicate an identification of an application to which the aforementioned non-native page belongs. If the application identifier in the attribute information of the non-native page is different from the identifier of the application, it may be determined that the non-native page is not an internal page of the application. If the application identifier in the attribute information of the non-native page is the same as the identifier of the application, it may be determined that the non-native page is an internal page of the application.
In one implementation, when the non-native page is an H5page, the attribute information of the non-native page may include objects in the H5 page. If the attribute information of the non-native page comprises a pageView object, the non-native page can be considered as an internal page of the application; if the attribute information of the non-native page does not include the pageView object, the non-native page is not considered as the internal page of the application;
in the embodiment of the application, when the non-native page is determined not to be the internal page of the application, the URL of the non-native page is used as the buried point data of the non-native page. When the data of the buried point is analyzed at the later stage, the non-native page can be obtained through the URL, so that the data of the buried point can be better analyzed.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a buried point data acquisition device according to an embodiment of the present invention, where the buried point data acquisition device may be a terminal device or a device (e.g., a chip) having a function of the terminal device. Specifically, as shown in fig. 3, the buried point data collecting device 30 may include:
a detection module 301, configured to detect whether a page jump occurs in a native page;
a determining module 302, configured to determine page component information of the native page when it is detected that the native page jumps;
an obtaining module 303, configured to obtain the embedded point data of a non-native page through an interceptor corresponding to a preset page implementation class if the page component information includes a component implemented based on the preset page implementation class, where the non-native page is a page implemented based on the preset page implementation class.
In one implementation manner, the preset page implementation class may include a first preset page implementation class and/or a second preset page implementation class; the first preset page implementation class may include a fifth generation hypertext markup language page implementation class and/or a subclass of the fifth generation hypertext markup language page implementation class, and the second preset page implementation class may include a nested page implementation class and/or a subclass of the nested page implementation class.
In an implementation manner, the obtaining module 303 may be specifically configured to obtain the embedded point data of the non-native page through a first interceptor corresponding to the first preset page implementation class when the preset page implementation class includes the first preset page implementation class.
In an implementation manner, the obtaining module 303 may be specifically configured to, under the condition that the preset page implementation class includes the second preset page implementation class, obtain the embedded point data of the non-native page through a second interceptor corresponding to the second preset page implementation class.
In one implementation, the native page may be a page of an application running in the terminal device; the obtaining module 303 may be specifically configured to obtain page information of a non-native page through an interceptor corresponding to a preset page implementation class, and if it is determined that the non-native page is not an internal page of the application according to the page information of the non-native page, use a uniform resource locator of the non-native page as buried point data of the non-native page.
In an implementation manner, the determining module 302 may be further configured to determine that the non-native page is not an internal page of the application if the page information of the non-native page does not include the preset page element, and the page information of each internal page of the application may include the preset page element.
In one implementation, the buried point data collection apparatus 30 may further include a processing module 304. The processing module 304 may be configured to perform data processing on the buried point data.
The embodiments of the present invention and the embodiments of the method shown in fig. 1-2 are based on the same concept, and the technical effects thereof are also the same, and for the specific principle, reference is made to the description of the embodiments shown in fig. 1-2, which is not repeated herein.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. The terminal device 40 may include a memory 401, a processor 402, and a communication interface 403, the memory 401, the processor 402, and the communication interface 403 being connected by one or more communication buses. Wherein the communication interface 403 is controlled by the processor 402 for transceiving information.
The Processor 402 may be a Central Processing Unit (CPU), and the Processor 402 may also be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor, and optionally, the processor 402 may be any conventional processor or the like. Wherein:
a memory 401 for storing program instructions.
A processor 402 for calling the program instructions stored in the memory 401 to cause the terminal device 40 to perform the following operations:
detecting whether page jumping occurs in a native page;
when detecting that the native page jumps, determining page component information of the native page;
if the page component information comprises a component realized based on a preset page realization class, acquiring buried point data of a non-native page through an interceptor corresponding to the preset page realization class, wherein the non-native page is a page realized based on the preset page realization class.
In one implementation manner, the preset page implementation class may include a first preset page implementation class and/or a second preset page implementation class; the first preset page implementation class may include a fifth generation hypertext markup language page implementation class and/or a subclass of the fifth generation hypertext markup language page implementation class, and the second preset page implementation class may include a nested page implementation class and/or a subclass of the nested page implementation class.
In an implementation manner, when the processor 402 executes the interceptor corresponding to the preset page implementation class to obtain the buried point data of the non-native page, the following operations may be specifically executed: and under the condition that the preset page implementation class comprises a first preset page implementation class, acquiring the data of the embedded point of the non-native page through a first interceptor corresponding to the first preset page implementation class.
In an implementation manner, when the processor 402 executes the interceptor corresponding to the preset page implementation class to obtain the buried point data of the non-native page, the following operations may be specifically executed: and under the condition that the preset page implementation class comprises the second preset page implementation class, acquiring the data of the embedded point of the non-native page through a second interceptor corresponding to the second preset page implementation class.
In one implementation, the native page may be a page of an application running in the terminal device; when the processor 402 executes the interceptor corresponding to the preset page implementation class to obtain the buried point data of the non-native page, the following operations may be specifically executed: acquiring page information of a non-native page through an interceptor corresponding to a preset page implementation class; and if the non-native page is determined not to be the internal page of the application according to the page information of the non-native page, using the uniform resource locator of the non-native page as the buried point data of the non-native page.
In one implementation, processor 402 may also perform the following operations: if the page information of the non-native page does not include the preset page element, determining that the non-native page is not the internal page of the application, and the page information of each internal page of the application may include the preset page element.
In an implementation manner, after obtaining the buried point data of the non-native page through the interceptor corresponding to the preset page implementation class, the processor 402 may further perform the following operations: and processing the data of the buried point data.
It should be noted that details that are not mentioned in the embodiment corresponding to fig. 4 and specific implementation manners of each step may refer to the embodiments shown in fig. 1 to fig. 2 and the foregoing contents, and are not described again here.
Embodiments of the present invention also provide a computer-readable storage medium, in which a computer program is stored, where the computer program includes program instructions, and the program instructions, when executed by a processor, cause the processor to execute the steps executed in the method embodiments shown in fig. 1-2.
While the invention has been described with reference to a number of embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A buried point data acquisition method is applied to terminal equipment and is characterized by comprising the following steps:
detecting whether page jumping occurs in a native page;
when detecting that the native page jumps, determining page component information of the native page;
and if the page component information comprises a component realized based on a preset page realization class, acquiring buried point data of a non-native page through an interceptor corresponding to the preset page realization class, wherein the non-native page is a page realized based on the preset page realization class.
2. The method according to claim 1, wherein the preset page implementation class comprises a first preset page implementation class and/or a second preset page implementation class; the first preset page implementation class comprises a fifth generation hypertext markup language page implementation class and/or a subclass of the fifth generation hypertext markup language page implementation class, and the second preset page implementation class comprises a nested page implementation class and/or a subclass of the nested page implementation class.
3. The method of claim 2, wherein the obtaining of the buried point data of the non-native page by the interceptor corresponding to the preset page implementation class comprises:
and under the condition that the preset page implementation class comprises the first preset page implementation class, acquiring the buried point data of the non-native page through a first interceptor corresponding to the first preset page implementation class.
4. The method of claim 2, wherein the obtaining of the buried point data of the non-native page by the interceptor corresponding to the preset page implementation class comprises:
and under the condition that the preset page implementation class comprises the second preset page implementation class, acquiring the data of the embedded point of the non-native page through a second interceptor corresponding to the second preset page implementation class.
5. The method according to claim 1, characterized in that the native page is a page of an application running in the terminal device;
the acquiring of the data of the buried point of the non-native page by the interceptor corresponding to the preset page implementation class includes:
acquiring page information of the non-native page through an interceptor corresponding to the preset page implementation class;
and if the non-native page is determined not to be the internal page of the application according to the page information of the non-native page, using the uniform resource locator of the non-native page as the buried point data of the non-native page.
6. The method of claim 5, further comprising:
if the page information of the non-native page does not include a preset page element, determining that the non-native page is not an internal page of the application, and the page information of each internal page of the application includes the preset page element.
7. The method according to any one of claims 1 to 6, wherein after the interceptor corresponding to the preset page implementation class obtains the buried point data of the non-native page, the method further comprises:
and carrying out data processing on the buried point data.
8. An apparatus for buried point data collection, the apparatus comprising means for performing the method of any one of claims 1 to 7.
9. A terminal device comprising a memory for storing a computer program comprising program instructions and a processor configured to invoke the program instructions to perform the method of any of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010128119.2A CN111338960A (en) | 2020-02-27 | 2020-02-27 | Buried point data acquisition method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010128119.2A CN111338960A (en) | 2020-02-27 | 2020-02-27 | Buried point data acquisition method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111338960A true CN111338960A (en) | 2020-06-26 |
Family
ID=71183959
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010128119.2A Pending CN111338960A (en) | 2020-02-27 | 2020-02-27 | Buried point data acquisition method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111338960A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111897613A (en) * | 2020-07-31 | 2020-11-06 | 平安普惠企业管理有限公司 | Page access method and related equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106100936A (en) * | 2016-08-10 | 2016-11-09 | 乐视控股（北京）有限公司 | Webpage method for monitoring performance and device and the webserver, client |
| CN107784065A (en) * | 2017-08-17 | 2018-03-09 | 平安壹钱包电子商务有限公司 | Business datum tracking, device, computer equipment and storage medium |
| CN109885781A (en) * | 2019-02-27 | 2019-06-14 | 百度在线网络技术（北京）有限公司 | Mix page unified view method, apparatus, equipment and storage medium |
| CN110298724A (en) * | 2019-05-22 | 2019-10-01 | 深圳壹账通智能科技有限公司 | It orders recommended method, device, computer equipment and storage medium |
| CN110298000A (en) * | 2019-05-21 | 2019-10-01 | 平安普惠企业管理有限公司 | Acquisition methods, terminal device and the medium of page parameter |
-
2020
- 2020-02-27 CN CN202010128119.2A patent/CN111338960A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106100936A (en) * | 2016-08-10 | 2016-11-09 | 乐视控股（北京）有限公司 | Webpage method for monitoring performance and device and the webserver, client |
| CN107784065A (en) * | 2017-08-17 | 2018-03-09 | 平安壹钱包电子商务有限公司 | Business datum tracking, device, computer equipment and storage medium |
| CN109885781A (en) * | 2019-02-27 | 2019-06-14 | 百度在线网络技术（北京）有限公司 | Mix page unified view method, apparatus, equipment and storage medium |
| CN110298000A (en) * | 2019-05-21 | 2019-10-01 | 平安普惠企业管理有限公司 | Acquisition methods, terminal device and the medium of page parameter |
| CN110298724A (en) * | 2019-05-22 | 2019-10-01 | 深圳壹账通智能科技有限公司 | It orders recommended method, device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111897613A (en) * | 2020-07-31 | 2020-11-06 | 平安普惠企业管理有限公司 | Page access method and related equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11068323B2 (en) | Automatic registration of empty pointers | |
| US10862906B2 (en) | Playbook based data collection to identify cyber security threats | |
| US8756593B2 (en) | Map generator for representing interrelationships between app features forged by dynamic pointers | |
| US10505960B2 (en) | Malware detection by exploiting malware re-composition variations using feature evolutions and confusions | |
| US20130318496A1 (en) | Detection of central-registry events influencing dynamic pointers and app feature dependencies | |
| CN108363662A (en) | A kind of applied program testing method, storage medium and terminal device | |
| US10491629B2 (en) | Detecting sensitive data sent from client device to third-party | |
| US20100306593A1 (en) | Automatic bug reporting tool | |
| CN110287056A (en) | Webpage error message acquisition methods and device | |
| US10291492B2 (en) | Systems and methods for discovering sources of online content | |
| US20240111809A1 (en) | System event detection system and method | |
| CN110781052A (en) | Offline monitoring method and device, computer equipment and storage medium | |
| CN109902030A (en) | A kind of method of application program of mobile phone automatic test step record and playback | |
| CN111338960A (en) | Buried point data acquisition method and device | |
| CN115017428A (en) | Information display method, device, system and storage medium | |
| US9104573B1 (en) | Providing relevant diagnostic information using ontology rules | |
| CN112463519A (en) | Flatter-based page use behavior data non-buried point statistical method, equipment and storage medium | |
| CN109684156B (en) | Monitoring method, device, terminal and storage medium based on mixed mode application | |
| US20200067985A1 (en) | Systems and methods of interactive and intelligent cyber-security | |
| CN113312263B (en) | Anomaly monitoring method and device | |
| CN113094240B (en) | Abnormality monitoring method for application program, mobile terminal and storage medium | |
| CN112559278B (en) | Method and device for acquiring operation data | |
| CN113986768A (en) | Application stability testing method, device, equipment and medium | |
| CN111427642B (en) | Data processing method, device, terminal equipment and computer readable storage medium | |
| CN111414525A (en) | Data acquisition method and device for small program, computer 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 |