CN116028321A - Buried point data acquisition method, system and storage medium - Google Patents
Buried point data acquisition method, system and storage medium Download PDFInfo
- Publication number
- CN116028321A CN116028321A CN202211677579.6A CN202211677579A CN116028321A CN 116028321 A CN116028321 A CN 116028321A CN 202211677579 A CN202211677579 A CN 202211677579A CN 116028321 A CN116028321 A CN 116028321A
- Authority
- CN
- China
- Prior art keywords
- page
- event
- buried point
- behavior
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a buried point data acquisition method, a system and a storage medium, which belong to the computer application technology and solve the problem that the existing correlation keys of user login events and behavior events cannot analyze and touch user behaviors due to different ends, and the buried point data lose the acquisition meaning, and the buried point data acquisition method comprises the following steps: step A, embedding a fully buried point SDK in a terminal for collecting behavior events; b, when a behavior event is acquired, acquiring a unique identification code of a current user from the rear end, encrypting, completing the encryption, and then sending the encrypted unique identification code to a buried point acquisition system for unified decryption; and C, performing element event fine-granularity management on the behavior event acquired by the buried point acquisition system. The behavior event is provided with the encrypted user unique identification code, so that the safety of the behavior data message is ensured, and the defects that the user event cannot be associated to the behavior event, the behavior is unoccupied and the data cannot be used due to the fact that the user login event and the behavior event are respectively acquired are overcome.
Description
Technical Field
The invention relates to a computer application technology, in particular to a buried data acquisition method, a buried data acquisition system and a storage medium.
Background
At present, with the rapid development and popularization of the internet, mobile internet, 5G and big data technologies, the production and life of people are increasingly on-line. Accordingly, for numerous online products, more records with finer granularity and more timely deep mining analysis and feedback on user behaviors are needed to meet the user demands, so that the user demands are better known, the user is better served, and more advanced buried point acquisition technology is needed. The buried point acquisition is used as one of important data infrastructures, can acquire user behaviors in real time, can support data applications such as business operation analysis, accurate marketing, user behavior analysis, intelligent recommendation and the like, and can assist business decision making and business growth.
However, the existing buried point method has the following several drawbacks.
1. For the collection of behavior events and user events, the current embedded point scheme in the industry is that the user login events and the behavior events are collected separately, and the downstream application systems are associated, but the method has great disadvantages. On the one hand, for a cross-platform inter-jump access scene, such as H5, applet and APP inter-jump access, the associated keys of a user login event and a behavior event cannot be unified due to different ends, so that a downstream application cannot complement user information to the behavior event through the associated keys, namely, cannot locate which user the current behavior belongs to, and cannot analyze and reach the user behavior, and the part of buried point data loses the meaning and value of acquisition and even wastes acquisition and storage resources;
2. event coverage is incomplete. The granularity of the acquisition content of the click event is thicker, the fields are not rich enough, the user portraits cannot be more comprehensively constructed, the user behaviors are analyzed, the requirement of the buried point needs to be lifted in advance, and the historical behavior data before the buried point cannot be traced; the user behavior data collected by the buried points cannot correspond to the background business process data, so that no further correlation analysis can be performed.
3. When a new channel of a buried point project is accessed, the problems of strong coupling among page events, the naming of click events and front-end page development are solved, event management and naming are lacked, the buried point position is managed offline through manual work, the problem that the project is in online demand management is solved, the project is not corresponding to the reported data, the development flow is greatly influenced, and the project online progress is influenced.
For the pain points, no innovation scheme is provided in the current theory and application in the industry. The new network bank data acquisition team searches out a set of system and effective fully buried point acquisition solution, and builds the fully buried point acquisition system in a project standing way. The fully buried point acquisition system can solve the problems, provides huge power for business operation and business promotion, and is produced into a fully buried point acquisition product capable of being quickly landed, and has wide market prospect.
Disclosure of Invention
In view of the above, the invention provides a fully buried point acquisition method to solve the problems that the existing correlation keys of user login events and behavior events are different in end, the current behavior cannot be positioned to which user, the user behavior cannot be analyzed and touched, the meaning and value of acquisition of the partially buried point data are lost, the event coverage is incomplete, and the access is not timely.
The technical scheme adopted by the invention is as follows:
a method for collecting buried data, comprising:
embedding a fully buried point SDK in the terminal for collecting behavior events; the collection behavior event comprises a collection page event, a collection click event and a collection mixing event;
when a behavior event is acquired, acquiring a unique identification code of a current user from a rear end, encrypting and completing the unique identification code to the behavior event, and then transmitting the unique identification code to a buried point acquisition system for unified decryption;
and performing element event fine-granularity management on the behavior event acquired by the buried point acquisition system based on the buried point inner pipe system.
In this technical scheme, the terminal includes: android, IOS, H5, applet; the method has the advantages that corresponding full embedded point SDKs can be embedded into different ends, the method is controllable, the application scenarios are multiple, the implementation is convenient and reliable, the mode that codes are embedded into the points is avoided, the manual development and maintenance cost is greatly reduced, the development efficiency is improved, the cost is reduced and the efficiency is improved, secondly, the behavior event is provided with an encrypted user unique identification code, the safety of a behavior data message is ensured, the defects that the user login event and the behavior event are respectively acquired, the time delay of the downstream application system for carrying out association is shortened, the generation mechanism of the cross-platform jump associated main key is different, the user event cannot be associated to the behavior event, the behavior is not dominant, and the data cannot be used are overcome. Aiming at the problem of strong coupling of page naming of a waiting product manager in a buried point development flow, the page title is sent by default, the meta event management function is added, and the problems of blind naming before development, cooperation strong coupling of front-end development and product team naming are avoided in a mode of naming according to specifications when the embedded point development flow is used.
Further, the collecting page event specifically includes: according to the fully buried point page event data model, when the monitoring controller appears on the current access page, the recorded last access page is used as a source page to complement the attribute field of the current acquisition page event, and the last access page is used as a complete page event to be sent to the fully buried point acquisition system.
In this solution, it should be noted that a complete page event includes a current page and a source page, and is used to analyze the user path, where to go from, which is essential for user path analysis.
Further, the collecting click event specifically includes: and according to the fully buried point clicking event data model, acquiring attribute fields corresponding to clicking events by monitoring all interfaces triggered by clicking actions and uploading the attribute fields to a fully buried point acquisition system.
In the technical scheme, it is required to be noted that any clicking action of a user triggers an interface, and the interface triggered by all actions is monitored to ensure that all clicking actions are acquired and collected without omission.
Further, the collecting the mixing event specifically includes: according to the fully buried point mixed event data model, acquiring attribute fields of corresponding mixed events by monitoring events except pages and clicking behaviors, and uploading the attribute fields to a fully buried point acquisition system.
In the technical scheme, besides the page access and button clicking actions of the user respectively correspond to the page collecting event and the clicking event, some actions such as APP cold start, APP entering the background, APP entering the foreground and the like are adopted to collect the cold and hot login states of the user into the mixed event and are used for adopting different recommendation mechanisms according to the cold and hot login states of the user at the downstream so as to recommend commodities to the user or analyze the behaviors of the user.
Further, for the data record with failed uploading, the terminal automatically reports the data record or manually uploads the data record again according to the uploading state of the event when the terminal is started next time, and the data record can be uploaded one by one or in batches according to the number of the data records.
In the technical scheme, the automatic reporting refers to three collected buried points, which are all sent to an HTTP service interface of a buried point collecting system in a fixed format; the upload state is classified into an upload success state and an upload failure state.
Further, the method for collecting the fully buried point SDK specifically comprises the following steps: after the user accesses, loading the full embedded point function into the memory, and then realizing the collection and reporting of page events, the collection and reporting of click events and the collection and reporting of mixed events through the full embedded point SDK.
Further, when the behavior event is collected, the unique identification code of the current user is obtained from the back end, encrypted and then completed to the behavior event, and then sent to the buried point collection system for unified decryption specifically comprises: when the user behavior triggers the fully buried point SDK and acquires a behavior event, an API interface of a service system is automatically called, a current user unique identification code is acquired from the rear end, and is encrypted and then completed to the behavior event, and the encrypted unique identification code is sent to the buried point acquisition system from the source and then decrypted uniformly. If the current user service can identify the state, namely the unique user identification code can be obtained, encryption is carried out, otherwise, the user is emptied.
In the technical scheme, the user login state is a user service identifiable state, and the other states are unrecognizable states, so that the user identity cannot be identified, and the unique user identification code cannot be obtained.
Further, the managing the element event fine granularity of the behavior event acquired by the buried point acquisition system based on the buried point inner pipe system specifically includes: based on the embedded point inner pipe system, maintaining and managing page points and clicking points of each project;
based on the buried point inner pipe system, the front end of the source carries out parameter removal processing on the page path according to the type of the terminal before the source is sent up to obtain a page I D.
Further, the step C specifically includes:
c1, maintaining and managing page points and clicking points of each project based on a buried point inner pipe system;
and C2, based on the buried point inner pipe system, the front end of the source carries out parameter removal processing on the page path according to the type of the terminal before the front end of the source is sent up to obtain a page I D. The page events of each project are limited, each page event corresponds to one UI diagram, if the page paths do not go to parameters, different users may correspond to different parameters, and there are countless page paths, which page is the current page, the page paths do not correspond to the UI diagrams one by one after going to the parameters, and the page paths are used for downstream identification of which page the user accesses to perform user behavior analysis or targeted actions such as event marketing.
The embedded point-based inner pipe system comprises the steps that the front end of a source carries out parameter removal processing on a page path according to the type of a terminal where the front end of the source is located before uploading, and the page I D is obtained specifically:
C21. if the terminal type web_type=h5, or web_type=h5uni, deleting all content in the/#/middle of the current page path curr_page_url, reserving#; delete question marks? All parameters thereafter.
C22. If the terminal type web_type=h5muti, or web_type=h5mutiv 3, the first valued part used/split after the # of the current page path curr_page_url is deleted; delete question marks? All parameters thereafter.
C23. If the terminal type web_type=h5v3, or web_type=wxmini, then the question mark of the current page path curr_page_url is deleted? All parameters thereafter.
C24. If the terminal type web_type=app, the interface class name to which the current page belongs is taken as the page I D directly by the current page path curr_page_url, and the page path referencing processing is not needed.
C3. Based on the embedded point inner pipe system, after the main data stream reaches the embedded point acquisition system, the page title alias and the click event alias of the main data stream are updated through the page point position and the click point position of the embedded point inner pipe system.
A buried data acquisition system for implementing a buried data acquisition method, comprising:
the acquisition module is used for: the method comprises the steps of acquiring at least one buried point data to be stored, wherein the buried point data are obtained when a corresponding buried point event is triggered;
the processing module is used for: after the user behavior event information acquired by the acquisition module is sent to the processing module, the processing module analyzes and translates the event attribute of each event, updates the current data stream by the point location information maintained by the buried point inner pipe system, and sends the updated current data stream to the real-time kafka message queue for convenient downstream real-time data storage and real-time behavior index calculation. Translating the gps longitude and latitude and ip address into specific countries, provinces, cities and regions; analyzing the equipment information into a specific equipment operating system, equipment brands and equipment operating system versions; decrypting the encrypted unique user identification code; translating access time stamps into a year, month, day, time, second format, and so on.
In summary, due to the adoption of the technical scheme, the beneficial effects of the invention are as follows:
according to the scheme, corresponding full-embedded point SDKs can be embedded into different ends, the method is controllable, the application scene is multiple, the implementation is convenient and reliable, the mode that codes are embedded into points is avoided, the manual naming and coding of each event are needed, the manual development and maintenance cost is greatly reduced, the development efficiency is improved, the cost is reduced and the efficiency is improved, secondly, the behavior event is provided with an encrypted user unique identification code, the safety of a behavior data message is ensured, the defects that the user login event and the behavior event are respectively acquired, the time delay of the association of a downstream application system and the generation mechanism of a cross-platform jump associated main key are different, the user event cannot be associated to the behavior event, the behavior is unowned, and the data cannot be used are overcome. Aiming at the problem of strong coupling of page naming of a waiting product manager in a buried point development flow, the page title is sent by default, the meta event management function is added, and the problems of blind naming before development, cooperation strong coupling of front-end development and product team naming are avoided in a mode of naming according to specifications when the embedded point development flow is used.
Drawings
The invention will now be described by way of example and with reference to the accompanying drawings in which:
FIG. 1 is a flow chart of a method for collecting fully buried points according to the present invention;
FIG. 2 is a schematic diagram of a method for collecting buried points according to the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, based on the embodiments of the invention, which are apparent to those of ordinary skill in the art without inventive faculty, are intended to be within the scope of the invention.
In addition, the embodiments of the present invention and the features of the embodiments may be combined with each other without collision.
In addition, the embodiments of the present invention and the features of the embodiments may be combined with each other without collision.
Examples
As shown in fig. 1-2, the embodiment of the invention discloses a buried data acquisition method, which comprises the following steps:
a method for collecting buried data, comprising:
step A, embedding a fully buried point SDK in a terminal for collecting behavior events; the collection behavior event comprises a collection page event, a collection click event and a collection mixing event;
in step a, the terminal type includes: android, IOS, H5, applet;
the fields of the page event collection include: channel unique identification app_id, encrypted user unique identification e_useid, event type event_type, device cache identification token, session sequence number post_num, terminal type web_type, access behavior timestamp log_time, gps longitude gps_lon, gps latitude gps_last, front end version number code_version, current page path current_page_url, source page path src_page_url, current page title current_page_title, source page title src_page_title, device unique identification dev_id, device vendor dev_company;
the fields of the click event collection include: channel unique identification app_id, encrypted user unique identification e_useid, event type event_type, device cache identification token, session sequence number post_num, terminal type web_type, access behavior timestamp log_time, gps longitude gps_lon, gps latitude gps_last, front end version number code_version, click event unique identification click_id, click event name click_name, element text content elmt_content, element tag type elmt_type, element class name elmt_class, element selector elmt_selector, current page path current_page_url, source page path src_page_url, current page title current_page_title, source page title page_title, device unique identification dev_id, device vendor dev_company;
the fields of the mixed event collection include: channel unique identification app_id, encrypted user unique identification e_useid, event type event_type, device cache identification token, session sequence number post_num, terminal type web_type, access behavior timestamp log_time, gps longitude gps_lon, gps latitude gps_last, front-end version number code_version, hot and cold login status hot_cold_ind, device unique identification dev_id, device vendor dev_company, custom content self_defined_content;
the method for collecting the fully buried point SDK in the step A specifically comprises the following steps: after the user accesses, loading the full embedded point function into the memory, and then realizing page event acquisition and reporting, click event acquisition and reporting and mixed event acquisition and reporting through the full embedded point SDK;
the collecting page event in the step a specifically includes:
a1, according to a fully buried point page event data model, when a monitoring controller appears on a current access page, automatically completing an attribute field corresponding to a page event of a page source page and an attribute field corresponding to a page event of the current page, and taking the attribute fields as complete page events to be sent to a fully buried point acquisition system; and when the page event Activity and the SDK are initialized, an Application object is transmitted, then an Application is added to the Application, the Activity life cycle callback of the Activity page is obtained through the Application, then an entering page method is executed in the onactivity resource, and the entering page is reported. For page event fragments, after receiving the page OnCreate callback, add an android. Fragment. App. Fragment Life technologies callback for the class of appCompatitive Activity under the AndoridX package, and check if @ TrackPage annotation is added at onFragmentRecumed, if so, identify it as a page, and invoke page event reporting. Ignoring if no annotation is added; for Activity under the app package, and in case of API level greater than 28 (android 8.0), add android.app.fragmentmanager.fragmentlifecyclecalllbs callback, the subsequent processing logic is consistent. For activities under the application package, while the API level is less than 28, no support is made. And simultaneously, when determining that isfinish is true in the activity. Onstop, performing deregistration.
The collecting click event in the step a specifically includes:
a2, acquiring attribute fields of corresponding click events by monitoring all interfaces triggered by click actions according to the fully buried point click event data model and uploading the attribute fields to a fully buried point acquisition system; such as: acquiring and uploading TabBar click events by monitoring UITabBarController; by listening to uinating controller, the click event of the return button is acquired and sent up. The click event is realized by customizing the Gradle plugin on the basis of a transition API of Gradle. The custom Transform is after the packing flow of Apk is after the java class compilation generation, before the Dex file is generated, and at the same time, before the Dex file conversion of the third party dependency library that will be applied. Therefore, on the basis of the principle, the method pile inserting is performed. The addition of our buried point method to click events by ASM is also because it operates on the basis of class files, so we do byte code instrumentation.
The collecting and mixing event in the step A specifically comprises the following steps:
a3, according to the fully buried point mixed event data model, acquiring attribute fields of the corresponding mixed event by monitoring events except pages and clicking behaviors, and uploading the attribute fields to a fully buried point acquisition system. If the APP is monitored to be cold started, the APP enters a background, the APP enters a foreground, a cold and hot login state is obtained according to a fully buried point mixed event data model, other attributes are complemented, and the cold and hot login state is uploaded to a mixed event.
Step B, when a behavior event is acquired, acquiring a unique identification code of a current user from the rear end, encrypting and completing the unique identification code to the behavior event, and then uploading the unique identification code to a buried point acquisition system and uniformly decrypting the encrypted unique identification code;
in the step B, for the data record with failed uploading, the terminal automatically reports the data record or manually uploads the data record again according to the uploading state of the event when the terminal is started next time, and the data record can be uploaded one by one or in batches according to the number of the data record; in detail, for the data record with failed uploading, the data is locally cached, and is automatically reported when the next cold start is performed, or the page end is manually uploaded to the corresponding behavior event according to the event uploading state, and the page end can be uploaded in a piece-by-piece or batch mode according to the number of the data records. In order to avoid that the occupied space is too large due to the fact that the data is cached, the log cache adopts an LRU mechanism (Least recently used ) and the size is limited to 512K.
The step B specifically comprises the following steps: when the user behavior triggers the fully buried point SDK and acquires a behavior event, an API interface of a service system is automatically called, a current user unique identification code is acquired from the rear end, and is encrypted and then completed to the behavior event, and the encrypted unique identification code is sent to the buried point acquisition system from the source and then decrypted uniformly. If the current user service can identify the state, namely the unique user identification code can be obtained, encryption is carried out, otherwise, the user is emptied.
The encryption algorithm can use a symmetric encryption algorithm or an asymmetric encryption algorithm, and the system needing decryption can be agreed in advance.
And C, performing element event fine-granularity management on the behavior event acquired by the buried point acquisition system based on the buried point inner pipe system.
The step C specifically comprises the following steps:
c1, the aliases of the page and the clicking event can be automatically updated into the main data stream in real time along with manual maintenance and event change, and specifically comprises the following steps: based on the embedded point inner pipe system, maintaining and managing page points and clicking points of each project; the page point location mainly maintains project channel codes, page UI diagrams, page IDs (parameter removing URLs), page titles, page title aliases, creation time and closing time; the click point mainly maintains item channel code, page ID (parametrical URL), page title alias, click ID, element selector ID, click name, click alias, creation time, and closing time.
C2, based on the buried point inner pipe system, the front end of the source carries out parameter removal processing on the page path according to the type of the terminal before the source is sent up to obtain a page ID;
the embedded point inner pipe system is used for carrying out parameter removal processing on a page path by a source front end according to the type of a terminal before the source front end is sent up, and the obtaining of the page ID specifically comprises the following steps:
C21. if the terminal type web_type=h5, or web_type=h5uni, deleting all content in the/#/middle of the current page path curr_page_url, reserving#; delete question marks? All parameters thereafter.
C22. If the terminal type web_type=h5muti, or web_type=h5mutiv 3, the first valued part used/split after the # of the current page path curr_page_url is deleted; delete question marks? All parameters thereafter.
C23. If the terminal type web_type=h5v3, or web_type=wxmini, then the question mark of the current page path curr_page_url is deleted? All parameters thereafter.
C24. If the terminal type web_type=app, the interface class name of the current page is taken as the page ID directly by the current page path curr_page_url, and the page path referencing process is not needed.
C3. Based on the embedded point inner pipe system, after the main data stream reaches the embedded point acquisition system, the page title alias and the click event alias of the main data stream are updated through the page point position and the click point position of the embedded point inner pipe system. The point location alias update is updated through a Key-value mechanism of a redis cache.
C31. For key=channel unique identification app_id+page ID of the page point (current page path curr_page_url is parameterized, see step C2), value=current page title alias curr_page_title_w (default to current page title name curr_page_title).
C32. For key=channel unique identification app_id+page ID (current page path curr_page_url going parameters, see step C2) +click event unique identification click_id (element selector elmt_selector if empty), value=click event alias click_name_w (click event name is taken by default, click_name is taken when empty).
In the present specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, and identical and similar parts between the embodiments are all enough to refer to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for collecting buried data, comprising:
step A, embedding a fully buried point SDK in a terminal for collecting behavior events; the collection behavior event comprises a collection page event, a collection click event and a collection mixing event;
step B, when a behavior event is acquired, acquiring a unique identification code of a current user from the rear end, encrypting and completing the unique identification code to the behavior event, and then uploading the unique identification code to a buried point acquisition system and uniformly decrypting the encrypted unique identification code;
and C, performing element event fine-granularity management on the behavior event acquired by the buried point acquisition system based on the buried point inner pipe system.
2. The method for collecting buried data according to claim 1, wherein said collecting page event in said step a specifically comprises: according to the fully buried point page event data model, when the monitoring controller appears on the current access page, the recorded last access page is used as a source page to complement the attribute field of the current acquisition page event, and the last access page is used as a complete page event to be sent to the fully buried point acquisition system.
3. The method for collecting buried data according to claim 1, wherein said collecting click event in said step a specifically comprises: and according to the fully buried point clicking event data model, acquiring attribute fields corresponding to clicking events by monitoring all interfaces triggered by clicking actions and uploading the attribute fields to a fully buried point acquisition system.
4. The method according to claim 1, wherein the acquisition mixing event in the step a specifically includes: according to the fully buried point mixed event data model, acquiring attribute fields of corresponding mixed events by monitoring events except pages and clicking behaviors, and uploading the attribute fields to a fully buried point acquisition system.
5. The method for collecting buried data according to claim 1, wherein in the step B, for the data record with failed uploading, the terminal automatically reports the data record with failed uploading at the next cold start, or for the data record with failed uploading, the page end manually re-uploads the data record according to the event uploading state, and the page end can select to upload the data record piece by piece or in batch according to the number of the data records.
6. The method for collecting buried point data according to claim 1, wherein said method for collecting fully buried point SDK in step a specifically comprises: after the user accesses, loading the full embedded point function into the memory, and then realizing the collection and reporting of page events, the collection and reporting of click events and the collection and reporting of mixed events through the full embedded point SDK.
7. The method for collecting buried data according to claim 1, wherein said step B specifically comprises: when the user behavior triggers the fully buried point SDK and acquires a behavior event, an API interface of a service system is automatically called, a current user unique identification code is acquired from the rear end, and is encrypted and then completed to the behavior event, and the encrypted unique identification code is sent to the buried point acquisition system from the source and then decrypted uniformly; if the current user service can identify the state, namely the unique user identification code can be obtained, encryption is carried out, otherwise, the user is emptied.
8. The method for collecting buried data according to claim 1, wherein said step C specifically comprises:
c1, maintaining and managing page points and clicking points of each project based on a buried point inner pipe system;
and C2, based on the buried point inner pipe system, the front end of the source carries out parameter removal processing on the page path according to the type of the terminal before the source is sent up to obtain the page ID.
The embedded point inner pipe system is used for carrying out parameter removal processing on a page path by a source front end according to the type of a terminal before the source front end is sent up, and the obtaining of the page ID specifically comprises the following steps:
C21. if the terminal type web_type=h5, or web_type=h5uni, deleting all content in the/#/middle of the current page path curr_page_url, reserving#; delete question marks? All parameters thereafter.
C22. If the terminal type web_type=h5muti, or web_type=h5mutiv 3, the first valued part used/split after the # of the current page path curr_page_url is deleted; delete question marks? All parameters thereafter.
C23. If the terminal type web_type=h5v3, or web_type=wxmini, then the question mark of the current page path curr_page_url is deleted? All parameters thereafter.
C24. If the terminal type web_type=app, the interface class name of the current page is taken as the page ID directly by the current page path curr_page_url, and the page path referencing process is not needed.
C3. Based on the embedded point inner pipe system, after the main data stream reaches the embedded point acquisition system, the page title alias and the click event alias of the main data stream are updated through the page point position and the click point position of the embedded point inner pipe system.
9. A buried data acquisition system for implementing the buried data acquisition method according to any one of claims 1 to 8, comprising:
the acquisition module is used for: the method comprises the steps of acquiring at least one buried point data to be stored, wherein the buried point data are obtained when a corresponding buried point event is triggered;
the processing module is used for: after the user behavior event information acquired by the acquisition module is sent to the processing module, the processing module analyzes and translates the event attribute of each event, updates the current data stream by the point location information maintained by the buried point inner pipe system, and sends the updated current data stream to the real-time kafka message queue for convenient downstream real-time data storage and real-time behavior index calculation.
10. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, which is executed by a processor to implement the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211677579.6A CN116028321A (en) | 2022-12-26 | 2022-12-26 | Buried point data acquisition method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211677579.6A CN116028321A (en) | 2022-12-26 | 2022-12-26 | Buried point data acquisition method, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116028321A true CN116028321A (en) | 2023-04-28 |
Family
ID=86069920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211677579.6A Pending CN116028321A (en) | 2022-12-26 | 2022-12-26 | Buried point data acquisition method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116028321A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116610387A (en) * | 2023-07-17 | 2023-08-18 | 杭州比智科技有限公司 | Channel docking and data analysis method based on dynamic loading and bitmap |
| CN116739668A (en) * | 2023-06-26 | 2023-09-12 | 云洞(上海)科技股份有限公司 | Advertisement delivery analysis method based on full link |
| CN117591381A (en) * | 2024-01-18 | 2024-02-23 | 南京研利科技有限公司 | Data reporting method and device |
-
2022
- 2022-12-26 CN CN202211677579.6A patent/CN116028321A/en active Pending
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116739668A (en) * | 2023-06-26 | 2023-09-12 | 云洞(上海)科技股份有限公司 | Advertisement delivery analysis method based on full link |
| CN116739668B (en) * | 2023-06-26 | 2024-03-12 | 紫灿科技(上海)股份有限公司 | Advertisement delivery analysis method based on full link |
| CN116610387A (en) * | 2023-07-17 | 2023-08-18 | 杭州比智科技有限公司 | Channel docking and data analysis method based on dynamic loading and bitmap |
| CN116610387B (en) * | 2023-07-17 | 2023-10-03 | 杭州比智科技有限公司 | Channel docking and data analysis method based on dynamic loading and bitmap |
| CN117591381A (en) * | 2024-01-18 | 2024-02-23 | 南京研利科技有限公司 | Data reporting method and device |
| CN117591381B (en) * | 2024-01-18 | 2024-04-09 | 南京研利科技有限公司 | Data reporting method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11947556B1 (en) | Computerized monitoring of a metric through execution of a search query, determining a root cause of the behavior, and providing a notification thereof | |
| CN116028321A (en) | Buried point data acquisition method, system and storage medium | |
| CN107220142B (en) | Method and device for executing data recovery operation | |
| JP6482602B2 (en) | Predictive storage service | |
| US11843528B2 (en) | Lower-tier application deployment for higher-tier system | |
| WO2021031688A1 (en) | Service parameter acquisition method and apparatus, computer device and storage medium | |
| EP3047371A1 (en) | Data flow exploration | |
| US11966797B2 (en) | Indexing data at a data intake and query system based on a node capacity threshold | |
| CN106874778B (en) | Intelligent terminal file acquisition and data recovery system and method based on android system | |
| CN105743730A (en) | Method and system used for providing real-time monitoring for webpage service of mobile terminal | |
| US11841834B2 (en) | Method and apparatus for efficient synchronization of search heads in a cluster using digests | |
| US9123006B2 (en) | Techniques for parallel business intelligence evaluation and management | |
| CN112017007A (en) | User behavior data processing method and device, computer equipment and storage medium | |
| CN106407429A (en) | File tracking method, device and system | |
| CN112394908A (en) | Method and device for automatically generating embedded point page, computer equipment and storage medium | |
| CN113254320A (en) | Method and device for recording user webpage operation behaviors | |
| CN111882368B (en) | On-line advertisement DPI encryption buried point and transparent transmission tracking method | |
| WO2013056032A2 (en) | Analyzing client data stores | |
| CN102831179B (en) | web page processing method and device | |
| US11676345B1 (en) | Automated adaptive workflows in an extended reality environment | |
| CN112685270A (en) | System monitoring log acquisition method and device, electronic equipment and medium | |
| US10353792B2 (en) | Data layering in a network management system | |
| CN113515715B (en) | Buried point event code generation method, buried point event code processing method and related equipment | |
| CN107181800B (en) | Web real-time sharing implementation method for state monitoring media data | |
| CN115630170B (en) | Document recommendation method, system, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |