Point burying method, medium and electronic equipment

Abstract

The invention provides a point burying method, a medium and electronic equipment, and the method comprises the steps: obtaining modular data of a target component in response to the detection of an interaction operation for the target component, the modular data comprising a module identifier and point burying information of the target component, and the point burying information being semantic information for a server to process point burying report data; generating burying point report data based on the module identifier of the target component, the burying point information and a page burying point identifier corresponding to the interactive operation; and sending the burying point report data to a server according to a preset report strategy. According to the technical scheme, the burying point identification can be set according to the page, the number of the burying point identification is greatly reduced, and the maintenance cost of the burying point data can be reduced; by reporting the burying point report data containing the semantic information, the server is helped to analyze the burying point data, and the analysis cost of the burying point data is reduced.

Description

Technical Field

[0001] The present disclosure relates to the fields of Internet technology and computer technology, and in particular, to a method, medium, and electronic device for embedding points. Background Art

[0002] Embedding points refers to inserting code or tags at the positions of components in an application or website that need to collect information, so as to collect and report the behavior data (embedded point data) generated by users at each component position, and optimize the page layout, user access link, etc. of the application or website by analyzing the embedded point data.

[0003] In related technologies, each page of the client contains multiple components. By setting separate click embedding point identifiers, exposure embedding point identifiers, and embedding point logics for each component, the embedding point data of each component is collected based on user behavior, and the embedding point data is reported by reporting the embedding point identifiers. Since the business logic of the client is complex, there are many components involved, and the corresponding embedding point identifiers are also numerous, the cost of maintaining and analyzing the embedding point data through the embedding point identifiers is relatively high. Summary of the Invention

[0004] In order to solve the above technical problems, a method, medium, and electronic device for embedding points are provided.

[0005] According to a first aspect of an embodiment of the present disclosure, a method for embedding points is provided, including:

[0006] In response to detecting an interaction operation on a target component, obtaining modular data of the target component, where the modular data includes: a module identifier of the target component and embedding point information, and the embedding point information is semantic information for the server to process the embedded point reporting data;

[0007] Generating embedded point reporting data based on the module identifier of the target component, the embedding point information, and a page embedding point identifier corresponding to the interaction operation;

[0008] Sending the embedded point reporting data to the server according to a preset reporting policy.

[0009] In some optional embodiments, before responding to detecting an interaction operation on a target component, it further includes:

[0010] Sending a page rendering request to the server, where the page rendering request carries a page identifier of the page to be rendered;

[0011] Receiving page rendering data returned by the server based on the page rendering request, where the page rendering data includes multiple modular data respectively corresponding to multiple components in the page to be rendered, and the modular data further includes module display information;

[0012] Render the page to be rendered based on the module identifiers and module display information of the multiple components.

[0013] In some alternative embodiments, the step of sending the buried point reporting data to the server according to the preset reporting policy includes:

[0014] Push a buried point data reporting message to a message queue, where at least one buried point data reporting message is stored in the message queue, and each buried point data reporting message carries the buried point reporting data;

[0015] Batch report the buried point reporting data carried by at least one buried point data reporting message in the message queue, and the batch reporting is to batch report at least one buried point reporting data to the server.

[0016] In some alternative embodiments, the page buried point identifier includes a page click buried point identifier and a page exposure buried point identifier;

[0017] The step of generating the buried point reporting data based on the module identifier, buried point information of the target component, and the page buried point identifier corresponding to the interaction operation includes:

[0018] Generate buried point semantic data based on the module identifier of the target component;

[0019] In response to the interaction operation being a click operation, generate the buried point reporting data based on the buried point semantic data and the page click buried point identifier of the page where the target component is located;

[0020] In response to the interaction operation being a display operation, generate the buried point reporting data based on the buried point semantic data and the page exposure buried point identifier of the page where the target component is located.

[0021] In some alternative embodiments, the step of generating the buried point semantic data based on the module identifier of the target component includes:

[0022] Based on the module identifier of the target component, obtain the module display information of the target component from a database, where the module display information includes at least one of a title, an image, a description, and a link of the target component;

[0023] Perform semantic recognition on the module display information to obtain semantic data;

[0024] Generate the buried point semantic data according to the semantic data and the buried point information.

[0025] According to the second aspect of the embodiments of the present disclosure, a buried point method is provided, including:

[0026] Receive the buried point reporting data reported by the client, where the buried point reporting data includes a module identifier, buried point information, and a page buried point identifier;

[0027] Based on at least one buried point reporting data received within a preset time period, cluster the at least one buried point reporting data based on the page buried point identifier in the buried point reporting data to obtain at least one page buried point instance, where each page buried point instance includes at least one buried point reporting data with the same page buried point identifier;

[0028] Based on the at least one page buried point instance, process the at least one buried point reporting data to obtain the buried point data processing result of each page.

[0029] In some optional embodiments, before receiving the buried point reporting data reported by the client, it further includes:

[0030] In response to receiving a page rendering request sent by the client, obtain the page identifier of the page to be rendered in the page rendering request;

[0031] Based on the page identifier, obtain the modular data of each component in the page to be rendered, where the modular data of each component includes: a module identifier, module display information, and buried point information;

[0032] Send the page rendering data of the page to be rendered to the client, where the page rendering data includes the modular data of each component.

[0033] According to the third aspect of the embodiments of the present disclosure, there is provided a buried point device, including:

[0034] A first acquisition module, configured to, in response to detecting an interaction operation on a target component, acquire the modular data of the target component, where the modular data includes: the module identifier of the target component and buried point information, and the buried point information is semantic information for the server to process buried point reporting data;

[0035] A data generation module, configured to generate buried point reporting data based on the module identifier of the target component, buried point information, and the page buried point identifier corresponding to the interaction operation;

[0036] A data reporting module, configured to send the buried point reporting data to the server according to a preset reporting policy.

[0037] In some optional embodiments, the device further includes:

[0038] A request module, configured to send a page rendering request to the server, where the page rendering request carries the page identifier of the page to be rendered;

[0039] A first receiving module, configured to receive page rendering data returned by the server based on the page rendering request, where the page rendering data includes a plurality of modular data respectively corresponding to a plurality of components in the page to be rendered, and the modular data further includes module display information;

[0040] A rendering module, configured to render the page to be rendered based on the module identifiers and module display information of the plurality of components.

[0041] In some alternative embodiments, the data reporting module includes:

[0042] A pushing sub-module, configured to push a data reporting message for buried point to a message queue, where at least one data reporting message for buried point is stored in the message queue, and each data reporting message for buried point carries the data to be reported for buried point;

[0043] A reporting sub-module, configured to batch report the data to be reported for buried point carried by at least one data reporting message for buried point in the message queue, and the batch reporting is to batch report at least one data to be reported for buried point to the server.

[0044] In some alternative embodiments, the page buried point identifier includes a page click buried point identifier and a page exposure buried point identifier;

[0045] The data generation module includes:

[0046] A first generation sub-module, configured to generate buried point semantic data based on the module identifier of the target component;

[0047] A second generation sub-module, configured to, in response to the interaction operation being a click operation, generate the data to be reported for buried point based on the buried point semantic data and the page click buried point identifier of the page where the target component is located;

[0048] A third generation sub-module, configured to, in response to the interaction operation being a display operation, generate the data to be reported for buried point based on the buried point semantic data and the page exposure buried point identifier of the page where the target component is located.

[0049] Specifically, the second generation sub-module is configured to obtain the module display information of the target component from a database based on the module identifier of the target component, where the module display information includes at least one of a title, an image, a description information, and a link of the target component; perform semantic recognition on the module display information to obtain semanticized data; and generate the buried point semantic data according to the semanticized data and the buried point information.

[0050] According to a fourth aspect of the embodiments of the present disclosure, there is provided a buried point device, including:

[0051] A second receiving module, configured to receive the buried point reporting data reported by the client, where the buried point reporting data includes a module identifier, buried point information, and a page buried point identifier;

[0052] A clustering module, configured to cluster at least one buried point reporting data received within a preset time period based on the page buried point identifier in the buried point reporting data, to obtain at least one page buried point instance, where each page buried point instance includes at least one buried point reporting data with the same page buried point identifier;

[0053] A processing module, configured to process at least one buried point reporting data based on the at least one page buried point instance, to obtain the buried point data processing result of each page.

[0054] In some alternative embodiments, the apparatus further includes:

[0055] An identifier obtaining module, configured to obtain the page identifier of the page to be rendered in the page rendering request in response to receiving the page rendering request sent by the client;

[0056] A second obtaining module, configured to obtain the modular data of each component in the page to be rendered based on the page identifier, where the modular data of each component includes: a module identifier, module display information, and buried point information;

[0057] A sending module, configured to send the page rendering data of the page to be rendered to the client, where the page rendering data includes the modular data of each component.

[0058] According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium storing computer program instructions, and when the computer program instructions are executed, the above-mentioned buried point method is implemented.

[0059] According to a sixth aspect of the embodiments of the present disclosure, there is provided an electronic device, where the electronic device includes:

[0060] A memory, configured to store a computer program product;

[0061] A processor, configured to execute the computer program product stored in the memory, and when the computer program product is executed, the above-mentioned buried point method is implemented.

[0062] According to a seventh aspect of the embodiments of the present disclosure, there is provided a computer program product including computer program instructions, and when the computer program instructions are executed by a processor, the above-mentioned buried point method is implemented.

[0063] Based on the above embodiments of the present disclosure, when an interaction operation on a target component is detected, the module identifier and buried point information of the target component can be obtained, and then, based on the module identifier of the target component, the buried point information, and the page buried point identifier corresponding to the interaction operation, buried point reporting data is generated and sent to the server according to a preset reporting strategy. Thus, the technical solution of the present disclosure can realize setting buried point identifiers according to pages, greatly reducing the number of buried point identifiers, helping to reduce the maintenance cost of buried point data; in addition, by reporting buried point reporting data containing semantic information, it helps the server analyze the buried point data, reduces the analysis cost of the buried point data, and improves the convenience of buried point data analysis.

[0064] The technical solution of the present disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] By describing the embodiments of the present disclosure in more detail with reference to the accompanying drawings, the above and other objects, features, and advantages of the present disclosure will become more apparent. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation to the present disclosure. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

[0066] Figure 1 It is a system framework diagram applicable to the buried point method of the present disclosure;

[0067] Figure 2 It is a flowchart of an embodiment of the buried point method of the present disclosure;

[0068] Figure 3 It is a flowchart of another embodiment of the buried point method of the present disclosure;

[0069] Figure 4 It is a flowchart of an embodiment of the buried point method of the present disclosure;

[0070] Figure 5 It is a flowchart of another embodiment of the buried point method of the present disclosure;

[0071] Figure 6 It is a schematic structural diagram of an embodiment of the buried point device of the present disclosure;

[0072] Figure 7 It is a schematic structural diagram of another embodiment of the buried point device of the present disclosure;

[0073] Figure 8 It is a schematic structural diagram of an embodiment of the buried point device of the present disclosure;

[0074] Figure 9Schematic structural diagram of yet another embodiment of the data logging device of the present disclosure;

[0075] Figure 10 It is a structural diagram of an electronic device provided by an exemplary embodiment of the present application. Detailed implementation manners

[0076] Hereinafter, exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments of the present disclosure. It should be understood that the present disclosure is not limited by the exemplary embodiments described herein.

[0077] It should be noted that: Unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions and values set forth in these embodiments do not limit the scope of the present disclosure.

[0078] Those skilled in the art can understand that terms such as "first", "second", etc. in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc., and neither represent any specific technical meaning nor indicate an inevitable logical order between them.

[0079] It should also be understood that in the embodiments of the present disclosure, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0080] It should also be understood that for any component, data or structure mentioned in the embodiments of the present disclosure, without clear definition or contrary indication in the context, it is generally understood as one or more.

[0081] In addition, the term " / and" in the present disclosure is only a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may indicate: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in the present disclosure generally represents an "or" relationship between the associated objects before and after.

[0082] It should also be understood that the present disclosure emphasizes the differences between the various embodiments. Their similarities or similarities can be referred to each other. For the sake of brevity, they will not be repeated one by one.

[0083] At the same time, it should be understood that for the sake of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0084] The following description of at least one exemplary embodiment is actually only illustrative and in no way a limitation of the present disclosure and its application or use.

[0085] Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such technologies, methods, and devices should be considered as part of the specification.

[0086] It should be noted that like reference numerals and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

[0087] Embodiments of the present disclosure can be applied to electronic devices such as terminal devices, computer systems, servers, etc., which can operate with many other general or special computing system environments or configurations. Examples of well-known terminal devices, computing systems, environments, and / or configurations suitable for use with electronic devices such as terminal devices, computer systems, or servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, network personal computers, minicomputer systems, mainframe computer systems, and distributed cloud computing technology environments including any of the above systems, etc.

[0088] Terminal devices, computer systems, servers, and other electronic devices can be described in the general context of computer system-executable instructions (such as program modules) executed by a computer system. Generally, program modules can include routines, programs, object programs, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. The computer system / server can be implemented in a distributed cloud computing environment. In a distributed cloud computing environment, tasks can be executed by remote processing devices linked through a communication network. In a distributed cloud computing environment, program modules can be located on local or remote computing system storage media including storage devices.

[0089] Exemplary system

[0090] Figure 1 Exemplary system architecture 100 of a data logging method and apparatus to which embodiments of the present disclosure can be applied is shown.

[0091] As Figure 1 shown, system architecture 100 can include terminal device 101, network 102, and server 103. Network 102 is used to provide a medium for a communication link between terminal device 101 and server 103. Network 102 can include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0092] Users can use the terminal device 101 to interact with the server 103 via the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as shooting applications, navigation applications, etc. Embedded point codes are set in each client application to collect user behavior data, generate embedded point reporting data, and send it to the server 103 for analysis and processing when the user performs an interaction operation through the client application.

[0093] The terminal device 101 can be various electronic devices, including but not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), in-vehicle terminals (such as in-vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc.

[0094] The server 103 can be a server that provides various services. For example, it is a background server for performing embedded point data analysis on the embedded point reporting data uploaded by the terminal device 101. The background server can analyze the received embedded point reporting data to obtain the usage situation of the client application, and optimize the page layout, user access link, etc. of the client application.

[0095] It should be noted that the embedded point method provided by the embodiments of the present disclosure can be jointly executed by the terminal device 101 and the server 103. Correspondingly, the embedded point device can be set in the server 103 and the terminal device 101.

[0096] It should be understood that Figure 1 the numbers of the terminal devices, networks, and servers in

[0097] Exemplary method

[0098] Figure 2 is a flowchart of an embodiment of the embedded point method of the present disclosure. As Figure 2 shown, the method is applied to Figure 1 the terminal devices (such as computers, servers) in

[0099] In step 201, in response to detecting an interaction operation for a target component, modular data of the target component is obtained. The modular data includes: a module identifier of the target component and embedded point information, and the embedded point information is semantic information for the server to process the embedded point reporting data.

[0100] In this embodiment, the target component is a component in the client with embedded code set. The embedded code is used to collect data on preset events of the target component in the client and report it to the server. The embedded code is developed by R & D personnel and integrated into the client program code. The interaction operation for the target component is an operation triggered by the user through the client interface, including high-frequency operations of embedded code, such as click operations, browsing operations, etc.

[0101] Among them, the modular data of the target component is the data used to render the target component and generate the embedded reporting data of the target component. The modular data includes a module identifier, module display information, and embedded information of the module. The modular data of the target component is sent by the server to the client when the client starts or opens a page according to the page content to be displayed by the client.

[0102] Among them, the module identifier (type) is used to identify the module; the client determines the component to which the current modular data belongs according to the type value, and then loads the corresponding rendering logic or component. The module display information (content) is used to store the data to be displayed by the component; the client can determine how to use the data in the content for display according to the type value, such as information such as title, picture, description, link, etc. The embedded information of the module is the information used to store the buried field and the value of the buried field. The buried field and the value of the buried field are sent from the server side to the client and are used to indicate the information that the client needs to report.

[0103] By performing semantic recognition processing on the title, picture, description information, etc. in the module display information, the semantic information of the corresponding component can be obtained. And according to the semantic information and the embedded information (information to be reported), the semantic information corresponding to the embedded information can be extracted from the semantic information to obtain the embedded semantic data. This helps the server analyze the embedded reporting data more quickly and accurately based on the embedded semantic data in the embedded reporting data; when the client detects an interaction operation for the target component, the client can obtain the buried field and the value of the buried field from the embedded information and report it to the server when sending the embedded reporting data to the server later.

[0104] When an interaction operation for this component occurs, the embedded reporting data can be generated according to step 202.

[0105] In step 202, based on the module identifier, embedded information of the target component, and the page embedded identifier corresponding to the interaction operation, the embedded reporting data is generated.

[0106] Among them, the page buried point identifiers include page click buried point identifiers and page exposure buried point identifiers. The page click buried point identifier is used to count the interaction times and frequencies of users with specific elements corresponding to specific components (such as buttons, icons, etc.). The page click buried point identifier records the active behaviors (active interaction operations) of users. For example, clicking an icon or a button. The page exposure buried point identifier is used to record whether certain component elements in the client page are seen by users, recording the exposure situation of the component elements, rather than the active interaction operation behaviors of users. For example, in a news application, the exposure buried point identifier can record whether a user has seen a certain news title or picture.

[0107] In this embodiment, a page may include multiple components, and the page buried point identifiers (page click buried point identifiers and page exposure buried point identifiers) of each component are the same.

[0108] In this embodiment, by organizing the module identifier and buried point information of the target component, such as splicing and packing, and then adding the page buried point identifier, the buried point reporting data can be obtained.

[0109] In step 203, according to the preset reporting strategy, send the buried point reporting data to the server.

[0110] Among them, the preset reporting strategy is used to indicate the strategy for sending the buried point reporting data to the server. For example, the reporting strategy is an asynchronous reporting strategy, which does not report immediately after an event (interaction operation) is triggered, but first caches the buried point reporting data locally and then reports it after a certain time interval, or reports it after obtaining a certain number of buried point reporting data; or, the reporting strategy is to immediately report the buried point reporting data to the server after an event (interaction operation) is triggered.

[0111] In some implementation manners, in order not to block the client interface, an asynchronous reporting strategy is adopted, and retry or caching processing is performed in case of failure.

[0112] In other implementation manners, in a scenario where user behaviors are frequent, through a batch reporting strategy, multiple buried point reporting data are uploaded to the server in batches to reduce the network request pressure.

[0113] It can be understood that, in order to ensure data security, before sending the buried point reporting data, it is necessary to perform verification and desensitization processing on the sensitive data in the buried point reporting data. For example, replace, delete or disorder the sensitive data in the buried point reporting data so that the sensitive data cannot be recognized; perform real-time desensitization processing on the sensitive data during data transmission to avoid data integrity problems; use an encryption algorithm to encrypt the sensitive data in the buried point reporting data to protect the data from being leaked.

[0114] Through the above steps 201 - 203, when an interaction operation for a target component is detected, the module identifier and the buried point information of the target component can be obtained, and then based on the module identifier of the target component, the buried point information, and the page buried point identifier corresponding to the interaction operation, the buried point reporting data is generated, and according to the preset reporting strategy, the buried point reporting data is sent to the server. Thus, the technical solution of the present disclosure can implement setting the buried point identifier according to the page, greatly reducing the number of buried point identifiers, helping to reduce the maintenance cost of the buried point data; in addition, by reporting the buried point reporting data containing semantic information, it helps the server analyze the buried point data, reduces the analysis cost of the buried point data, and improves the convenience of buried point data analysis.

[0115] Figure 3 It is a flowchart of another embodiment of the buried point method of the present disclosure. As Figure 3 shown, the method includes steps 301 - 307. Each step will be described separately below.

[0116] In step 301, a page rendering request is sent to the server, and the page rendering request carries the page identifier of the page to be rendered.

[0117] Among them, the page rendering request is used to instruct the client to obtain data from the server through the network and display the obtained data on the page. The page identifier can be the page link of the page to be rendered.

[0118] In this embodiment, the client can actively send a page rendering request to the server when opening the client page, so as to realize the server rendering the page, reducing the logic and complexity of the client.

[0119] In step 302, the page rendering data returned by the server based on the page rendering request is received. The page rendering data includes multiple modular data respectively corresponding to multiple components in the page to be rendered, and the modular data further includes module display information.

[0120] Among them, the module display information (content) is used to store the data to be displayed by the component; the client can determine how to use the data in the content for display according to the type value, such as information such as title, picture, description, link, etc. By modularizing the components in the page, and the modular data of each component includes a module identifier, buried point information, and module display information, it helps to reduce the coupling degree of each component in the page, and is also convenient for buried point statistics and analysis of the data of each module.

[0121] In step 303, based on the module identifiers and module display information of the multiple components, the page to be rendered is rendered.

[0122] In this embodiment, after the client receives the page rendering data, it can render the components corresponding to each module according to the module identifier and module display information of each component, thereby realizing the rendering of the page to be rendered.

[0123] In step 304, in response to detecting an interaction operation on the target component, obtain the modular data of the target component, where the modular data includes: the module identifier of the target component and the buried point information, and the buried point information is the semantic information used for the server to process the buried point reporting data.

[0124] In step 305, generate the buried point reporting data based on the module identifier of the target component, the buried point information, and the page buried point identifier corresponding to the interaction operation.

[0125] Specifically, first generate the buried point semantic data based on the module identifier of the target component and the buried point information; in response to the interaction operation being a click operation, generate the buried point reporting data based on the buried point semantic data and the page click buried point identifier of the page where the target component is located; in response to the interaction operation being a display operation, generate the buried point reporting data based on the buried point semantic data and the page exposure buried point identifier of the page where the target component is located.

[0126] Among them, the buried point semantic data refers to the buried point data with clear semantics, which helps the server better understand and utilize the buried point reporting data.

[0127] Specifically, based on the module identifier of the target component, obtain the module display information of the target component from the database, where the module display information includes at least one of the title, image, description information, and link of the target component; perform semantic recognition on the module display information to obtain semantic data; generate the buried point semantic data according to the semantic data and the buried point information.

[0128] Exemplarily, the above modular data content is illustrated by the following code.

[0129] {

[0130] "type":"content_buy_house_story_video",

[0131] "content":{

[0132] "title":"Buying a House Story",

[0133] "videoUrl":"https: / / example.com / video.mp4",

[0134] "description":"Real case sharing, the whole process from house selection to occupancy."

[0135] / / ... Other data related to display

[0136] },

[0137] "buried":{

[0138] "moduleId":"68",

[0139] "position":"Home Page - Featured Videos",

[0140] "extraInfo":"Other statistical information can be extended as needed"

[0141] }

[0142] }

[0143] As can be seen from the above code, corresponding components can be rendered based on the above modular data. Among them, the type of the component is the content_buy_house_story_video of the housing purchase story video, and the module display information of the component includes "title - Housing Purchase Story", "videoUrl - https: / / example.com / video.mp4", "description - Real case sharing, the whole process from house selection to move-in". By performing semantic recognition on the above content, the semantic information of this component can be "Case sharing of housing purchase stories, revealing the process from house selection to move-in". For this component, the buried point information that needs to be reported sent by the server side includes: "moduleId: 68", "position: Home Page - Featured Videos", "extraInfo: Other statistical information can be extended as needed". Therefore, the buried point semantic data is "Case sharing of housing purchase stories, revealing the process from house selection to move-in, "moduleId: 68", "position: Home Page - Featured Videos", "extraInfo: Other statistical information can be extended as needed".

[0144] In this implementation method, when a component corresponding to a functional module in the client page is exposed, the type (module identifier) and buried (buried point information) are obtained from the modular data, and the module identifier and buried point information are organized, plus the page exposure buried point identifier of the page where the target component is located, to generate the buried point reporting data; when a component corresponding to a functional module in the client page is clicked, the type (module identifier) and buried (buried point information) are obtained from the modular data, and the module identifier and buried point information are organized, plus the page click buried point identifier of the page where the target component is located, to generate the buried point reporting data.

[0145] In step 306, a message for reporting buried point data is pushed to the message queue, where at least one message for reporting buried point data is stored, and each message for reporting buried point data carries buried point reporting data.

[0146] Among them, the message queue is a queue for the buried point data generation unit to transfer messages to the buried point data reporting unit. After generating the buried point data, the buried point data generation unit can push a message for reporting buried point data carrying the buried point reporting data to the message queue.

[0147] Exemplarily, after the user triggers a click operation on component 1, the buried point reporting data corresponding to the click operation of component 1 can be inserted into the message queue. The buried point reporting data includes information related to the click behavior, such as the clicked element, click time, user identity, etc.

[0148] It can be understood that in a scenario where user behaviors are frequent, a large amount of buried point reporting data may be generated at the same time or within a very short time interval, and then a large amount of buried point reporting data is inserted into the message queue within a very short time interval.

[0149] In step 307, the buried point reporting data carried by at least one message for reporting buried point data in the message queue is reported in batches. Reporting in batches means reporting at least one buried point reporting data to the server in batches.

[0150] Among them, the buried point data reporting unit can pull messages from the message queue according to a set rule and perform batch reporting processing. The set rule can include: the maximum number of messages pulled each time, and the time for pulling messages each time.

[0151] Exemplarily, the preset rule for pulling messages from the message queue can be to pull at most 100 buried point reporting data each time, and the time for pulling messages each time is after sending the buried point reporting data pulled last time.

[0152] In addition to reporting data through the method of asynchronously and batch-sending buried point reporting data via the message queue, the buried point reporting data can also be reported in real time, that is, the buried point reporting data corresponding to each interaction operation is reported immediately, which helps to reduce intermediate links and human intervention. Reporting immediately reduces the possibility of data errors and enhances the reliability of the data.

[0153] Through the above steps 301 to 307, when the client renders the page each time, it obtains the modular data of each component in the page from the server for rendering, realizing page rendering by the server, with high rendering efficiency; and when sending buried point reporting data, batch and asynchronous reporting helps to reduce the network request pressure and avoid blocking the client interface.

[0154] Figure 4The flowchart of an embodiment of the data embedding method of the present disclosure is as follows. As Figure 4 shown, the method is applied to the Figure 1 server in

[0155] and includes steps 401 to 403. Each step will be described separately below.

[0156] Among them, the module identifier is used to identify the component; the client determines the component corresponding to the data embedding report according to the module identifier. The data embedding information is used to store the data embedding (buried) fields and the data embedding (buried) field values, and is the semantic information for the server to process the data embedding report, which helps the server analyze the data embedding report more quickly and accurately according to the semantic information. The page data embedding identifier is used to identify the page where the component is located and the operation type corresponding to the data embedding report.

[0157] Among them, the page data embedding identifier includes a page click data embedding identifier and a page exposure data embedding identifier. The page click data embedding identifier is used to count the interaction times and frequencies of users with specific elements (such as buttons, icons, etc.) corresponding to specific components. The page click data embedding identifier records the active behavior (active interaction operation) of users. For example, clicking an icon or a button. The page exposure data embedding identifier is used to record whether some component elements in the client page are seen by users, and records the exposure situation of the component elements, rather than the active interaction operation behavior of users. For example, in a news application, the exposure data embedding identifier can record whether a user has seen a certain news title or picture.

[0158] In step 402, based on at least one data embedding report received within a preset time period, at least one data embedding report is clustered based on the page data embedding identifier in the data embedding report to obtain at least one page data embedding instance, where each page data embedding instance includes at least one data embedding report with the same page data embedding identifier.

[0159] Among them, the preset time period is a preset time interval for analyzing and processing the data embedding report and optimizing the application layout and user access link according to the processing result. For example, time intervals such as one week and three days.

[0160] In this embodiment, clustering each data embedding report according to the page data embedding identifier helps to filter out the data embedding data of each page, and then analyze the data embedding reports of each page.

[0161] Furthermore, for each page data embedding instance, the front-end page module (component) corresponding to the data embedding data can also be determined through the module identifier, and then the data embedding reports of each component can be analyzed.

[0162] In step 403, based on at least one page buried point instance, at least one buried point reporting data is processed to obtain the buried point data processing result of each page.

[0163] Among them, the buried point data processing result is used to characterize the user's operations on the client, determine the user's usage habits and preferences, help discover problems existing in the product, perform targeted optimization and iteration on the product, and enhance the competitiveness of the product and user satisfaction. For example, by analyzing the user's click, browsing, purchase and other behavior data, the direction of product improvement can be found, and the user experience and conversion rate can be improved.

[0164] Through the above steps 401 to 403, after the server obtains the buried point reporting data reported by the client, it analyzes the problems existing in the application program according to the module identifier and buried point field with semantic information therein. Since the readability and understandability of the module identifier and buried point field are relatively strong, when analyzing the buried point reporting data, data cleaning, standardization and integration can be better performed, which helps to improve the speed and accuracy of data processing and optimize the accuracy of the obtained buried point data processing result; in addition, since the components within a page use the same page buried point identifier, the number of buried point identifiers is greatly reduced, and the maintainability is enhanced; moreover, clustering and post-processing of the buried point reporting data according to the page buried point identifier and module identifier helps to analyze the user behavior data of each page or each component, and perform targeted optimization and iteration.

[0165] Figure 5 It is a flowchart of another embodiment of the buried point method of the present disclosure; as Figure 5 shown, the method includes steps 501-503. Each step will be described separately below.

[0166] In step 501, in response to receiving a page rendering request sent by the client, the page identifier of the page to be rendered in the page rendering request is obtained.

[0167] Among them, the page rendering request is used to instruct the client to obtain data from the server through the network and display the obtained data on the page. The page identifier may be the page link of the page to be rendered.

[0168] In step 502, based on the page identifier, the modular data of each component in the page to be rendered is obtained, and the modular data of each component includes: module identifier, module display information, and buried point information.

[0169] In this embodiment, after receiving the page rendering request, the server can obtain the modular data of each component of the page to be rendered corresponding to the page identifier from the database according to the page identifier.

[0170] Among them, the module display information (content) is used to store the data to be displayed by the component; the client can determine how to use the data in the content for display according to the type value, such as information like title, picture, description, link, etc. By modularizing the components in the page, and the modular data of each component including the module identifier, buried point information, and module display information, it helps to reduce the coupling degree of each component in the page, and is also convenient for buried point statistics and analysis of the data of each module.

[0171] In step 503, send the page rendering data of the page to be rendered to the client, and the page rendering data includes the modular data of each component.

[0172] Through the above steps 501 to 503, when the client needs to render the page, the server obtains the modular data of each component in the page from the database, and sends the page rendering data composed of the modular data of each component to the client, realizing page rendering by the server, with high rendering efficiency.

[0173] Exemplary device

[0174] Figure 6 It is a schematic structural diagram of an embodiment of the buried point device of the present disclosure. This device can be located in Figure 1 the terminal device of the system shown, such as Figure 6 shown, including:

[0175] The first acquisition module 61 is configured to acquire the modular data of the target component in response to detecting an interaction operation on the target component, and the modular data includes: the module identifier of the target component and the buried point information, and the buried point information is the semantic information used for the server to process the buried point reporting data;

[0176] The data generation module 62 is configured to generate buried point reporting data based on the module identifier of the target component, the buried point information, and the page buried point identifier corresponding to the interaction operation;

[0177] The data reporting module 63 is configured to send the buried point reporting data to the server according to a preset reporting strategy.

[0178] Figure 7 It is a schematic structural diagram of another embodiment of the buried point device of the present disclosure. As Figure 7 shown, on the basis of the embodiment shown in Figure 6 in some embodiments of the present disclosure, the device further includes:

[0179] The request module 64 is configured to send a page rendering request to the server, and the page rendering request carries the page identifier of the page to be rendered;

[0180] The first receiving module 65 is configured to receive page rendering data returned by the server based on a page rendering request. The page rendering data includes a plurality of modular data respectively corresponding to a plurality of components in the page to be rendered, and the modular data further includes module display information;

[0181] The rendering module 66 is configured to render the page to be rendered based on the module identifiers and module display information of the plurality of components.

[0182] In some embodiments of the present disclosure, the data reporting module 63 includes:

[0183] The push sub-module 631 is configured to push a buried point data reporting message to a message queue. At least one buried point data reporting message is stored in the message queue, and each buried point data reporting message carries buried point reporting data;

[0184] The reporting sub-module 632 is configured to perform batch reporting on the buried point reporting data carried by at least one buried point data reporting message in the message queue. The batch reporting is to batch report at least one buried point reporting data to the server.

[0185] In some embodiments of the present disclosure, the page buried point identifier includes a page click buried point identifier and a page exposure buried point identifier;

[0186] The data generation module 62 includes:

[0187] The first generation sub-module 621 is configured to generate buried point semantic data based on the module identifier and buried point information of the target component;

[0188] The second generation sub-module 622 is configured to, in response to the interaction operation being a click operation, generate buried point reporting data based on the buried point semantic data and the page click buried point identifier of the page where the target component is located;

[0189] The third generation sub-module 623 is configured to, in response to the interaction operation being a display operation, generate buried point reporting data based on the buried point semantic data and the page exposure buried point identifier of the page where the target component is located.

[0190] In some embodiments of the present disclosure, the first generation sub-module 621 is specifically configured to obtain the module display information of the target component from the database based on the module identifier of the target component. The module display information includes at least one of the title, image, description information, and link of the target component; perform semantic recognition on the module display information to obtain semantic data; and generate buried point semantic data according to the semantic data and the buried point information.

[0191] Figure 8 It is a schematic structural diagram of an embodiment of the buried point device of the present disclosure. The device can be located in Figure 1 the server of the system shown in, such as Figure 8 shown, and includes:

[0192] A second receiving module 81, configured to receive the buried point reporting data reported by the client, where the buried point reporting data includes a module identifier, buried point information, and a page buried point identifier;

[0193] A clustering module 82, configured to cluster at least one buried point reporting data received within a preset time period based on the page buried point identifier in the buried point reporting data to obtain at least one page buried point instance, where each page buried point instance includes at least one buried point reporting data with the same page buried point identifier;

[0194] A processing module 83, configured to process at least one buried point reporting data based on at least one page buried point instance to obtain a buried point data processing result for each page.

[0195] Figure 9 A schematic structural diagram of another embodiment of the buried point device of the present disclosure. As Figure 9 shown, on the basis of the embodiment shown in Figure 8 In some embodiments of the present disclosure, the device further includes:

[0196] An identifier obtaining module 84, configured to obtain a page identifier of a page to be rendered in the page rendering request in response to receiving the page rendering request sent by the client;

[0197] A second obtaining module 85, configured to obtain modular data of each component in the page to be rendered based on the page identifier, where the modular data of each component includes: a module identifier, module display information, and buried point information;

[0198] A sending module 86, configured to send page rendering data of the page to be rendered to the client, where the page rendering data includes the modular data of each component. The device according to the embodiment of the present disclosure can be used to implement the methods of the above embodiments of the present disclosure, and the specific implementations between the two correspond to each other, and the specific implementations of the relevant parts are mutually referred to and will not be elaborated herein.

[0199] Exemplary electronic device, computer program product, computer-readable storage medium, and system

[0200] The embodiment of the present disclosure further provides an electronic device, including: a memory, configured to store a computer program; a processor, configured to execute the computer program stored in the memory, and when the computer program is executed, implement the buried point method of any one of the above embodiments of the present disclosure.

[0201] Next, with reference to Figure 10 to describe the electronic device according to the embodiment of the present disclosure, where a device for implementing the method of the embodiment of the present disclosure can be integrated. Figure 10 A structural diagram of an electronic device provided for a schematic embodiment of the present disclosure, as Figure 10As shown, the electronic device includes one or more processors 101, a memory 102 of one or more computer-readable storage media, and a computer program stored on the memory and executable on the processor. When executing the program in the memory 102, the above-mentioned data point embedding method can be implemented.

[0202] Specifically, in practical applications, the electronic device may further include components such as an input device 103 and an output device 104, and these components are interconnected through a bus system and / or other forms of connection mechanisms (not shown). Those skilled in the art can understand that Figure 10 the structure of the electronic device shown in does not constitute a limitation on the electronic device, and it may include more or fewer components than shown, or certain components, or different component arrangements. Among them:

[0203] The processor 101 can be a central processing unit (CPU) or other forms of processing units with data point embedding capabilities and / or instruction execution capabilities. By running or executing software programs and / or modules stored in the memory 102, and calling data stored in the memory 102, it performs various functions and processes data, thereby overall monitoring the electronic device.

[0204] The memory 102 can store one or more computer program products. The memory can include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The above-mentioned volatile memory can include, for example, random access memory (RAM) and / or cache memory, etc. The above-mentioned non-volatile memory can include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program products can be stored on the computer-readable storage media, and the processor 101 can run the computer program products to implement the data point embedding methods of the various embodiments of the present disclosure above and / or other desired functions.

[0205] The input device 103 can be used to receive input digital or character information. The input device 103 can include a keyboard, a mouse, a joystick, etc. related to user settings and function controls.

[0206] The output device 104 can output various information to the outside, including determined distance information, direction information, etc. The output device 104 can include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0207] The electronic device may further include a power supply for powering various components, which may be logically connected to the processor 101 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. The power supply may also include any components such as one or more DC or AC power supplies, a recharge system, a power failure detection circuit, a power converter or inverter, a power status indicator, etc.

[0208] Of course, for simplicity, Figure 10 only some of the components related to the present disclosure in the electronic device are shown, and components such as buses, input / output interfaces, etc. are omitted. In addition, according to specific application scenarios, the electronic device may further include any other appropriate components.

[0209] In addition to the above methods and devices, an embodiment of the present disclosure may also be a computer program product, which includes computer program instructions that, when run by a processor, cause the processor to execute the steps in the data embedding method according to various embodiments of the present disclosure described in the "Exemplary Method" section above of this specification.

[0210] The computer program product may be written in any combination of one or more programming languages for programming code to perform the operations of the embodiments of the present disclosure. The programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages such as the "C" language or similar programming languages. The programming code may be executed entirely on the user computing device, partially on the user device, executed as an independent software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0211] In addition, an embodiment of the present disclosure may also be a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are run by a processor, the processor is caused to execute the steps in the data embedding method according to various embodiments of the present disclosure described in the "Exemplary Method" section above of this specification.

[0212] A computer-readable storage medium may adopt any combination of one or more readable media. The readable media may be a readable signal medium or a readable storage medium. The readable storage medium may include, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0213] The basic principles of the present disclosure have been described above in conjunction with specific embodiments. However, it should be noted that the advantages, benefits, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, benefits, effects, etc. are essential for each embodiment of the present disclosure. In addition, the above-mentioned specific details are only for the purposes of illustration and easy understanding, rather than limitations. The above details do not limit the present disclosure to necessarily adopt the above specific details for implementation.

[0214] Each embodiment in this specification is described in a progressive manner. The key point of each embodiment is to illustrate the differences from other embodiments. For the same or similar parts among the embodiments, reference can be made to each other. For system embodiments, since they basically correspond to method embodiments, the description is relatively simple, and reference can be made to the partial description of the method embodiments for the relevant parts.

[0215] Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps including the above method embodiments; and the foregoing storage medium includes: ROM, RAM, magnetic disk, or optical disk and other media that can store program codes.

[0216] The methods and apparatuses of the present disclosure may be implemented in many ways. For example, the methods and apparatuses of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is only for illustration, and the steps of the method of the present disclosure are not limited to the above specific order described unless otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as a program recorded in a recording medium, and these programs include machine-readable instructions for implementing the methods according to the present disclosure. Therefore, the present disclosure also covers a recording medium storing a program for executing the methods according to the present disclosure.

[0217] The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the forms disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments were chosen and described in order to best explain the principles of the present disclosure and its practical application, and to enable others of ordinary skill in the art to understand the present disclosure and design various embodiments with various modifications suited to particular uses.

Claims

1. A method for logging, characterized in that, including: In response to detecting an interaction operation on a target component, obtain modular data of the target component, where the modular data includes: a module identifier of the target component and buried point information, and the buried point information is semantic information for the server to process buried point reporting data; Generate buried point reporting data based on the module identifier of the target component, the buried point information, and a page buried point identifier corresponding to the interaction operation; Send the buried point reporting data to the server according to a preset reporting policy.

2. The method according to claim 1, wherein Before responding to detecting an interaction operation on a target component, it further includes: Send a page rendering request to the server, where the page rendering request carries a page identifier of a page to be rendered; Receive page rendering data returned by the server based on the page rendering request, where the page rendering data includes multiple modular data respectively corresponding to multiple components in the page to be rendered, and the modular data further includes module display information; Render the page to be rendered based on the module identifiers and module display information of the multiple components.

3. The method according to any one of claims 1-2, characterized in that The step of sending the buried point reporting data to the server according to a preset reporting policy includes: Push a buried point data reporting message to a message queue, where at least one buried point data reporting message is stored in the message queue, and each buried point data reporting message carries the buried point reporting data; Batch report the buried point reporting data carried by at least one buried point data reporting message in the message queue, and the batch reporting is to batch report at least one buried point reporting data to the server.

4. The method according to any one of claims 1-3, characterized in that, The page buried point identifier includes a page click buried point identifier and a page exposure buried point identifier; The step of generating buried point reporting data based on the module identifier of the target component, the buried point information, and the page buried point identifier corresponding to the interaction operation includes: Generate buried point semantic data based on the module identifier of the target component; In response to the interaction operation being a click operation, generate the buried point reporting data based on the buried point semantic data and the page click buried point identifier of the page where the target component is located; In response to the interaction operation being a display operation, generate the buried point reporting data based on the buried point semantic data and the page exposure buried point identifier of the page where the target component is located.

5. The method according to claim 4, wherein The step of generating buried point semantic data based on the module identifier of the target component includes: Based on the module identifier of the target component, obtain module display information of the target component from a database, where the module display information includes at least one of a title, an image, description information, and a link of the target component; Perform semantic recognition on the module display information to obtain semantic data; Generate the buried point semantic data according to the semantic data and the buried point information.

6. A method for embedding points, characterized in that, including: Receive buried point reporting data reported by a client, where the buried point reporting data includes a module identifier, buried point information, and a page buried point identifier; Based on at least one buried point reporting data received within a preset time period, clustering the at least one buried point reporting data based on the page buried point identifier in the buried point reporting data to obtain at least one page buried point instance, wherein each page buried point instance includes at least one buried point reporting data with the same page buried point identifier; Based on the at least one page buried point instance, processing the at least one buried point reporting data to obtain the buried point data processing results of each page.

7. The method according to claim 6, wherein Before receiving the buried point reporting data reported by the client, it further includes: In response to receiving a page rendering request sent by the client, obtaining the page identifier of the page to be rendered in the page rendering request; Based on the page identifier, obtaining the modular data of each component in the page to be rendered, and the modular data of each component includes: module identifier, module display information, and buried point information; Sending the page rendering data of the page to be rendered to the client, and the page rendering data includes the modular data of each component.

8. A computer-readable storage medium, the storage medium stores computer program instructions, and when the computer program instructions are executed, the method described in any one of claims 1-7 above is implemented.

9. An electronic device, the electronic device includes: A memory for storing a computer program product; A processor for executing the computer program product stored in the memory, and when the computer program product is executed, the method described in any one of claims 1-7 above is implemented.

10. A computer program product, comprising computer program instructions, characterized in that, When the computer program instructions are executed by the processor, the method described in any one of claims 1-7 above is implemented.

Images