Intelligent point-of-sale management system and method

Abstract

The present invention belongs to the technical field of data collection and data analysis. The present invention provides an intelligent point-burying management system and method, including: when a new version instruction is received, the version data of the historical page is obtained to update the version data of the current page; when a modified page is received, the metadata of the modified page is verified to be the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, the modified page is added to the current page; when a modified point-burying event is received, if the modified point-burying event is different from the point-burying event of the current page, the modified point-burying event is added to the current page; when a point-burying event name is received, a query statement is constructed according to the point-burying event name, so that the total number of corresponding point-burying events on the day is queried and displayed in the point-burying event document. By adding three perspectives of version, page, and new version change, the point-burying document is more three-dimensional, the existing data is better analyzed and controlled, and new point-burying requirements are added.

Description

Technical Field

[0001] The present invention relates to the technical field of data collection and data analysis, and in particular to an intelligent point-of-sale management system and method. Background Art

[0002] Business tracking refers to collecting specific behaviors of a class of users when using an app so that the company can better serve users, for example, a user clicks a button. Tracking is iterated along with the app version, and the product defines which tracking is needed, and the developer needs to implement these logics according to the documentation. In addition, due to the increasing number of tracking points caused by version iteration, omissions and errors often occur during development and implementation, so how to reduce these errors in the tracking system has become an urgent problem to be solved.

[0003] Developers hope to see the new or modified tracking points in the new version compared to the old version, while product and data analysis colleagues want to focus on the tracking points of a certain module in the current version as a whole. Currently, the document systems on the market cannot solve these two pain points at the same time. Summary of the invention

[0004] The present invention provides an intelligent tracking management method and system to solve the above problems.

[0005] The technical solution provided by the present invention is as follows:

[0006] An intelligent tracking point management system, comprising:

[0007] A new version module is used to obtain the version data of the historical page to update the version data of the current page when receiving a new version instruction; the version data includes the metadata and embedded events of the page;

[0008] A newly added modification page module is used to verify whether the metadata of the modification page is the same as the metadata of the current page when the modification page is received, and when the metadata of the modification page is different from the metadata of the current page, add the modification page to the current page;

[0009] A new modification tracking point module is added, which is used to, when receiving a modification tracking point event, add a modification tracking point event to the current page if the modification tracking point event is different from the tracking point event of the current page;

[0010] The buried point verification module is used to construct a query statement according to the buried point event name when receiving the buried point event name, so as to query the total number of corresponding buried point events on the day and display it in the buried point event document.

[0011] More preferably, it also includes:

[0012] The display judgment module is used to compare the version data of the current page with the version data of the historical page when the current page receives a click instruction, and display the target version data that is different between the version data of the current page and the version data of the historical page.

[0013] Further preferably, the display determination module is further used for:

[0014] The page traversal submodule is used to traverse the metadata of each subpage in the current page. If the subpage does not exist in the historical page, the subpage is a newly added page;

[0015] The buried point traversal submodule is used to traverse the buried point events of the subpage if the subpage exists in the historical page.

[0016] Further preferably, the tracking point traversal submodule is also used for:

[0017] If the buried event of the sub-page does not appear in the corresponding historical page, the buried event of the sub-page is a newly added buried event, and the newly added buried event is placed in the sub-page;

[0018] If the buried event of the sub-page appears on the corresponding history page and the fields are inconsistent, the buried event of the sub-page is a modified buried event, and the modified buried event is placed in the sub-page;

[0019] If the buried event of the sub-page appears on the corresponding history page and the fields are consistent, the buried event of the sub-page has not been modified and the buried event of the sub-page is skipped.

[0020] More preferably, it also includes:

[0021] The global keyword search module is used to query the database according to the version keyword to obtain the corresponding version data when receiving the version keyword.

[0022] Further preferably, the global keyword search module is also used for:

[0023] Traverse the metadata of each subpage in the current page, and if the subpage matches the keyword, put the subpage in the search result page;

[0024] If the subpage does not match the keyword, traverse the buried events of the subpage;

[0025] If the embedding event of the subpage matches the keyword, the embedding event of the subpage is placed in the subpage;

[0026] If the embedding event of the sub-page does not match the keyword, the embedding event of the sub-page is skipped.

[0027] More preferably, it also includes:

[0028] The page classification and sorting module is used to set corresponding priorities according to the relevance of the metadata of each sub-page in the current page when displaying the current page, and classify and sort the sub-pages based on the priorities.

[0029] Further preferably, the page classification and sorting module is also used for:

[0030] A priority field of digital type is set in the metadata of each sub-page, and when the results are returned, the sub-pages are sorted and returned according to the priority field.

[0031] Further preferably, it includes:

[0032] The storage module is used to store the metadata of the current page, the buried events of the current page, the metadata of the modified page, the modified buried events, and the correlation degree data of the sub-pages.

[0033] An intelligent tracking point management method, comprising:

[0034] When a new version instruction is received, the version data of the historical page is obtained to update the version data of the current page; the version data includes metadata and embedded events of the page;

[0035] When a modified page is received, verify whether the metadata of the modified page is the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, add the modified page to the current page;

[0036] When a modification tracking event is received, if the modification tracking event is different from the tracking event of the current page, a modification tracking event is added to the current page;

[0037] When a buried point event name is received, a query statement is constructed according to the buried point event name to query the total number of corresponding buried point events on the day and display them in the buried point event document.

[0038] The present invention provides an intelligent tracking point management method and system, which has at least the following beneficial effects:

[0039] 1) Structured data storage makes automatic tracking verification and big data integration possible. The three perspectives of version, page, and new version change make tracking documents more three-dimensional. Product and data colleagues can better analyze and control existing data and add new tracking requirements. Developers can see the tracking requirements related to new version changes more clearly without interference.

[0040] 2) Global search is more convenient and easier to use than traditional document tools.

[0041] 3) When adding or modifying something, the existing data will be compared to prevent duplicate event pages from being generated and to prevent inconsistent event definitions from occurring. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments:

[0043] Figure 1 It is a schematic diagram of an embodiment of an intelligent tracking point management system in the present invention;

[0044] Figure 2 It is a schematic diagram of the interface in the present invention;

[0045] Figure 3 It is a schematic diagram of an embodiment of an intelligent tracking point management system in the present invention;

[0046] Figure 4 It is a schematic diagram of an embodiment of an intelligent tracking point management system in the present invention;

[0047] Figure 5 It is a schematic diagram of an embodiment of an intelligent tracking point management system in the present invention;

[0048] Figure 6 It is a schematic diagram of an embodiment of an intelligent tracking point management system in the present invention;

[0049] Figure 7 It is a schematic diagram of an embodiment of an intelligent burial point management method in the present invention;

[0050] Figure 8 It is a schematic diagram showing the execution logic of the judgment module in the present invention;

[0051] Fig. 9 It is a schematic diagram of the execution logic of the global keyword search module in the present invention. DETAILED DESCRIPTION

[0052] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0053] In order to simplify the drawings, only the parts related to the present invention are schematically shown in each figure, and they do not represent the actual structure of the product. In addition, in order to simplify the drawings and facilitate understanding, in some figures, only one of the parts with the same structure or function is schematically drawn or marked. In this article, "one" not only means "only one", but also means "more than one".

[0054] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0055] In this document, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0056] In addition, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0057] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the specific implementation methods of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings and other implementation methods can be obtained based on these drawings without creative work.

[0058] It should be noted that in order to better illustrate the technical solution of the present invention, the following concepts are described:

[0059] Version: Corresponding to the product iteration version, each product version should establish a corresponding tracking document version, for example: APPV5.1. Contains multiple pages.

[0060] Page: corresponds to an APP or H5 page, indicating an actual application function page, such as an APP personal center page. The page contains multiple embedded events.

[0061] Tracking event: corresponds to a certain user behavior that needs to be recorded and really needs to be developed and implemented, for example: the event of a user clicking a shopping cart button. Tracking event documents contain event names, descriptions, parameter descriptions, and schematic images.

[0062] The system of the present invention is a document system that includes multiple functional modules. The product uses a functional module such as creating a new page to edit the tracking point, and the development uses a functional module to compare the new version with the previous version. Through the present invention, product and data users can better analyze and control existing data, add new tracking point requirements, and developers can see the new version change related tracking point requirements more clearly without interference.

[0063] The present invention provides an embodiment of an intelligent tracking point management system. Figure 1 As shown, specifically including:

[0064] The new version module 100 is used to obtain the version data of the historical page to update the version data of the current page when receiving the new version instruction; the version data includes the metadata and embedded events of the page.

[0065] Specifically, since the tracking point requirement is also part of the version requirement, it will also be iterated; the tracking point is often defined based on the APP function page or module, for example: the user clicks a button in the personal center.

[0066] Therefore, the new module provided in this embodiment can realize viewing documents from three perspectives: version, page, and new version additions and modifications.

[0067] In the tracking point system, programmatic checks can be performed to reduce errors such as the increasing number of tracking points caused by version iterations, and omissions and errors that often occur during development and implementation.

[0068] Among them, the new version module is used to create a new version to inherit the previous version data: inherit the previous version data, generate an identical new version, and then product colleagues use the following related functions to add and change the current version tracking event.

[0069] When creating a new version, query the database. If there is no historical version, create a new empty version; if there is a historical version, copy all the data of this historical version to the new version (we use mongodb to store data, which is a database. Copying to the new version is equivalent to adding relevant records to the database.)

[0070] The newly added modification page module 200 is used to verify whether the metadata of the modification page is the same as the metadata of the current page when the modification page is received. When the metadata of the modification page is different from the metadata of the current page, the modification page is added to the current page.

[0071] Specifically, it can include adding a new modification page. Based on a certain version, the new modification page operation will be persisted in the database. When adding a new modification, the existing data will be verified, and the operation will be rejected when duplication occurs.

[0072] A newly added modification tracking point module 300 is used for, when receiving a modification tracking point event, adding a modification tracking point event to the current page if the modification tracking point event is different from the tracking point event of the current page.

[0073] Specifically, add a new modification page tracking point, based on a certain page, and persist the new modification tracking point operation to the database. When adding a new modification, the existing data will be checked, and the operation will be rejected if duplication occurs.

[0074] The buried point verification module 400 is used to construct a query statement according to the buried point event name when receiving the buried point event name, so as to query the total number of corresponding buried point events on the day and display them in the buried point event document.

[0075] Intelligent tracking point verification, based on the document definition, constructs query conditions to query the Alibaba Cloud API and obtains the corresponding tracking point entry data. Among them, API (Application Programming Interface, application programming interface).

[0076] Regarding the intelligent verification of buried points, based on a certain version of a certain page, all the buried point event information of this page can be found from the database, and a query statement can be constructed according to the event name to query the total number of corresponding events on the day and return it to the front end to display in the event document. The intelligent verification of buried points is to display the buried point data in the document system.

[0077] The system in this embodiment is a tracking document system, which is all about defining tracking requirements around products and developing and viewing tracking requirements.

[0078] Generally speaking, this embodiment is a backend system, so the program includes a front-end interface and a back-end program. This embodiment focuses on the back-end program. Figure 2 It is the front-end interface of this embodiment.

[0079] In this embodiment, the three perspectives of version, page, and new version change make the tracking point document more three-dimensional. Product and data colleagues can better analyze and control existing data, add new tracking point requirements, and developers can see the tracking point requirements related to new version changes more clearly without interference. Global search is more convenient and easy to use than traditional document tools. When adding new modifications, it will compare existing data to prevent the generation of duplicate event pages and prevent inconsistent event definitions.

[0080] Embodiment 2

[0081] Based on the above embodiment, the parts in this embodiment that are the same as those in the above embodiment will not be repeated one by one. This embodiment provides an embodiment of an intelligent tracking point management system, which specifically includes all the modules in the first embodiment, wherein, Figure 3 As shown, it also includes:

[0082] The display judgment module 500 is used to compare the version data of the current page with the version data of the historical page when the current page receives a click instruction, and display that the version data of the current page and the version data of the historical page have different target version data.

[0083] The display judgment module further includes:

[0084] The page traversal submodule is used to traverse the metadata of each subpage in the current page. If the subpage does not exist in the historical page, the subpage is a newly added page;

[0085] The buried point traversal submodule is used to traverse the buried point events of the subpage if the subpage exists in the historical page.

[0086] The tracking point traversal submodule is also used for:

[0087] If the buried event of the sub-page does not appear in the corresponding historical page, the buried event of the sub-page is a newly added buried event, and the newly added buried event is placed in the sub-page;

[0088] If the buried event of the sub-page appears on the corresponding history page and the fields are inconsistent, the buried event of the sub-page is a modified buried event, and the modified buried event is placed in the sub-page;

[0089] If the buried event of the sub-page appears on the corresponding history page and the fields are consistent, the buried event of the sub-page has not been modified and the buried event of the sub-page is skipped.

[0090] For example, only the data that has changed between the current version and the previous version is displayed: When the user clicks on the background page to display only the tracking points that have changed from the previous version, this logic is executed:

[0091] Query the database for all data of the corresponding two versions (current version a, previous version b) and compare them according to the following logic:

[0092] 1) Traverse the pages of a:

[0093] Page a1 does not appear in version b. A1 is a newly added page. Put a1 into the result page.

[0094] Page a2 exists in version b (b2), and we continue to compare page events.

[0095] 2) Traverse a2 page events:

[0096] Event ae1 does not appear on page b2. ae1 is a newly added event. Put ae1 into the event of page a2.

[0097] Event ae2 appears on page b2 and the fields are inconsistent. ae2 is modified and put into the event of page a2.

[0098] Event ae3 appears on page b2 and has the same fields. ae3 is not modified, so the ae3 event is skipped.

[0099] According to the above logic, the returned data (pseudo code) is {pages: [a1, a2: {events: [ae1, ae2]}]}.

[0100] In this embodiment, a display judgment module is added, so that product and data colleagues can better analyze and control existing data and add new tracking requirements. Developers can see the tracking requirements related to new version changes more clearly without interference.

[0101] Embodiment 3

[0102] Based on the above embodiment, the parts in this embodiment that are the same as those in the above embodiment will not be repeated one by one. This embodiment provides an embodiment of an intelligent tracking point management system, specifically including: Figure 4 As shown, all modules of the first embodiment; or; as Figure 5 As shown, all modules in Embodiment 1 and Embodiment 2, among which, also include:

[0103] The global keyword search module 600 is used to query the database according to the version keyword to obtain the corresponding version data when a version keyword is received.

[0104] Specifically, the global keyword search module 600 is further used for:

[0105] The metadata of each sub-page in the current page is traversed, and if the sub-page matches the keyword, the sub-page is placed in the search result page.

[0106] If the sub-page does not match the keyword, the buried events of the sub-page are traversed.

[0107] If the embedding event of the sub-page matches the keyword, the embedding event of the sub-page is placed in the sub-page.

[0108] If the embedding event of the sub-page does not match the keyword, the embedding event of the sub-page is skipped.

[0109] Exemplary, global keyword search: Figure 2 The input box in the lower right corner of the page image shown corresponds to the front-end page of this function.

[0110] Query the database to obtain version data based on the specified version, and process the search according to the following logic:

[0111] 1) Traverse the page:

[0112] a) The metadata of page a1 matches the search keyword, and a1 is placed in the result page;

[0113] b) The metadata of page a2 does not match the keyword, and the search for page events of a2 continues.

[0114] 2) Traverse a2 page events:

[0115] a) Event ae1 metadata matches the keyword and puts ae1 into the a2 page event;

[0116] b) The event ae2 metadata does not match the keyword, skipping the ae2 event.

[0117] According to the above logic, the returned data (pseudo code) is {pages: [a1, a2: {events:

[0118] [ae1]}]}.

[0119] In this embodiment, a global keyword search module is newly added, which can facilitate searching version data by keyword. The global search is more convenient and easier to use than traditional document tools.

[0120] Embodiment 4

[0121] Based on the above embodiment, the parts in this embodiment that are the same as those in the above embodiment will not be repeated one by one. This embodiment provides an embodiment of an intelligent tracking point management system, specifically including: Figure 6 As shown, all modules of the first embodiment; or any combination of all modules of the second embodiment and the third embodiment; wherein, it also includes:

[0122] The page classification and sorting module 700 is used to set corresponding priorities according to the relevance of the metadata of each sub-page in the current page when displaying the current page, and classify and sort the sub-pages based on the priorities.

[0123] Specifically, the page classification and sorting module is also used to:

[0124] A priority field of digital type is set in the metadata of each sub-page, and when the results are returned, the sub-pages are sorted and returned according to the priority field.

[0125] For example, page classification and sorting: The order is very important for documents. For example, you need to put related pages such as nursery rhyme lessons, nursery rhyme lesson details, and nursery rhyme lesson albums in the APP together to facilitate product development and view related page embedding documents based on the APP functions.

[0126] A numeric priority field is set in each page metadata. When returning results, the pages are always returned in order of the priority field.

[0127] The storage module is used to store the metadata of the current page, the buried events of the current page, the metadata of the modified page, the modified buried events, and the correlation degree data of the sub-pages.

[0128] In this embodiment, the intelligent tracking management system includes two parts: document background and intelligent verification. The document background is designed to build a clear and easy-to-maintain system that can reduce ineffective communication between product (document writer) and development (implementing tracking according to the document). Intelligent verification can help development and testing improve tracking accuracy and reduce error and omission rates.

[0129] The document backend uses MongoDB as the database to store embedded document data, and implements the following functions at the data level:

[0130] The new version inherits the data of the previous version, adds a modification page, adds a modification page tracking, only displays the data that has changed between the current version and the previous version, global keyword search, and page classification sorting. Tracking intelligent verification, according to the document definition, construct query conditions to query the Alibaba Cloud API, and obtain the corresponding tracking entry data. Among them, API (Application Programming Interface, application programming interface).

[0131] In this embodiment, structured data storage makes it possible to automatically check and integrate big data. The three perspectives of version, page, and new version change make the tracking document more three-dimensional. Product and data colleagues can better analyze and control existing data and add new tracking requirements. Developers can see the tracking requirements related to new version changes more clearly without interference. Global search is more convenient and easy to use than traditional document tools. When adding new modifications, it will compare existing data to prevent the generation of duplicate event pages and prevent inconsistent event definitions.

[0132] Embodiment 5

[0133] Based on the above embodiment, the parts in this embodiment that are the same as those in the above embodiment will not be repeated one by one. This embodiment provides an intelligent tracking point management method, such as Figure 7 As shown, including:

[0134] When receiving a new version instruction, S100 obtains the version data of the historical page to update the version data of the current page; the version data includes the metadata and embedded events of the page.

[0135] S200: When a modified page is received, it is checked whether the metadata of the modified page is the same as the metadata of the current page. When the metadata of the modified page is different from the metadata of the current page, the modified page is added to the current page.

[0136] S300: When a modification embedding event is received, if the modification embedding event is different from the embedding event of the current page, a modification embedding event is added to the current page.

[0137] S400 When receiving the name of a buried point event, a query statement is constructed according to the name of the buried point event to query the total number of corresponding buried point events on the day and display it in the buried point event document.

[0138] The above steps are not in any order, but are the execution flow of different functions of the entire system. When a function is needed, it can be used directly.

[0139] Embodiment 6

[0140] Based on the above embodiment, the parts in this embodiment that are the same as those in the above embodiment will not be described one by one. This embodiment provides an intelligent tracking point management method, which may also include:

[0141] When the current page receives a click instruction, the version data of the current page is compared with the version data of the historical page, and it is displayed that the version data of the current page and the version data of the historical page have different target version data.

[0142] Preferably, when the current page receives a click instruction, the version data of the current page is compared with the version data of the historical page, and the version data of the current page and the version data of the historical page are displayed to have different target version data, such as Figure 8 As shown, specifically including:

[0143] S501 traverses the metadata of each sub-page in the current page. If the sub-page does not exist in the historical page, the sub-page is a newly added page.

[0144] Specifically, a current page includes multiple sub-pages. The specific content of each sub-page is different, but the quality inspection of each sub-page is relevant. Before adding a new page, it is necessary to check whether the new page already exists in the original page. If so, it will not be added. If not, it will be added.

[0145] In a specific scenario, when updating a version, the page may also need to be updated, but some pages will remain unchanged. Therefore, when adding a new page, the metadata of this version of the page will be traversed to determine whether to add this page.

[0146] S502: If the sub-page exists in the historical page, traverse the buried events of the sub-page.

[0147] Wherein, if the sub-page exists in the historical page, traversing the buried events of the sub-page in S502 specifically includes:

[0148] S5021 If the buried event of the sub-page does not appear in the corresponding historical page, the buried event of the sub-page is a newly added buried event, and the newly added buried event is placed in the sub-page.

[0149] S5022 If the buried event of the sub-page appears in the corresponding history page and the fields are inconsistent, the buried event of the sub-page is modified and the buried event of the sub-page is placed in the sub-page.

[0150] S5023 If the buried event of the sub-page appears on the corresponding history page and the fields are consistent, the buried event of the sub-page has not been modified, and the buried event of the sub-page is skipped.

[0151] This embodiment provides an intelligent tracking point management method, which may also include:

[0152] When a version keyword is received, a database is queried according to the version keyword to obtain corresponding version data.

[0153] When a version keyword is received, the database is queried according to the version keyword to obtain the corresponding version data, such as Fig. 9 As shown, specifically including:

[0154] S601 traverses the metadata of each sub-page in the current page, and if the sub-page matches the keyword, the sub-page is placed in the search result page.

[0155] S602: If the sub-page does not match the keyword, traverse the buried events of the sub-page.

[0156] S603: If the embedding event of the sub-page matches the keyword, the embedding event of the sub-page is placed in the sub-page.

[0157] S604: If the embedding event of the sub-page does not match the keyword, skip the embedding event of the sub-page.

[0158] When the current page is displayed, a corresponding priority is set according to the relevance of the metadata of each sub-page in the current page, and the sub-pages are classified and sorted based on the priority.

[0159] Preferably, when displaying the current page, setting a corresponding priority according to the relevance of the metadata of each subpage in the current page, and classifying and sorting the subpages based on the priority specifically includes:

[0160] A priority field of digital type is set in the metadata of each sub-page, and when the results are returned, the sub-pages are sorted and returned according to the priority field.

[0161] The intelligent tracking point management method provided by the present invention has at least the following beneficial effects: structured data storage, which makes automatic tracking point verification and big data integration possible. The three perspectives of version, page, and new version change make the tracking point document more three-dimensional, product and data colleagues can better analyze and control existing data, add new tracking point requirements, and developers can see the tracking point requirements related to new version changes more clearly without interference. Global search is more convenient and easy to use than traditional document tools. When adding new modifications, the existing data will be compared to prevent the generation of duplicate event pages and prevent the occurrence of inconsistent event definitions.

[0162] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0163] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed with hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0164] In the embodiments provided in the present application, it should be understood that the disclosed systems and methods can be implemented in other ways. Exemplarily, the system embodiments described above are merely schematic. Exemplarily, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation. Exemplarily, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0165] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0166] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0167] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. It should be noted that the content contained in the storage medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable storage media do not include electrical carrier signals and telecommunication signals.

[0168] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention, and these improvements and modifications should also be considered as the protection scope of the present invention.

Claims

1. An intelligent tracking point management system, characterized in that: The intelligent tracking point management system is a tracking point document system, including: The new version module is used to obtain the version data of the historical page to update the version data of the current page when receiving the new version instruction; the version data includes the metadata and embedded events of the page; when creating a new version, query the database, if there is no historical version, create a new empty version; if there is a historical version, copy all the data of this historical version to the new version; A newly added modification page module is used to verify whether the metadata of the modification page is the same as the metadata of the current page when the modification page is received, and when the metadata of the modification page is different from the metadata of the current page, add the modification page to the current page; A new modification tracking point module is added, which is used to, when receiving a modification tracking point event, add a modification tracking point event to the current page if the modification tracking point event is different from the tracking point event of the current page; A tracking point verification module is used to construct a query statement according to the tracking point event name when receiving the tracking point event name, so as to query the total number of corresponding tracking point events on the same day and display it in the tracking point event document; Also includes: A display judgment module, used for comparing the version data of the current page with the version data of the historical page when the current page receives a click instruction, and displaying that the version data of the current page and the version data of the historical page have different target version data; The global keyword search module is used to query the database according to the version keyword to obtain the corresponding version data when receiving the version keyword.

2. According to claim 1, the intelligent tracking point management system is characterized in that: The display judgment module further includes: The page traversal submodule is used to traverse the metadata of each subpage in the current page. If the subpage does not exist in the historical page, the subpage is a newly added page; The buried point traversal submodule is used to traverse the buried point events of the subpage if the subpage exists in the historical page.

3. According to claim 2, the intelligent point management system is characterized in that: The tracking point traversal submodule is also used for: If the buried event of the sub-page does not appear in the corresponding historical page, the buried event of the sub-page is a newly added buried event, and the newly added buried event is placed in the sub-page; If the buried event of the sub-page appears on the corresponding history page and the fields are inconsistent, the buried event of the sub-page is a modified buried event, and the modified buried event is placed in the sub-page; If the buried event of the sub-page appears on the corresponding history page and the fields are consistent, the buried event of the sub-page has not been modified and the buried event of the sub-page is skipped.

4. According to claim 1, the intelligent tracking point management system is characterized in that: The global keyword search module is also used for: Traverse the metadata of each subpage in the current page, and if the subpage matches the keyword, put the subpage in the search result page; If the subpage does not match the keyword, traverse the buried events of the subpage; If the embedding event of the subpage matches the keyword, the embedding event of the subpage is placed in the subpage; If the embedding event of the sub-page does not match the keyword, the embedding event of the sub-page is skipped.

5. According to claim 1, the intelligent tracking point management system is characterized in that: Also includes: The page classification and sorting module is used to set corresponding priorities according to the relevance of the metadata of each sub-page in the current page when displaying the current page, and classify and sort the sub-pages based on the priorities.

6. The intelligent tracking point management system according to claim 5 is characterized in that: The page classification and sorting module is also used for: A priority field of digital type is set in the metadata of each sub-page, and when the results are returned, the sub-pages are sorted and returned according to the priority field.

7. The intelligent tracking point management system according to any one of claims 1 to 6, characterized in that: include: The storage module is used to store the metadata of the current page, the buried events of the current page, the metadata of the modified page, the modified buried events, and the correlation degree data of the sub-pages.

8. An intelligent point management method, characterized in that: include: When receiving a new version instruction, obtain the version data of the historical page to update the version data of the current page; the version data includes the metadata and embedded events of the page; when creating a new version, query the database, if there is no historical version, create a new empty version; if there is a historical version, copy all the data of this historical version to the new version; When a modified page is received, verify whether the metadata of the modified page is the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, add the modified page to the current page; When a modification tracking event is received, if the modification tracking event is different from the tracking event of the current page, a modification tracking event is added to the current page; When receiving the name of the buried point event, construct a query statement according to the buried point event name, so as to query the total number of the corresponding buried point events on the day and display it in the buried point event document; When the current page receives a click instruction, the version data of the current page is compared with the version data of the historical page, and the version data of the current page and the version data of the historical page are displayed to show that there are different target version data; When a version keyword is received, a database is queried according to the version keyword to obtain corresponding version data.

Images