Data generation method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a data generation method and device, electronic equipment and a storage medium, and the method comprises the steps: responding to a triggering operation for a user interaction component in a form, obtaining a subitem component through data associated with the user interaction component in the form, acquiring behavior data corresponding to the trigger operation and first business data associated with the user interaction component; acquiring second business data associated with the form through a data acquisition component associated with a form component of the form in the form; wherein the form component is a component corresponding to a root node in a document object model (DOM) tree of the form; and generating burying point data of the form according to the behavior data, the first business data and the second business data. Through the embodiment, the burying point data of the form can be accurately generated, and a data basis is provided for improving the operation experience of a user for the form.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and in particular, to a data generation method, apparatus, electronic device, and storage medium. Background Art

[0002] With the development of computer technologies, web pages have become the main platforms for people to obtain information and communicate with each other. Users can fill in question answers, registration information, etc. in the forms on the web pages, so as to achieve purposes such as questionnaire surveys and user registrations based on the forms. The structure of a form is usually relatively complex, and may include one or more user input boxes, and may also include one or more trigger controls. Based on this, in order to improve the user operation experience for forms, it is necessary to provide a technical solution that can accurately generate buried point data for forms, so as to provide a data basis for improving the user operation experience for forms. Summary of the Invention

[0003] Embodiments of the present disclosure provide a data generation method, apparatus, electronic device, and storage medium, which can accurately generate buried point data for forms and provide a data basis for improving the user operation experience for forms.

[0004] In a first aspect, an embodiment of the present disclosure provides a data generation method, including:

[0005] In response to a trigger operation on a user interaction component in a form, obtain behavior data corresponding to the trigger operation and first service data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form;

[0006] Obtain second service data associated with the form through a data acquisition component associated with a form component of the form; wherein, the form component is a component corresponding to the root node in the document object model (DOM) tree of the form;

[0007] Generate buried point data for the form according to the behavior data, the first service data, and the second service data.

[0008] In a second aspect, an embodiment of the present disclosure provides a data generation apparatus, including:

[0009] A first acquisition unit, configured to, in response to a trigger operation on a user interaction component in a form, obtain behavior data corresponding to the trigger operation and first service data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form;

[0010] A second acquisition unit, configured to acquire second service data associated with the form through a data acquisition component associated with a form component of the form; wherein, the form component is a component corresponding to a root node in a document object model (DOM) tree of the form.

[0011] A data generation unit, configured to generate buried point data of the form according to the behavior data, the first service data, and the second service data.

[0012] In a third aspect, embodiments of the present disclosure provide an electronic device, including: a processor; and a memory configured to store computer-executable instructions, where the computer-executable instructions, when executed, cause the processor to implement the steps of the method described in the first aspect above.

[0013] In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium, configured to store computer-executable instructions, where the computer-executable instructions, when executed by a processor, implement the steps of the method described in the first aspect above.

[0014] In one or more embodiments of the present disclosure, first, in response to a trigger operation on a user interaction component in a form, a behavior data corresponding to the trigger operation and first service data associated with the user interaction component are acquired through a data acquisition sub-item component associated with the user interaction component in the form, and then, second service data associated with the form is acquired through a data acquisition component associated with a form component of the form, where the form component is a component corresponding to a root node in a document object model (DOM) tree of the form, and finally, buried point data of the form is generated according to the behavior data, the first service data, and the second service data. It can be seen that through this embodiment, the behavior data corresponding to the trigger operation, the first service data associated with the user interaction component, and the second service data associated with the form can be accurately acquired through the data acquisition sub-item component and the data acquisition component of the form, and the buried point data of the form is generated according to the behavior data, the first service data, and the second service data, so as to achieve the effect of accurately generating the buried point data of the form and provide a data basis for improving the operation experience of a user for the form. Description of the Drawings

[0015] In order to more clearly illustrate the technical solutions in one or more embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings described below are only some embodiments recorded in the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0016] Figure 1Schematic flowchart of a data generation method provided by an embodiment of the present disclosure;

[0017] Figure 2 Schematic diagram of a form provided by an embodiment of the present disclosure;

[0018] Figure 3 Schematic structural diagram of the DOM tree of a form provided by an embodiment of the present disclosure;

[0019] Figure 4 Schematic hierarchical structure diagram of components in a form provided by another embodiment of the present disclosure;

[0020] Figure 5 Schematic structural diagram of a data generation device provided by an embodiment of the present disclosure;

[0021] Figure 6 Schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Detailed implementation manners

[0022] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of the present disclosure, the following will clearly and completely describe the technical solutions in one or more embodiments of the present disclosure with reference to the accompanying drawings in one or more embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all the embodiments. Based on one or more embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present disclosure.

[0023] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure shall be informed to the user and the user's authorization shall be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0024] For example, when responding to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server, or a storage medium that performs the operations of the technical solutions of the present disclosure according to the prompt message.

[0025] As an optional but non-limiting implementation manner, the manner of sending a prompt message to the user in response to receiving an active request from the user may be, for example, in the form of a pop-up window, and the prompt message may be presented in text in the pop-up window. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0026] It is understandable that the above-mentioned notice and the process of obtaining user authorization are only illustrative and do not limit the implementation manner of the present disclosure. Other manners that comply with relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0027] An embodiment of the present disclosure provides a data generation method, which can accurately generate buried point data of a form and provide a data basis for improving the operation experience of a user for the form. This data generation method can be applied to a terminal device and executed by the terminal device. The terminal device includes, but is not limited to, electronic devices such as mobile phones, computers, desktop computers, laptop computers, tablet computers, PADs, in-vehicle computers, and wearable devices.

[0028] Figure 1 is a schematic flowchart of the data generation method provided by an embodiment of the present disclosure, as Figure 1 shown, this process includes:

[0029] Step S102, in response to a trigger operation on a user interaction component in the form, obtain the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form;

[0030] Step S104, obtain the second service data associated with the form through a data acquisition component associated with the form component of the form; wherein, the form component is the component corresponding to the root node in the DOM (Document Object Model) tree of the form;

[0031] Step S106, generate the buried point data of the form according to the behavior data, the first service data, and the second service data.

[0032] In this embodiment, first, in response to a trigger operation on a user interaction component in the form, obtain the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form. Then, obtain the second service data associated with the form through a data acquisition component associated with the form component of the form, where the form component is the component corresponding to the root node in the DOM tree of the form. Finally, generate the buried point data of the form according to the behavior data, the first service data, and the second service data. It can be seen that through this embodiment, the behavior data corresponding to the trigger operation, the first service data associated with the user interaction component, and the second service data associated with the form can be accurately obtained through the data acquisition sub-item component and the data acquisition component of the form, and the buried point data of the form can be generated according to the behavior data, the first service data, and the second service data, so as to achieve the effect of accurately generating the buried point data of the form and provide a data basis for improving the operation experience of a user for the form.

[0033] The method in Figure 1 will be introduced in detail below. In this embodiment, a form is displayed on the terminal device. In the web page where the form is located, in addition to the form, it may also include at least one of pictures, videos, and texts, or may not include other elements, that is, only the form is displayed on the web page. User interaction components are displayed in the form. User interaction components refer to components with which users can perform interaction behaviors, including but not limited to at least one of input boxes and buttons.

[0034] Figure 2 is a schematic diagram of a form provided by an embodiment of the present disclosure. As Figure 2 shown, in an example, a web page is displayed on the terminal device, and a form is displayed in the web page. Moreover, only the form is displayed on the web page and no other elements are displayed. For example, on the user reservation page, as Figure 2 shown, the form includes a user name input box, a user interest type selection box, a user description input box, and a submit button. The user name input box, the user interest type selection box, the user description input box, and the submit button are all user interaction components.

[0035] In this embodiment, when the terminal device interacts with the server and displays the web page, the terminal device can receive HTML (Hyper Text Markup Language) data, XML (Extensible Markup Language) data, or XHTML (Extensible Hyper Text Markup Language) data sent by the server, use the received data as a parsing object, and parse the parsing object to obtain a DOM tree. The DOM tree includes multiple nodes with a hierarchical relationship. The nodes have a corresponding relationship with the components in the web page. Based on the DOM tree, the web page to be displayed can be rendered. For the form, the form also has a corresponding DOM tree. The DOM tree of the form is a part of the DOM tree of the web page. The DOM tree of the form includes multiple nodes with a hierarchical relationship. The nodes have a corresponding relationship with the components in the form. Based on the DOM tree of the form, the form can be rendered.

[0036] Figure 3 is a schematic structural diagram of the DOM tree of a form provided by an embodiment of the present disclosure. As Figure 3 shown, in the DOM tree of the form, there is a root node and multiple child nodes. Among them, the root node corresponds to the form component of the form, and the child nodes can correspond to the user interaction components in the form. For example, it corresponds to Figure 2The user name input box, user interest type selection box, user description input box, and submit button in it. The form component is a component invisible to the user, and the user interaction component is a component visible to the user. The form component is used to store the basic data of the form, including but not limited to the form name, form source, form attributes, etc. The form component can also be used to manage each user interaction component.

[0037] Reference Figure 3 , since the root node of the DOM tree of the form corresponds to the form component of the form, and the child nodes of the DOM tree of the form correspond to the user interaction components in the form, therefore, the node corresponding to the form component is the parent node of the node corresponding to the user interaction component, and the form component is the parent component of the user interaction component.

[0038] In one embodiment, the DOM tree of the form can be a virtual DOM tree, then the form component and the user interaction component are the components corresponding to the virtual DOM tree. Among them, the virtual DOM tree can be a react DOM tree, then the form component and the user interaction component are react components. The virtual DOM tree is compiled to obtain a real DOM tree, and the form is obtained by rendering the real DOM tree. In another embodiment, the DOM tree of the form can be a real DOM tree, then the form component and the user interaction component are the components corresponding to the real DOM tree, and the form is obtained by rendering the real DOM tree.

[0039] It can be understood that the DOM tree of the form is a part of the DOM tree of the web page where the form is located. The form component corresponds to the root node in the DOM tree of the form, and the root node in the DOM tree of the form is not the root node in the DOM tree of the web page. In the DOM tree of the web page, there is another root node of the web page, and the root node of the web page is the parent node of the root node in the DOM tree of the form.

[0040] In this embodiment, the user interaction component in the form is also associated with a data acquisition sub-item component. The form component of the form is also associated with a data acquisition component. Figure 4 This is a schematic diagram of the hierarchical structure of the components in the form provided by another embodiment of the present disclosure. Reference Figure 4 , in the components of the form, in addition to including the form component corresponding to the root node in the DOM tree and the user interaction component corresponding to the child node in the DOM tree, it also includes a data acquisition component associated with the form component and a data acquisition sub-item component associated with the user interaction component. Among them, the data acquisition sub-item component wraps the user interaction component, and the data acquisition component wraps the form component. In one embodiment, based on the virtual DOM tree react technology, the structure of the components in the form shown in Figure 4 is implemented. In Figure 4 , the user interaction component can be Figure 2The user name input box, user interest type selection box, user description input box, and submission button in

[0041] In one embodiment, the data acquisition sub-component and the data acquisition component are used to generate the buried point data of the form. To avoid affecting the user's operation of the form, the data acquisition sub-component and the data acquisition component are set to be in an invisible state, which are invisible components to the user, so as to ensure the user's normal operation of the form.

[0042] Refer again to Figure 3 As shown, in Figure 3 In the DOM tree of the form shown, at the root node, that is, the node corresponding to the form component, a listener is marked. This listener is the schematic representation in the DOM tree of the data acquisition component associated with the form component. By wrapping the data acquisition component outside the form component, the effect of adding a listener at the root node of the form is achieved, so as to obtain the second business data of the form through the data acquisition component.

[0043] Similarly, in Figure 3 In the DOM tree of the form shown, at the child node, that is, the node corresponding to the user interaction component, a listener is marked. This listener is the schematic representation in the DOM tree of the data acquisition sub-component associated with the user interaction component. By wrapping the data acquisition sub-component outside the user interaction component, the effect of adding a listener at the user interaction component of the form is achieved, so as to obtain the behavior data corresponding to the trigger operation and the first business data associated with the user interaction component through the data acquisition sub-component.

[0044] Based on the above Figure 2 The form schematically shown in Figure 3 The DOM tree structure of the form schematically shown in Figure 4 And the hierarchical structure of the components in the form schematically shown in

[0045] In step S102 above, in response to a trigger operation on the user interaction component in the form, the behavior data corresponding to the trigger operation and the first business data associated with the user interaction component are obtained through the data acquisition sub-component associated with the user interaction component in the form.

[0046] In the above step S104, through the data acquisition component associated with the form component of the form, the second business data associated with the form is acquired. As described above, the form component is the component corresponding to the root node in the DOM tree of the form. The second business data includes all the business data in the form, including but not limited to the form name, form source, and the first business data corresponding to each user interaction component in the form, etc.

[0047] In the above step S106, based on the behavior data, the first business data, and the second business data, the buried point data of the form is generated.

[0048] It can be seen that through this embodiment, the behavior data corresponding to the trigger operation, the first business data associated with the user interaction component, and the second business data associated with the form can be accurately acquired through the data acquisition sub-component and the data acquisition component of the form, and based on the behavior data, the first business data, and the second business data, the buried point data of the form is generated, so as to achieve the effect of accurately generating the buried point data of the form and provide a data basis for improving the user's operation experience for the form.

[0049] Moreover, through this embodiment, the buried point data of the form can be generated based on the behavior data, the first business data, and the second business data, so that the buried point data of the form covers the behavior data and the business data, improving the diversity and comprehensiveness of the buried point data of the form.

[0050] Moreover, through this embodiment, there is no need to implant the code for acquiring the buried point data of the form in the form in a hard-coded manner. Only by developing the data acquisition component and the data acquisition sub-component for the form can the buried point data be generated, reducing the programming difficulty, reducing the code intrusion of the form when acquiring the buried point data, and the data acquisition component and the data acquisition sub-component can be adapted to different forms, expanding the application scenarios for generating the buried point data, so that the operation experience of the user for the form can be effectively evaluated through the buried point data.

[0051] In one embodiment, before responding to the trigger operation on the user interaction component in the form, the above method flow further includes:

[0052] The data acquisition sub-component is associated with the user interaction component by setting the data acquisition sub-component to wrap the user interaction component;

[0053] The data acquisition component is associated with the form component by setting the data acquisition component to wrap the form component.

[0054] In this embodiment, before responding to a trigger operation on a user interaction component in a form, a data acquisition sub-item component is created. The data acquisition sub-item components correspond one-to-one with the user interaction components in the form, and the data acquisition sub-item components belonging to the form can be created by developing components for the form.

[0055] In this embodiment, a data acquisition component is also created. The data acquisition component corresponds to the form component of the form. Generally speaking, if a form has a form component, it also has a data acquisition component. The data acquisition component belonging to the form can be created by developing components for the form.

[0056] Next, set the data acquisition sub-item component to wrap the corresponding user interaction component, and associate the data acquisition sub-item component with the user interaction component through the way of component wrapping. Also, set the data acquisition component to wrap the form component, and associate the data acquisition component with the form component through the way of component wrapping.

[0057] In this embodiment, in order not to affect the user's operation of the form, the data acquisition sub-item component and the data acquisition component are set to be in an invisible state, which are invisible components to the user, so as to ensure the user's normal operation of the form.

[0058] It can be seen that through this embodiment, based on the way of component wrapping, the data acquisition sub-item component can be quickly associated with the user interaction component, and the data acquisition component can be quickly associated with the form component, thereby improving the generation efficiency of the buried point data of the form.

[0059] In one embodiment, before obtaining the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through the data acquisition sub-item component associated with the user interaction component in the form, the above method flow further includes:

[0060] Based on the event delegation mechanism between components, set the user interaction component to report the behavior data of the trigger operation to the associated data acquisition sub-item component.

[0061] In this embodiment, before responding to a trigger operation on a user interaction component in the form and obtaining the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through the data acquisition sub-item component associated with the user interaction component in the form, based on the event delegation mechanism between components, set the user interaction component to report the behavior data of the trigger operation to the associated data acquisition sub-item component, so that the data acquisition sub-item component can obtain the behavior data corresponding to the trigger operation from the associated user interaction component.

[0062] In one example, based on the event delegation mechanism between components, each user interaction component in the form reports the behavior data of the trigger operation that occurs on the user interaction component to the associated data acquisition sub-item component. Thus, in accordance with the principle of upward bubbling propagation of event data, the data acquisition sub-item component obtains the behavior data of the trigger operation that occurs on the associated user interaction component from the associated user interaction component.

[0063] It can be seen that through this embodiment, based on the event delegation mechanism between components, each user interaction component in the form can be set to report the behavior data of the trigger operation that occurs on the user interaction component to the associated data acquisition sub-item component, thereby facilitating the data acquisition sub-item component to quickly obtain the behavior data of the trigger operation.

[0064] Correspondingly, in one embodiment, the behavior data corresponding to the trigger operation is obtained through the data acquisition sub-item component associated with the user interaction component in the form, including:

[0065] Through the data acquisition sub-item component, the behavior data corresponding to the trigger operation reported by the user interaction component is obtained.

[0066] In this embodiment, the user interaction component can collect the behavior data corresponding to the trigger operation and report the behavior data to the associated data acquisition sub-item component. The trigger operation is the user operation corresponding to the trigger event. In one example, the trigger event includes but is not limited to at least one of a form submission event, a form cancellation event, a form modification event, a form input event, a form click event, a form blur event, a form paste event, a form exposure event, and a form sub-item exposure event.

[0067] Among them, the form submission event refers to the event that the user submits the form to the server, the form cancellation event refers to the event that the user exits the form, the form modification event refers to the event that the user modifies the data input into the form, the form input event refers to the event that the user inputs data in the form, the form click event refers to the event that the user performs a click in the form, the form blur event refers to the event that the form is not on the page where the current cursor is located due to user operation on the form, the form paste event refers to the event that the user pastes the copied data into the form, the form exposure event refers to the event that the form is on the page where the current cursor is located due to user operation on the form, and the form sub-item exposure event refers to the event that a sub-item in the form such as an input item or a click item is on the page where the current cursor is located due to user operation on the form.

[0068] Accordingly, the trigger operations corresponding to the above trigger events are respectively: form submission operation, form cancellation operation, form modification operation, form input operation, form click operation, form blur operation (such as the operation of exiting the form), form paste operation, form exposure operation (such as the operation of entering the form), and form sub-item exposure operation (such as the operation of making the sub-items of the form visible by swiping the screen).

[0069] Accordingly, the behavior data corresponding to the above trigger operations are respectively: form submission time, form cancellation time, form modification start time and end time, form input start time and end time, form click time, form blur time, form paste time, form exposure start time and end time (the end time is the form blur time), and form sub-item exposure start time and end time.

[0070] In this embodiment, the behavior data may further include the form exposure duration, which is calculated based on the form exposure start time and end time. In this embodiment, when the terminal device responds to the user inputting data in the form, it can also automatically verify the input data, such as determining whether the number of digits of the mobile phone number is correct. Based on this, the form verification start time and end time can also be obtained as the behavior data corresponding to the trigger operation.

[0071] It can be seen that through this embodiment, the data acquisition sub-item component can obtain the behavior data corresponding to the trigger operation reported by the user interaction component, and through the event delegation mechanism between components, the efficiency of the data acquisition sub-item component in obtaining the behavior data corresponding to the trigger operation can be improved.

[0072] In another embodiment, based on the event delegation mechanism between components, the data acquisition sub-item component can be set to be able to listen for the trigger operations on the associated user interaction component.

[0073] In this embodiment, through the event delegation mechanism between components, the data acquisition sub-item component is set to be able to listen for the trigger operations on the associated user interaction component. Examples of trigger operations can be seen in the above explanations.

[0074] Through this embodiment, based on the event delegation mechanism between components, the data acquisition sub-item component can be set to be able to listen for the trigger operations on the associated user interaction component, so that the data acquisition sub-item component can learn in the first time that a trigger operation has occurred on the user interaction component.

[0075] Based on this, in this embodiment, the behavior data corresponding to the trigger operation is obtained through the data acquisition sub-item component, including: after the data acquisition sub-item component monitors the trigger operation on the associated user interaction component, the behavior data corresponding to the trigger operation is obtained. For example, after the data acquisition sub-item component monitors that a click operation has occurred on the associated user interaction component, the click time corresponding to the click operation is obtained.

[0076] In this embodiment, the user interaction component may not collect the behavior data corresponding to the trigger operation. Instead, after the data acquisition sub-item component monitors the trigger operation on the associated user interaction component, it collects the behavior data corresponding to the trigger operation. The behavior data corresponding to the trigger operation can be referred to the above explanation.

[0077] Through this embodiment, after the data acquisition sub-item component monitors that a trigger operation has occurred on the associated user interaction component, it can quickly collect the behavior data corresponding to the trigger operation, thus eliminating the process of using the user interaction component to collect the behavior data corresponding to the trigger operation.

[0078] In one embodiment, the first service data associated with the user interaction component is obtained through the data acquisition sub-item component associated with the user interaction component in the form, including:

[0079] The first service data associated with the user interaction component is obtained from the component attribute data of the user interaction component through the data acquisition sub-item component.

[0080] In this embodiment, the first service data associated with the user interaction component is recorded in the component attribute data of the user interaction component. The first service data includes but is not limited to the service fields corresponding to the user interaction component. Examples of the service fields can be "user name", "user interest type", "user description", and "submit control", etc. Based on this, through the data acquisition sub-item component, based on the component attribute data proxy mechanism, the first service data associated with the user interaction component is obtained from the component attribute data of the associated user interaction component.

[0081] It can be seen that through this embodiment, the first service data associated with the user interaction component can be quickly and accurately obtained from the component attribute data of the user interaction component through the data acquisition sub-item component.

[0082] In one embodiment, before obtaining the second service data associated with the form through the data acquisition component associated with the form component of the form, it is also possible to:

[0083] Report the behavior data and the first service data to the data acquisition component through the data acquisition sub-item component; the data acquisition component is the upper-level component of the data acquisition sub-item component;

[0084] Accordingly, through the data acquisition component associated with the form components of the form, the second business data associated with the form is acquired, including:

[0085] In response to the data acquisition component receiving the behavior data and the first business data, through the data acquisition component, the second business data associated with the form is acquired.

[0086] According to the previous description, the form component is the superior component of each user interaction component. Based on this, the data acquisition component is the superior component of each data acquisition sub-item component. Therefore, in this embodiment, before acquiring the second business data associated with the form through the data acquisition component, through each data acquisition sub-item component, the behavior data and the first business data acquired by each data acquisition sub-item component are respectively reported to the data acquisition component for summarization.

[0087] Accordingly, since it is not necessary for the data acquisition component to separately acquire the second business data and generate the buried point data, in response to the data acquisition component receiving the behavior data and the first business data reported by one or more data acquisition sub-item components, through the data acquisition component, the second business data associated with the form is acquired. The second business data includes all business data in the form, including but not limited to the form name, form source, the first business data corresponding to each user interaction component in the form, etc.

[0088] It can be seen that through this embodiment, the behavior data and the first business data can be reported to the data acquisition component through the data acquisition sub-item component, and the acquisition of the second business data associated with the form by the data acquisition component is triggered through this reporting operation, so as to realize the data transmission between the data acquisition sub-item component and the data acquisition component, enabling the data acquisition component to acquire the second business data only when necessary and avoiding wasting the processing resources of the terminal device.

[0089] In one embodiment, through the data acquisition component associated with the form components of the form, the second business data associated with the form is acquired, including:

[0090] Through the data acquisition component, the business data associated with the form component is acquired from the component attribute data of the form component as the second business data associated with the form.

[0091] In this embodiment, the component attribute data of the form component records the business data associated with the form component. The business data associated with the form component is the business data associated with the form. Based on this, through the data acquisition component, based on the component attribute data proxy mechanism, the business data associated with the form component is obtained from the component attribute data of the form component as the business data associated with the form, that is, as the second business data. The second business data includes all the business data in the form, including but not limited to the form name, form source, the first business data corresponding to each user interaction component in the form, etc.

[0092] It can be seen that through this embodiment, the data acquisition component can quickly and accurately obtain the business data associated with the form component from the component attribute data of the form component as the second business data associated with the form.

[0093] In one embodiment, the data acquisition component sends the first business data, the second business data, and the behavior data to the data reporting module in the terminal device. The data reporting module generates the buried point data of the form according to the behavior data, the first business data, and the second business data, and reports the buried point data of the form to the server.

[0094] In one embodiment, generating the buried point data of the form according to the behavior data, the first business data, and the second business data includes:

[0095] Completing the first business data according to the second business data;

[0096] Generating the buried point data of the form according to the behavior data and the completed first business data.

[0097] According to the foregoing description, the second business data includes all the business data in the form, including but not limited to the form name, form source, the first business data corresponding to each user interaction component in the form, etc. Therefore, it can be considered that the second business data at least includes the first business data corresponding to each user interaction component in the form. Considering the situation where the first business data associated with the user interaction component is not recorded in the component attribute data of the user interaction component, resulting in the failure of the data acquisition sub-component to obtain the first business data, in this embodiment, first, the first business data is completed according to the second business data, and then, the buried point data of the form is generated according to the behavior data and the completed first business data. For example, the behavior data and the completed first business data are jointly used as the buried point data of the form.

[0098] It can be seen that through this embodiment, it is possible to consider the situation where the component attribute data of the user interaction component does not record the first service data associated with the user interaction component, resulting in the failure of the data acquisition sub-item component to obtain the first service data. First, the first service data is supplemented according to the second service data, and then, according to the behavior data and the supplemented first service data, the buried point data of the form is generated to ensure the comprehensiveness of the buried point data.

[0099] In one embodiment, supplementing the first service data according to the second service data includes:

[0100] Generate the correspondence between the behavior data and the first service data; the corresponding behavior data and the first service data come from the same user interaction component;

[0101] Based on this correspondence, if there is behavior data missing the corresponding first service data, then based on the second service data, supplement the first service data for the behavior data missing the first service data.

[0102] In this embodiment, establish the correspondence between the behavior data and the first service data. The corresponding behavior data and the first service data come from the same user interaction component. For example, the behavior data corresponding to the trigger operation occurring on a certain user interaction component includes the data "January 1st" input by the user, and the first service data associated with this user interaction component is "date", then establish the correspondence between the behavior data "January 1st" and the first service data "date". In the established correspondence, one first service data can correspond to one or more behavior data.

[0103] Then, according to the established correspondence, determine whether there is behavior data missing the corresponding first service data. If there is behavior data missing the corresponding first service data, then based on the second service data, supplement the first service data for the behavior data missing the first service data.

[0104] In this embodiment, it is possible to compare the first service data reported by the data sub-item acquisition component with the first service data included in the second service data, and determine the first service data that is more than the first service data reported by the data sub-item acquisition component in the first service data included in the second service data. This additional first service data is the first service data that needs to be supplemented, and supplement this additional first service data to the behavior data missing the corresponding first service data.

[0105] For example, the behavioral data "February 1st" input by the user lacks the corresponding first business data. By comparing the first business data reported by the data sub-item acquisition component with the first business data included in the first and second business data, it is determined that the first business data that is extra in the first business data included in the second business data compared to the first business data reported by the data sub-item acquisition component is the "user reporting date". This extra first business data, "user reporting date", is the first business data that needs to be filled in. The extra first business data, "user reporting date", is filled in for the behavioral data "February 1st" that lacks the corresponding first business data, resulting in the correspondence between the behavioral data "February 1st" and the "user reporting date".

[0106] It can be seen that through this embodiment, the correspondence between behavioral data and first business data can be generated. The corresponding behavioral data and first business data come from the same user interaction component. Based on this correspondence, if there is behavioral data lacking the corresponding first business data, then based on the second business data, the first business data is filled in for the behavioral data lacking the first business data, thereby filling in the first business data so that all behavioral data has the corresponding first business data.

[0107] In this embodiment, when the data reporting module generates the buried point data of the form based on the behavioral data and the filled-in first business data, each behavioral data and the corresponding first business data can be used as the buried point data of the form, and a unique identifier is set for the buried point data of the form. The buried point data of the form and the corresponding unique identifier are reported to the server.

[0108] In summary, through the above data generation method, the following technical effects can be achieved:

[0109] 1. The behavioral data corresponding to the trigger operation, the first business data associated with the user interaction component, and the second business data associated with the form can be accurately obtained through the data acquisition sub-item component and the data acquisition component of the form, and the buried point data of the form can be generated based on the behavioral data, the first business data, and the second business data, thereby achieving the effect of accurately generating the buried point data of the form and providing a data basis for improving the user operation experience for the form;

[0110] 2. The buried point data of the form can be generated based on the behavioral data, the first business data, and the second business data, so that the buried point data of the form covers the behavioral data and the business data, improving the diversity and comprehensiveness of the buried point data of the form;

[0111] 3. There is no need to implant the code for obtaining the buried point data of the form in a hard - coded manner in the form. Just develop a data acquisition component and a data acquisition sub - item component for the form, and the buried point data can be generated, reducing the programming difficulty, reducing the code intrusion of the form when obtaining the buried point data, and the data acquisition component and the data acquisition sub - item component can be adapted to different forms, expanding the application scenarios for generating buried point data, so that the operation experience of users for the form can be effectively evaluated through the buried point data.

[0112] Figure 5 Schematic diagram of the structure of a data generation device provided by an embodiment of the present disclosure, as Figure 5 shown, the device includes:

[0113] A first acquisition unit 51, configured to, in response to a trigger operation on a user interaction component in a form, obtain behavior data corresponding to the trigger operation and first service data associated with the user interaction component through a data acquisition sub - item component associated with the user interaction component in the form;

[0114] A second acquisition unit 52, configured to obtain second service data associated with the form through a data acquisition component associated with a form component of the form; wherein, the form component is a component corresponding to the root node in the document object model (DOM) tree of the form;

[0115] A data generation unit 53, configured to generate buried point data of the form according to the behavior data, the first service data, and the second service data.

[0116] Optionally, it further includes a wrapping component, configured to: before the response to the trigger operation on the user interaction component in the form, associate the data acquisition sub - item component with the user interaction component by setting the data acquisition sub - item component to wrap the user interaction component; and associate the data acquisition component with the form component by setting the data acquisition component to wrap the form component.

[0117] Optionally, it further includes a delegation component, configured to: before obtaining the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through the data acquisition sub - item component associated with the user interaction component in the form, set the user interaction component to report the behavior data of the trigger operation to the associated data acquisition sub - item component based on the event delegation mechanism between components.

[0118] Optionally, the first acquisition unit 51 is specifically configured to: obtain the behavior data corresponding to the trigger operation reported by the user interaction component through the data acquisition sub - item component.

[0119] Optionally, the first obtaining unit 51 is specifically configured to: obtain, through the data obtaining sub-item component, first service data associated with the user interaction component from the component attribute data of the user interaction component.

[0120] Optionally, it further includes a reporting component, configured to report the behavior data and the first service data to the data obtaining component through the data obtaining sub-item component before obtaining, through the data obtaining component associated with the form component in the form, second service data associated with the form; the data obtaining component is the superior component of the data obtaining sub-item component; correspondingly, the second obtaining unit 52 is specifically configured to: in response to the data obtaining component receiving the behavior data and the first service data, obtain, through the data obtaining component, second service data associated with the form.

[0121] Optionally, the second obtaining unit 52 is specifically configured to: obtain, through the data obtaining component, service data associated with the form component from the component attribute data of the form component as the second service data associated with the form.

[0122] Optionally, the data generating unit 53 is specifically configured to: supplement the first service data according to the second service data; generate the buried point data of the form according to the behavior data and the supplemented first service data.

[0123] Optionally, the data generating unit 53 is further specifically configured to: generate a correspondence relationship between the behavior data and the first service data; the corresponding behavior data and the first service data come from the same user interaction component; based on the correspondence relationship, if there is behavior data lacking the corresponding first service data, supplement the first service data for the behavior data lacking the first service data based on the second service data.

[0124] The data generating device in the embodiments of the present disclosure can implement each process of the above data generating method embodiments, and achieve the same effects and functions, which will not be repeated here.

[0125] An embodiment of the present disclosure further provides an electronic device. Figure 6 The structural schematic diagram of the electronic device provided by an embodiment of the present disclosure is shown in Figure 6As shown, electronic devices can vary significantly due to differences in configuration or performance. They can include one or more processors 601 and a memory 602. One or more applications or data can be stored in the memory 602. Among them, the memory 602 can be for transient storage or persistent storage. The applications stored in the memory 602 can include one or more modules (not shown in the figure), and each module can include a series of computer-executable instructions in the electronic device. Further, the processor 601 can be configured to communicate with the memory 602 and execute a series of computer-executable instructions in the memory 602 on the electronic device. The electronic device can also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input or output interfaces 605, one or more keyboards 606, etc.

[0126] In a specific embodiment, an electronic device includes a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to implement the following process:

[0127] In response to a trigger operation on a user interaction component in a form, through a data acquisition sub-item component associated with the user interaction component in the form, obtain the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component;

[0128] Through a data acquisition component associated with the form component of the form in the form, obtain the second service data associated with the form; wherein, the form component is the component corresponding to the root node in the document object model (DOM) tree of the form;

[0129] Generate the buried point data of the form according to the behavior data, the first service data, and the second service data.

[0130] The electronic device in the embodiments of the present disclosure can implement each process of the above data generation method embodiments and achieve the same effects and functions, which will not be repeated here.

[0131] Another embodiment of the present disclosure also provides a computer-readable storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process:

[0132] In response to a trigger operation on a user interaction component in a form, through a data acquisition sub-item component associated with the user interaction component in the form, obtain the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component;

[0133] Obtain the second service data associated with the form through the data acquisition component associated with the form component of the form; wherein, the form component is the component corresponding to the root node in the document object model (DOM) tree of the form.

[0134] Generate the buried point data of the form according to the behavior data, the first service data, and the second service data.

[0135] The storage medium in the embodiments of the present disclosure can implement each process of the above data generation method embodiment, and achieve the same effects and functions, which will not be repeated here.

[0136] In each embodiment of the present disclosure, the computer-readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disc, or the like.

[0137] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structures of diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many method flow improvements today can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement to a method flow cannot be implemented using a hardware entity module. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is an integrated circuit whose logic function is determined by a user's programming of the device. Designers can program a digital system "integrated" onto a single PLD by themselves, without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compilers used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one type of HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing a little logical programming on the method flow using the above-mentioned several hardware description languages and programming it into an integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0138] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to make the controller implement the same function in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or the structures within the hardware component.

[0139] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0140] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing the embodiments of the present disclosure, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0141] Those skilled in the art should understand that one or more embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, one or more embodiments of the present disclosure can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, one or more embodiments of the present disclosure can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0142] The present disclosure is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present disclosure. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing device generate a means for implementing the functions specified in one or more flows Figure 1 one or more flows and / or blocks Figure 1 or a means for implementing the functions specified in one or more blocks.

[0143] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including an instruction means that implements the functions specified in one or more flows Figure 1 one or more flows and / or blocks Figure 1 or a means for implementing the functions specified in one or more blocks.

[0144] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more flows Figure 1 one or more flows and / or blocks Figure 1 or a means for implementing the functions specified in one or more blocks.

[0145] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, commodity or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the existence of additional identical elements in the process, method, commodity or device comprising the element.

[0146] One or more embodiments of the present disclosure may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present disclosure may also be practiced in a distributed computing environment where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

[0147] Each embodiment in the present disclosure is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant parts, reference can be made to the description of the method embodiment.

[0148] The above are only embodiments of the present disclosure and are not intended to limit the present disclosure. For those skilled in the art, various changes and modifications can be made to the present disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present disclosure shall be included within the scope of the claims of the present disclosure.

Claims

1. A data generation method, characterized in that, Including: In response to a trigger operation on a user interaction component in a form, obtain the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form; Obtain the second service data associated with the form through a data acquisition component associated with the form component of the form; wherein, the form component is the component corresponding to the root node in the document object model (DOM) tree of the form; Generate the buried point data of the form according to the behavior data, the first service data, and the second service data.

2. The method according to claim 1, wherein Before the step of in response to a trigger operation on a user interaction component in a form, the method further includes: Associate the data acquisition sub-item component with the user interaction component by setting the data acquisition sub-item component to wrap the user interaction component; Associate the data acquisition component with the form component by setting the data acquisition component to wrap the form component.

3. The method according to claim 1, wherein Before the step of obtaining, through a data acquisition sub-item component associated with the user interaction component in the form, the behavior data corresponding to the trigger operation and the first service data associated with the user interaction component, the method further includes: Based on the event delegation mechanism between components, set the user interaction component to report the behavior data of the trigger operation to the associated data acquisition sub-item component.

4. The method according to claim 3, wherein The step of obtaining, through a data acquisition sub-item component associated with the user interaction component in the form, the behavior data corresponding to the trigger operation includes: Obtain the behavior data corresponding to the trigger operation reported by the user interaction component through the data acquisition sub-item component.

5. The method according to claim 1, characterized in that, The step of obtaining, through a data acquisition sub-item component associated with the user interaction component in the form, the first service data associated with the user interaction component includes: Obtain the first service data associated with the user interaction component from the component attribute data of the user interaction component through the data acquisition sub-item component.

6. The method according to claim 1, wherein Before the step of obtaining, through a data acquisition component associated with the form component of the form, the second service data associated with the form, the method further includes: Report the behavior data and the first service data to the data acquisition component through the data acquisition sub-item component; the data acquisition component is the superior component of the data acquisition sub-item component; The step of obtaining, through a data acquisition component associated with the form component of the form, the second service data associated with the form includes: In response to the data acquisition component receiving the behavior data and the first service data, obtain the second service data associated with the form through the data acquisition component.

7. The method according to claim 1, wherein The step of obtaining, through a data acquisition component associated with the form component of the form, the second service data associated with the form includes: Through the data acquisition component, obtain the business data associated with the form component from the component attribute data of the form component as the second business data associated with the form.

8. The method according to claim 1, characterized in that, Generating the buried point data of the form according to the behavior data, the first business data, and the second business data includes: Completing the first business data according to the second business data; Generating the buried point data of the form according to the behavior data and the first business data after completion.

9. The method according to claim 8, wherein Completing the first business data according to the second business data includes: Generating a correspondence relationship between the behavior data and the first business data; the corresponding behavior data and the first business data come from the same user interaction component; Based on the correspondence relationship, if there is behavior data lacking the corresponding first business data, then based on the second business data, complete the first business data for the behavior data lacking the first business data.

10. A data generation device, characterized in that, Including: A first acquisition unit, configured to, in response to a trigger operation on a user interaction component in a form, obtain the behavior data corresponding to the trigger operation and the first business data associated with the user interaction component through a data acquisition sub-item component associated with the user interaction component in the form; A second acquisition unit, configured to obtain the second business data associated with the form through a data acquisition component associated with the form component of the form; wherein, the form component is the component corresponding to the root node in the document object model (DOM) tree of the form; A data generation unit, configured to generate the buried point data of the form according to the behavior data, the first business data, and the second business data.

11. An electronic device, characterized in that, Including: A processor; And, A memory configured to store computer-executable instructions, and when the computer-executable instructions are executed, the processor implements the steps of the method according to any one of claims 1-9 above.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the method according to any one of claims 1-9 above are implemented.

Images