Method and device for acquiring buried point data, storage medium and electronic equipment

Abstract

The application discloses a method and device for acquiring buried point data, a storage medium and electronic equipment. The method comprises the following steps: acquiring parameter information corresponding to a target page of a client; the parameter information comprises a page interaction identifier; generating a buried point identifier corresponding to the page interaction identifier; acquiring a first attribute identifier and a second attribute identifier in the buried point identifier within a target time period; the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; acquiring a third attribute identifier in the buried point identifier according to the first attribute identifier and the second attribute identifier; the third attribute identifier is an association identifier used for associating a buried point information table; and determining buried point data of the target page within the target time period according to the third attribute identifier. The application solves the technical problems of inaccurate acquisition and low efficiency of buried point data in the related art.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a method and device for acquiring buried point data, a storage medium and an electronic device. BACKGROUND

[0002] Common application software collects traffic data representing user behavior, such as access page, click touch point, dwell time, advertisement exposure, etc., by using buried points. These traffic data are mainly used to adjust APP page layout, optimize user access link, analyze user focus on hot products, etc., so as to improve customer product use experience, increase page conversion rate and product transaction rate. However, in the process of collecting traffic data by using buried points, when the business is online, some pages or touch points on the page are easy to be missed, and some basic information parameter requirements are missed in the buried point scheme, such as device model, touch point position, advertisement display content, etc. The buried point code of each page or touch point needs to be written separately, which not only has a large workload, but also is easy to miss errors, thereby causing inaccurate acquisition of buried point data and low acquisition efficiency, etc. SUMMARY

[0003] The embodiments of the present application provide a method and device for acquiring buried point data, a storage medium and an electronic device, so as to at least solve the technical problems of inaccurate acquisition of buried point data and low acquisition efficiency in the related art.

[0004] According to an aspect of the embodiments of the present application, a method for acquiring buried point data is provided, including: acquiring parameter information corresponding to a target page of a client; wherein the parameter information includes a page interaction identifier; generating a buried point identifier corresponding to the page interaction identifier; acquiring a first attribute identifier and a second attribute identifier in the buried point identifier; wherein the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; acquiring a third attribute identifier in the buried point identifier according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is an association identifier used for associating a buried point information table; and determining buried point data of the target page in a target time period according to the third attribute identifier.

[0005] According to another aspect of the embodiments of the present application, there is also provided a method for acquiring buried point data, comprising: acquiring parameter information corresponding to a target page of a client; wherein the parameter information comprises a page interaction identifier; generating a buried point identifier corresponding to the page interaction identifier; acquiring a first attribute identifier and a second attribute identifier in the buried point identifier; wherein the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; acquiring a third attribute identifier in the buried point identifier according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is an association identifier used for associating a buried point information table; and determining buried point data of the target page in a target time period according to the third attribute identifier.

[0006] According to still another aspect of the embodiments of the present application, there is also provided an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the method for acquiring buried point data by using the computer program.

[0007] According to still another aspect of the embodiments of the present application, there is also provided a computer readable storage medium storing a computer program, wherein the computer program is configured to execute the method for acquiring buried point data when running.

[0008] In the embodiments of the present application, the parameter information corresponding to the target page of the client is acquired; wherein the parameter information comprises the page interaction identifier; the buried point identifier corresponding to the page interaction identifier is generated; the first attribute identifier and the second attribute identifier in the buried point identifier are acquired; wherein the first attribute identifier is the unique identifier information indicating the page interaction identifier, and the second attribute identifier is the interaction type identifier of the page interaction identifier; the third attribute identifier in the buried point identifier is acquired according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is the association identifier used for associating the buried point information table; and the buried point data of the target page in the target time period is determined according to the third attribute identifier, in the method. Since the buried point identifier corresponding to the page interaction identifier is automatically generated, and the buried point data in the client page is flexibly acquired through the buried point identifier, the accuracy of acquiring the buried point data is improved, the efficiency of acquiring the buried point data is improved, and the technical problems of inaccurate acquisition of the buried point data and low efficiency of acquisition in the related art are solved. BRIEF DESCRIPTION OF DRAWINGS

[0009] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0010] Figure 1 is a schematic diagram of an application environment of an optional buried point data acquisition method according to an embodiment of the application;

[0011] Figure 2 is a schematic diagram of an application environment of another optional buried point data acquisition method according to an embodiment of the application;

[0012] Figure 3 is a flowchart of an optional data processing according to an embodiment of the application;

[0013] Figure 4 is a flowchart of another optional buried point data acquisition method according to an embodiment of the application;

[0014] Figure 5 is a flowchart of yet another optional buried point data acquisition method according to an embodiment of the application;

[0015] Figure 6 is a structural schematic diagram of an optional data processing device according to an embodiment of the application;

[0016] Figure 7 is a structural schematic diagram of an optional electronic device according to an embodiment of the application. DETAILED DESCRIPTION

[0017] In order to make the technical personnel of the present application better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should belong to the scope of protection of the present application.

[0018] It is to be understood that the terms "first", "second", and the like used in the description and the claims of the present application as well as the above-described drawings are used to distinguish similar objects, and are not necessarily used to describe a particular sequential or chronological order. It is to be understood that the data thus used can be interchanged, where appropriate, so that the embodiments of the present application described herein can be carried out in other than the order shown or described herein. Furthermore, the terms "comprise" and "have", and any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or apparatus that comprises a list of steps or units is not necessarily limited to those steps or units that are clearly listed, but can include other steps or units that are not clearly listed or inherent to such processes, methods, products, or apparatuses.

[0019] According to an aspect of the embodiments of the present application, there is provided a method for acquiring a buried point data, which can be applied in the application environment as shown in Figure 1 The application environment includes a terminal device 102 for human-computer interaction with a user, a network 104, and a server 106. The user 108 can perform human-computer interaction with the terminal device 102, and the terminal device 102 runs a buried point management application. The terminal device 102 includes a human-computer interaction screen 1022, a processor 1024, and a memory 1026. The human-computer interaction screen 1022 is used to display page interaction identifiers of different target pages; the processor 1024 is used to acquire parameter information corresponding to a target page of a client; and the memory 1026 is used to store the parameter information corresponding to the target page of the client.

[0020] In addition, the server 106 includes a database 1062 and a processing engine 1064. The database 1062 is used to store the parameter information corresponding to the target page of the client. The processing engine 1064 is used to acquire the parameter information corresponding to the target page of the client; generate a buried point identifier corresponding to the page interaction identifier; acquire a first attribute identifier and a second attribute identifier in the buried point identifier; the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; acquire a third attribute identifier in the buried point identifier according to the first attribute identifier and the second attribute identifier; the third attribute identifier is an association identifier used to associate a buried point information table; and determine buried point data of the target page in the target time period according to the third attribute identifier.

[0021] In one or more embodiments, the method for acquiring a buried point data described above can be applied in the application environment as shown in Figure 2 Figure 2 ​As shown, the user 202 and the user equipment 204 can be in human-computer interaction. The user equipment 204 includes a memory 206 and a processor 208. In the embodiment, the user equipment 204 can, but is not limited to, refer to the terminal equipment 102 to perform the operation of obtaining the target page of the above-mentioned terminal equipment 102.

[0022] Optionally, the terminal equipment 102 and the user equipment 204 include, but are not limited to, a mobile phone, a set-top box, a television, a tablet computer, a notebook computer, a PC, a vehicle-mounted electronic device, a wearable device, and the like. The network 104 can include, but is not limited to, a wireless network or a wired network. The wireless network includes WIFI and other wireless communication networks. The wired network can include, but is not limited to, a wide area network, a metropolitan area network, and a local area network. The server 106 can include, but is not limited to, any hardware device capable of computing. The server can be a single server, a server cluster composed of multiple servers, or a cloud server. The above is only an example, and the embodiment is not limited in this regard.

[0023] As an optional implementation, as shown in the figure, Figure 3 The embodiment of the application provides a method for obtaining a page interaction identifier, and the method comprises the following steps:

[0024] S302, obtaining parameter information corresponding to a target page of a client; wherein the parameter information includes a page interaction identifier.

[0025] In the embodiment of the application, the parameter information corresponding to the client page is obtained by a software development kit (SDK), and the target page includes part or all of the pages in the client. The page interaction identifier includes a picture or a text type touch point or a button in the page. The parameter information corresponding to the target page includes a device number (a randomly generated virtual code) of a terminal where the client is located, an ID of a currently logged-in user, a user access time, an APP type, a device type (IOS, Android, etc.), a user agent (User Agent, UA), a page ID, a uniform resource locator (Uniform Resource Locator, URL), a click touch point ID (also referred to as “EVENT_ID”), and an automatic page interaction identifier (also referred to as “TAP_ID”).

[0026] S304, generating a page interaction identifier corresponding to the page interaction identifier.

[0027] Specifically, for example, the page interaction identifier POINT_ID corresponding to the product detail button identifier is 1011, and the page interaction identifier EVENT_ID is product_detail.

[0028] S306, Obtain the first attribute identifier and the second attribute identifier from the aforementioned tracking identifier; wherein, the first attribute identifier is a unique identifier indicating the aforementioned page interaction identifier, and the second attribute identifier is the interaction type identifier of the aforementioned page interaction identifier. Here, the first attribute identifier and the second attribute identifier are, but are not limited to, string identifiers.

[0029] As shown in Table (1), the first attribute is identified as EVENT_ID and the second attribute is identified as TAP_ID. Here, the second attribute identified as TAP_ID includes, but is not limited to, a string randomly generated by the SDK.

[0030] Table (1)

[0031] POINT ID EVENT ID POINT NAME 1011 product detail product detail button 1012 order submit order submit button

[0032] Table (2)

[0033] ID POINT ID TAP ID TAP NAME 1 1001 3b12f5900a107cbd My Contacts (IOS side) 2 1001 61e1974451386ed9 My Contacts (Android side) 3 1002 ae76cade57a195e8 My Messages (ver 5.0) 4 1002 97ce21dede39cb5d My Messages (ver 5.1)

[0034] S308, obtain the third attribute identifier from the above-mentioned tracking identifiers based on the first attribute identifier and the second attribute identifier; wherein, the third attribute identifier is a correlation identifier used to associate the tracking information table. Here, the third attribute identifier includes, but is not limited to, a string identifier.

[0035] Specifically, the third attribute is identified by the POINT_ID field in the above table (1) or table (2). Regardless of whether the client updates, the POINT_ID is unique. For example, the POINT_ID corresponding to the button with the same function will not change due to the version number change.

[0036] S310, determine the tracking data of the target page within the target time period based on the third attribute identifier mentioned above.

[0037] Specifically, since the POINT_ID corresponding to buttons with the same function will not change due to version number changes, the tracking data corresponding to different page identifiers in the target page can be counted based on the POINT_ID.

[0038] In this embodiment of the invention, a method is employed to obtain parameter information corresponding to the target page of the client; wherein the parameter information includes a page interaction identifier; generate a tracking identifier corresponding to the page interaction identifier; obtain a first attribute identifier and a second attribute identifier from the tracking identifier; wherein the first attribute identifier is a unique identifier indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; obtain a third attribute identifier from the tracking identifier based on the first and second attribute identifiers; wherein the third attribute identifier is an association identifier used to associate with the tracking information table; and determine the tracking data of the target page within the target time period based on the third attribute identifier. In this method, since the tracking identifier corresponding to the page interaction identifier is automatically generated, and the tracking data in the client page is flexibly obtained through the tracking identifier, not only is the accuracy of tracking data acquisition improved, but the efficiency of tracking data acquisition is also improved, thereby solving the technical problems of inaccurate and inefficient tracking data acquisition in related technologies.

[0039] In one or more embodiments, the tracking identifiers corresponding to the page interaction identifiers mentioned above include:

[0040] Obtain the operating system type of the aforementioned client; generate the aforementioned first attribute identifier corresponding to the aforementioned operating system type based on the aforementioned operating system type; wherein, the same page interaction identifier has the same aforementioned third attribute identifier in different types of operating systems.

[0041] Specifically, in this embodiment of the invention, as shown in Table (2) above, the SDK generates different TAP_IDs for the same touch point or button based on different operating system types (such as iOS, Android, PC, etc. on mobile phones), as shown in ID1 and ID2 in Table (2). ID1 and ID2 both correspond to the same third attribute identifier: POINT_ID is 1001.

[0042] In one or more embodiments, the above-mentioned generation of the tracking identifier corresponding to the above-mentioned page interaction identifier further includes:

[0043] Obtain the version information corresponding to the aforementioned client; generate the aforementioned first attribute identifier corresponding to the aforementioned version information based on the aforementioned version information; wherein, the same page interaction identifier has the same aforementioned third attribute identifier in different version information.

[0044] Specifically, in this embodiment of the invention, as shown in Table (2) above, the SDK generates different TAP_IDs for the same touch point or button on different versions of the client, such as ID1 and ID2 in Table (2). ID3 and ID3 both correspond to the same third attribute identifier: POINT_ID is 1002.

[0045] In one or more embodiments, the above-mentioned method for acquiring the buried point data further comprises:

[0046] According to the above-mentioned version information, the second attribute identifier corresponding to the above-mentioned version information is generated; wherein the same page interaction identifier has the same third attribute identifier in different version information.

[0047] Specifically, as shown in Table (3), the EVENT_ID is changed from auto_click to open_message, and the POINT_ID remains unchanged, still being 1002. In this way, the one-to-one relationship between the POINT_ID and the EVENT_ID is still ensured.

[0048] Table (3)

[0049]

[0050] In one or more embodiments, before determining the buried point data of the target page in the target time period according to the third attribute identifier, the method further comprises:

[0051] Acquiring the Chinese annotation information corresponding to the first attribute identifier.

[0052] Specifically, the buried point data reported through the SKD is identified according to the configuration information (TAP_ID) in the big data information corresponding to the client, and then the corresponding Chinese annotation (POINT_NAME) is matched.

[0053] According to the Chinese annotation information, the buried point detail data corresponding to the first attribute identifier in the target time period is cleaned.

[0054] According to the POINT_NAME, the buried point detail data in the target time period that does not meet the requirements is removed, and the incomplete data is repaired.

[0055] The cleaned buried point detail data is stored in the buried point information table.

[0056] In one or more embodiments, the determination of the buried point data of the target page in the target time period according to the third attribute identifier comprises:

[0057] The detail data corresponding to the first attribute identifier and the second attribute identifier with the same first attribute identifier in the buried point information table is merged;

[0058] According to the merged detail data, the click volume and / or the independent visitor volume of the target page are acquired.

[0059] Specifically, in the embodiments of the present application, the same contact point can change TAP ID due to APP version change, page revision and other factors, or change EVENT ID due to automatic burying being changed to custom burying, but the POINT ID of the contact point will not change and always remains unique, so that the data of different business dates, different EVENT IDs or different TAP IDs can be merged by using the POINT ID, and the continuity and consistency of the burying data are ensured.

[0060] For example, the POINT ID of a page button or a contact point can be obtained according to the TAP ID in the automatic burying information table, or the POINT ID of the button or the contact point can be obtained according to the EVENT ID in the page button or contact point information table. The burying data of the same day is merged and summarized by using the obtained POINT ID, and the summary data of each day before the POINT ID is concatenated to complete the alignment of the incremental data and the historical data of the new burying.

[0061] It is very important to collect traffic data through burying, which will directly affect product development decisions, such as Figure 4 As shown in the figure, the burying method used in the related art is manual custom burying, and the process includes the following steps:

[0062] 1) The product manager proposes a burying requirement.

[0063] 2) The analyst determines a burying scheme.

[0064] 3) The burying development engineer develops related codes, tests, and puts them online.

[0065] 4) The APP collects and reports burying data.

[0066] 5) The big data department cleans and identifies the data.

[0067] 6) The business department analyzes and uses the data, and reports the data.

[0068] However, the above process has the following technical problems:

[0069] 1. The burying requirement needs to be proposed in advance, and the burying scheme needs to be planned in advance. After the business is put online, there are problems such as no burying requirement after the development of the software, or individual pages or contact points are missed, and some basic information parameters are missed in the burying scheme, such as device model, contact position, and ad display content.

[0070] 2. The burying development complexity is high, and the code is easy to miss

[0071] Each page or contact point burying code needs to be written separately, and errors and omissions are easy to occur, causing the reported data to not meet the original burying scheme.

[0072] 3. Buried points online must follow the APP release version, and the iteration cost is high

[0073] Because the buried point code and other APP function codes are written together, they must be released together with the online version, affecting software development efficiency.

[0074] 4. The traffic data will be missing before the buried point goes online, and it cannot be backfilled

[0075] The buried point code can only report the collected data after it goes online, so before the correct buried point goes online, data cannot be collected. Once the above 1 or 2 occurs, data will be missing, and the missing data cannot be backfilled afterwards, affecting business analysis and product iteration.

[0076] To solve the above technical problems, based on the above embodiments, as Figure 5 shown, in an application embodiment, the buried point data acquisition method further includes the following contents:

[0077] 1. Develop an automatic buried point special SDK

[0078] SDK is a collection of development tools for specific software packages, software frameworks, hardware platforms, operating systems, etc. when developing application software, so that everyone can use it directly and reduce the cost of repeated development.

[0079] In the embodiment of the application, the SDK is written in JAVA, and the main content is to report buried point information. The reporting parameters mainly include: device number (randomly generated virtual number), current login user ID, user access time, APP type, device type (IOS, Android, etc.), user agent (User Agent, UA), access page ID, uniform resource locator (Uniform Resource Locator, URL), click touch point ID (also known as "EVENT_ID"), automatic buried point ID (also known as "TAP_ID") and the like.

[0080] 2. When a new business development page is added, the SDK developed in step 1 is included by default.

[0081] 3. After the newly added page goes online, the SDK starts working and automatically collects and reports all parameters configured in step 1.

[0082] 4. Collect automatic buried point data and do basic cleaning before entering the database. Unconfigured automatic buried point data processing ends at this step. If related information needs to be configured, go to step 6.

[0083] 5. Use the automatic buried point ID (TAP_ID) reported in step 1 to identify and filter related data through the buried point data table in step 4 to meet the needs of business analysis.

[0084] 6. In order to make the automatic burying point data more convenient to use and more suitable for human reading needs, configure the automatic burying point ID (TAP_ID) that they need to use, the corresponding Chinese annotation (POINT_NAME), and some other touch point information in the burying point management system.

[0085] 7. The big data will identify the reported automatic burying point data according to the configuration information (TAP_ID) in step 6, match the corresponding Chinese annotation (POINT_NAME), and store the detailed data, through Chinese quick identification, extraction or filtering of related burying point detailed data.

[0086] 8. The big data identifies and classifies the reported data of different business dates, different EVENT_IDs or different TAP_IDs according to the POINT_ID by cleaning and converting the detailed data in step 7, and then aggregates and statistics the click access quantity (Page View, PV) of each page or touch point, independent visitor (Unique Visitor, UV), etc., and then stores the statistical data, through the subsequent automatically generated report forms such as report forms and boards, to directly see the merged burying point statistical data.

[0087] In the embodiment of the application, the same touch point may change TAP_ID due to APP version change, page revision and other factors, or EVENT_ID change due to automatic burying point change to custom burying point, but the POINT_ID will not change, and it will always maintain its uniqueness. Therefore, it can realize the merging of data of different business dates, different EVENT_IDs or different TAP_IDs, and guarantee the coherence and consistency of burying point data in time.

[0088] The embodiment of the application also has the following beneficial technical effects:

[0089] 1. Compared with the prior art of planning burying point requirements before the business goes online, the embodiment of the application obtains burying point data through the burying point identification automatic allocation method, without the need for product managers and analysts to intervene in the early stage, saving human cost and improving the efficiency of burying point acquisition.

[0090] 2. The automatic burying point is realized through the encapsulated SDK, and all burying point development engineers can reuse it, without the need to develop code for each page and each touch point one by one, greatly reducing the development workload, improving the work efficiency, reducing the failure rate, and guaranteeing the completeness and accuracy of information.

[0091] 3. When new parameters are needed due to business expansion, modifying the SDK and issuing it can realize the adjustment of the reporting rules, and all historical configured automatic burying points are updated simultaneously, greatly reducing the maintenance cost.

[0092] 4. Adding or modifying automatic event tracking points can be controlled via SDK configuration switches, taking effect immediately upon configuration, with virtually no development cost, no need to wait for version release, and extremely high iteration efficiency.

[0093] 5. Once the business goes live, the event tracking data can be collected. The automatic event tracking configuration information will not affect the use of the event tracking data, regardless of whether it is filled in or when it is filled in, thus ensuring the continuity of the data and guaranteeing the needs of business analysis.

[0094] 6. In this embodiment of the invention, based on the changes in the tracking ID caused by version updates, the touch point and tracking ID are set to a one-to-many mapping relationship. The tracking IDs of different versions are connected and merged through a unique physical primary key, thus ensuring the continuity of tracking data.

[0095] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0096] According to another aspect of the present invention, a device for acquiring embedded data for implementing the above-described embedded data acquisition method is also provided. For example... Figure 6 As shown, the device includes:

[0097] The first acquisition unit 602 is used to acquire parameter information corresponding to the target page of the client; wherein, the parameter information includes page interaction identifier;

[0098] The first generation unit 604 is used to generate the tracking point identifiers corresponding to the above-mentioned page interaction identifiers.

[0099] The second acquisition unit 606 is used to acquire the first attribute identifier and the second attribute identifier in the above-mentioned tracking identifier; wherein, the first attribute identifier is a unique identifier that indicates the page interaction identifier, and the second attribute identifier is the interaction type identifier of the page interaction identifier.

[0100] The third acquisition unit 608 is used to acquire the third attribute identifier in the above-mentioned tracking identifier based on the first attribute identifier and the second attribute identifier; wherein, the third attribute identifier is an association identifier used to associate the tracking information table.

[0101] The determining unit 610 is used to determine the embedded data of the target page within the target time period based on the third attribute identifier.

[0102] In the embodiment of the present application, the parameter information corresponding to the target page of the client is acquired; wherein the parameter information includes a page interaction identifier; the page interaction identifier is generated; the first attribute identifier and the second attribute identifier in the page interaction identifier are acquired; wherein the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier; the third attribute identifier in the page interaction identifier is acquired according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is an association identifier used for associating a page interaction information table; and the method for determining the page interaction data of the target page in the target time period according to the third attribute identifier is determined; in the method, the page interaction identifier is automatically generated, and the page interaction data in the client page is flexibly acquired through the page interaction identifier, which not only improves the accuracy of the page interaction data acquisition, but also improves the efficiency of the page interaction data acquisition, thereby solving the technical problems of inaccurate and low-efficiency page interaction data acquisition in the related art.

[0103] In one or more embodiments, the first generation unit 604 includes:

[0104] The first acquisition module is configured to acquire an operating system type of the client.

[0105] The first generation module is configured to generate the first attribute identifier corresponding to the operating system type according to the operating system type; wherein the same page interaction identifier has the same third attribute identifier in different types of operating systems.

[0106] In one or more embodiments, the first generation unit 604 further includes:

[0107] The second acquisition module is configured to acquire version information corresponding to the client.

[0108] The second generation module is configured to generate the first attribute identifier corresponding to the version information according to the version information; wherein the same page interaction identifier has the same third attribute identifier in different version information.

[0109] In one or more embodiments, the page interaction management device further includes:

[0110] The second generation unit is configured to generate the second attribute identifier corresponding to the version information according to the version information; wherein the same page interaction identifier has the same third attribute identifier in different version information.

[0111] In one or more embodiments, the page interaction management device further includes:

[0112] A fourth obtaining unit is configured to obtain Chinese annotation information corresponding to the first attribute identifier.

[0113] A data processing unit is configured to perform data cleaning on the detailed data of the first attribute identifier in the target time period according to the Chinese annotation information.

[0114] A storage unit is configured to store the cleaned detailed data in the burying point information table.

[0115] In one or more embodiments, the determining unit 610 comprises:

[0116] A merging module is configured to merge the detailed data corresponding to the first attribute identifier and the second attribute identifier with the same first attribute identifier in the burying point information table.

[0117] A third obtaining module is configured to obtain the click volume and / or the independent visitor volume of the target page according to the merged detailed data.

[0118] According to still another aspect of the embodiments of the present application, an electronic device for implementing the burying point data obtaining method is provided, which can be a terminal device or a server as shown in the drawings. Figure 1 The present embodiment takes the electronic device as a server for example to illustrate. As shown in the drawings, the electronic device comprises a memory 702 and a processor 704, the memory 702 stores a computer program, and the processor 704 is configured to execute the steps in any of the method embodiments by the computer program. Figure 7

[0119] Optionally, in the present embodiment, the electronic device can be located in at least one of the network devices in the computer network.

[0120] Optionally, in the present embodiment, the processor can be configured to execute the following steps by the computer program:

[0121] S1, obtaining parameter information corresponding to a target page of a client; wherein the parameter information comprises a page interaction identifier;

[0122] S2, generating a burying point identifier corresponding to the page interaction identifier;

[0123] S3, obtaining a first attribute identifier and a second attribute identifier in the burying point identifier; wherein the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier;

[0124] ​S4, obtaining a third attribute identifier in the trace point identifier according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is an association identifier used for associating a trace point information table;

[0125] S5, determining the trace point data of the target page in the target time period according to the third attribute identifier.

[0126] Optionally, those skilled in the art can understand that, Figure 7 The structure shown is only schematic, and the electronic device can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, or other terminal devices. Figure 7 It does not limit the structure of the electronic device. For example, the electronic device can further include more or less components (such as a network interface, etc.) than those shown in Figure 7 , or have a different configuration from Figure 7 .

[0127] The memory 702 can be used to store software programs and modules, such as program instructions / modules corresponding to the trace point data acquisition method and device in the embodiments of the present application. The processor 704 executes various functions and data processing by running the software programs and modules stored in the memory 702, that is, implements the trace point data acquisition method described above. The memory 702 can include a high-speed random access memory, and can also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 702 can further include a memory remotely arranged with respect to the processor 704, which can be connected to the terminal through a network. Examples of the network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. Specifically, the memory 702 can be used to store, but is not limited to, a page interaction identifier. As an example, as shown in ​ , the memory 702 can include, but is not limited to, the first acquisition unit 602, the first generation unit 604, the second acquisition unit 606, the third acquisition unit 608, and the determination unit 610 in the data processing device. In addition, it can also include, but is not limited to, other module units in the trace point data acquisition device, which will not be described in detail in this example.

[0128] Optionally, the transmission device 707 is configured to receive or send data via a network. Examples of the network include a wired network and a wireless network. In an example, the transmission device 707 includes a network adapter (NIC), which can be connected to other network devices and routers through a network cable to communicate with the Internet or a local area network. In an example, the transmission device 707 is a radio frequency (RF) module, which is configured to communicate with the Internet in a wireless manner.

[0129] In addition, the electronic device further includes a display 708 configured to display the page interaction identifier, and a connection bus 710 configured to connect various module components in the electronic device.

[0130] In other embodiments, the terminal device or the server can be a node in a distributed system, and the distributed system can be a blockchain system. The blockchain system can be a distributed system formed by the plurality of nodes communicating with each other via a network. The nodes can form a peer-to-peer (P2P) network, and any computing device, such as a server or a terminal, can become a node in the blockchain system by joining the P2P network.

[0131] In one or more embodiments, the present application also provides a computer program product or a computer program including computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to enable the computer device to perform the above-mentioned method for obtaining buried point data. The computer program is configured to execute the steps in any of the above-mentioned method embodiments when running.

[0132] Optionally, in the present embodiment, the computer readable storage medium can be configured to store a computer program for executing the following steps:

[0133] S1, obtaining parameter information corresponding to a target page of a client; wherein the parameter information includes a page interaction identifier;

[0134] S2, generating a buried point identifier corresponding to the page interaction identifier;

[0135] S3, obtaining a first attribute identifier and a second attribute identifier in the buried point identifier; wherein the first attribute identifier is unique identifier information indicating the page interaction identifier, and the second attribute identifier is an interaction type identifier of the page interaction identifier;

[0136] S4, obtaining a third attribute identifier in the buried point identifier according to the first attribute identifier and the second attribute identifier; wherein the third attribute identifier is an association identifier used for associating a buried point information table;

[0137] S5, determining the buried point data of the target page in the target time period according to the third attribute identifier.

[0138] Optionally, in the embodiment, all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device by a program, and the program can be stored in a computer readable storage medium, and the storage medium can include a flash disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, etc.

[0139] The serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.

[0140] The integrated units in the above embodiments, if realized in the form of software function units and sold or used as independent products, can be stored in the above computer readable storage medium. Based on such understanding, the technical solutions of the present application or the whole or part of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a plurality of instructions for causing one or more computer devices (which can be personal computers, servers or network devices, etc.) to execute all or part of the steps of the embodiments of the present application.

[0141] In the above embodiments of the present application, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0142] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented by other means. Among them, the above-mentioned device embodiments are only schematic, for example, the division of units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed each other can be through some interface, indirect coupling or communication connection between units or modules, which can be electrical or other forms.

[0143] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0144] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0145] The above is only the preferred embodiment of the present application, and it should be noted that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should be considered as the protection scope of the present application.

Claims

1. A method for acquiring embedded data, characterized in that, include: Obtain parameter information corresponding to the target page on the client; wherein, the parameter information includes page interaction identifiers; Generate the tracking identifiers corresponding to the page interaction identifiers; Obtain the first attribute identifier and the second attribute identifier from the tracking identifier; wherein, the first attribute identifier is a unique identifier that indicates the page interaction identifier, and the second attribute identifier is the interaction type identifier of the page interaction identifier; The third attribute identifier in the tracking identifier is obtained based on the first attribute identifier and the second attribute identifier; wherein, the third attribute identifier is an association identifier used to associate the tracking information table; The tracking data of the target page within the target time period is determined based on the third attribute identifier; The step of determining the tracking data of the target page within the target time period based on the third attribute identifier includes: Merge the detailed data corresponding to the first attribute identifier and the second attribute identifier with the same first attribute identifier in the tracking information table; obtain the click volume and / or unique visitor volume of the target page based on the merged detailed data; If the second attribute identifier changes or the first attribute identifier changes at the same touchpoint, the third attribute identifier remains unchanged. The third attribute identifier is used to merge the data of the embedded points with different business dates, different first attribute identifiers, or different second attribute identifiers.

2. The method according to claim 1, characterized in that, The step-by-step identifiers corresponding to the page interaction identifiers include: Obtain the operating system type of the client; Based on the operating system type, a first attribute identifier corresponding to the operating system type is generated; wherein, the same page interaction identifier has the same third attribute identifier in different types of operating systems.

3. The method according to claim 1, characterized in that, The step of generating the tracking identifier corresponding to the page interaction identifier also includes: Obtain the version information corresponding to the client; Based on the version information, a first attribute identifier corresponding to the version information is generated; wherein, the same page interaction identifier has the same third attribute identifier in different version information.

4. The method according to claim 3, characterized in that, The method further includes: Based on the version information, a second attribute identifier corresponding to the version information is generated; wherein, the same page interaction identifier has the same third attribute identifier in different version information.

5. The method according to claim 1, characterized in that, Before determining the tracking data of the target page within the target time period based on the third attribute identifier, the method further includes: Obtain the Chinese annotation information corresponding to the first attribute identifier; Based on the Chinese annotation information, the detailed data of the embedded points corresponding to the first attribute identifier within the target time period are cleaned. The cleaned embedded point details are stored in the embedded point information table.

6. A device for managing embedded data points, characterized in that, include: The first acquisition unit is used to acquire parameter information corresponding to the target page of the client. The parameter information includes page interaction identifiers; The first generation unit is used to generate the tracking identifiers corresponding to the page interaction identifiers; The second acquisition unit is used to acquire the first attribute identifier and the second attribute identifier in the tracking identifier; wherein, the first attribute identifier is a unique identifier that indicates the page interaction identifier, and the second attribute identifier is the interaction type identifier of the page interaction identifier; The third acquisition unit is used to acquire the third attribute identifier in the tracking identifier based on the first attribute identifier and the second attribute identifier; wherein, the third attribute identifier is an association identifier used to associate the tracking information table; The determining unit is used to determine the embedded data of the target page within the target time period based on the third attribute identifier; The determining unit is further configured to merge the detailed data corresponding to the first attribute identifier and the second attribute identifier with the same first attribute identifier in the tracking information table; and obtain the click volume and / or unique visitor volume of the target page based on the merged detailed data; If the second attribute identifier changes or the first attribute identifier changes at the same touchpoint, the third attribute identifier remains unchanged. The third attribute identifier is used to merge the data of the embedded points with different business dates, different first attribute identifiers, or different second attribute identifiers.

7. The apparatus according to claim 6, characterized in that, The first generation unit includes: The first acquisition module is used to acquire the operating system type of the client. The first generation module is used to generate the first attribute identifier corresponding to the operating system type according to the operating system type; wherein, the same page interaction identifier has the same third attribute identifier in different types of operating systems.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method described in any one of claims 1 to 5.

9. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 5 through the computer program.

Images