CN116136772A - Buried point data acquisition method and device - Google Patents

Buried point data acquisition method and device Download PDF

Info

Publication number
CN116136772A
CN116136772A CN202111356355.0A CN202111356355A CN116136772A CN 116136772 A CN116136772 A CN 116136772A CN 202111356355 A CN202111356355 A CN 202111356355A CN 116136772 A CN116136772 A CN 116136772A
Authority
CN
China
Prior art keywords
buried
point
embedded
buried point
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
Application number
CN202111356355.0A
Other languages
Chinese (zh)
Inventor
张金龙
李崇
李娟�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kunlun Digital Technology Co ltd
China National Petroleum Corp
Original Assignee
Kunlun Digital Technology Co ltd
China National Petroleum Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kunlun Digital Technology Co ltd, China National Petroleum Corp filed Critical Kunlun Digital Technology Co ltd
Priority to CN202111356355.0A priority Critical patent/CN116136772A/en
Publication of CN116136772A publication Critical patent/CN116136772A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/73Program documentation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention provides a buried point data acquisition method and device. The method comprises the following steps: injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed; if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data; the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification. The invention can reduce the complexity of the embedded point code and improve the execution efficiency of the service code.

Description

Buried point data acquisition method and device
Technical Field
The invention relates to the technical field of data processing, in particular to a buried data acquisition method and device.
Background
As software applications evolve, one or more buried points are typically placed on a software application or page in order to account for and analyze the user's behavior or events on the software application or page. The buried point is a specific data acquisition mode, and is used for capturing, processing and transmitting user behaviors or events.
At present, in the related art, when data is collected in a buried point mode, a buried point code needs to be written in a service code of a software application or a page, and in the process of using the software application or browsing the page, if a function corresponding to the buried point code is triggered, buried point data representing the triggered buried point corresponding function can be obtained.
As the number of buried points is increased, a large number of buried point codes irrelevant to service logic are written in the original service codes, so that the service codes and the buried point codes have higher coupling property, and the execution and maintenance of the service codes are not facilitated.
Disclosure of Invention
Accordingly, the present invention is directed to a method and an apparatus for collecting embedded point data, which can reduce the complexity of embedded point codes and improve the execution efficiency of service codes.
In a first aspect, the present invention provides a method for collecting buried data, the method comprising:
injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data;
the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification.
The embedding point identification is injected into the service code of the desktop end or the mobile end, and the embedding point identification comprises the following steps:
determining a buried point position and a buried point event corresponding to the buried point position in a service code of a desktop end or a mobile end;
determining respective buried point identifications of the buried points according to respective corresponding buried point events of the buried points in the service code;
and injecting the buried point identifiers corresponding to the buried point positions.
Further, before determining the embedded point position in the service code of the desktop end or the mobile end and the embedded point event corresponding to the embedded point position, the method further includes:
and packaging the buried point codes corresponding to each buried point event to obtain the buried point identification corresponding to each buried point event.
Wherein the buried point event comprises: at least one of an initialization event of a page, a click event of a page, and an exposure event of a page.
Further, after the access data of the user at the desktop end or the mobile end is collected to obtain the embedded data, the method further includes:
and transmitting the buried data in a message queue mode.
Further, after the access data of the user at the desktop end or the mobile end is collected to obtain the embedded data, the method further includes:
storing the buried data in a log;
and acquiring the embedded point data in the log through a log collecting system and sending the embedded point data in the acquired log to a message queue.
In a second aspect, the present invention provides a buried data acquisition device, which specifically includes:
the embedded point unit is used for injecting embedded point identification into the service codes of the desktop end or the mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
the acquisition unit is used for calling the embedded point identifier to acquire access data of a user at a desktop end or a mobile end to obtain embedded point data if the embedded point identifier is triggered in the execution process of the service code;
the embedded point identification is obtained by carrying out encapsulation processing on the embedded point code, and the embedded point code corresponding to the embedded point identification can be executed when the embedded point identification is called.
Wherein, the buried point unit includes:
the position subunit is used for determining the buried point position in the service code of the desktop end or the mobile end and the buried point event corresponding to the buried point position;
the searching subunit is used for determining the buried point identification corresponding to each buried point according to the buried point event corresponding to each buried point in the service code;
and the injection subunit is used for injecting the buried point identifiers corresponding to the buried point positions.
In a third aspect, the present invention provides an electronic device, comprising: a processor, a memory, a communication interface, and a communication bus; wherein,,
the processor, the communication interface and the memory complete communication with each other through a communication bus;
the processor is used for calling the computer instructions in the memory to execute the steps of the buried data acquisition method.
In a fourth aspect, the present invention provides a computer readable storage medium storing computer instructions that, when executed, cause the computer to perform the steps of the above-described buried data acquisition method.
According to the embedded point data acquisition method and device, embedded point identification is injected into the service codes of the desktop end or the mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed; if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data; the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification. The complexity of the embedded point code can be reduced, and the execution efficiency of the service code can be improved.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
For a clearer description of embodiments of the invention or of solutions in the prior art, reference will be made below for a brief description of the drawings used in the embodiments or in the prior art, it being understood that the following drawings illustrate only some embodiments of the invention and are therefore not to be considered limiting of the scope, from which other relevant drawings can be obtained, without the inventive effort of a person skilled in the art.
FIG. 1 is a schematic diagram of a first flow chart of a method for collecting buried data according to the present invention;
FIG. 2 is a schematic flow chart of a specific embodiment of step S101 in a method for collecting buried data according to the present invention;
FIG. 3 is a schematic flow chart of another embodiment of step S101 in the method for collecting buried data according to the present invention;
FIG. 4 is a schematic diagram of a second flow chart of a method for collecting buried data according to the present invention;
FIG. 5 is a schematic view of a third flow chart of a method for collecting buried data according to the present invention;
FIG. 6 is a schematic diagram of a buried data acquisition device according to the present invention;
fig. 7 is a schematic structural diagram of an electronic device provided by 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 only some embodiments of the present invention, 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, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present invention.
The embodiment of the invention provides a buried data acquisition method, which is shown in fig. 1, and specifically comprises the following steps:
s101: injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
in the step, the embedded point identification corresponding to each embedded point event is obtained by carrying out encapsulation processing on the embedded point code corresponding to each embedded point event; determining a buried point position where a buried point needs to be set in the service code and a buried point event corresponding to the buried point position; determining a buried point identifier of the buried point position according to the buried point event corresponding to the buried point position, and injecting the buried point identifier of the buried point position into the buried point position. Excessive injection of buried point codes in service codes can be avoided, so that the complexity of the buried point codes can be reduced, and the execution efficiency of the service codes is improved.
The embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification. And the buried point identification is not executed in the service code execution process.
S102: if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data;
in the step, the embedded point code corresponding to the embedded point identifier can be determined according to the embedded point identifier after the embedded point identifier is triggered by monitoring through the service code executing process. After the embedded point codes corresponding to the embedded point identifiers are executed, the access data of the user can be acquired.
After the embedded point code is executed, access data of the user can be acquired, and the acquired access data of the user is the embedded point data. For example: the user's access data includes, but is not limited to, page dwell time, page function usage, and live active users.
As can be seen from the above description, the embedded point data acquisition method provided by the present invention injects embedded point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed; if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data; the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification. The complexity of the embedded point code can be reduced, and the execution efficiency of the service code can be improved.
In an embodiment of the present invention, referring to fig. 2, step S101 in the method for collecting buried data specifically includes the following:
s1011: determining a buried point position and a buried point event corresponding to the buried point position in a service code of a desktop end or a mobile end;
s1012: determining respective buried point identifications of the buried points according to respective corresponding buried point events of the buried points in the service code;
s1013: and injecting the buried point identifiers corresponding to the buried point positions.
In this embodiment, according to the requirement of collecting user access data, a buried point position and a buried point event corresponding to the buried point position are set in the service code.
For example: and if the click data of the specific button is required to be collected, setting a buried point position at a service code corresponding to the button, and determining a buried point event of the buried point position as a click event.
Further, it is necessary to determine in advance a buried point identifier corresponding to each buried point event. When determining the respective buried point identification of each buried point according to the respective corresponding buried point event of each buried point in the service code, determining the respective corresponding buried point identification of each buried point according to the respective corresponding buried point identification of each buried point event. And injecting the buried point identifiers corresponding to the buried point positions.
Note that, in this embodiment, the buried point event includes: initialization events, click events, and exposure events. The initialization event, the click event and the exposure event each correspond to a buried point code and at least one buried point identifier.
From the above description, it can be known that the embodiment of the present invention can inject the embedded point identifier into the service code of the desktop end or the mobile end, thereby reducing the number of embedded point codes in the service code, further reducing the complexity of the embedded point codes, and improving the execution efficiency of the service code.
In an embodiment of the present invention, referring to fig. 3, step S1010 is further included before step S1011 in the above embodiment, and specifically includes the following steps:
s1010: and packaging the buried point codes corresponding to each buried point event to obtain the buried point identification corresponding to each buried point event.
In this step, corresponding buried point codes are written according to each buried point event. Buried events are mainly divided into two categories: 1) Click events, mainly describing the clicking behavior of the user in the application or on the page, such as clicking tab, clicking button, etc. 2) The page event mainly describes pages browsed by the user, such as a first page, a detail page and the like, and meanwhile, the using time of the user application is calculated through the page stay time.
The initialization event is the content of each loading of the page browsed by the user. Click events are the clicking actions of a user within an application or page. The exposure event is the content currently displayed by the user operated terminal.
The embedded point identification corresponding to the encapsulated embedded point code can be obtained by encapsulating the embedded point code. And the buried point identifier corresponding to the buried point code is the buried point identifier corresponding to the buried point event.
In this embodiment, the packaging method adopted is different according to different writing languages of the codes. For example: the embedded point code can be packaged into the embedded point identifier of. C by adopting the language C, and the embedded point code can be packaged into the embedded point identifier of. Js by adopting JavaScript grammar. The buried event includes initialization, clicking and exposure in the page.
It should be noted that, the embedded point identifier may acquire at least one data of a unique identifier of the user device, a user identifier, a program version number, a program version name, a system language, an operating system and version, an area, a mobile phone model, a mobile phone brand, a screen width, a client log generation time, a network mode, a longitude, a latitude, and a page skip front page, in addition to access data of the user.
In an embodiment of the present invention, referring to fig. 4, after step S102 in the embodiment of the method for collecting buried data, step S103 is further included, which specifically includes the following:
s103: and transmitting the buried data in a message queue mode.
When the method is applied specifically, the buried point data is sent in a message queue mode, so that the data transmission throughput, the timeliness of data transmission and the availability of data transmission in the data transmission process can be improved.
In an embodiment of the present invention, referring to fig. 5, after step S102 in the embodiment of the method for collecting buried data, the method specifically includes the following steps:
s104: storing the buried data in a log;
s105: and acquiring the embedded point data in the log through a log collecting system and sending the embedded point data in the acquired log to a message queue.
In this embodiment, when the message queue mode cannot meet the throughput and timeliness of data transmission, the buried data is stored in the log collection system; the log collection system is used for transmitting the stored embedded point data to a message queue; and further transmitting the buried data transmitted by the log collecting system in a message queue mode.
And receiving the buried point data acquired by the buried point codes through a log collecting system. Timeliness of buried data acquisition can be guaranteed, and the problem of data loss caused by high throughput of message queue transmission data can be avoided.
In this embodiment, the service receiving end adopts the programming language of the embedded point code to check whether the embedded point identifier is introduced into the page, if so, any embedded point event of clicking, exposing and page refreshing is introduced, the embedded point data is sent to the embedded point background, and finally the embedded point data is transmitted to the service receiving end through the message queue.
The embodiment of the invention provides a specific implementation manner of a buried data acquisition device capable of realizing all contents in the buried data acquisition method, and referring to fig. 6, the buried data acquisition device specifically comprises the following contents:
the embedded point unit 10 is used for injecting embedded point identifiers into service codes of the desktop end or the mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
the acquisition unit 20 is configured to invoke the buried point identifier to acquire access data of a user at a desktop end or a mobile end to obtain buried point data if the buried point identifier is triggered during the execution of the service code;
the embedded point identification is obtained by carrying out encapsulation processing on the embedded point code, and the embedded point code corresponding to the embedded point identification can be executed when the embedded point identification is called.
Wherein, the buried point unit includes:
the position subunit is used for determining the buried point position in the service code of the desktop end or the mobile end and the buried point event corresponding to the buried point position;
the searching subunit is used for determining the buried point identification corresponding to each buried point according to the buried point event corresponding to each buried point in the service code;
and the injection subunit is used for injecting the buried point identifiers corresponding to the buried point positions.
The buried point unit in the above embodiment specifically further includes the following:
and the packaging subunit is used for packaging the embedded point codes corresponding to each embedded point event to obtain the embedded point identifiers corresponding to each embedded point event.
Wherein the buried point event comprises: at least one of an initialization event of a page, a click event of a page, and an exposure event of a page.
The buried point data acquisition arrangement in the above embodiment specifically further includes the following:
and the transmission unit is used for transmitting the buried data in a message queue mode.
The buried point data acquisition arrangement in the above embodiment specifically further includes the following:
a storage unit, configured to store the buried data in a log;
and the transfer unit is used for acquiring the buried point data in the log through the log collecting system and sending the buried point data in the acquired log to the message queue.
The embodiment of the buried data acquisition device provided by the invention can be specifically used for executing the processing flow of the embodiment of the buried data acquisition method in the embodiment, and the functions of the embodiment of the buried data acquisition device are not repeated herein, and can be described in detail with reference to the embodiment of the method.
From the above description, the embodiment of the invention provides the embedded point data acquisition device, which can reduce the complexity of the embedded point code and improve the execution efficiency of the service code. Timeliness and usability of buried point data transmission can be improved, and accuracy of buried point data transmission is improved.
The embodiment of the invention provides an embodiment of an electronic device for implementing all or part of the contents in the embodiment of the method for collecting the embedded data, referring to fig. 7, the electronic device specifically includes the following contents:
processor 810, communication interface (Communications Interface) 820, memory 830, and communication bus 840, wherein processor 810, communication interface 820, memory 830 accomplish communication with each other through communication bus 840. Processor 810 may call computer instructions in memory 830 to perform the following method:
injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data;
the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification.
An embodiment of the present invention provides a computer readable storage medium for implementing all or part of the content in the embodiment of the method for collecting buried point data, where the computer readable storage medium stores computer instructions, where the computer instructions when executed cause the computer to perform all steps of the method for collecting buried point data in the above embodiment, for example, where the processor implements the following steps when executing the computer instructions:
injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data;
the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification.
Although the invention provides method operational steps as described in the examples or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one way of performing the order of steps and does not represent a unique order of execution. When implemented by an actual device or client product, the instructions may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment) as shown in the embodiments or figures.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device (system) embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the section of the method embodiments for relevance.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other. The present invention is not limited to any single aspect, nor to any single embodiment, nor to any combination and/or permutation of these aspects and/or embodiments. Moreover, each aspect and/or embodiment of the invention may be used alone or in combination with one or more other aspects and/or embodiments.
Finally, it should be noted that: the above examples are only specific embodiments of the present invention, and are not intended to limit the scope of the present invention, but it should be understood by those skilled in the art that the present invention is not limited thereto, and that the present invention is described in detail with reference to the foregoing examples: any person skilled in the art may modify or easily conceive of the technical solution described in the foregoing embodiments, or perform equivalent substitution of some of the technical features, while remaining within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the corresponding technical solutions. Are intended to be encompassed within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (10)

1. A method for collecting buried data, comprising:
injecting buried point identifiers into service codes of a desktop end or a mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
if the buried point identification is triggered in the execution process of the service code, invoking the buried point code based on the buried point identification to acquire access data of a user at a desktop end or a mobile end to obtain buried point data;
the embedded point identification is obtained by packaging the embedded point code, and the embedded point code corresponds to at least one embedded point identification.
2. The method for collecting embedded point data according to claim 1, wherein the embedding the embedded point identifier in the service code of the desktop end or the mobile end includes:
determining a buried point position and a buried point event corresponding to the buried point position in a service code of a desktop end or a mobile end;
determining respective buried point identifications of the buried points according to respective corresponding buried point events of the buried points in the service code;
and injecting the buried point identifiers corresponding to the buried point positions.
3. The method for collecting embedded points according to claim 2, further comprising, before determining the embedded point position in the service code of the desktop or mobile terminal and the embedded point event corresponding to the embedded point position:
and packaging the buried point codes corresponding to each buried point event to obtain the buried point identification corresponding to each buried point event.
4. The method of claim 2, wherein the buried point event comprises: at least one of an initialization event of a page, a click event of a page, and an exposure event of a page.
5. The method for collecting embedded data according to claim 1, further comprising, after collecting access data of the user at the desktop or the mobile terminal to obtain the embedded data:
and transmitting the buried data in a message queue mode.
6. The method for collecting embedded data according to claim 5, further comprising, after collecting the access data of the user at the desktop or mobile terminal to obtain the embedded data:
storing the buried data in a log;
and acquiring the embedded point data in the log through a log collecting system and sending the embedded point data in the acquired log to a message queue.
7. A buried data acquisition device, comprising:
the embedded point unit is used for injecting embedded point identification into the service codes of the desktop end or the mobile end; when a user accesses a page corresponding to the service code through a desktop end or a mobile end, the service code can be executed;
the acquisition unit is used for calling the embedded point identifier to acquire access data of a user at a desktop end or a mobile end to obtain embedded point data if the embedded point identifier is triggered in the execution process of the service code;
the embedded point identification is obtained by carrying out encapsulation processing on the embedded point code, and the embedded point code corresponding to the embedded point identification can be executed when the embedded point identification is called.
8. The buried point data acquisition apparatus according to claim 7, wherein said buried point unit includes:
the position subunit is used for determining the buried point position in the service code of the desktop end or the mobile end and the buried point event corresponding to the buried point position;
the searching subunit is used for determining the buried point identification corresponding to each buried point according to the buried point event corresponding to each buried point in the service code;
and the injection subunit is used for injecting the buried point identifiers corresponding to the buried point positions.
9. An electronic device, comprising: a processor, a memory, a communication interface, and a communication bus; wherein,,
the processor, the communication interface and the memory complete communication with each other through a communication bus;
the processor is configured to invoke computer instructions in the memory to perform the steps of the buried data acquisition method according to any of claims 1 to 7.
10. A computer readable storage medium storing computer instructions which, when executed, cause the computer to perform the steps of the buried data acquisition method of any of claims 1 to 7.
CN202111356355.0A 2021-11-16 2021-11-16 Buried point data acquisition method and device Pending CN116136772A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111356355.0A CN116136772A (en) 2021-11-16 2021-11-16 Buried point data acquisition method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111356355.0A CN116136772A (en) 2021-11-16 2021-11-16 Buried point data acquisition method and device

Publications (1)

Publication Number Publication Date
CN116136772A true CN116136772A (en) 2023-05-19

Family

ID=86334123

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111356355.0A Pending CN116136772A (en) 2021-11-16 2021-11-16 Buried point data acquisition method and device

Country Status (1)

Country Link
CN (1) CN116136772A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117290256A (en) * 2023-11-24 2023-12-26 北京中指实证数据信息技术有限公司 Code burying method for counting user behaviors

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117290256A (en) * 2023-11-24 2023-12-26 北京中指实证数据信息技术有限公司 Code burying method for counting user behaviors

Similar Documents

Publication Publication Date Title
CN103942225B (en) A kind of resource transfer method, client and the system of mixed type applications client
CN109240697B (en) Call processing method and device and storage medium
CN104821954A (en) Cross-platform remote procedure call method
CN104504060A (en) File downloading method in browser, browser client side and device
CN106815524B (en) Malicious script file detection method and device
CN104731869B (en) The page shows method and device
CN110928767A (en) Webpage analysis method, device, equipment and storage medium
CN108494762A (en) Web access method, device and computer readable storage medium, terminal
CN110598135A (en) Network request processing method and device, computer readable medium and electronic equipment
CN103530338A (en) Frame for carrying out page rendering on calculation equipment and page generation method
CN103023870A (en) Method, device and equipment for outputting data in message
CN105095220B (en) A kind of browser implementation method, terminal and virtualization agent device
CN111666199B (en) Debugging method executed on intelligent terminal and software debugger
CN113076294A (en) Information sharing method and device
CN109725887B (en) Data interaction method and device based on message research and development framework and terminal equipment
CN116136772A (en) Buried point data acquisition method and device
CN111680247B (en) Local calling method, device and equipment of webpage character strings and storage medium
CN108509228B (en) Page loading method, terminal equipment and computer readable storage medium
CN107943921B (en) Page sharing information generation method and device, computer equipment and storage medium
CN109634758A (en) Method and middleware platform based on JSON document control event and behavior
CN112463519A (en) Flatter-based page use behavior data non-buried point statistical method, equipment and storage medium
CN109684156B (en) Monitoring method, device, terminal and storage medium based on mixed mode application
CN114253441B (en) Method and device for enabling target function, storage medium and electronic device
CN114237926A (en) Multi-platform interaction method, device, equipment, storage medium and computer program product
CN112527656A (en) Websocket interface test method, device and equipment

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