CN111143184B - Data processing method, device and system - Google Patents
Data processing method, device and system Download PDFInfo
- Publication number
- CN111143184B CN111143184B CN201911383405.7A CN201911383405A CN111143184B CN 111143184 B CN111143184 B CN 111143184B CN 201911383405 A CN201911383405 A CN 201911383405A CN 111143184 B CN111143184 B CN 111143184B
- Authority
- CN
- China
- Prior art keywords
- attribute information
- custom attribute
- data
- custom
- root node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 18
- 230000003993 interaction Effects 0.000 claims abstract description 133
- 230000002452 interceptive effect Effects 0.000 claims abstract description 65
- 230000006870 function Effects 0.000 claims description 74
- 238000012545 processing Methods 0.000 claims description 36
- 238000000034 method Methods 0.000 claims description 31
- 230000005587 bubbling Effects 0.000 claims description 26
- 230000005540 biological transmission Effects 0.000 claims description 7
- 238000007405 data analysis Methods 0.000 claims description 4
- 238000013480 data collection Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 8
- 238000012423 maintenance Methods 0.000 description 8
- 238000003491 array Methods 0.000 description 5
- 230000006399 behavior Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000007619 statistical method Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000000712 assembly Effects 0.000 description 2
- 238000000429 assembly Methods 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24573—Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
Abstract
The disclosure relates to a data processing method, device and system. Comprising the following steps: setting a custom attribute mark on the buried point element; the custom attribute mark is used for storing custom attribute information on the root node of the buried point element; receiving custom attribute information transmitted to a root node of a buried point element; and determining the target element and interaction data corresponding to the target element according to the custom attribute information. Therefore, the interactive data of the target element can be obtained without calling an additional reporting function, the data is convenient to collect and maintain, and the complexity of reporting the buried point is reduced.
Description
Technical Field
The disclosure relates to the technical field of internet, and in particular relates to a data processing method, device and system.
Background
With the development of internet technology, the statistical analysis of the behavior of internet users and the provision of personalized services to clients according to the statistical analysis result have also been developed rapidly, and guidance can be provided in software and page design. In the process of statistically analyzing user behaviors, it is one of the common ways to embed points in target elements. The buried point is a record of user behavior process and result to meet the requirements of quick, efficient and rich data application. In the traditional technology, on the embedded point element, the function reported by the embedded point is triggered through the interaction event, so that the statistical analysis on the behavior of the user is realized.
However, in the conventional technology, the reporting logic of the buried point and the business logic are often coupled together, which is not beneficial to the collection and maintenance of the data, and increases the complexity of reporting the buried point.
Disclosure of Invention
The disclosure provides a data processing method, device and system, which at least solve the problem that buried point reporting logic and business logic are often coupled together in the related art, which is not beneficial to data collection and maintenance. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a data processing method, including:
setting a custom attribute mark on the buried point element; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
receiving custom attribute information transmitted to a root node of the buried point element;
and determining a target element and interaction data corresponding to the target element according to the custom attribute information.
In one embodiment, the determining, according to the custom attribute information, a target element and interaction data corresponding to the target element includes:
and if the interaction data is null, calling a reporting API function to acquire the interaction data.
In one embodiment, the setting the custom attribute flag on the buried point element includes:
and setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
In one embodiment, the receiving custom attribute information on the root node that is delivered to the buried point element by bubbling, includes:
receiving user-defined attribute information transmitted by a preset interaction data callback function; the interaction data callback function is arranged on a root node of the API file and is used for reporting custom attribute information transmitted to the root node of the embedded point element in an bubbling mode.
In one embodiment, the determining, according to the custom attribute information, a target element and interaction data corresponding to the target element includes:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
According to a second aspect of embodiments of the present disclosure, there is provided a data processing method, including:
The engineering file end sets a custom attribute mark on the embedded point element and sets an interactive data callback function on the root node of the API file; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
the engineering file end receives the interactive operation performed by the embedded point element and generates custom attribute information;
the engineering file end transmits the custom attribute information to the root node of the embedded point element;
the engineering file end adopts the interactive data callback function to report the self-defined attribute information to a server end;
and the server analyzes the self-defined attribute information to obtain corresponding target elements and interaction data corresponding to the target elements.
In one embodiment, the server side parses the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element, where the parsing includes:
and if the interaction data is null, calling a reporting API function to acquire the interaction data.
In one embodiment, the setting, by the engineering file end, a custom attribute flag on the buried point element, and setting, by the engineering file end, an interactive data callback function on a root node of the API file, includes:
And setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
In one embodiment, the server side parses the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element, where the parsing includes:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
According to a third aspect of embodiments of the present disclosure, there is provided a data processing apparatus comprising:
an attribute information marking unit configured to perform setting of a custom attribute mark on the buried point element; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
an attribute information receiving unit configured to perform receiving of custom attribute information transferred to a root node of the buried point element;
and the interactive data acquisition unit is configured to determine a target element and interactive data corresponding to the target element according to the custom attribute information.
In one embodiment, the apparatus further comprises:
and the first interactive data updating unit is configured to execute the calling and reporting API function and acquire the interactive data.
In one embodiment, the attribute information marking unit is further configured to perform:
and setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
In one embodiment, the attribute information receiving unit is further configured to perform:
receiving user-defined attribute information transmitted by a preset interaction data callback function; the interaction data callback function is arranged on a root node of the API file and is used for reporting custom attribute information transmitted to the root node of the embedded point element in an bubbling mode.
In one embodiment, the interaction data acquisition unit is further configured to perform:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
According to a fourth aspect of embodiments of the present disclosure, there is provided a data processing system, the data processing system including an engineering file side and a server side; the engineering file end comprises an attribute mark setting unit, an attribute information generating unit, an attribute information transmission unit and an attribute information callback unit, and the server end comprises a data analysis unit;
The attribute mark setting unit is configured to execute setting of a custom attribute mark on the buried point element and setting of an interactive data callback function on a root node of the API file; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
the attribute information generating unit is configured to execute the interactive operation performed by the buried point element, and generate custom attribute information;
the attribute information transmission unit is configured to transmit the custom attribute information to a root node of the buried point element;
the attribute information callback unit is configured to execute the interaction data callback function and report the custom attribute information to a server side;
the data analysis unit is configured to analyze the custom attribute information to obtain corresponding target elements and interaction data corresponding to the target elements.
In one embodiment, the system further comprises:
and the second interactive data updating unit is configured to execute the calling and reporting API function and acquire the interactive data.
In one embodiment, the attribute flag setting unit is further configured to perform:
And setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
In one embodiment, the data parsing unit is further configured to perform:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
According to a fifth aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the data processing method of the first aspect or the second aspect.
According to a sixth aspect of embodiments of the present disclosure, there is provided a storage medium comprising: the instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the data processing method of the first or second aspect described above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
The self-defined attribute mark is arranged on the embedded point element, and the self-defined attribute information on the root node of the embedded point element is stored in the self-defined attribute mark, wherein the self-defined attribute information represents the interaction information of the interaction event, can be reported independently and independently of the reporting of the business logic, and can realize the decoupling of the embedded point reporting logic and the business logic. The method comprises the steps of receiving decoupled custom attribute information transmitted to a root node of a buried point element, analyzing the decoupled custom attribute information to obtain corresponding buried point element and data, determining the corresponding buried point element as a target element, determining the corresponding data as interaction data corresponding to the target element, acquiring the interaction data of the target element without calling an additional reporting function, facilitating data collection and maintenance, and reducing complexity of report of the buried point.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a flow chart illustrating a method of data processing according to an exemplary embodiment.
Fig. 2 is a flow chart illustrating one possible implementation of step S300 according to an exemplary embodiment.
FIG. 3 is a flowchart illustrating a method of data processing according to an exemplary embodiment.
Fig. 4 is a block diagram of a data processing apparatus according to an exemplary embodiment.
FIG. 5 is a block diagram of a data processing system shown in accordance with an illustrative embodiment.
FIG. 6 is a block diagram of a data processing device, according to an example embodiment.
Fig. 7 is a block diagram of a data processing apparatus according to an exemplary embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
FIG. 1 is a flow chart of a data processing method, as shown in FIG. 1, according to an exemplary embodiment, including the steps of:
in step S100, a custom attribute flag is set on the buried point element; the custom attribute mark is used for storing custom attribute information on the root node of the buried point element.
In step S200, custom attribute information is received that is passed on to the root node of the buried element.
In step S300, according to the custom attribute information, a target element and interaction data corresponding to the target element are determined.
The embedded point element is an element for carrying out embedded point setting according to the requirement of a user, and the element can be an element such as a button, a card and the like needing embedded point. The custom attribute mark is a mark which is set by oneself and used for storing custom attribute information on the root node of the embedded point element.
Specifically, a custom attribute flag is set on an element requiring a buried point, for example, a custom attribute flag data-log= "eventName" is added on the element requiring a buried point, where eventName is a specific buried point value. Monitoring an interaction event (such as click action) on a root node (document) in an entry file of the project, registering an interaction data callback function of the interaction event, when the interaction information of a target element is transferred to the root node, receiving custom attribute information transferred to the root node of the embedded point element by a server, obtaining a corresponding embedded point element and data according to the custom attribute information, determining the corresponding embedded point element as the target element, and determining the corresponding data as interaction data corresponding to the target element. The interaction data callback function receives an event (event) value as a parameter, the event. Target in the event value represents a target element participating in interaction, the event. Target. Attributes in the event value are bound attribute arrays, the interaction event to be reported is collected by judging data-log in the arrays, and interaction data corresponding to the target element is determined. The transmission of the interaction information of the target element to the root node can be realized by an event bubbling principle of a browser, and the method is not particularly limited herein, and is based on the fact that the interaction information of the target element can be transmitted to the root node, so that the acquisition of the custom attribute information is facilitated.
According to the data processing method, the custom attribute mark is arranged on the embedded point element, and the custom attribute information on the root node of the embedded point element is stored in the custom attribute mark, wherein the custom attribute information represents the interaction information of the interaction event, can be reported independently, is independent of the reporting of the business logic, and can realize the decoupling of the embedded point reporting logic and the business logic. The method comprises the steps of receiving decoupled custom attribute information transmitted to a root node of a buried point element, analyzing the decoupled custom attribute information to obtain corresponding buried point element and data, determining the corresponding buried point element as a target element, determining the corresponding data as interaction data corresponding to the target element, acquiring the interaction data of the target element without calling an additional reporting function, facilitating data collection and maintenance, and reducing complexity of report of the buried point.
In one exemplary embodiment, for an implementation manner of step S300, determining, according to the custom attribute information, the target element and the interaction data corresponding to the target element includes: and if the interaction data is null, calling a reporting API function to acquire the interaction data.
The reporting API function is a function for acquiring the interaction data and reporting the interaction data to the server.
Specifically, the bubbling process of part of interaction events is blocked by some external factors, the custom attribute information of the corresponding target element cannot be transmitted to the root node of the buried point element, the custom attribute information transmitted to the root node of the buried point element in a bubbling manner cannot be received, and the target element and the interaction data corresponding to the target element cannot be determined according to the custom attribute information. When the interaction event that the bubbling process is blocked exists, the reporting API function is called to acquire the interaction data.
In the above embodiment, when there is an interaction event in which the bubbling process is blocked, the reporting API function is called to obtain the interaction data, and the interaction data is matched with a scheme for obtaining the interaction data in a bubbling manner, so that the integrity of the interaction data collection can be ensured, and the phenomenon that the interaction data cannot be obtained due to the blocking of the bubbling event is avoided.
In one exemplary embodiment, to perform an implementation before step S100, setting the custom attribute flag on the buried element includes:
And setting a custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
The data acquisition type is the type of data to be acquired, which is set according to specific user requirements. For example, the type of interaction event is a click, and the data collection type is a click operation for the buried element.
Specifically, when the data acquisition type is a click operation for the embedded point element, setting a preset custom attribute collection mark according to the preset data acquisition type, setting a custom attribute mark on the element needing to be embedded point, for example, adding a custom attribute mark data-log= "eventName" on the element needing to be embedded point to obtain a corresponding custom attribute mark, wherein the eventName corresponds to a specific embedded point value.
In the above embodiment, the preset custom attribute collection flag is set according to the preset data collection type, so as to obtain the corresponding custom attribute flag, and provide a basis for setting the custom attribute flag on the embedded point element subsequently, so as to decouple the embedded point reporting logic from the service logic.
In one exemplary embodiment, for an implementation manner of step S200, receiving custom attribute information transmitted to a root node of a buried element includes:
Receiving user-defined attribute information transmitted by a preset interaction data callback function; the interaction data callback function is arranged on a root node of the API file and used for reporting self-defined attribute information transmitted to the root node of the buried point element in a bubbling mode.
Wherein, the API file refers to an entry file of the project. The interactive data callback function is a callback function responding to the interactive action, for example, when the interactive action is clicking, the interactive data callback function is a callback function of a clicking event, that is, when a corresponding button, card or the like is clicked, the interactive data callback function reports the custom attribute information transferred to the root node of the embedded point element in a bubbling mode.
Specifically, an interactive data callback function is set on a root node of the API file, when an interactive action occurs, the event bubbling principle of the browser transmits the interactive action (for example, clicking) of the embedded point element to the root node of the API file, and the user-defined attribute information on the root node of the embedded point element is reported through the interactive data callback function.
In the above embodiment, by setting the interaction data callback function on the root node of the API file and receiving the custom attribute information transmitted by the interaction data callback function, the interaction event can be automatically reported after the interaction event occurs, and the interaction data of the target element can be obtained without calling an additional reporting function, so that the collection and maintenance of the data are facilitated, and the complexity of reporting the buried point is reduced.
FIG. 2 is a flow chart illustrating one possible implementation of step S300 according to an exemplary embodiment, as shown in FIG. 2, for determining a target element and interaction data corresponding to the target element according to custom attribute information, including the steps of:
in step S310, the custom attribute information is parsed to obtain corresponding buried point elements and data.
In step S320, the buried point element corresponding to the custom attribute information is determined as the target element, and the data corresponding to the custom attribute information is determined as the interaction data.
Specifically, the event reported by the interaction data callback function exists in the form of an event data packet (custom attribute information), and the event data packet can be presented in the form of a code event. The event data packet event comprises event, target and event, target, attributes, wherein the event, target corresponds to a specific element of interaction, the event, target, attributes are bound self-defined attribute information, and interaction events to be reported can be collected by judging data-log in the event, target, attributes. For example, an event data packet (custom attribute information) is parsed, a buried point element corresponding to an event target is determined as a target element, and data corresponding to data-log in event targets is determined as interaction data.
In the above embodiment, the custom attribute information is parsed to obtain the corresponding embedded point element and data, the embedded point element corresponding to the custom attribute information is determined as the target element, the data corresponding to the custom attribute information is determined as the interactive data, the interactive data of the target element can be obtained without calling an additional reporting function in the whole process, the data collection and maintenance are facilitated, and the complexity of embedded point reporting is reduced.
FIG. 3 is a flow chart of a data processing method, as shown in FIG. 3, according to an exemplary embodiment, including the steps of:
in step S10, the engineering file end sets a custom attribute mark on the buried point element, and sets an interactive data callback function on the root node of the API file; the custom attribute mark is used for storing custom attribute information on the root node of the buried point element.
In step S20, the engineering file end receives the interaction operation performed by the embedded point element, and generates custom attribute information.
In step S30, the engineering file end transfers the custom attribute information to the root node of the buried element.
In step S40, the engineering file end adopts an interactive data callback function to report the custom attribute information to the server end.
In step S50, the server analyzes the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element.
The embedded point element is an element which is arranged at the engineering file end according to the user requirement, and the element can be an element such as a button, a card and the like which need to be embedded with the point. The custom attribute mark is custom attribute information on a self-set root node for storing the embedded point element. The API file refers to an entry file of the engineering file end. The interactive data callback function is a callback function responding to the interactive action, for example, when the interactive action is clicking, the interactive data callback function is a callback function of a clicking event, that is, when a corresponding button, card or the like is clicked, the interactive data callback function reports the custom attribute information transferred to the root node of the embedded point element in a bubbling mode to the server side.
Specifically, a custom attribute mark is set on an element needing to be buried at an engineering file end, for example, a custom attribute mark data-log= "eventName" is added on the element needing to be buried, wherein eventName is a specific buried point value, an interactive data callback function is set on a root node of an API file, when an interactive action occurs, an event bubbling principle of a browser transmits the interactive action (for example, clicking) of the buried element to the root node of the API file, and custom attribute information on the root node of the buried element is reported through the interactive data callback function. Monitoring an interaction event (for example, click action) on a root node (document) in an entry file of an engineering, registering an interaction data callback function of the interaction event, transmitting the interaction information of a target element to the root node by an event bubbling principle of a browser after performing interaction operation on a buried point element, receiving custom attribute information transmitted to the root node of the buried point element in a bubbling mode by a server, reporting the custom attribute information to the server by the interaction data callback function, and determining the corresponding target element and interaction data corresponding to the target element from the custom attribute information by the server. The interaction data callback function receives an event (event) value as a parameter, the event. Target in the event value corresponds to a target element participating in interaction, the event. Target. Attributes in the event value are bound attribute arrays, and interaction events to be reported are collected through data-log in the arrays through judgment, so that interaction data corresponding to the target element is determined. The transmission of the interaction information of the target element to the root node can be realized by an event bubbling principle of a browser, and the method is not particularly limited herein, and is based on the fact that the interaction information of the target element can be transmitted to the root node, so that the acquisition of the custom attribute information is facilitated.
According to the data processing method, the custom attribute mark is arranged on the embedded point element of the engineering file end, and the custom attribute information on the root node of the embedded point element is stored in the custom attribute mark, wherein the custom attribute information represents the interaction information of the interaction event, can be reported independently, is independent of the reporting of the business logic, and can realize decoupling of the embedded point reporting logic and the business logic. And the decoupled custom attribute information transmitted to the root node of the embedded point element is reported to the server through the interactive data callback function, the server analyzes the decoupled custom attribute information to obtain the corresponding target element and the interactive data corresponding to the target element, the interactive data of the target element can be obtained without calling an additional reporting function, the data collection and maintenance are facilitated, and the complexity of embedded point reporting is reduced.
In an exemplary embodiment, for an implementation manner of step S50, the server side parses the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element, where the method includes: and if the interaction data is null, calling a reporting API function to acquire the interaction data.
The reporting API function is a function for acquiring the interaction data and reporting the interaction data to the server.
Specifically, the bubbling process of part of interaction events is blocked by some external factors, the custom attribute information of the corresponding target element cannot be transmitted to the root node of the buried point element, the custom attribute information transmitted to the root node of the buried point element in a bubbling manner cannot be received, and the target element and the interaction data corresponding to the target element cannot be determined according to the custom attribute information. When the interaction event that the bubbling process is blocked exists, the reporting API function is called to acquire the interaction data.
In the above embodiment, when there is an interaction event in which the bubbling process is blocked, the reporting API function is called to obtain the interaction data, and the interaction data is matched with a scheme for obtaining the interaction data in a bubbling manner, so that the integrity of the interaction data collection can be ensured, and the phenomenon that the interaction data cannot be obtained due to the blocking of the bubbling event is avoided.
In one exemplary embodiment, to perform an implementation before step S10, the engineering file end sets a custom attribute flag on the embedded point element, and sets an interactive data callback function on the root node of the API file, which includes: and setting a custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
The data acquisition type is the type of data to be acquired, which is set according to specific user requirements. For example, the type of interaction event is a click, and the data collection type is a click operation for the buried element.
Specifically, when the data acquisition type is a click operation for the embedded point element, setting a preset custom attribute collection mark according to the preset data acquisition type, setting a custom attribute mark on the element needing to be embedded point, for example, adding a custom attribute mark data-log= "eventName" on the element needing to be embedded point to obtain a corresponding custom attribute mark, wherein the eventName corresponds to a specific embedded point value.
In the above embodiment, the preset custom attribute collection flag is set according to the preset data collection type, so as to obtain the corresponding custom attribute flag, and provide a basis for setting the custom attribute flag on the embedded point element subsequently, so as to decouple the embedded point reporting logic from the service logic.
In one exemplary embodiment, to execute the implementation manner of step S50, the server side parses the custom attribute information to obtain the corresponding target element and the interaction data corresponding to the target element, including:
Analyzing the self-defined attribute information to obtain corresponding buried point elements and data; and determining the buried point element corresponding to the custom attribute information as a target element, and determining the data corresponding to the custom attribute information as interaction data.
Specifically, the event reported by the interaction data callback function exists in the form of an event data packet (custom attribute information), and the event data packet can be presented in the form of a code event. The event data packet event comprises event, target and event, target, attributes, wherein the event, target corresponds to a specific element of interaction, the event, target, attributes are bound self-defined attribute information, and interaction events to be reported can be collected by judging data-log in the event, target, attributes. For example, an event data packet (custom attribute information) is parsed, a buried point element corresponding to an event target is determined as a target element, and data corresponding to data-log in event targets is determined as interaction data.
In the above embodiment, the custom attribute information is parsed to obtain the corresponding embedded point element and data, the embedded point element corresponding to the custom attribute information is determined as the target element, the data corresponding to the custom attribute information is determined as the interactive data, the interactive data of the target element can be obtained without calling an additional reporting function in the whole process, the data collection and maintenance are facilitated, and the complexity of embedded point reporting is reduced.
FIG. 4 is a block diagram of a data processing apparatus according to an example embodiment. Referring to fig. 4, the apparatus includes an attribute information marking unit 401, an attribute information receiving unit 402, and an interactive data acquiring unit 403.
An attribute information marking unit 401 configured to perform setting of custom attribute marks on buried point elements; the custom attribute mark is used for storing custom attribute information on the root node of the buried point element;
an attribute information receiving unit 402 configured to perform receiving custom attribute information delivered to a root node of a buried point element;
and the interaction data obtaining unit 403 is configured to determine the target element and the interaction data corresponding to the target element according to the custom attribute information.
FIG. 5 is a block diagram of a data processing system, according to an illustrative embodiment. Referring to fig. 5, the system includes a generic project file side and a server side; the engineering file side includes an attribute flag setting unit 501, an attribute information generating unit 502, an attribute information transmitting unit 503, and an attribute information callback unit 504, and the server side includes a data parsing unit 505.
An attribute flag setting unit 501 configured to perform setting of a custom attribute flag on a buried element and setting of an interactive data callback function on a root node of an API file; the custom attribute mark is used for storing custom attribute information on the root node of the buried point element;
The attribute information generating unit 502 is configured to perform an interactive operation performed by the receiving buried point element to generate custom attribute information;
an attribute information transmission unit 503 configured to perform transfer of custom attribute information onto a root node of the buried point element;
the attribute information callback unit 504 is configured to execute the interaction data callback function and report the custom attribute information to the server side;
the data parsing unit 505 is configured to parse the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element.
The specific manner in which the individual units perform the operations in relation to the apparatus of the above embodiments has been described in detail in relation to the embodiments of the method and will not be described in detail here.
Fig. 6 is a block diagram illustrating an apparatus 600 for data processing according to an example embodiment. For example, device 600 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.
Referring to fig. 6, device 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input/output (I/O) interface 612, a sensor component 614, and a communication component 616.
The processing component 602 generally controls overall operation of the device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.
The memory 604 is configured to store various types of data to support operations at the device 600. Examples of such data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, and the like. The memory 604 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 606 provides power to the various components of the device 600. The power components 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 600.
The multimedia component 608 includes a screen between the device 600 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 608 includes a front camera and/or a rear camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 600 is in an operational mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the device 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.
The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 614 includes one or more sensors for providing status assessment of various aspects of the device 600. For example, the sensor assembly 614 may detect an on/off state of the device 600, a relative positioning of the assemblies, such as a display and keypad of the device 600, the sensor assembly 614 may also detect a change in position of the device 600 or one of the assemblies of the device 600, the presence or absence of user contact with the device 600, an orientation or acceleration/deceleration of the device 600, and a change in temperature of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 616 is configured to facilitate communication between the device 600 and other devices, either wired or wireless. The device 600 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a storage medium is also provided, such as a memory 604 including instructions executable by the processor 620 of the device 600 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, for example, a ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
Fig. 7 is a block diagram illustrating an apparatus 700 for data processing according to an example embodiment. For example, the apparatus 700 may be provided as a server. Referring to fig. 7, apparatus 800 includes a processing component 722 that further includes one or more processors and memory resources represented by memory 732 for storing instructions, such as applications, executable by processing component 722. The application programs stored in memory 732 may include one or more modules that each correspond to a set of instructions. Further, the processing component 722 is configured to execute instructions to perform the data processing methods described above.
The apparatus 700 may further comprise a power component 726 configured to perform power management of the apparatus 700, a wired or wireless network interface 750 configured to connect the apparatus 700 to a network, and an input output (I/O) interface 758. The apparatus 700 may operate based on an operating system stored in memory 732, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (18)
1. A method of data processing, comprising:
setting a custom attribute mark on the buried point element; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
receiving custom attribute information transmitted to a root node of the buried point element;
determining a target element and interaction data corresponding to the target element according to the custom attribute information;
the receiving the custom attribute information transferred to the root node of the buried point element comprises the following steps:
setting an interactive data callback function on a root node of an API file, transmitting the interactive action of the embedded point element to the root node of the API file in an bubbling mode when the interactive action occurs, and reporting the custom attribute information on the root node of the embedded point element through the interactive data callback function; wherein, the API file is an engineering entry file.
2. The method of claim 1, wherein determining, according to the custom attribute information, a target element and interaction data corresponding to the target element includes:
and if the interaction data is null, calling a reporting API function to acquire the interaction data.
3. The method according to claim 1, wherein the setting the custom attribute flag on the buried element includes:
and setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
4. The method of claim 1, wherein determining, according to the custom attribute information, a target element and interaction data corresponding to the target element includes:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
5. A method of data processing, comprising:
The engineering file end sets a custom attribute mark on the embedded point element and sets an interactive data callback function on the root node of the API file; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
the engineering file end receives the interactive operation performed by the embedded point element and generates custom attribute information;
the engineering file end transmits the custom attribute information to the root node of the embedded point element;
the engineering file end adopts the interactive data callback function to report the self-defined attribute information to a server end;
and the server analyzes the self-defined attribute information to obtain corresponding target elements and interaction data corresponding to the target elements.
6. The data processing method according to claim 5, wherein the server-side parses the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element, and the method comprises:
and if the interaction data is null, calling a reporting API function to acquire the interaction data.
7. The method of claim 5, wherein the engineering file end sets a custom attribute flag on the buried element and sets an interactive data callback function on a root node of the API file, comprising:
And setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
8. The data processing method according to claim 5, wherein the server-side parses the custom attribute information to obtain a corresponding target element and interaction data corresponding to the target element, and the method comprises:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
9. A data processing apparatus, comprising:
an attribute information marking unit configured to perform setting of a custom attribute mark on the buried point element; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
an attribute information receiving unit configured to perform receiving of custom attribute information transferred to a root node of the buried point element;
the interactive data acquisition unit is configured to determine a target element and interactive data corresponding to the target element according to the custom attribute information;
The attribute information receiving unit is specifically configured to execute setting an interactive data callback function on a root node of an API file, when an interactive action occurs, the interactive action of the embedded point element is transmitted to the root node of the API file in a bubbling mode, and the custom attribute information on the root node of the embedded point element is reported through the interactive data callback function; wherein, the API file is an engineering entry file.
10. The data processing apparatus of claim 9, wherein the apparatus further comprises:
and the first interactive data updating unit is configured to execute the calling and reporting API function and acquire the interactive data.
11. The data processing apparatus according to claim 9, wherein the attribute information marking unit is further configured to perform:
and setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
12. The data processing apparatus according to claim 9, wherein the interactive data acquisition unit is further configured to perform:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
And determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
13. A data processing system, wherein the data processing system comprises an engineering file end and a server end; the engineering file end comprises an attribute mark setting unit, an attribute information generating unit, an attribute information transmission unit and an attribute information callback unit, and the server end comprises a data analysis unit;
the attribute mark setting unit is configured to execute setting of a custom attribute mark on the buried point element and setting of an interactive data callback function on a root node of the API file; the custom attribute mark is used for storing custom attribute information on a root node of the buried point element;
the attribute information generating unit is configured to execute the interactive operation performed by the buried point element, and generate custom attribute information;
the attribute information transmission unit is configured to transmit the custom attribute information to a root node of the buried point element;
the attribute information callback unit is configured to execute the interaction data callback function and report the custom attribute information to a server side;
The data analysis unit is configured to analyze the custom attribute information to obtain corresponding target elements and interaction data corresponding to the target elements.
14. The data processing system of claim 13, wherein the system further comprises:
and the second interactive data updating unit is configured to execute the calling and reporting API function and acquire the interactive data.
15. The data processing system according to claim 13, wherein the attribute flag setting unit is further configured to perform:
and setting a preset custom attribute collection mark according to a preset data acquisition type to obtain a corresponding custom attribute mark.
16. The data processing system of claim 13, wherein the data parsing unit is further configured to perform:
analyzing the custom attribute information to obtain corresponding buried point elements and data;
and determining the buried point element corresponding to the custom attribute information as the target element, and determining the data corresponding to the custom attribute information as the interaction data.
17. An electronic device, comprising:
a processor;
A memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the data processing method of any one of claims 1 to 8.
18. A storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the data processing method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911383405.7A CN111143184B (en) | 2019-12-27 | 2019-12-27 | Data processing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911383405.7A CN111143184B (en) | 2019-12-27 | 2019-12-27 | Data processing method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111143184A CN111143184A (en) | 2020-05-12 |
| CN111143184B true CN111143184B (en) | 2023-11-07 |
Family
ID=70521460
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911383405.7A Active CN111143184B (en) | 2019-12-27 | 2019-12-27 | Data processing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143184B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019085083A1 (en) * | 2017-11-01 | 2019-05-09 | 平安科技（深圳）有限公司 | Control matching method and apparatus, computer device, and storage medium |
| CN109960633A (en) * | 2019-03-28 | 2019-07-02 | 深圳市跃动运营科技有限公司 | A kind of data visualization buries point methods, storage medium and intelligent terminal |
| CN110059282A (en) * | 2019-04-23 | 2019-07-26 | 北京奇艺世纪科技有限公司 | A kind of acquisition methods and system of interactive class data |
| CN110196953A (en) * | 2019-05-30 | 2019-09-03 | 北京腾云天下科技有限公司 | A kind of application buries point methods, device, calculates equipment and system |
-
2019
- 2019-12-27 CN CN201911383405.7A patent/CN111143184B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019085083A1 (en) * | 2017-11-01 | 2019-05-09 | 平安科技（深圳）有限公司 | Control matching method and apparatus, computer device, and storage medium |
| CN109960633A (en) * | 2019-03-28 | 2019-07-02 | 深圳市跃动运营科技有限公司 | A kind of data visualization buries point methods, storage medium and intelligent terminal |
| CN110059282A (en) * | 2019-04-23 | 2019-07-26 | 北京奇艺世纪科技有限公司 | A kind of acquisition methods and system of interactive class data |
| CN110196953A (en) * | 2019-05-30 | 2019-09-03 | 北京腾云天下科技有限公司 | A kind of application buries point methods, device, calculates equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111143184A (en) | 2020-05-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111274131A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112291631A (en) | Information acquisition method, device, terminal and storage medium | |
| CN113259226A (en) | Information synchronization method and device, electronic equipment and storage medium | |
| CN115185717A (en) | Interface calling method and device, electronic equipment and storage medium | |
| CN110704030A (en) | Interface configuration information generation method and device, electronic equipment and storage medium | |
| CN111343481B (en) | Data sharing method and device, electronic equipment and storage medium | |
| CN110968492B (en) | Information processing method and device and storage medium | |
| CN112486770A (en) | Client dotting reporting method and device, electronic equipment and storage medium | |
| CN110764847A (en) | User information processing method and device, electronic equipment and storage medium | |
| CN111079040A (en) | Resource sniffing method, device, terminal, server and storage medium | |
| CN108012258B (en) | Data traffic management method and device for virtual SIM card, terminal and server | |
| CN111143184B (en) | Data processing method, device and system | |
| CN115509872A (en) | Client behavior data acquisition method and device | |
| CN112333233B (en) | Event information reporting method and device, electronic equipment and storage medium | |
| CN111131000B (en) | Information transmission method, device, server and terminal | |
| CN114417133A (en) | Business data processing method and device, electronic equipment and computer storage medium | |
| CN114239531A (en) | Template recommendation method and device, electronic equipment and storage medium | |
| CN107257384B (en) | Service state monitoring method and device | |
| CN111736890A (en) | Data updating method and device, electronic equipment and storage medium | |
| CN111526084A (en) | Information processing method, device, equipment and storage medium | |
| CN112819061B (en) | Password information identification method, device, equipment and storage medium | |
| CN113965476B (en) | Inspection method, device and equipment based on application | |
| CN111104297B (en) | Multi-process data dotting method and device, electronic equipment and storage medium | |
| CN113191792B (en) | Task processing method, device, electronic equipment, storage medium and program product | |
| CN113420205B (en) | Method and device for determining shared source account, terminal equipment and server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |