WO2018113385A1 - 对客户端的应用程序动态埋点的方法、系统、客户端及服务器 - Google Patents

对客户端的应用程序动态埋点的方法、系统、客户端及服务器 Download PDF

Info

Publication number
WO2018113385A1
WO2018113385A1 PCT/CN2017/105013 CN2017105013W WO2018113385A1 WO 2018113385 A1 WO2018113385 A1 WO 2018113385A1 CN 2017105013 W CN2017105013 W CN 2017105013W WO 2018113385 A1 WO2018113385 A1 WO 2018113385A1
Authority
WO
WIPO (PCT)
Prior art keywords
buried
data
control
buried point
point data
Prior art date
Application number
PCT/CN2017/105013
Other languages
English (en)
French (fr)
Inventor
黄伟淦
Original Assignee
上海壹账通金融科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 上海壹账通金融科技有限公司 filed Critical 上海壹账通金融科技有限公司
Publication of WO2018113385A1 publication Critical patent/WO2018113385A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3604—Software analysis for verifying properties of programs

Definitions

  • the present invention relates to the field of computer technologies, and in particular, to a method, system, client, and server for dynamically burying an application of a client.
  • the industry generally collects and statistically analyzes the data indicators by burying the software system. That is to say, collecting and statistically analyzing the data indicators by means of burying points is actually a visual health check on the software system, and its importance is self-evident.
  • the existing dynamic burying scheme requires the mobile terminal program to upload the screen capture data by means of screen capture.
  • This existing dynamic burying scheme has a great influence on the running performance of the mobile terminal program and is prone to errors.
  • the main object of the present invention is to provide a method and system for dynamically burying an application of a client, which aims to collect abnormal information more flexibly.
  • the method for dynamically burying an application of a client includes the following steps:
  • the application client detects and receives the buried point data sent by the server, and the buried point data carries the mapping relationship data between the identifier of the control to be buried and the operation type;
  • the application client determines, according to the mapping relationship data corresponding to the buried point data, a control that needs to be buried and a corresponding operation type, and The operation data of each control determined and/or statistically determined according to the corresponding operation type during the running of the page.
  • the buried point data is a buried point message
  • the application client determines, according to the mapping relationship data corresponding to the buried point data, a step of determining a parameter to be buried and a corresponding operation type, and further Includes:
  • the application client parses the buried message into a buried point configuration file supported by the application client by using a corresponding message parsing converter;
  • the step of determining, by the application client, the control and the corresponding operation type that needs to be buried based on the mapping relationship data corresponding to the buried point data includes: the application client is corresponding to the embedded point configuration file The mapping relationship data determines a control and a corresponding operation type that need to be buried.
  • the burying point data is a burying point configuration file
  • the step of determining, by the application client, the control that needs to bury the point statistics and the corresponding operation type based on the mapping relationship data corresponding to the burying point data includes: The application client determines, according to the mapping relationship data corresponding to the buried point configuration file, a control that needs to be buried and a corresponding operation type.
  • the step of collecting and/or statistically determining the operation data of each control according to the corresponding operation type during the running of the page comprises: mapping according to a predetermined control, an operation type, and an intermediate layer interception code And finding the middle layer interception code corresponding to each of the determined controls, and enabling the found middle layer interception code to identify, record, and/or count the number of operations of the same type of operation data of the determined respective controls during the running of the page.
  • the method for dynamically burying the application of the client further includes:
  • the server receives a buried point data command sent by the user, the server responds to the buried point data command to generate a buried point data parameter setting interface, where the buried point data parameter setting interface includes a selection item or an input item to be buried, and each The candidate to be buried identifies the selection item or the input item of the operation type corresponding to the selection item or the input item;
  • the server If the mapping relationship data between the to-be-buried control and the operation type set by the user based on the buried point data parameter setting interface is received, the server generates the mapping data according to the mapping relationship between the received control point and the operation type. Describe the buried point data.
  • the present invention further provides a system for dynamically burying an application of a client, where the system for dynamically burying a client application includes an application client and a server, and the application client include:
  • the receiving module is configured to detect and receive the buried point data sent by the server, where the buried point data carries the mapping relationship data between the identifier of the control to be buried and the operation type;
  • a collection and statistics module configured to: if the user accesses the predetermined page through the application client, determine, according to the mapping relationship data corresponding to the buried point data, a control that needs to be buried and a corresponding operation type, and The operational data of the respective controls are collected and/or statistically determined according to the corresponding operation type during the operation of the page.
  • the buried point data is a buried message
  • the application client further includes a parsing module, where the parsing module is configured to parse the buried point message into the application by using a corresponding message parsing converter.
  • the collection and statistics module is further configured to determine, according to the mapping relationship data corresponding to the buried point configuration file, a control and a corresponding operation type that need to be buried, and according to the corresponding operation type during the running of the page. Collect and/or statistically determine operational data for each control.
  • the burying point data is a burying point configuration file
  • the collecting and statistic module is further configured to determine, according to the mapping relationship data corresponding to the burying point configuration file, a control that needs to bury a point statistic and a corresponding operation type.
  • the collection and statistics module is further configured to find a middle layer interception code corresponding to each determined control according to a predetermined mapping relationship between the control, the operation type, and the middle layer interception code, and enable the found during the running of the page.
  • the middle layer interception code identifies, records, and/or counts the number of operations of the same type of operations on the determined operational data of each control.
  • the server is configured to generate a buried point data parameter setting interface, where the buried point data parameter setting interface includes a to-be-buried point, if the buried point data generating instruction sent by the user is received, a control selection item or an input item, and a selection item or an input item of each operation type corresponding to the selection item or the input item to be buried point control;
  • the server is further configured to: according to the mapping relationship between the to-be-buried control and the operation type set by the user based on the buried point data parameter setting interface, according to the received control point and the operation type
  • the mapping relationship data generates the buried point data.
  • the application client detects and receives the buried point data sent by the server, and if the user accesses the predetermined page through the application client, the user
  • the application client determines, according to the mapping relationship corresponding to the buried point data, a control and a corresponding operation type that need to be buried, and collects and/or statistically determines according to the corresponding operation type during the running of the page.
  • the operation data of each control so that in the process of dynamic burying, the application client does not need to upload the screen capture data, only needs to receive the burying point data sent by the server, and collects and/or collects based on the mapping relationship corresponding to the burying point data.
  • the operation data of the statistical control can be used, it will not have too much impact on the running performance of the application client, and the accuracy is high, and it is not easy to make mistakes.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for dynamically burying an application of a client according to the present invention
  • FIG. 2 is a schematic flowchart of a fourth embodiment of a method for dynamically burying an application of a client according to the present invention
  • FIG. 3 is a schematic flowchart of a fifth embodiment of a method for dynamically burying an application of a client according to the present invention
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a system for dynamically embedding an application of a client according to the present invention
  • FIG. 5 is a schematic diagram of functional modules of a second embodiment of a system for dynamically burying an application of a client according to the present invention.
  • the present invention provides a method for dynamically burying an application of a client.
  • the method of dynamically burying the client's application can be implemented based on the application client and server.
  • the application client can be, for example, but not limited to, a cell phone, a tablet, and the like.
  • the application is installed in the client, and the application may be, for example but not limited to, WeChat, QQ, telephone application, SMS application, Taobao APP, and the like.
  • FIG. 1 is a schematic flowchart diagram of a first embodiment of a method for dynamically burying an application of a client according to the present invention.
  • the method for dynamically burying the application of the client includes:
  • step S10 the application client detects and receives the buried point data sent by the server, and the buried point data carries the mapping relationship data between the identifier of the control to be buried and the operation type;
  • the server may send the buried point data to the application client when receiving the embedded data sending instruction sent by the user.
  • the server can also automatically send the buried data to the application client according to the preset condition.
  • mapping relationship between the identifier to be buried and the operation type to be carried by the user based on the server setting the buried point data may be set.
  • mapping relationship between the identifier of the to-be-buried control and the operation type to be carried by the buried point data may also be set by default.
  • Step S20 If the user accesses the predetermined page through the application client, the application client determines, according to the mapping relationship data corresponding to the buried point data, a control that needs to be buried and a corresponding operation type. And collecting and/or statistically determining the operation data of each control according to the corresponding operation type during the running of the page.
  • the predetermined page may be a page corresponding to an APP that needs to be dynamically buried.
  • the application client can obtain the correspondence between the identifier of the embedded control and the operation type according to the buried point data, that is, the control that needs to bury the statistics and the corresponding operation type, and the operation type can include, for example, a click operation and an operation duration.
  • the click operation and operation time data of each of the determined operation controls are collected and/or statistically determined during the execution of the predetermined page.
  • collecting and/or statistical operation data may be the number of times the operation data of the determined respective controls are identified, recorded, and/or counted for the same type of operation.
  • the operation data of each control collected and/or statistically determined according to the corresponding operation type during the running of the page may be, but not limited to, the following manner:
  • the operation data of the determined respective controls are collected and/or statistically operated according to a preset operation data processing program. For example, the number of times the operation data of each of the determined controls is identified, recorded, and/or counted for the same type of operation.
  • the preset operation data processing program can recognize the operation data of each control in real time.
  • the preset operation data processing program may also record the identified operation data and/or count the number of times of the same type of operation.
  • the middle layer interception code corresponding to each determined control is found, and is enabled during the running of the page.
  • the middle layer interception code collects and/or statistically operates the operational data of the determined individual controls. For example, the number of times the operation data of each of the determined controls is identified, recorded, and/or counted for the same type of operation.
  • the middle layer interception code can intercept the upper layer driven data packet, for example, can intercept the operation data of the user trigger control and identify the operation data. Record and/or count the number of operations of the same type, and so on.
  • the method for dynamically burying a client application by the client the application client detects and receives the buried data sent by the server, and if the user accesses the predetermined page through the application client, the application Determining, by the program client, the control and the corresponding operation type that need to be buried according to the mapping relationship corresponding to the buried point data, and collecting and/or statistically determining each according to the corresponding operation type during the running of the page.
  • the operation data of the control so that in the process of dynamic burying, the application client does not need to upload the screen capture data, only needs to receive the buried point data sent by the server, and collects and/or statistical controls based on the mapping relationship corresponding to the buried point data.
  • the operation data can be used, it will not have too much impact on the running performance of the application client, and the accuracy is high, and it is not easy to make mistakes.
  • the present invention also proposes a method for dynamically burying the application of the client.
  • the buried point data is a buried point message
  • the method further includes:
  • the application client parses the buried message into a buried point configuration file supported by the application client by using a corresponding message parsing converter;
  • the step of determining, by the application client, the control and the corresponding operation type that needs to be buried based on the mapping relationship data corresponding to the buried point data includes: the application client is corresponding to the embedded point configuration file The mapping relationship data determines a control and a corresponding operation type that need to be buried.
  • the server may send a burying packet to the application client when receiving the burying packet sending instruction sent by the user.
  • the server can also automatically send a buried message to the application client according to a preset condition.
  • mapping relationship between the identifier to be buried and the operation type to be carried by the user based on the server may be set.
  • mapping relationship between the identifier of the to-be-buried control and the operation type that is required to be carried in the buried-point packet may also be set by default.
  • the burying packet sent by the server is a burying packet in a unified format, that is, the format of the burying packet sent by the server to all types of application clients is the same.
  • the application client that receives the burying point message in the unified format can process the burying point message in the unified format. Since the server only needs to send a buried format message in a unified format, it is not necessary to change the format of the buried message according to different types of the application client, so the server sends the buried point. The message is more flexible and more versatile.
  • the packet parsing converters corresponding to different types of application clients may be different, so that various types of application clients may use the corresponding packet parsing converter to parse the unified format sent by the server.
  • a control identifier and an operation type mapping relationship are button:click, that is, the control identifier is a button, and the corresponding operation type is click (click event), and the message parsing converter corresponding to the application client supporting the Android operating system is supported.
  • the button:click can be parsed into Button:click, and the message parser corresponding to the application client supporting the iOS operating system can resolve the button:click into UIButton:tap.
  • the application client may obtain a correspondence between the identifier of the to-be-buried control and the operation type according to the burying point configuration file, that is, determine a control that needs to bury the statistics and a corresponding operation type, and the operation type may include, for example, Click operation and operation duration, etc., and collect and/or statistically determine the click operation and operation time data of each operation control during the predetermined page operation.
  • the present invention also proposes a method for dynamically burying the application of the client.
  • the buried point data is a buried point configuration file
  • the step of determining, by the application client, the control and the corresponding operation type that needs to be buried based on the mapping relationship data corresponding to the buried point data includes: The application client determines, according to the mapping relationship data corresponding to the buried point configuration file, a control that needs to be buried and a corresponding operation type.
  • the server may send a burying point configuration file to the application client when receiving the burying point configuration file sending instruction sent by the user.
  • the server can also automatically send a burying profile to the application client according to a preset condition.
  • the mapping relationship between the identifier to be buried and the operation type to be carried by the burying point configuration file may be set by the user based on the server.
  • the mapping relationship between the identifier of the to-be-buried control and the operation type that is required to be carried in the buried-point configuration file may also be set by default.
  • the burying point configuration file sent by the server is a burying point configuration file corresponding to an application client that is to receive the burying point configuration file, so that the application that receives the burying point configuration file is received.
  • the program client can directly call the buried point configuration file.
  • the predetermined page may be a page corresponding to an APP that needs to be dynamically buried.
  • the application client can obtain the correspondence between the identifier of the to-be-buried control and the operation type according to the burying point configuration file, that is, the control that needs to bury the statistics and the corresponding operation type, and the operation type can include, for example, a click operation and an operation duration.
  • the click operation and operation duration data of each operation control are collected and/or statistically determined during the execution of the predetermined page.
  • the present invention also proposes application dynamics to the client based on any one of the first to third embodiments of the method for dynamically burying the application of the client according to the present invention.
  • a fourth embodiment of the method of burying a point, as shown in FIG. 2, FIG. 2 The method for dynamically burying the application of the client of the present invention is a schematic flowchart of the method for dynamically burying the application of the client.
  • the method for dynamically burying the application of the client may further include:
  • Step S30 when the embedded data needs to be sent to an application client supporting the same type of operating system, or when the application client needs to support different types of operating systems, the server may perform the buried data in real time or at a time. Sent to each of the application clients.
  • some application clients may support the Android operating system, and some application clients may support the iOS operating system.
  • Some buried data may only need to be sent to an application client of a certain operation type.
  • the server can send buried data to application clients that support this type of operation. It is also possible that some buried data needs to send buried data to an application client supporting the Android operating system and supporting the iOS operating system. At this time, the server can respectively support the application client supporting the Android operating system and supporting the iOS operating system.
  • Send buried point data In this embodiment, the server may determine whether it needs to send to an application client supporting the same type of operating system according to a buried point data sending instruction sent by the household, or need to send to an application client supporting a different type of operating system.
  • FIG. 3 is a schematic flowchart of a fifth embodiment of a method for dynamically burying an application of a client according to the present invention, where the application of the client is dynamically buried
  • the method can also include:
  • Step S40 If receiving a buried point data generation instruction sent by the user, the server generates a buried point data parameter setting interface according to the buried point data generation instruction, where the buried point data parameter setting interface includes an option to be buried or The input item, and the selection or input item of the operation type corresponding to the selection item or the input item of each item to be buried.
  • the item to be buried control item may include a plurality of preset control identifiers, and the user may select one, two or more control identifiers by clicking.
  • the input point to be buried may be an input box, and the user may input one, two or more control identifiers set by the user into the input box.
  • Each time a user sets a control ID it also sets an action type associated with the control ID.
  • the selection of the operation type may include a plurality of preset operation types, and the user may select one, two or more operation types by clicking.
  • the operation type input item may be an input box, and the user may input one, two or more operation types set by the user into the input box.
  • Step S50 If the mapping relationship between the to-be-buried control and the operation type set by the user based on the buried point data parameter setting interface is received, the server according to the mapping relationship between the received control to be buried and the operation type The data generates the buried point data.
  • mapping data between the received to-be-buried control and the operation type may be generated according to a preset encoding rule to generate the buried point data. And send the buried data to the corresponding application client.
  • the present invention further provides a system for dynamically burying an application of a client.
  • the system for dynamically burying the application of the client includes the application client 10 and the server 20.
  • the application client 10 can be, for example but not limited to, a cell phone, a tablet, or the like.
  • the application is installed in the client, and the application may be, for example but not limited to, WeChat, QQ, telephone application, SMS application, Taobao APP, and the like.
  • FIG. 4 is a schematic diagram of functional modules of a first embodiment of a system for dynamically embedding an application of a client according to the present invention.
  • the application client 10 includes:
  • the receiving module 11 is configured to detect and receive the buried point data sent by the server, where the buried point data carries mapping data between the identifier of the control to be buried and the type of operation;
  • the server may send the buried point data to the application client when receiving the embedded data sending instruction sent by the user.
  • the server can also automatically send the buried data to the application client according to the preset condition.
  • mapping relationship between the identifier to be buried and the operation type to be carried by the user based on the server setting the buried point data may be set.
  • mapping relationship between the identifier of the to-be-buried control and the operation type to be carried by the buried point data may also be set by default.
  • the collecting and collecting module 12 is configured to: if the user accesses the predetermined page through the application client, determine, according to the mapping relationship data corresponding to the buried point data, a control that needs to be buried and a corresponding operation type, And collecting and/or statistically determining the operation data of each control according to the corresponding operation type during the running of the page.
  • the predetermined page may be a page corresponding to an APP that needs to be dynamically buried.
  • the collection and statistics module 12 can obtain the correspondence between the identifier of the to-be-buried control and the operation type according to the buried point data, that is, the control that needs to be buried and the corresponding operation type, and the operation type can include, for example, a click operation and an operation duration.
  • the click operation and operation duration data of each operation control are collected and/or statistically determined during the execution of the predetermined page.
  • collecting and/or statistical operation data may be the number of times the operation data of the determined respective controls are identified, recorded, and/or counted for the same type of operation.
  • the operation data collected and/or statistically determined by the collection and statistics module 12 during the running of the page according to the corresponding operation type may be, but not limited to, the following manner:
  • the first method, the collection and statistics module 12 is further configured to collect and/or statistically operate the operation data of the determined respective controls according to a preset operation data processing program during the running of the page. For example, the number of times the operation data of each of the determined controls is identified, recorded, and/or counted for the same type of operation.
  • the preset operation data processing program can recognize the operation data of each control in real time.
  • the preset operation data processing program may also record the identified operation data and/or count the number of times of the same type of operation.
  • the collection and statistics module 12 is further configured to find a middle layer interception code corresponding to each control according to a predetermined mapping relationship between the control, the operation type, and the middle layer interception code, and enable the middle found during the running of the page.
  • the layer interception code collects and/or statistically operates the operational data of the determined individual controls. For example, the number of times the operation data of each of the determined controls is identified, recorded, and/or counted for the same type of operation.
  • the middle layer interception code can intercept the upper layer driven data packet, for example, can intercept the operation data of the user trigger control and identify the operation data. Record and/or count the number of operations of the same type, and so on.
  • the system for dynamically burying the application of the client by the application detects and receives the buried data sent by the server through the application client, and if the user accesses the predetermined page through the application client, the application Determining, by the program client, the control and the corresponding operation type that need to be buried according to the mapping relationship corresponding to the buried point data, and collecting and/or statistically determining each according to the corresponding operation type during the running of the page.
  • the operation data of the control so that in the process of dynamic burying, the application client does not need to upload the screen capture data, only needs to receive the buried point data sent by the server, and collects and/or statistical controls based on the mapping relationship corresponding to the buried point data.
  • the operation data can be used, it will not have too much impact on the running performance of the application client, and the accuracy is high, and it is not easy to make mistakes.
  • FIG. 5 is a schematic diagram of a functional module of a second embodiment of a system for dynamically embedding an application of a client according to the present invention, wherein the buried point data is a buried message, and the application client
  • the terminal further includes a parsing module 13 for parsing the buried message into a buried point configuration file supported by the application client by using a corresponding message parsing converter;
  • the collection and statistics module 12 is further configured to determine, according to the mapping relationship data corresponding to the buried point configuration file, a control that needs to be buried and a corresponding operation type, and according to the corresponding operation during the running of the page. Type collection and/or statistically determined operational data for each control.
  • the server may send a burying packet to the application client when receiving the burying packet sending instruction sent by the user.
  • the server can also automatically send a buried message to the application client according to a preset condition.
  • mapping relationship between the identifier to be buried and the operation type to be carried by the user based on the server may be set.
  • mapping relationship between the identifier of the to-be-buried control and the operation type that is required to be carried in the buried-point packet may also be set by default.
  • the burying packet sent by the server is a burying packet in a unified format, that is, the format of the burying packet sent by the server to all types of application clients is the same.
  • the application client that receives the burying point message in the unified format can process the burying point message in the unified format. Because the server only needs to send the burying point message in a unified format, it is not necessary to change the format of the burying packet according to different types of the application client. Therefore, the server sends the burying message more flexibly and has higher versatility.
  • the packet parsing converters corresponding to different types of application clients may be different, so that various types of application clients may use their corresponding parsing and parsing conversions.
  • the device parses the burying point message sent by the server in a unified format, and generates a burying point configuration file supported by the application client.
  • a control identifier and an operation type mapping relationship are button:click, that is, the control identifier is a button, and the corresponding operation type is click (click event), and the message parsing converter corresponding to the application client supporting the Android operating system is supported.
  • the button:click can be parsed into Button:click, and the message parser corresponding to the application client supporting the iOS operating system can resolve the button:click into UIButton:tap.
  • the collection and statistics module 130 can obtain the correspondence between the identifier of the to-be-buried control and the operation type according to the buried-point configuration file, that is, determine the control that needs to be buried and the corresponding operation type, and the operation type can be, for example, Including the click operation and the operation duration, etc., the click operation and the operation duration data of each operation control are collected and/or statistically determined during the running of the predetermined page.
  • the present invention also proposes a system for dynamically burying the application of the client.
  • the burying point data is a burying point configuration file
  • the collecting and statistic module 12 is further configured to determine, according to the mapping relationship data corresponding to the burying point configuration file, a control that needs to bury a point statistic and a corresponding Type of operation.
  • the server may send a burying point configuration file to the application client when receiving the burying point configuration file sending instruction sent by the user.
  • the server can also automatically send a burying profile to the application client according to a preset condition.
  • the mapping relationship between the identifier to be buried and the operation type to be carried by the burying point configuration file may be set by the user based on the server.
  • the mapping relationship between the identifier of the to-be-buried control and the operation type that is required to be carried in the buried-point configuration file may also be set by default.
  • the burying point configuration file sent by the server is a burying point configuration file corresponding to an application client that is to receive the burying point configuration file, so that the application that receives the burying point configuration file is received.
  • the program client can directly call the buried point configuration file.
  • the predetermined page may be a page corresponding to an APP that needs to be dynamically buried.
  • the collection and statistics module 12 can obtain the correspondence between the identifier of the to-be-buried control and the operation type according to the buried-point configuration file, that is, the control that needs to be buried and the corresponding operation type, and the operation type can include, for example, a click operation and an operation duration. And so on, the click operation and the operation duration data of each operation control are collected and/or statistically determined during the running of the predetermined page.
  • the present invention also proposes application dynamics to the client based on any one of the first to third embodiments of the system for dynamically embedding the application of the client according to the present invention.
  • a fourth embodiment of a system for burying points the server 20 is configured to send the embedded data to an application client supporting an operating system of the same type, or to an application client supporting a different type of operating system When transmitting, the buried point data is sent to each of the application clients in real time or at a time.
  • some application clients may support the Android operating system, and some application clients may support the iOS operating system, and some data may only need to be operated to a certain type of operation.
  • the application client of the type is sent.
  • the server can send the buried data to the application client supporting this type of operation. It is also possible that some buried data needs to send buried data to an application client supporting the Android operating system and supporting the iOS operating system. At this time, the server can respectively support the application client supporting the Android operating system and supporting the iOS operating system.
  • Send buried point data In this embodiment, the server may determine whether it needs to send to an application client that supports the same type of operating system according to a buried point data sending instruction sent by the user, or needs to send to an application client that supports a different type of operating system.
  • the present invention also proposes application dynamics to the client according to any one of the first to fourth embodiments of the system for dynamically embedding the application of the client according to the present invention.
  • the server 20 is configured to generate a burying point data parameter setting interface, where the burying point is generated, in response to the burying point data generating instruction, when receiving a burying point data generating instruction issued by a user
  • the data parameter setting interface includes a selection item or an input item to be buried, and a selection item or an input item of the operation type corresponding to the selection item or the input item to be buried;
  • the server 20 is further configured to: according to the mapping relationship between the to-be-buried control and the operation type set by the user based on the buried point data parameter setting interface, according to the received control point to be buried and the operation type
  • the mapping relationship data generates the buried point data.
  • the item to be buried control item may include a plurality of preset control identifiers, and the user may select one, two or more control identifiers by clicking.
  • the input point to be buried may be an input box, and the user may input one, two or more control identifiers set by the user into the input box.
  • Each time a user sets a control ID it also sets an action type associated with the control ID.
  • the selection of the operation type may include a plurality of preset operation types, and the user may select one, two or more operation types by clicking.
  • the operation type input item may be an input box, and the user may input one, two or more operation types set by the user into the input box.
  • mapping data between the received to-be-buried control and the operation type may be generated according to a preset encoding rule to generate the buried point data. And send the buried data to the corresponding application client.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • a storage medium such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种对客户端的应用程序动态埋点的方法及系统，该方法包括：应用程序客户端侦测并接收服务器发送的埋点数据（S10）；若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据（S20）。在进行动态埋点的过程中，不需要应用程序客户端上传截屏数据，只需要接收服务器发送的埋点数据，并基于埋点数据对应的映射关系收集及/或统计控件的操作数据即可，不会对应用程序客户端的运行性能造成太大影响，且准确性较高，不容易出错。

Description

对客户端的应用程序动态埋点的方法、系统、客户端及服务器
本申请要求于2016年12月24日提交中国专利局、申请号为201611211423.3、发明名称为“对客户端的应用程序动态埋点的方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在申请中。
技术领域
本发明涉及计算机技术领域，尤其涉及一种对客户端的应用程序动态埋点的方法、系统、客户端及服务器。
背景技术
目前，对于基于“移动终端+服务器”运行架构的软件系统(该软件系统包括安装于移动终端的移动端程序和安装于服务器的服务器程序)而言，为了整体上验证所述软件系统的业务逻辑是否顺畅，以及之前的一些基本假设是否成立等，一般需要通过获取移动端程序的数据指标进行验证。
现有技术中，业界通常采用对所述软件系统进行埋点的方式收集并统计分析所述数据指标。也就是说，通过埋点的方式收集并统计分析所述数据指标，其实是对于所述软件系统的一个可视化健康检查，其重要性不言而喻。
为了在所述软件系统上线运行之后，调整所收集数据的类型，以更好的进行可视化健康检查，动态埋点的方案对业界来说显得更为迫切。
然而，现有的动态埋点方案需要移动端程序通过截屏的方式上传截屏数据，这种现有的动态埋点方案对移动端程序的运行性能造成很大影响，容易出错。
发明内容
本发明的主要目的在于提供一种对客户端的应用程序动态埋点的方法及系统，旨在更加灵活地收集异常信息。
为实现上述目的，本发明提供的对客户端的应用程序动态埋点的方法包括以下步骤：
应用程序客户端侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
优选地，所述埋点数据为埋点报文，所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型的步骤之前，还包括：
所述应用程序客户端利用对应的报文解析转换器将所述埋点报文解析成该应用程序客户端支持的埋点配置文件；
所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型的步骤包括：所述应用程序客户端基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
优选地，所述埋点数据为埋点配置文件，所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型的步骤包括：所述应用程序客户端基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
优选地，所述在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据的步骤包括：根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
优选地，所述对客户端的应用程序动态埋点的方法还包括：
若接收到用户发出的埋点数据指令，则服务器响应所述埋点数据指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则服务器根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
此外，为实现上述目的，本发明还提供一种对客户端的应用程序动态埋点的系统，所述对客户端的应用程序动态埋点的系统包括应用程序客户端和服务器，所述应用程序客户端包括：
接收模块，用于侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
收集及统计模块，用于若用户通过所述应用程序客户端访问预先确定的页面，则基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
优选地，所述埋点数据为埋点报文，所述应用程序客户端还包括解析模块，所述解析模块用于利用对应的报文解析转换器将所述埋点报文解析成该应用程序客户端支持的埋点配置文件；
所述收集及统计模块还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
优选地，所述埋点数据为埋点配置文件，所述收集及统计模块还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
优选地，所述收集及统计模块还用于根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
优选地，所述服务器用于若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
所述服务器还用于若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
本发明提出的对客户端的应用程序动态埋点的方法及系统，通过应用程序客户端侦测并接收服务器发送的埋点数据，若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据，从而在进行动态埋点的过程中，不需要应用程序客户端上传截屏数据，只需要接收服务器发送的埋点数据，并基于埋点数据对应的映射关系收集及/或统计控件的操作数据即可，不会对应用程序客户端的运行性能造成太大影响，且准确性较高，不容易出错。
附图说明
图1为本发明对客户端的应用程序动态埋点的方法第一实施例的流程示意图；
图2为本发明对客户端的应用程序动态埋点的方法第四实施例的流程示意图；
图3为本发明对客户端的应用程序动态埋点的方法第五实施例的流程示意图；
图4为本发明对客户端的应用程序动态埋点的系统第一实施例的功能模块示意图；
图5为本发明对客户端的应用程序动态埋点的系统的第二实施例的功能模块示意图。
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明提供一种对客户端的应用程序动态埋点的方法。该对客户端的应用程序动态埋点的方法可以基于应用程序客户端和服务器实现。应用程序客户端例如可以为但不限于手机、平板电脑等。客户端中安装有应用程序，应用程序例如可以为但不限于微信、QQ、电话应用、短信应用、淘宝APP等。参照图1，图1为本发明对客户端的应用程序动态埋点的方法第一实施例的流程示意图。在该实施例中，该对客户端的应用程序动态埋点的方法包括：
步骤S10，应用程序客户端侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
在本实施例中，服务器可以在接收到用户发送的埋点数据发送指令时，向应用程序客户端发送埋点数据。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点数据。
可以由用户基于服务器设置埋点数据所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点数据所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
步骤S20，若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
在本实施例中，所述预先确定的页面可以为需要进行动态埋点的APP对应的页面。应用程序客户端可以根据埋点数据获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
可选的，收集及/或统计操作数据可以为对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
可选的，在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据可以采用但不限于以下方式：
方式一，在所述页面运行期间根据预设的操作数据处理程序对确定的各个控件的操作数据进行收集及/或统计操作数据。例如，对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
在本方式中，预设的操作数据处理程序可以实时的识别对各个控件的操作数据。可选的，预设的操作数据处理程序还可以对识别的操作数据进行记录及/或统计同类型操作的次数。
方式二，根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到 的中间层拦截代码对确定的各个控件的操作数据进行收集及/或统计操作数据。例如，对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
在本方式中，中间层拦截代码可以拦截上层驱动的数据包，例如，可以拦截用户触发控件的操作数据，并对操作数据进行识别。记录及/或统计同类型操作的次数等。通过采用中间层拦截代码，可以不必编写额外的操作数据识别程序，可以直接利用现有系统的识别程序，只需要通过中间层拦截代码进行拦截即可。
本发明提供的对客户端的应用程序动态埋点的方法，通过应用程序客户端侦测并接收服务器发送的埋点数据，若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据，从而在进行动态埋点的过程中，不需要应用程序客户端上传截屏数据，只需要接收服务器发送的埋点数据，并基于埋点数据对应的映射关系收集及/或统计控件的操作数据即可，不会对应用程序客户端的运行性能造成太大影响，且准确性较高，不容易出错。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的方法的第一实施例，本发明还提出了对客户端的应用程序动态埋点的方法的第二实施例，所述埋点数据为埋点报文，步骤S20之前，还包括：
所述应用程序客户端利用对应的报文解析转换器将所述埋点报文解析成该应用程序客户端支持的埋点配置文件；
所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型的步骤包括：所述应用程序客户端基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
在本实施例中，服务器可以在接收到用户发送的埋点报文发送指令时，向应用程序客户端发送埋点报文。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点报文。
可以由用户基于服务器设置埋点报文所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点报文所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
可选的，在本实施例中，服务器发送的埋点报文为一种统一格式的埋点报文，即，服务器向所有类型的应用程序客户端发送的埋点报文的格式均相同。相应的，接收统一格式的埋点报文的应用程序客户端均可以处理这种统一格式的埋点报文。由于服务器仅需发送统一格式的埋点报文即可，不必依据应用程序客户端的不同类型而变换埋点报文的格式，因此服务器发送埋点 报文更加灵活，通用性更高。
在本实施例中，不同类型的应用程序客户端所对应的报文解析转换器可能不同，从而各种类型的应用程序客户端均可以利用其对应的报文解析转换器解析服务器发送的统一格式的埋点报文，并生成该应用程序客户端支持的埋点配置文件。例如，一个控件标识和操作类型映射关系为button:click，即控件标识为button，其对应的操作类型为click(单击事件)，支持Android操作系统的应用程序客户端对应的报文解析转换器可以将button:click解析成Button:click，支持iOS操作系统的应用程序客户端对应的报文解析转换器可以将button:click解析成UIButton:tap。
在本实施例中，应用程序客户端可以根据埋点配置文件获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的方法的第一实施例，本发明还提出了对客户端的应用程序动态埋点的方法的第三实施例，所述埋点数据为埋点配置文件，所述应用程序客户端基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型的步骤包括：所述应用程序客户端基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
在本实施例中，服务器可以在接收到用户发送的埋点配置文件发送指令时，向应用程序客户端发送埋点配置文件。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点配置文件。
可以由用户基于服务器设置埋点配置文件所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点配置文件所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
可选的，在本实施例中，服务器发送的埋点配置文件为与待接收所述埋点配置文件的应用程序客户端对应格式的埋点配置文件，以使得接收该埋点配置文件的应用程序客户端可以直接调用所述埋点配置文件。
在本实施例中，所述预先确定的页面可以为需要进行动态埋点的APP对应的页面。应用程序客户端可以根据埋点配置文件获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的方法的第一至第三任一实施例，本发明还提出了对客户端的应用程序动态埋点的方法的第四实施例，如图2所示，图2 为本发明对客户端的应用程序动态埋点的方法第四实施例的流程示意图，所述对客户端的应用程序动态埋点的方法还可以包括：
步骤S30，在所述埋点数据需要向支持相同类型操作系统的应用程序客户端发送，或者，需要向支持不同类型操作系统的应用程序客户端发送时，服务器实时或者定时将所述埋点数据发送给各个所述应用程序客户端。
在本实施例中，有些应用程序客户端可能支持Android操作系统，有些应用程序客户端可能支持iOS操作系统，可能有些埋点数据只需要向某一种操作类型的应用客户端发送，此时，服务器可以向支持这种操作类型的应用客户端发送埋点数据。也可能有些埋点数据需要同时向支持Android操作系统和支持iOS操作系统的应用程序客户端发送埋点数据，则此时，服务器可以分别向支持Android操作系统和支持iOS操作系统的应用程序客户端发送埋点数据。在本实施例中，服务器可以根据户发送的埋点数据发送指令确定需要向支持相同类型操作系统的应用程序客户端发送，还是需要向支持不同类型操作系统的应用程序客户端发送。
进一步地，为了进一步提高服务器发送埋点报文的灵活性，基于本发明对客户端的应用程序动态埋点的方法的第一至第四任一实施例，本发明还提出了对客户端的应用程序动态埋点的方法的第五实施例，如图3所示，图3为本发明对客户端的应用程序动态埋点的方法第五实施例的流程示意图，所述对客户端的应用程序动态埋点的方法还可以包括：
步骤S40，若接收到用户发出的埋点数据生成指令，则服务器响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项。
在本实施例中，所述待埋点控件选择项可以包括若干预设的控件标识，用户可以通过点击的方式选取其中一项、二项或多项控件标识。所述待埋点输入项可以为一输入框，用户可以将其设置的一项、二项或多项控件标识输入该输入框内。在用户每次设置一项控件标识时，还要对应该控件标识设置一与其关联的操作类型。所述操作类型的选择项可以包括若干预设的操作类型，用户可以通过点击的方式选取其中一项、二项或多项操作类型。所述操作类型输入项可以为一输入框，用户可以将其设置的一项、二项或多项操作类型输入该输入框内。
步骤S50，若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则服务器根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
在本实施例中，可以根据预设的编码规则将所述接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。并将埋点数据发送至对应的应用程序客户端。
本发明进一步提供一种对客户端的应用程序动态埋点的系统。所述对客户端的应用程序动态埋点的系统包括应用程序客户端10和服务器20。应用程序客户端10例如可以为但不限于手机、平板电脑等。客户端中安装有应用程序，应用程序例如可以为但不限于微信、QQ、电话应用、短信应用、淘宝APP等。参照图4，图4为本发明对客户端的应用程序动态埋点的系统第一实施例的功能模块示意图。在第一实施例中，所述应用程序客户端10包括：
接收模块11，用于侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
在本实施例中，服务器可以在接收到用户发送的埋点数据发送指令时，向应用程序客户端发送埋点数据。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点数据。
可以由用户基于服务器设置埋点数据所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点数据所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
收集及统计模块12，用于若用户通过所述应用程序客户端访问预先确定的页面，则基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
在本实施例中，所述预先确定的页面可以为需要进行动态埋点的APP对应的页面。收集及统计模块12可以根据埋点数据获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
可选的，收集及/或统计操作数据可以为对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
可选的，收集及统计模块12在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据可以采用但不限于以下方式：
方式一，收集及统计模块12还用于在所述页面运行期间根据预设的操作数据处理程序对确定的各个控件的操作数据进行收集及/或统计操作数据。例如，对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
在本方式中，预设的操作数据处理程序可以实时的识别对各个控件的操作数据。可选的，预设的操作数据处理程序还可以对识别的操作数据进行记录及/或统计同类型操作的次数。
方式二，收集及统计模块12还用于根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行收集及/或统计操作数据。例如，对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
在本方式中，中间层拦截代码可以拦截上层驱动的数据包，例如，可以拦截用户触发控件的操作数据，并对操作数据进行识别。记录及/或统计同类型操作的次数等。通过采用中间层拦截代码，可以不必编写额外的操作数据识别程序，可以直接利用现有系统的识别程序，只需要通过中间层拦截代码进行拦截即可。
本发明提供的对客户端的应用程序动态埋点的系统，通过应用程序客户端侦测并接收服务器发送的埋点数据，若用户通过所述应用程序客户端访问预先确定的页面，则所述应用程序客户端基于所述埋点数据对应的所述映射关系确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据，从而在进行动态埋点的过程中，不需要应用程序客户端上传截屏数据，只需要接收服务器发送的埋点数据，并基于埋点数据对应的映射关系收集及/或统计控件的操作数据即可，不会对应用程序客户端的运行性能造成太大影响，且准确性较高，不容易出错。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的系统的第一实施例，本发明还提出了对客户端的应用程序动态埋点的系统的第二实施例，参照图5，图5为本发明对客户端的应用程序动态埋点的系统的第二实施例的功能模块示意图，所述埋点数据为埋点报文，所述应用程序客户端还包括解析模块13，所述解析模块13用于利用对应的报文解析转换器将所述埋点报文解析成该应用程序客户端支持的埋点配置文件；
所述收集及统计模块12还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
在本实施例中，服务器可以在接收到用户发送的埋点报文发送指令时，向应用程序客户端发送埋点报文。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点报文。
可以由用户基于服务器设置埋点报文所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点报文所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
可选的，在本实施例中，服务器发送的埋点报文为一种统一格式的埋点报文，即，服务器向所有类型的应用程序客户端发送的埋点报文的格式均相同。相应的，接收统一格式的埋点报文的应用程序客户端均可以处理这种统一格式的埋点报文。由于服务器仅需发送统一格式的埋点报文即可，不必依据应用程序客户端的不同类型而变换埋点报文的格式，因此服务器发送埋点报文更加灵活，通用性更高。
在本实施例中，不同类型的应用程序客户端所对应的报文解析转换器可能不同，从而各种类型的应用程序客户端均可以利用其对应的报文解析转换 器解析服务器发送的统一格式的埋点报文，并生成该应用程序客户端支持的埋点配置文件。例如，一个控件标识和操作类型映射关系为button:click，即控件标识为button，其对应的操作类型为click(单击事件)，支持Android操作系统的应用程序客户端对应的报文解析转换器可以将button:click解析成Button:click，支持iOS操作系统的应用程序客户端对应的报文解析转换器可以将button:click解析成UIButton:tap。
在本实施例中，收集及统计模块130可以根据埋点配置文件获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的系统的第一实施例，本发明还提出了对客户端的应用程序动态埋点的系统的第三实施例，所述埋点数据为埋点配置文件，所述收集及统计模块12还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
在本实施例中，服务器可以在接收到用户发送的埋点配置文件发送指令时，向应用程序客户端发送埋点配置文件。可选的，服务器也可以根据预设条件自动向应用程序客户端发送埋点配置文件。
可以由用户基于服务器设置埋点配置文件所需携带的待埋点控件标识和操作类型之间的映射关系。可选的，埋点配置文件所需携带的待埋点控件标识和操作类型之间的映射关系也可以为默认设置的。
可选的，在本实施例中，服务器发送的埋点配置文件为与待接收所述埋点配置文件的应用程序客户端对应格式的埋点配置文件，以使得接收该埋点配置文件的应用程序客户端可以直接调用所述埋点配置文件。
在本实施例中，所述预先确定的页面可以为需要进行动态埋点的APP对应的页面。收集及统计模块12可以根据埋点配置文件获得待埋点控件标识和操作类型的对应关系，即，确定出需埋点统计的控件和对应的操作类型，操作类型例如可以包括点击操作和操作时长等，在该预先确定的页面运行期间收集及/或统计确定的各个操作控件的点击操作和操作时长数据。
进一步地，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的系统的第一至第三任一实施例，本发明还提出了对客户端的应用程序动态埋点的系统的第四实施例，所述服务器20用于在所述埋点数据需要向支持相同类型操作系统的应用程序客户端发送，或者，需要向支持不同类型操作系统的应用程序客户端发送时，实时或者定时将所述埋点数据发送给各个所述应用程序客户端。
在本实施例中，有些应用程序客户端可能支持Android操作系统，有些应用程序客户端可能支持iOS操作系统，可能有些埋点数据只需要向某一种操 作类型的应用客户端发送，此时，服务器可以向支持这种操作类型的应用客户端发送埋点数据。也可能有些埋点数据需要同时向支持Android操作系统和支持iOS操作系统的应用程序客户端发送埋点数据，则此时，服务器可以分别向支持Android操作系统和支持iOS操作系统的应用程序客户端发送埋点数据。在本实施例中，服务器可以根据户发送的埋点数据发送指令确定需要向需要向支持相同类型操作系统的应用程序客户端发送，还是需要向支持不同类型操作系统的应用程序客户端发送。
进一步的，为了进一步提高服务器发送埋点数据的灵活性，基于本发明对客户端的应用程序动态埋点的系统的第一至第四任一实施例，本发明还提出了对客户端的应用程序动态埋点的系统的第五实施例，所述服务器20用于若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
所述服务器20还用于若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
在本实施例中，所述待埋点控件选择项可以包括若干预设的控件标识，用户可以通过点击的方式选取其中一项、二项或多项控件标识。所述待埋点输入项可以为一输入框，用户可以将其设置的一项、二项或多项控件标识输入该输入框内。在用户每次设置一项控件标识时，还要对应该控件标识设置一与其关联的操作类型。所述操作类型的选择项可以包括若干预设的操作类型，用户可以通过点击的方式选取其中一项、二项或多项操作类型。所述操作类型输入项可以为一输入框，用户可以将其设置的一项、二项或多项操作类型输入该输入框内。
在本实施例中，可以根据预设的编码规则将所述接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。并将埋点数据发送至对应的应用程序客户端。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是 利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
Figure PCTCN2017105013-appb-000001

Claims (16)

  1. 页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
  2. 如权利要求3所述的对客户端的应用程序动态埋点的方法，其特征在于，所述在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据的步骤包括：根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
  3. 如权利要求1所述的对客户端的应用程序动态埋点的方法，其特征在于，所述对客户端的应用程序动态埋点的方法还包括：
    若接收到用户发出的埋点数据指令，则服务器响应所述埋点数据指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则服务器根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  4. 如权利要求2所述的对客户端的应用程序动态埋点的方法，其特征在于，所述对客户端的应用程序动态埋点的方法还包括：
    若接收到用户发出的埋点数据指令，则服务器响应所述埋点数据指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则服务器根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  5. 如权利要求3所述的对客户端的应用程序动态埋点的方法，其特征在于，所述对客户端的应用程序动态埋点的方法还包括：
    若接收到用户发出的埋点数据指令，则服务器响应所述埋点数据指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则服务器根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  6. 一种对客户端的应用程序动态埋点的系统，其特征在于，所述对客户端的应用程序动态埋点的系统包括应用程序客户端和服务器，所述应用程序客户端包括：
    接收模块，用于侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
    收集及统计模块，用于若用户通过所述应用程序客户端访问预先确定的页面，则基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
  7. 如权利要求10所述的对客户端的应用程序动态埋点的系统，其特征在于，所述埋点数据为埋点报文，所述应用程序客户端还包括解析模块，所述解析模块用于利用对应的报文解析转换器将所述埋点报文解析成该应用程序客户端支持的埋点配置文件；
    所述收集及统计模块还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
  8. 如权利要求10所述的对客户端的应用程序动态埋点的系统，其特征在于，所述埋点数据为埋点配置文件，所述收集及统计模块还用于基于所述埋点配置文件对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型。
  9. 如权利要求10所述的对客户端的应用程序动态埋点的系统，其特征在于，所述收集及统计模块还用于根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
  10. 如权利要求11所述的对客户端的应用程序动态埋点的系统，其特征在于，所述收集及统计模块还用于根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
  11. 如权利要求12所述的对客户端的应用程序动态埋点的系统，其特征在于，所述收集及统计模块还用于根据预先确定的控件、操作类型和中间层拦截代码的映射关系，找到确定的各个控件对应的中间层拦截代码，并在该 页面运行期间启用找到的中间层拦截代码对确定的各个控件的操作数据进行识别、记录及/或统计同类型操作的次数。
  12. 如权利要求10所述的对客户端的应用程序动态埋点的系统，其特征在于，所述服务器用于若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    所述服务器还用于若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  13. 如权利要求11所述的对客户端的应用程序动态埋点的系统，其特征在于，所述服务器用于若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    所述服务器还用于若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  14. 如权利要求12所述的对客户端的应用程序动态埋点的系统，其特征在于，所述服务器用于若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    所述服务器还用于若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
  15. 一种客户端，其特征在于，所述客户端包括：
    接收模块，用于侦测并接收服务器发送的埋点数据，所述埋点数据携带有待埋点控件标识和操作类型之间的映射关系数据；
    收集及统计模块，用于若用户通过所述应用程序客户端访问预先确定的页面，则基于所述埋点数据对应的所述映射关系数据确定需埋点统计的控件和对应的操作类型，并在所述页面运行期间根据所述对应的操作类型收集及/或统计确定的各个控件的操作数据。
  16. 一种服务器，其特征在于，所述服务器用于：
    若接收到用户发出的埋点数据生成指令，则响应所述埋点数据生成指令，生成埋点数据参数设置界面，所述埋点数据参数设置界面包括待埋点控件选择项或者输入项，及各个待埋点控件标识选择项或者输入项对应的操作类型的选择项或者输入项；
    若接收到用户基于所述埋点数据参数设置界面设置的待埋点控件和操作类型之间的映射关系数据，则根据接收到的待埋点控件和操作类型之间的映射关系数据生成所述埋点数据。
PCT/CN2017/105013 2016-12-24 2017-09-30 对客户端的应用程序动态埋点的方法、系统、客户端及服务器 WO2018113385A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611211423.3A CN106598868B (zh) 2016-12-24 2016-12-24 对客户端的应用程序动态埋点的方法及系统
CN201611211423.3 2016-12-24

Publications (1)

Publication Number Publication Date
WO2018113385A1 true WO2018113385A1 (zh) 2018-06-28

Family

ID=58603616

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/105013 WO2018113385A1 (zh) 2016-12-24 2017-09-30 对客户端的应用程序动态埋点的方法、系统、客户端及服务器

Country Status (2)

Country Link
CN (1) CN106598868B (zh)
WO (1) WO2018113385A1 (zh)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109445985A (zh) * 2018-09-03 2019-03-08 平安普惠企业管理有限公司 应用程序的回滚方法及系统
CN109522191A (zh) * 2018-10-16 2019-03-26 深圳壹账通智能科技有限公司 一种采集交互行为指令的属性信息的方法及装置
CN109597949A (zh) * 2018-10-22 2019-04-09 平安科技（深圳）有限公司 基于数据标准化的第三方埋点标识生成方法和设备
CN109766256A (zh) * 2018-12-21 2019-05-17 中国平安财产保险股份有限公司 应用程序中h5页面性能测试方法、装置和计算机设备
CN110502415A (zh) * 2019-08-27 2019-11-26 北京思维造物信息科技股份有限公司 一种埋点设置方法、装置及设备
CN111190807A (zh) * 2018-11-14 2020-05-22 杭州萤石软件有限公司 一种埋点测试方法及设备
CN111367562A (zh) * 2018-12-25 2020-07-03 阿里巴巴集团控股有限公司 数据采集方法、装置、存储介质及处理器
CN112000587A (zh) * 2020-10-29 2020-11-27 四川新网银行股份有限公司 一种基于关联对象操作统计的测试工时自动统计方法
CN112015467A (zh) * 2020-09-04 2020-12-01 杭州网易再顾科技有限公司 埋点方法、介质、装置和计算设备
CN112115041A (zh) * 2020-08-06 2020-12-22 北京健康之家科技有限公司 应用程序的动态埋点方法、装置、存储介质及计算机设备
CN112148606A (zh) * 2020-09-22 2020-12-29 京东数字科技控股股份有限公司 埋点测试方法、装置、设备及计算机可读介质
CN112286515A (zh) * 2020-10-30 2021-01-29 上海淇玥信息技术有限公司 一种基于html5的可视化埋点方法、装置和电子设备
CN113064785A (zh) * 2020-12-31 2021-07-02 开鑫金服(南京)信息服务有限公司 基于运行时机制的用户行为采集方法、设备及存储介质
CN113448832A (zh) * 2020-06-18 2021-09-28 北京新氧科技有限公司 一种控件曝光检测方法及应用程序运行监测系统
CN114661569A (zh) * 2022-03-25 2022-06-24 中企云链（北京）金融信息服务有限公司 用户行为数据动态埋点采集方法

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106598868B (zh) * 2016-12-24 2018-03-02 上海壹账通金融科技有限公司 对客户端的应用程序动态埋点的方法及系统
CN107800757B (zh) * 2017-03-28 2020-10-27 平安壹钱包电子商务有限公司 用户行为记录方法及装置
CN107295088B (zh) * 2017-06-29 2020-04-10 广东神马搜索科技有限公司 打点信息监测方法、装置及客户端
CN109213652A (zh) * 2017-06-30 2019-01-15 北京嘀嘀无限科技发展有限公司 用户行为数据采集方法和装置
CN107609004B (zh) * 2017-07-21 2020-08-18 深圳市小牛在线互联网信息咨询有限公司 应用程序埋点方法和装置、计算机设备和存储介质
CN107864065B (zh) * 2017-08-16 2020-11-24 深圳壹账通智能科技有限公司 无埋点数据采集方法、系统及计算机可读存储介质
CN107861982A (zh) * 2017-09-29 2018-03-30 五八有限公司 动态确定应用程序页面布局的方法、终端、服务器及系统
CN109597743B (zh) * 2017-09-30 2022-06-21 北京国双科技有限公司 页面圈选方法、点击量统计方法及相关设备
CN107832218B (zh) * 2017-11-10 2019-03-12 平安科技（深圳）有限公司 动态页面中的埋点处理方法、装置和计算机设备
CN107943651B (zh) * 2017-11-22 2021-01-29 网易（杭州）网络有限公司 信息获取方法、介质、装置和计算设备
CN108304176B (zh) * 2017-12-14 2021-09-07 广东数果科技有限公司 一种跨平台移动终端的可视化埋点方法
CN108510287B (zh) * 2018-01-16 2020-06-30 平安科技（深圳）有限公司 客户回访的判断方法、电子装置及计算机可读存储介质
CN109739717B (zh) * 2018-04-12 2021-01-26 京东方科技集团股份有限公司 一种页面数据采集的方法及装置、服务器
CN110489597A (zh) * 2018-05-10 2019-11-22 华为技术有限公司 一种获取数据的方法和终端设备
CN109542529B (zh) * 2018-10-26 2022-04-05 深圳壹账通智能科技有限公司 基于函数名称的埋点方法、装置、计算机设备及存储介质
CN110347582B (zh) * 2019-05-21 2024-05-28 平安银行股份有限公司 埋点测试方法和装置
CN110443677A (zh) * 2019-07-05 2019-11-12 五八有限公司 一种信息处理方法及装置
CN110442502B (zh) * 2019-07-23 2021-12-31 北京三快在线科技有限公司 一种埋点的方法、装置、设备及存储介质
CN112416995B (zh) * 2019-08-23 2023-12-08 腾讯科技（深圳）有限公司 一种数据统计方法、装置、计算机设备及存储介质
CN110909284A (zh) * 2019-10-11 2020-03-24 口碑(上海)信息技术有限公司 一种数据处理系统以及方法
CN110781064B (zh) * 2019-10-28 2023-05-26 深圳市思迪信息技术股份有限公司 客户端用户行为数据动态埋点采集的方法及装置
CN112783754A (zh) * 2019-11-07 2021-05-11 北京沃东天骏信息技术有限公司 一种对页面进行测试的方法和装置
CN111124906B (zh) * 2019-12-17 2022-06-28 蚂蚁财富(上海)金融信息服务有限公司 基于动态埋点的跟踪方法、编译方法、装置和电子设备
CN111459811B (zh) * 2020-03-26 2023-07-18 广州虎牙科技有限公司 埋点数据校验方法和装置
CN111782503B (zh) * 2020-05-20 2024-04-19 北京皮尔布莱尼软件有限公司 一种应用埋点测试方法及移动终端
CN113190411A (zh) * 2021-05-12 2021-07-30 北京奇艺世纪科技有限公司 数据处理方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103631699A (zh) * 2012-08-28 2014-03-12 纽海信息技术（上海）有限公司 日志管理系统及日志监控、获取和查询方法
CN104572043A (zh) * 2013-10-16 2015-04-29 阿里巴巴集团控股有限公司 一种对客户端应用的控件进行实时埋点的方法及装置
CN104915296A (zh) * 2015-06-29 2015-09-16 北京金山安全软件有限公司 埋点测试方法、数据的查询方法及装置
CN106066826A (zh) * 2016-05-24 2016-11-02 北京金山安全软件有限公司 埋点的自动测试方法、装置以及终端
CN106202440A (zh) * 2016-07-13 2016-12-07 华为技术有限公司 数据处理方法、装置及设备
CN106598868A (zh) * 2016-12-24 2017-04-26 上海亿账通互联网科技有限公司 对客户端的应用程序动态埋点的方法及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130066710A1 (en) * 2010-03-02 2013-03-14 Digg, Inc. Including content items in advertisements

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103631699A (zh) * 2012-08-28 2014-03-12 纽海信息技术（上海）有限公司 日志管理系统及日志监控、获取和查询方法
CN104572043A (zh) * 2013-10-16 2015-04-29 阿里巴巴集团控股有限公司 一种对客户端应用的控件进行实时埋点的方法及装置
CN104915296A (zh) * 2015-06-29 2015-09-16 北京金山安全软件有限公司 埋点测试方法、数据的查询方法及装置
CN106066826A (zh) * 2016-05-24 2016-11-02 北京金山安全软件有限公司 埋点的自动测试方法、装置以及终端
CN106202440A (zh) * 2016-07-13 2016-12-07 华为技术有限公司 数据处理方法、装置及设备
CN106598868A (zh) * 2016-12-24 2017-04-26 上海亿账通互联网科技有限公司 对客户端的应用程序动态埋点的方法及系统

Cited By (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109445985A (zh) * 2018-09-03 2019-03-08 平安普惠企业管理有限公司 应用程序的回滚方法及系统
CN109522191A (zh) * 2018-10-16 2019-03-26 深圳壹账通智能科技有限公司 一种采集交互行为指令的属性信息的方法及装置
CN109597949A (zh) * 2018-10-22 2019-04-09 平安科技（深圳）有限公司 基于数据标准化的第三方埋点标识生成方法和设备
CN109597949B (zh) * 2018-10-22 2024-04-02 平安科技（深圳）有限公司 基于数据标准化的第三方埋点标识生成方法和设备
CN111190807A (zh) * 2018-11-14 2020-05-22 杭州萤石软件有限公司 一种埋点测试方法及设备
CN111190807B (zh) * 2018-11-14 2023-08-18 杭州萤石软件有限公司 一种埋点测试方法及设备
CN109766256B (zh) * 2018-12-21 2023-02-07 中国平安财产保险股份有限公司 应用程序中h5页面性能测试方法、装置和计算机设备
CN109766256A (zh) * 2018-12-21 2019-05-17 中国平安财产保险股份有限公司 应用程序中h5页面性能测试方法、装置和计算机设备
CN111367562A (zh) * 2018-12-25 2020-07-03 阿里巴巴集团控股有限公司 数据采集方法、装置、存储介质及处理器
CN111367562B (zh) * 2018-12-25 2023-05-02 阿里巴巴集团控股有限公司 数据采集方法、装置、存储介质及处理器
CN110502415A (zh) * 2019-08-27 2019-11-26 北京思维造物信息科技股份有限公司 一种埋点设置方法、装置及设备
CN110502415B (zh) * 2019-08-27 2023-11-28 北京思维造物信息科技股份有限公司 一种埋点设置方法、装置及设备
CN113448832A (zh) * 2020-06-18 2021-09-28 北京新氧科技有限公司 一种控件曝光检测方法及应用程序运行监测系统
CN113448832B (zh) * 2020-06-18 2024-03-12 北京新氧科技有限公司 一种控件曝光检测方法及应用程序运行监测系统
CN112115041A (zh) * 2020-08-06 2020-12-22 北京健康之家科技有限公司 应用程序的动态埋点方法、装置、存储介质及计算机设备
CN112115041B (zh) * 2020-08-06 2023-08-22 北京水滴科技集团有限公司 应用程序的动态埋点方法、装置、存储介质及计算机设备
CN112015467A (zh) * 2020-09-04 2020-12-01 杭州网易再顾科技有限公司 埋点方法、介质、装置和计算设备
CN112015467B (zh) * 2020-09-04 2024-05-17 杭州网易再顾科技有限公司 埋点方法、介质、装置和计算设备
CN112148606A (zh) * 2020-09-22 2020-12-29 京东数字科技控股股份有限公司 埋点测试方法、装置、设备及计算机可读介质
CN112148606B (zh) * 2020-09-22 2024-05-17 京东科技控股股份有限公司 埋点测试方法、装置、设备及计算机可读介质
CN112000587A (zh) * 2020-10-29 2020-11-27 四川新网银行股份有限公司 一种基于关联对象操作统计的测试工时自动统计方法
CN112000587B (zh) * 2020-10-29 2021-11-23 四川新网银行股份有限公司 一种基于关联对象操作统计的测试工时自动统计方法
CN112286515A (zh) * 2020-10-30 2021-01-29 上海淇玥信息技术有限公司 一种基于html5的可视化埋点方法、装置和电子设备
CN113064785A (zh) * 2020-12-31 2021-07-02 开鑫金服(南京)信息服务有限公司 基于运行时机制的用户行为采集方法、设备及存储介质
CN114661569A (zh) * 2022-03-25 2022-06-24 中企云链（北京）金融信息服务有限公司 用户行为数据动态埋点采集方法
CN114661569B (zh) * 2022-03-25 2024-04-26 中企云链股份有限公司 用户行为数据动态埋点采集方法

Also Published As

Publication number Publication date
CN106598868A (zh) 2017-04-26
CN106598868B (zh) 2018-03-02

Similar Documents

Publication Publication Date Title
WO2018113385A1 (zh) 对客户端的应用程序动态埋点的方法、系统、客户端及服务器
CN111083225B (zh) 在物联网平台中的数据处理方法、装置及物联网平台
US10554805B2 (en) Information processing method, terminal, and computer-readable storage medium
US10735590B2 (en) Framework for predictive customer care support
WO2018184420A1 (zh) 软件测试方法、装置、电子设备及介质
CN105207806A (zh) 分布式服务的监控方法及装置
WO2017131774A1 (en) Log event summarization for distributed server system
CN104980421B (zh) 一种批量请求处理方法及系统
CN111198797B (zh) 操作监控方法及装置、操作分析方法及装置
CN106713011B (zh) 一种获取测试数据的方法与系统
KR102060262B1 (ko) 이동전화번호를 변경하기 위한 서비스 요청을 인식하기 위한 방법 및 장치
WO2019061998A1 (zh) 断点智能分流方法、电子装置及计算机可读存储介质
CN107566480B (zh) 移动终端应用的用户活动信息采集方法及装置、存储介质
CN105553770B (zh) 一种数据采集控制方法和装置
CN112241362A (zh) 一种测试方法、装置、服务器及存储介质
WO2021012741A1 (zh) 基于经验库的异常前端操作提醒的方法及相关设备
CN110162982B (zh) 检测非法权限的方法及装置、存储介质、电子设备
US11283929B2 (en) Identifying unreported issues through customer service interactions and website analytics
US20170223136A1 (en) Any Web Page Reporting and Capture
CN115629940A (zh) 一种微服务全链路追踪方法、装置、系统及介质
CN114936249A (zh) 一种文件解析、转换方法、装置、设备及可读存储介质
WO2021129849A1 (zh) 日志处理方法、装置、设备和存储介质
CN113452533B (zh) 计费自巡检、自愈合方法、装置、计算机设备和存储介质
CN111741046B (zh) 数据上报方法、获取方法、装置、设备及介质
CN112818204A (zh) 一种业务的处理方法、装置、设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17883797

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17883797

Country of ref document: EP

Kind code of ref document: A1