Method, device and equipment for generating buried point parameters, and storage medium

Abstract

Embodiments of the present application provide a kind of buried point parameter generation method, device, equipment and storage medium.The method comprises: in response to page rendering instruction, obtain page configuration information, and the initial buried point parameter corresponding to multiple page attributes respectively is included in page configuration information;Page configuration information is parsed, and the level and initial buried point parameter corresponding to multiple page attributes respectively are determined;The initial buried point parameter of the highest level page attribute is used as the target buried point parameter of the highest level page attribute;From the next level page attribute of the highest level page attribute, the target buried point parameter of target page attribute is obtained by successively carrying out buried point parameter processing operation to each level page attribute;According to the target buried point parameter corresponding to multiple page attributes respectively, update page configuration information.The above scheme generates the target buried point parameter of all levels of page attribute by automatic splicing, without manual splicing, can improve the configuration efficiency of target buried point parameter.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and in particular, to a method and device for generating a buried point parameter, and a storage medium. BACKGROUND

[0002] Buried point refers to adding program code for data collection to a page element in a page that needs to be collected, so as to collect data of user interaction behavior occurring in the page element. The data collection of the page element is performed according to a buried point parameter of a page attribute corresponding to the page element. The buried point parameter can define information to be collected when a user performs a specific interactive operation on the page. The page element can include a page and a component contained in the page. The buried point parameter configured for the page can define information to be collected when the user triggers the page. The buried point parameter configured for the component can define information to be collected when the user triggers the component. According to the buried point parameter, the client can collect corresponding information when the user performs a specific interactive operation on the page, and generate buried point log data. The buried point log data can be reported to the server for analyzing user interaction behavior.

[0003] When the page contains page elements with a nested relationship, the page attributes corresponding to the page elements also have a corresponding nested relationship. The developer usually first determines the initial buried point parameter corresponding to the level of each page attribute, then splices the initial buried point parameter of any page attribute and the initial buried point parameters corresponding to all upper page attributes nested with the page attribute to obtain the target buried point parameter of the page attribute, and configures the target buried point parameter in the page attribute. Therefore, the client can generate buried point log data based on the target buried point parameter of the page attribute corresponding to any page element when the user triggers the page element. The buried point log data can include initial information corresponding to the page element and initial information corresponding to all upper page elements nested with the page element. The buried point log data can reflect a complete user interaction path, which is helpful for comprehensive and detailed user behavior analysis. However, this buried point parameter generation method requires manual splicing, which is relatively cumbersome, has low artificial configuration efficiency, and requires a large amount of human resources. SUMMARY

[0004] The embodiments of the present application provide a buried point parameter generation method, device, equipment and storage medium, to solve the problem of low buried point parameter configuration efficiency in the prior art.

[0005] In a first aspect, the embodiments of the present application provide a buried point parameter generation method, comprising:

[0006] In response to a page rendering command, obtain page configuration information; the page configuration information includes initial tracking parameters corresponding to multiple page attributes.

[0007] Parse the page configuration information to determine the hierarchy corresponding to the multiple page attributes and the initial tracking parameters;

[0008] Use the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute;

[0009] Starting from the next level of page attributes below the highest level page attribute, the tracking parameter processing operation is performed sequentially for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking splicing condition; splicing the initial tracking parameter of the target page attribute with the target tracking parameter of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameter of the target page attribute.

[0010] The page configuration information is updated based on the target tracking parameters corresponding to the multiple page attributes.

[0011] Secondly, embodiments of the present invention provide a device for generating embedding point parameters, the device comprising:

[0012] The acquisition module is used to acquire page configuration information in response to page rendering instructions; the page configuration information includes initial tracking parameters corresponding to multiple page attributes.

[0013] The parsing module is used to parse the page configuration information, determine the levels corresponding to the multiple page attributes, and the initial tracking parameters.

[0014] The processing module is used to take the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute; starting from the next level of page attributes of the highest-level page attribute, it sequentially performs tracking parameter processing operations for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking concatenation condition; concatenating the initial tracking parameters of the target page attribute with the target tracking parameters of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameters of the target page attribute;

[0015] The update module is used to update the page configuration information according to the target tracking parameters corresponding to the multiple page attributes.

[0016] In a third aspect, an electronic device is provided, which includes a processor and a memory. The memory is configured to store one or more computer instructions. When the one or more computer instructions are executed by the processor, the electronic device is enabled to implement the method for generating a buried point parameter in the first aspect. The electronic device can further include a communication interface configured to communicate with other devices or communication systems.

[0017] In a fourth aspect, a non-transitory machine readable storage medium is provided. The non-transitory machine readable storage medium stores executable code. When the executable code is executed by a processor of an electronic device, the processor is enabled to implement the method for generating a buried point parameter in the first aspect.

[0018] In a fifth aspect, a computer program product is provided. The computer program product includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is enabled to implement the method for generating a buried point parameter in the first aspect.

[0019] In the embodiments of the present application, in response to a page rendering instruction, page configuration information is obtained. The page configuration information includes initial buried point parameters corresponding to a plurality of page attributes, respectively. Then, the page configuration information is parsed to determine levels corresponding to the plurality of page attributes and initial buried point parameters. The initial buried point parameter of a highest level page attribute is taken as a target buried point parameter of the highest level page attribute. Starting from the next level page attribute of the highest level page attribute, the buried point parameter processing operation is performed on each level page attribute in turn. The buried point parameter processing operation includes: determining a target page attribute that satisfies a first buried point splicing condition; splicing the initial buried point parameter of the target page attribute and the target buried point parameter of the page attribute of the previous level corresponding to the target page attribute to obtain the target buried point parameter of the target page attribute; and updating the page configuration information according to the target buried point parameters corresponding to the plurality of page attributes, respectively.

[0020] In the above scheme, the target buried point parameters of the page attributes of all levels are generated by automatic splicing, without manual splicing. The configuration efficiency of the target buried point parameters can be improved, manual configuration can be reduced, and the consumption of human resources can be reduced. BRIEF DESCRIPTION OF DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0022] Figure 1A flowchart of an embodiment of a method for generating a buried point parameter provided by the embodiment of the present application;

[0023] Figure 2 A structural schematic diagram of a device for generating a buried point parameter provided by the embodiment of the present application;

[0024] Figure 3 The device for generating a buried point parameter provided by the embodiment shown in Figure 2 A structural schematic diagram of an electronic device corresponding to the device for generating a buried point parameter provided by the embodiment. DETAILED DESCRIPTION

[0025] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below in connection with the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without any creative work fall within the protection scope of the present application.

[0026] The technical solution of the embodiment of the present application can be applied to a scenario of collecting user interactive behavior data by using a buried point.

[0027] As described in the background, in the case that a page contains page attributes with a nested relationship, usually, a developer splices an initial buried point parameter corresponding to a level to which each page attribute belongs, and a target buried point parameter of any page attribute is obtained by splicing the initial buried point parameter of the page attribute and initial buried point parameters corresponding to all upper page attributes nested with the page attribute, and the target buried point parameter is configured in the page attribute. The client can generate a buried point log data according to the configured target buried point parameter. This way needs manual splicing by the developer, is relatively cumbersome, has low manual configuration efficiency, and needs to consume a large amount of human resources.

[0028] To solve the technical problem of low efficiency of configuration of a buried point parameter, the inventor conceives that only the initial buried point parameter corresponding to the level of each page attribute can be configured by a developer, and the target buried point parameter can be automatically spliced by a client according to the initial buried point parameter of the page attribute, so as to improve the configuration efficiency of the target buried point parameter and reduce the consumption of human resources. Therefore, through a series of researches, the inventor proposes the technical scheme of the present application. In the embodiment of the present application, in response to a page rendering instruction, page configuration information is obtained, wherein the page configuration information includes initial buried point parameters corresponding to a plurality of page attributes respectively. Then, the page configuration information is parsed to determine the levels and the initial buried point parameters corresponding to the plurality of page attributes respectively. The initial buried point parameter of the highest level page attribute is taken as the target buried point parameter of the highest level page attribute. Starting from the next level page attribute of the highest level page attribute, the buried point parameter processing operation is performed on the page attribute of each level in turn, wherein the buried point parameter processing operation includes: determining a target page attribute that meets a first buried point splicing condition; and splicing the initial buried point parameter of the target page attribute and the target buried point parameter of the page attribute of the previous level corresponding to the target page attribute to obtain the target buried point parameter of the target page attribute. In the embodiment of the present application, the target buried point parameters of the page attributes of all levels are generated by automatic splicing, without manual splicing, so that the configuration efficiency of the target buried point parameter can be improved, manual configuration can be reduced, and the consumption of human resources can be reduced. The target buried point parameter generated in the embodiment of the present application can be used to generate buried point log data reflecting a complete user interaction path, so as to realize comprehensive and detailed user behavior analysis.

[0029] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose authorization or refusal.

[0030] Some embodiments of the present application can be described in detail below with reference to the accompanying drawings. The embodiments described below and the features and steps in the embodiments can be combined with each other without conflict. In addition, the step sequence in each method embodiment described below is only an example, not a strict limitation.

[0031] Figure 1 A flowchart of one embodiment of a buried point parameter generation method provided by the embodiment of the present application, which can include the following steps:

[0032] 101, in response to a page rendering instruction, obtaining page configuration information.

[0033] The page configuration information may include initial tracking parameters corresponding to multiple page attributes.

[0034] Page attributes can be used to define the display appearance of corresponding page elements and trigger events. For example, page attributes can include display parameters and event tracking parameters. Display parameters define the display appearance of the corresponding page element, while event tracking parameters define the trigger events for the corresponding page element. These trigger events refer to the information that the page element needs to collect.

[0035] The page configuration information can be obtained from the server. For example, the client can respond to a page rendering instruction by sending a page rendering request to the server, and the server can respond to the page rendering request by sending the page configuration information back to the client through an API (Application Programming Interface).

[0036] The configuration information on this page can be in JSON format, etc., and this invention does not limit it.

[0037] 102. Parse the page configuration information to determine the level and initial tracking parameters corresponding to multiple page attributes.

[0038] Because page elements can be nested, page attributes corresponding to page elements also have corresponding nesting relationships, with higher-level page attributes containing lower-level page attributes.

[0039] For example, the page configuration information in JSON format is as follows:

[0040] {

[0041] “page”:{

[0042] “logParams”:{

[0043] "pagename":"detail"

[0044] },

[0045] “serviceModel”:{

[0046] “logParams”:{

[0047] "modelname":"service"

[0048] },

[0049] "button":{

[0050] “logParams”:{

[0051] "buttonname": "zixun"

[0052] }

[0053] }

[0054] }

[0055] }

[0056] }

[0057] This page configuration information can be considered a global page attribute, which is the highest-level page attribute. This highest-level page attribute contains a page attribute named "page". The "page" page attribute includes a page attribute named "logParams":{"pagename":"detail"} and a page attribute named "serviceModel". "logParams":{"pagename":"detail"} is the initial tracking parameter corresponding to the "page" page attribute. The page attribute named "page" can correspond to the page element "page", and the initial tracking parameter "logParams":{"pagename":"detail"} defines the initial information to be collected when the page is triggered as "pagename":"detail". The "serviceModel" page attribute includes a page attribute named "logParams":{"modelname":"service"} and a page attribute named "button". The `logParams` parameter, `{"modelname":"service"}`, is the initial tracking parameter for the page attribute named "serviceModel". The page attribute "serviceModel" can correspond to a service module. The initial tracking parameter `logParams`, `{"modelname":"service"}`, defines the initial information to be collected when the service module is triggered as `"modelname":"service"`. Similarly, the page attribute named "button" contains the `logParams` parameter `{"buttonname":"zixun"}`. `logParams`, `{"buttonname":"zixun"}`, is the initial tracking parameter for the page attribute named "button". The page attribute "button" can correspond to a button. The initial tracking parameter `logParams`, `{"buttonname":"zixun"}`, defines the initial information to be collected when the button is triggered as `"buttonname":"zixun"`.

[0058] 103. Use the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute, and start from the next level of page attribute of the highest-level page attribute, and perform tracking parameter processing operations for each level of page attribute in turn.

[0059] The data tracking parameter processing operation includes: determining the target page attribute that meets the first data tracking concatenation condition; concatenating the initial data tracking parameters of the target page attribute with the target data tracking parameters of the page attribute at the next higher level corresponding to the target page attribute to obtain the target data tracking parameters of the target page attribute; and updating the page configuration information according to the target data tracking parameters corresponding to multiple page attributes.

[0060] Referring to the example above, if the page attribute named "page" meets the first event tracking concatenation condition, the initial event tracking parameter "logParams":{"pagename":"detail"} of the page attribute named "page" can be concatenated with the target event tracking parameter of the highest-level page element to obtain the target event tracking parameter of the page attribute named "page". In this example, the initial event tracking parameter, i.e., the target event tracking parameter, of the global page element, which is the highest-level page element, is empty, so the target event tracking parameter of the page attribute named "page" is "logParams":{"pagename":"detail"}. In the next level page attribute named "page", namely the page attribute named "logParams" ("logParams":{"pagename":"detail") and the page attribute named "serviceModel", if the page attribute named "serviceModel" meets the first data entry concatenation condition, the initial data entry parameter "logParams":{"modelname":"service") of the page attribute named "serviceModel" can be concatenated with the target data entry parameter "logParams":{"pagename":"detail") of the page attribute named "page" at the previous level, resulting in the target data entry parameter "logParams":{"pagename":"detail","modelname":"service") of the page attribute named "serviceModel". In the next level page attribute named "serviceModel", namely the page attribute named "logParams" ("logParams":{"modelname":"service"}) and the page attribute named "button", if the page attribute named "button" satisfies the first tracking point concatenation condition, the initial tracking point parameter "logParams":{"buttonname":"zixun"} of the page attribute named "button" is concatenated with the target tracking point parameter "logParams":{"pagename":"detail","modelname":"service"} of the page attribute named "serviceModel" at the previous level, resulting in the target tracking point parameter "logParams":{"pagename":"detail","modelname":"service","buttonname":"zixun"} of the page attribute named "button".

[0061] In practical applications, the page attribute named "page" corresponds to the page element "page", the page attribute named "serviceModel" corresponds to the page element "service module", and the page attribute named "button" corresponds to the page element "button". Pages can nest service modules, and service modules can nest buttons. The target tracking parameter for the page attribute named "page" is "logParams":{"pagename":"detail"}, which defines the information to be collected when the page is triggered: "pagename":"detail". The target tracking parameter for the page attribute named "serviceModel" is "logParams":{"pagename":"detail","modelname":"service"}, which defines the information to be collected when the service module is triggered, including the initial information "modelname":"service" to be collected when the service module is triggered, and the initial information "pagename":"detail" to be collected when the page is triggered. The target tracking parameter for the page attribute named "button" is "logParams":{"pagename":"detail","modelname":"service","buttonname":"zixun"}. This target tracking parameter defines the information to be collected when the button is triggered, including the initial information to be collected for the triggered button ("buttonname":"zixun"), the initial information to be collected for the triggered service module ("modelname":"service"), and the initial information to be collected for the triggered page ("pagename":"detail"). By using the target tracking parameter for the page attribute, when the page element corresponding to this attribute is triggered, the initial information of that page element and the initial information of all nested parent page elements can be collected, generating tracking log data, which is helpful for comprehensive data analysis.

[0062] 104. Update the page configuration information according to the target tracking parameters corresponding to multiple page attributes.

[0063] This involves updating the initial tracking parameters corresponding to multiple page attributes to the target tracking parameters, thereby updating the page configuration information. Based on this updated page configuration information, the system can collect the initial information of the page element corresponding to the page attribute, as well as the initial information of all parent page elements nested within that page element, based on the target tracking parameters of the page attribute, and generate tracking log data, which is helpful for comprehensive data analysis.

[0064] In this embodiment, in response to a page rendering command, page configuration information is obtained. This information includes initial tracking parameters corresponding to multiple page attributes. The page configuration information is then parsed to determine the levels and initial tracking parameters corresponding to the multiple page attributes. The initial tracking parameters of the highest-level page attribute are used as the target tracking parameters for that attribute. Starting from the next level of page attributes, tracking parameter processing operations are performed sequentially for each level of page attribute. These operations include: determining the target page attribute that meets the first tracking concatenation condition; concatenating the initial tracking parameters of the target page attribute with the target tracking parameters of the page attribute at the next higher level to obtain the target tracking parameters for the target page attribute. The page configuration information is then updated based on the target tracking parameters corresponding to the multiple page attributes. This embodiment generates target tracking parameters for all levels of page attributes automatically, eliminating the need for manual concatenation. This improves the efficiency of target tracking parameter configuration, reduces manual configuration, and lowers the consumption of human resources. In this embodiment, the target tracking parameters generated can be used to generate tracking log data that reflects the complete user interaction path, so as to achieve comprehensive and detailed user behavior analysis.

[0065] In some embodiments, determining the target page attribute that satisfies the first embedding point splicing condition may include: obtaining at least one first index parameter; and determining the target page attribute that matches the at least one first index parameter.

[0066] Specifically, based on the page attribute's identifier information, such as attribute name, and according to matching rules, the page attribute that matches at least one first index parameter can be determined. The matching rules can be exact match, partial match, regular expression match, or fuzzy match, etc.

[0067] For example, at least one first index parameter includes two first index parameters, "button" and "Model". Based on the partial matching matching rules, a page attribute named "serviceModel" and a page attribute named "button" can be indexed.

[0068] Obtaining at least one first index parameter can be achieved by obtaining at least one pre-configured first index parameter. Since different first index parameters can match different page attributes, different scenarios can be processed with different target page attribute types, and the first index parameters can be flexibly configured to meet different scenario requirements.

[0069] In some embodiments, parsing page configuration information to determine the levels and initial tracking parameters corresponding to multiple page attributes may include: parsing page configuration information to determine the levels and initial tracking parameters corresponding to multiple page attributes; and mapping multiple page attributes to multiple model objects.

[0070] Mapping multiple page attributes to multiple model objects allows the hierarchical relationship of multiple model objects to correspond to the hierarchical relationship of multiple page attributes. The initial tracking parameters corresponding to each of the multiple model objects are also the initial tracking parameters of the multiple page attributes corresponding to the multiple model objects.

[0071] For example, page configuration information can be in a structured data format such as JSON. This configuration information can be parsed into a data format that can be processed by object-oriented programming languages ​​such as Objective-C, mapping multiple page attributes to multiple model objects. These model objects can then execute specific functions to facilitate data processing.

[0072] Using the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute; starting from the next level of page attributes, sequentially performing tracking parameter processing operations for each level of page attribute may include: using the initial tracking parameters of the highest-level model object as the target tracking parameters of the highest-level model object; instantiating the highest-level model object and executing the tracking parameter processing function, so as to realize that starting from the next level of model objects, sequentially performing tracking parameter processing operations for each level of model objects.

[0073] The step-by-step parameter processing operation may include: determining a target model object that meets the second step-by-step splicing condition; splicing the initial step-by-step parameters of the target model object with the target step-by-step parameters of the model object at the next higher level corresponding to the target model object to obtain the target step-by-step parameters of the target model object.

[0074] The execution process of the tracking parameter processing function can be as follows: search for at least one target model object that satisfies the second tracking concatenation condition in the next level model object of the model object currently executing the tracking parameter processing function; concatenate the initial tracking parameters of any target model object with the target tracking parameters of the model object currently executing the tracking parameter processing function; determine whether any target model object satisfies the tracking processing condition, and if any target model object satisfies the tracking processing condition, execute the tracking parameter processing function for any target model object.

[0075] Since the highest-level model object nests other-level model objects, instantiating the highest-level model object automatically instantiates the nested model objects at the same time. Using the aforementioned tracking parameter processing function, all levels of model objects can be recursively traversed to generate target tracking parameters for model objects that meet the second tracking concatenation condition. The target tracking parameters of the model object are also the target tracking parameters of the corresponding page attributes of the model object.

[0076] Optionally, a root class can be pre-configured, which contains the function for handling tracking parameters. Multiple model objects corresponding to multiple page attributes can inherit from this root class so that multiple model objects can execute the function for handling tracking parameters.

[0077] Optionally, a tracking parameter protocol can be pre-configured, which can define processing judgment functions and index parameter configuration functions, so that multiple model objects can follow the tracking parameter protocol and execute the processing judgment functions and index parameter configuration functions.

[0078] Optionally, at least one second index parameter returned by the execution index parameter configuration function can be pre-configured. Searching for at least one target model object satisfying the second tracking point concatenation condition in the next-level model object of the model object currently executing the tracking point parameter processing function may include: determining at least one second index parameter returned by the execution index parameter configuration function of the model object currently executing the tracking point parameter processing function; and, based on at least one second index parameter, determining at least one target model object matching the at least one second index parameter in the next-level model object of the model object currently executing the tracking point parameter processing function.

[0079] Specifically, based on the model object's identification information, such as the object name, and according to matching rules, at least one target model object that matches at least one second index parameter can be determined. The matching rules can be exact matching, partial matching, regular expression matching, or fuzzy matching, etc.

[0080] Optionally, the return values ​​of the processing judgment functions executed by different model objects can be pre-configured. As an optional implementation, the event tracking condition can refer to the return value of the processing judgment function being a predetermined value, such as 1. For example, the return value of the processing judgment function executed by the lowest-level model object can be pre-set to a value other than the predetermined value, causing the event tracking parameter processing function to stop executing when it reaches the lowest-level model object. Furthermore, developers can also set the return value of the processing judgment function executed by model objects other than the lowest-level model object that do not require event tracking to a value other than the predetermined value. As another optional implementation, the event tracking condition can refer to the model object having initial event tracking parameters.

[0081] In some embodiments, the page configuration information may include initial tracking parameters and display parameters corresponding to multiple page attributes.

[0082] Parsing page configuration information to determine the hierarchy and initial tracking parameters corresponding to multiple page attributes may include: parsing page configuration information, determining the hierarchy and initial tracking parameters corresponding to multiple page attributes, and determining the display parameters corresponding to multiple page attributes.

[0083] In some embodiments, the method may further include: rendering and generating a user interaction page based on the target tracking parameters and display parameters corresponding to multiple page attributes.

[0084] As mentioned earlier, parsing page configuration information can map multiple page attributes to multiple model objects. Rendering and generating a user interaction page based on the target tracking parameters and display parameters corresponding to each of the multiple page attributes can include: rendering and generating a user interaction page based on the target tracking parameters and display parameters corresponding to each of the multiple model objects.

[0085] In some implementations, the method may further include: in response to a user's triggering operation on any page element in the user interaction page, generating tracking log data based on the target tracking parameters of the page attributes corresponding to the page element; and reporting the tracking log data to the server.

[0086] The server can receive and store reported event tracking log data, and use data mining, machine learning, and other technologies to analyze the log data and extract features of user interaction behavior. Based on the analysis results, page configurations are optimized to improve user experience.

[0087] Figure 2 This is a schematic diagram of a device for generating embedded parameters according to an embodiment of the present invention. The device may include:

[0088] The acquisition module 201 is used to obtain page configuration information in response to page rendering instructions; wherein, the page configuration information includes initial tracking parameters corresponding to multiple page attributes;

[0089] Parsing module 202 is used to parse page configuration information and determine the level and initial tracking parameters corresponding to multiple page attributes.

[0090] The processing module 203 is used to take the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute; starting from the next level of page attributes of the highest-level page attribute, the tracking parameter processing operation is performed sequentially for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking concatenation condition; concatenating the initial tracking parameters of the target page attribute with the target tracking parameters of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameters of the target page attribute;

[0091] Update module 204 is used to update page configuration information based on the target tracking parameters corresponding to multiple page attributes.

[0092] In some embodiments, the processing module may determine the target page attribute that satisfies the first embedding point splicing condition by: obtaining at least one first index parameter; and determining the target page attribute that matches the at least one first index parameter.

[0093] In some embodiments, the parsing module parsing page configuration information to determine the hierarchy and initial tracking parameters corresponding to multiple page attributes may include: parsing page configuration information to determine the hierarchy and initial tracking parameters corresponding to multiple page attributes; and mapping multiple page attributes to multiple model objects.

[0094] The processing module uses the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute. Starting from the next level of page attributes, the tracking parameter processing operation is performed sequentially for each level of page attribute. This may include: using the initial tracking parameters of the highest-level model object as the target tracking parameters of the highest-level model object; instantiating the highest-level model object and executing the tracking parameter processing function, so as to realize that starting from the next level of model objects, the tracking parameter processing operation is performed sequentially for each level of model objects.

[0095] The step-by-step parameter processing operation includes: determining a target model object that meets the second step-by-step splicing condition; splicing the initial step-by-step parameters of the target model object with the target step-by-step parameters of the model object at the next higher level corresponding to the target model object to obtain the target step-by-step parameters of the target model object.

[0096] The event tracking parameter processing function can be as follows: Search for at least one target model object that satisfies the second event tracking concatenation condition in the next-level model object of the model object currently executing the event tracking parameter processing function; concatenate the initial event tracking parameters of any target model object with the target event tracking parameters of the model object currently executing the event tracking parameter processing function to obtain the target event tracking parameters of any target model object; determine whether any target model object satisfies the event tracking processing condition; if any target model object satisfies the event tracking processing condition, execute the event tracking parameter processing function on any target model object.

[0097] In some embodiments, the page configuration information may include display parameters corresponding to multiple page attributes;

[0098] The parsing module parses the page configuration information and determines the hierarchy and initial tracking parameters corresponding to multiple page attributes. This can include: parsing the page configuration information, determining the hierarchy and initial tracking parameters corresponding to multiple page attributes, and determining the display parameters corresponding to multiple page attributes.

[0099] In some embodiments, the device may further include:

[0100] The rendering module is used to render and generate user interaction pages based on the target tracking parameters and display parameters corresponding to multiple page attributes.

[0101] In some embodiments, the device may further include:

[0102] The log generation module is used to respond to user actions triggered by any page element on the user interaction page, generate event log data based on the target event parameters of the page attributes corresponding to any page element, and report the event log data to the server.

[0103] In some embodiments, updating the page configuration information based on the target tracking parameters corresponding to multiple page attributes may include: updating the initial tracking parameters corresponding to the multiple page attributes to the target tracking parameters to update the page configuration information.

[0104] Figure 2 The device shown can perform Figure 1 For the methods shown in the embodiments, the parts not described in detail in this embodiment can be referred to the following: Figure 1 The relevant descriptions of the illustrated embodiments are provided below. For the execution process and technical effects of this technical solution, please refer to [link / reference]. Figure 1 The descriptions in the illustrated embodiments will not be repeated here.

[0105] In one possible design, Figure 1 The method for generating embedded point parameters provided in the illustrated embodiment can be applied to an electronic device, such as... Figure 3 As shown, the electronic device may include a processor 31 and a memory 32. The memory 32 is used to store data supporting the electronic device in performing the aforementioned operations. Figure 1 In the illustrated embodiment, the program for generating embedding parameters is provided, and the processor 31 is configured to execute the program stored in the memory 32.

[0106] The program includes one or more computer instructions, wherein when executed by processor 31, the one or more computer instructions can perform the following steps:

[0107] In response to a page rendering command, obtain page configuration information; the page configuration information includes initial tracking parameters corresponding to multiple page attributes.

[0108] Parse the page configuration information to determine the hierarchy corresponding to the multiple page attributes and the initial tracking parameters;

[0109] Use the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute;

[0110] Starting from the next level of page attributes below the highest level page attribute, the tracking parameter processing operation is performed sequentially for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking splicing condition; splicing the initial tracking parameter of the target page attribute with the target tracking parameter of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameter of the target page attribute.

[0111] The page configuration information is updated based on the target tracking parameters corresponding to the multiple page attributes.

[0112] Optionally, processor 31 is also used to perform the aforementioned Figure 1 All or part of the steps in the illustrated embodiments.

[0113] The structure of the electronic device may also include a communication interface 33 for the electronic device to communicate with other devices or communication systems.

[0114] In addition, embodiments of the present invention provide a computer storage medium for storing computer software instructions used by the aforementioned electronic device, which includes instructions for executing the above-mentioned... Figure 1 The program involved in the method for generating embedded point parameters shown.

[0115] In addition, embodiments of the present invention provide a computer program product. This computer program product includes a computer program or instructions. When the computer program or instructions are executed by a processor, the processor is able to perform the above-described functions. Figure 1 The steps or functions of the method shown.

[0116] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for generating embedded point parameters, characterized in that, Applied to the client side, including: In response to a page rendering command, obtain page configuration information; the page configuration information includes initial tracking parameters corresponding to multiple page attributes. Parse the page configuration information to determine the hierarchy corresponding to the multiple page attributes and the initial tracking parameters; Use the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute; Starting from the next level of page attributes below the highest level page attribute, the tracking parameter processing operation is performed sequentially for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking splicing condition; splicing the initial tracking parameter of the target page attribute with the target tracking parameter of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameter of the target page attribute. The page configuration information is updated based on the target tracking parameters corresponding to the multiple page attributes.

2. The method according to claim 1, characterized in that, The target page attributes that satisfy the first embedding point splicing condition include: Obtain at least one first index parameter; Determine the target page attribute that matches the at least one first index parameter.

3. The method according to claim 1, characterized in that, The step of parsing the page configuration information and determining the hierarchy corresponding to the multiple page attributes and the initial tracking parameters includes: Parse the page configuration information to determine the levels corresponding to the multiple page attributes and the initial tracking parameters; map the multiple page attributes to multiple model objects; The step of using the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute, and performing tracking parameter processing operations sequentially for each level of page attribute starting from the next level of the highest-level page attribute, includes: using the initial tracking parameters of the highest-level model object as the target tracking parameters of the highest-level model object; instantiating the highest-level model object and executing the tracking parameter processing function, so as to realize that the tracking parameter processing operations are performed sequentially for each level of model object starting from the next level of the highest-level model object; The step-by-step parameter processing operation includes: determining a target model object that meets the second step-by-step splicing condition; splicing the initial step-by-step parameters of the target model object with the target step-by-step parameters of the model object at the next higher level corresponding to the target model object to obtain the target step-by-step parameters of the target model object.

4. The method according to claim 1, characterized in that, The page configuration information also includes display parameters corresponding to multiple page attributes; The step of parsing the page configuration information and determining the hierarchy corresponding to the multiple page attributes and the initial tracking parameters includes: The page configuration information is parsed to determine the levels corresponding to the multiple page attributes and the initial tracking parameters, and the display parameters corresponding to the multiple page attributes are also determined.

5. The method according to claim 4, characterized in that, Also includes: Based on the target tracking parameters and display parameters corresponding to the multiple page attributes, a user interaction page is rendered and generated.

6. The method according to claim 5, characterized in that, Also includes: In response to a user's trigger operation on any page element in the user interaction page, track point log data is generated based on the target track point parameters of the page attributes corresponding to the page element. The data from the data collection points is reported to the server.

7. The method according to claim 1, characterized in that, The step of updating the page configuration information according to the target tracking parameters corresponding to the multiple page attributes includes: The initial tracking parameters corresponding to the multiple page attributes are updated to the target tracking parameters to update the page configuration information.

8. A device for generating embedded point parameters, characterized in that, include: The acquisition module is used to retrieve page configuration information in response to page rendering commands; The page configuration information includes initial tracking parameters corresponding to multiple page attributes; The parsing module is used to parse the page configuration information, determine the levels corresponding to the multiple page attributes, and the initial tracking parameters. The processing module is used to take the initial tracking parameters of the highest-level page attribute as the target tracking parameters of the highest-level page attribute; Starting from the next level of page attributes below the highest level page attribute, the tracking parameter processing operation is performed sequentially for each level of page attribute; wherein, the tracking parameter processing operation includes: determining the target page attribute that meets the first tracking splicing condition; splicing the initial tracking parameter of the target page attribute with the target tracking parameter of the page attribute corresponding to the previous level of the target page attribute to obtain the target tracking parameter of the target page attribute. The update module is used to update the page configuration information according to the target tracking parameters corresponding to the multiple page attributes.

9. An electronic device, characterized in that, include: The device includes a memory, a processor, and a communication interface; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor performs the method for generating embedding parameters as described in any one of claims 1 to 7.

10. A non-transitory machine-readable storage medium, characterized in that, The non-transitory machine-readable storage medium stores executable code, which, when executed by a processor of an electronic device, causes the processor to perform the embedding parameter generation method as described in any one of claims 1 to 7.

Images