CN115509872A - Client behavior data acquisition method and device - Google Patents
Client behavior data acquisition method and device Download PDFInfo
- Publication number
- CN115509872A CN115509872A CN202210888364.2A CN202210888364A CN115509872A CN 115509872 A CN115509872 A CN 115509872A CN 202210888364 A CN202210888364 A CN 202210888364A CN 115509872 A CN115509872 A CN 115509872A
- Authority
- CN
- China
- Prior art keywords
- field
- value
- page
- view event
- file
- 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.)
- Pending
Links
Images
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/3438—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 monitoring of user actions
-
- 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
Abstract
The invention provides a client behavior data acquisition method, which associates a page, a view and a self-defined field by establishing a mapping relation between a value of the page attribute field, a value of the view event field and a value of the self-defined field, wherein the client can acquire a mapping relation file and store the mapping relation file locally, when a user behavior triggers a buried point function to acquire the value of the current page attribute field and the value of the view attribute field, the acquired value is matched with the value stored in the mapping relation file, after the matching is successful, the value of the self-defined field in the mapping relation can also be added into log data recorded by the view event triggered by the user behavior at this time, the self-defined field is used for describing service data, and the service data is mapped with the page and the view, so that the acquired information of the buried point data is more comprehensive, the requirement of data analysis is met, when the log data is uploaded to a server, only the data matched with the mapping relation is uploaded, and the storage resource of the server is saved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a client behavior data acquisition method and device, electronic equipment and a readable storage medium.
Background
The embedded point is a commonly used data analysis and collection method, user behavior data can be counted through the embedded point, and problems existing in application can be analyzed and improved for developers based on the statistical result of the user behavior data.
At present, a full-embedded-point mode is used for collecting user behavior data, and the full-embedded-point mode can be used for collecting behavior information of all pages and controls.
However, the data volume acquired by the full buried point is huge, and the data can be analyzed only by screening, so that a large amount of redundant data is generated, resources of a terminal and a server are wasted, and the buried point data obtained by the full buried point mode cannot accurately reflect the association with the service.
Disclosure of Invention
The embodiment of the invention provides a client behavior data acquisition method and device, electronic equipment and a readable storage medium. The method and the device solve the problems that the buried point data occupies server side resources and the buried point data cannot reflect the association with the service in the prior art.
In a first aspect, an embodiment of the present invention provides a method for acquiring client behavior data, where the method includes:
acquiring a mapping relation file, wherein the mapping relation file comprises: the relation among the value of a page attribute field, the value of a view event field and the value of a custom field, wherein the page attribute field is a field which uniquely represents the page, the view event field is a field which uniquely represents the view event, and the custom field is a field related to the view event;
responding to an operation behavior of a user, and acquiring first attribute information of a page of a client and second attribute information of a view event corresponding to the page through a buried point process in the client;
and sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
In a second aspect, an embodiment of the present invention provides a client behavior data acquisition apparatus, where the apparatus includes:
a mapping file obtaining module, configured to obtain a mapping relationship file, where the mapping relationship file includes: the relation among the value of the page attribute field, the value of the view event field and the value of the self-defining field, wherein the page attribute field is the field which uniquely represents the page, the view event field is the field which uniquely represents the view event, and the self-defining field is the field related to the view event;
the behavior information acquisition module is used for responding to the operation behavior of a user and acquiring first attribute information of a page of a client and second attribute information of a view event corresponding to the page through a point burying process in the client;
and the matching module is used for sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
In a third aspect, an embodiment of the present invention further provides an electronic device, including a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of the first aspect.
In a fourth aspect, the present invention also provides a computer-readable storage medium, where instructions of the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of the first aspect.
In the embodiment of the invention, the mapping relation between the values of the page attribute field and the view event field and the value of the custom field is established, the page, the view and the custom field are associated, the client can obtain the mapping relation file and store the mapping relation file in the local, when the user behavior triggers the embedded point function to obtain the values of the current page attribute field and the view attribute field, the obtained values are matched with the values stored in the mapping relation file, after the matching is successful, the value of the custom field in the mapping relation can also be added into the log data recorded by the view event triggered by the user behavior at this time, the custom field is used for describing the service data, and the service data is mapped with the page and the view, so that the obtained embedded point data information is more comprehensive to meet the requirement of data analysis, meanwhile, when the log data is uploaded to the service terminal, only the data matched with the mapping relation is uploaded, and the storage resource of the service terminal is saved.
Drawings
Fig. 1 is a flowchart illustrating steps of a method for collecting client behavior data according to an embodiment of the present invention;
fig. 2 is a flowchart of steps of another client behavior data collection method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a buried point interaction provided by an embodiment of the present invention;
fig. 4 is a block diagram of a client behavior data acquisition apparatus according to an embodiment of the present invention;
FIG. 5 is a logic block diagram of an electronic device provided by an embodiment of the invention;
fig. 6 is a logic block diagram of another electronic device according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
Fig. 1 is a flowchart of steps of a method for acquiring client behavior data according to an embodiment of the present invention, and as shown in fig. 1, the method may include:
In the embodiment of the present invention, the mapping file is established according to the mapping relationship between the page and the view, and a custom field is added in the mapping relationship, where the custom field is a field related to a view event, for example: for the login event, the page name, the page class name, the view name and the view event type of the login page can be obtained by obtaining the data of the buried point, and for the values of fields such as the risk event class, the page code, the risk event code and the like of the login event, the login event and the corresponding page can be mapped in a self-defining mode, and the mapping relation among the page, the view and the self-defined field is established, so that when the view event is triggered, log data containing the values of the page attribute field, the view event field and the self-defined field can be obtained, and the data of the buried point with more abundant data volume can be obtained.
In the embodiment of the present invention, for the behavior of the user, the embedded point process may be triggered to start collecting the behavior data of the user, for example: if the view corresponds to a login button, when a user opens a page, the embedded point process starts to record the opening time of the page, and operates the page until the page is closed, if the user clicks the login button in the page, the embedded point process is triggered to record the clicking operation of the user, and according to data acquired by the embedded point process, first attribute information of the page triggered by the user is obtained, wherein the first attribute information comprises: the page name, the page class name, and the second attribute information include: view identification, view name, etc.
And 103, sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
In the embodiment of the invention, the mapping relation stores the value of the page attribute field, the mapping relation between the value of the view event field and the value of the custom field, after the value corresponding to the currently triggered page and view event of the user is obtained based on the operation behavior of the user, the obtained attribute value representing the current page and view event can be matched with the attribute value in the mapping relation, if the matching is successful, the value of the custom field corresponding to the value of the page attribute field and the value of the view event field in the mapping relation is obtained, and the value of the custom field can be added to the currently obtained buried point data, so that the buried point data collected for a certain view event contains richer data.
Furthermore, after the data of the buried point is obtained, the data of the buried point can be stored locally and uploaded to the server side according to a preset rule, and the server side can receive the data of the buried point and further analyze the data of the buried point.
In summary, in the embodiment of the present invention, a mapping relationship between a value of a page attribute field, a value of a view event field, and a value of a custom field is established, a page, a view, and a custom field are associated, a client may obtain a mapping relationship file and store the mapping relationship file locally, when a user behavior triggers a buried point function to obtain the value of a current page attribute field and the value of a view attribute field, the obtained value is matched with the value stored in the mapping relationship file, after the matching is successful, the value of the custom field in the mapping relationship may also be added to log data recorded by the view event triggered by the user behavior at this time, the custom field is used to describe service data, and the service data is mapped with the page and the view, so that information of the obtained buried point data is more comprehensive, thereby satisfying the requirement of data analysis, and at the same time, when the log data is uploaded to a service end, only the data matched with the mapping relationship is uploaded, thereby saving storage resources of the service end.
Fig. 2 is a flowchart of steps of a client behavior data collection method according to an embodiment of the present invention, and as shown in fig. 2, the method may include:
For this step, reference may be made to step 101, which is not described herein again.
Specifically, in the embodiment of the present invention, the mapping relationship file obtained by the client may be a file in Json (JavaScript Object Notation) format, the Json format is a lightweight data exchange format, and the Json file defines a correspondence between attribute names and attribute values of a page attribute field, a view event field, and some custom fields, for example, for a registration event, the correspondence between the attribute and the attribute value defined in the Json file includes: page class name field: "cl assName": "com, baoyin, credit, cashloan, login, activity, new clcheckphoneaactity", view event field: "viewTag": "btn _ next", and custom fields: "eventID": "getVerificationClick", "riskType": "REGISTER", "riskavent": "R EGISTER" and the like. After the client side obtains the json file, the character strings in the json file are obtained through analysis of the json file and stored as Hash mapping, and then the target log data are obtained through matching with data in the Hash mapping.
This step may refer to step 102, which is not described herein again.
Optionally, step 203 may specifically include:
substep 2031, in response to the operation on the page, acquiring the life cycle information of the page through a preset page monitoring function, and using the life cycle information as first attribute information, where the first attribute information includes: page creation time, page destruction time, and page class name.
In the embodiment of the present invention, the monitoring of the page lifecycle may be implemented through a "register activity lifecycle callbacks" interface, so as to record the process from creation to destruction of the page, and obtain the page class name of the current page.
Sub-step 2032, in response to the operation on the view, obtaining second attribute information of the view event through a preset event monitoring function, where the second attribute information includes: view event tag, view event name.
In the embodiment of the invention, the preset event monitoring function can be a callback method of android, the behavior data of a user can be captured by the callback method, each view event has a view event label with a unique identifier and a view event name, which view event occurs to the user can be captured by the callback method, the view event label is determined according to the determined view event, the view event name is used as second attribute information, and the obtained second attribute information is matched with the first attribute information and the mapping relation, so that the value of a custom field corresponding to the view event can be determined.
And 204, sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
This step may specifically refer to step 103, which is not described herein again.
Optionally, the method further comprises:
step 205, the log data is sent to the server in a compressed file form at a preset time interval.
In the embodiment of the present invention, log data obtained from the obtained buried point data may be locally compressed at the client and then uploaded to the server, and the reporting mode may be: reporting every preset interval, for example, every 30 seconds after the application is started, or every 15 seconds. If the user is in the non-network condition, the embedded point data collected in the non-network condition can be stored at the client side, and is reported when the network is normal next time. The preset time interval is set to avoid data loss caused by overlarge data volume reported once or exceeding the limit.
Further, the reporting mode may also be that the user reports the exposed content when leaving the page, or reports the cached log data when the log data cached in the client reaches a preset threshold, and clears the client cache to wait for saving new log data.
And step 206, uploading the log data to a server in a compressed file form when the number of the log data is greater than or equal to a preset threshold value.
In the embodiment of the present invention, the reporting mode may also be: when the number of the log data stored in the client is larger than or equal to a preset threshold, compressing the log data and reporting the compressed log data, for example; the preset threshold value is set to be 1000, when the number of the log data locally stored by the client reaches 1000, the 1000 log data are compressed and reported to the server, and the problem that the data volume of the log data locally stored by the client is too large, the resources of the client are occupied, and the execution of other processes of the client is influenced is avoided. Further, the log data reported to the server may be reported in a list form.
Optionally, the method further comprises:
and step 207, when the application program is updated, the mapping relation file is obtained again.
In the embodiment of the present invention, when an application program is updated, if a page is changed by adding or deleting, the corresponding relationship between the page and the view is also changed, at this time, the original mapping relationship file cannot support the updated application program, and therefore, the mapping relationship in the mapping relationship file needs to be updated synchronously, and when the application program is restarted, the updated mapping relationship file is obtained to replace the original mapping relationship file, and the updated mapping relationship file is stored locally.
Optionally, the method further comprises:
step 208, the log data further includes: operating system type, application version, device information.
In the embodiment of the present invention, the log data records specific attribute data of a view event triggered by a user operation behavior and index data common to different view events, for example, for a login page, the specific attribute data includes: user identification, equipment identification, browsing time, browsing event, page identification and the like, and the general index data is as follows: and if the information such as the application version, the operating system version, the equipment model, the network environment, the equipment manufacturer, the height and the width of the screen and the like is specific to other pages such as a payment page, the general index data is the same as that of the login page. The attribute index data specific to each event can be acquired in a point burying mode and stored in log data to serve as the basis of data analysis.
Referring to fig. 3, fig. 3 is an architecture diagram of a point burying scheme, which includes a server, a client and a data warehouse, where logParams is a parameter dedicated to a point burying and returned by the server from a request, and PassValue is used for following a jump protocol and is used for a server log; interceptors, AOP (Aspect organized Programming), are used for different levels of buried point applications, respectively. For an android client, a buried point code can be inserted through AspectJ (a frame facing to a tangent plane), a buried point method file and a mapping management file are uploaded through an uploading plug-in, for an IOS client, the buried point code can be inserted through ASPECTS, the buried point method file is composed of Apath (path), the dynamic buried point process further comprises version management and updating, a buried point data warehouse is used for solving the buried point requirement of the client, and after the client acquires the buried point data, the buried point data is uploaded to a server.
In summary, in the embodiment of the present invention, a mapping relationship between a value of a page attribute field, a value of a view event field, and a value of a custom field is established, a page, a view, and a custom field are associated, a client may obtain a mapping relationship file and store the mapping relationship file locally, when a user behavior triggers a buried point function to obtain the value of a current page attribute field and the value of a view attribute field, the obtained value is matched with the value stored in the mapping relationship file, after the matching is successful, the value of the custom field in the mapping relationship may also be added to log data recorded by the view event triggered by the user behavior at this time, the custom field is used to describe service data, and the service data is mapped with the page and the view, so that information of the obtained buried point data is more comprehensive, thereby satisfying the requirement of data analysis, and at the same time, when the log data is uploaded to a service end, only the data matched with the mapping relationship is uploaded, thereby saving storage resources of the service end.
Fig. 4 is a block diagram of a client behavior data acquisition apparatus according to an embodiment of the present invention, and as shown in fig. 4, the apparatus 30 includes;
a mapping file obtaining module 301, configured to obtain a mapping relationship file, where the mapping relationship file includes: the relation among the value of a page attribute field, the value of a view event field and the value of a custom field, wherein the page attribute field is a field which uniquely represents the page, the view event field is a field which uniquely represents the view event, and the custom field is a field related to the view event;
a behavior information obtaining module 302, configured to, in response to an operation behavior of a user, obtain, through a buried point process in a client, first attribute information of a page of the client and second attribute information of a view event corresponding to the page;
a matching module 303, configured to sort according to the mapping relationship, match the value of the first attribute information with the value of the page attribute field, match the value of the second attribute information with the value of the view event field, store the matched value of the page attribute field, the value of the view event field, and the value of the custom field as a piece of log data when matching is successful, and send the log data to a server.
Optionally, the behavior information obtaining module 302 includes:
the page information acquisition sub-module is used for responding to the operation on the page, acquiring the life cycle information of the page through a preset page monitoring function, and taking the life cycle information as first attribute information, wherein the first attribute information comprises: the method comprises the steps of (1) page creation time, page destruction time and page class names;
a view information obtaining sub-module, configured to, in response to a view operation, obtain second attribute information of the view event through a preset event listening function, where the second attribute information includes: view event tag, view event name.
Optionally, the apparatus further comprises:
the log file uploading module is used for uploading the log data to the server in a compressed file form at preset time intervals; or when the number of the log data is larger than or equal to a preset threshold value, uploading the log data to a server in a compressed file form.
Optionally, the apparatus further comprises:
and the mapping relation file analysis module is used for analyzing the preset format of the mapping relation file and storing the analyzed file locally.
Optionally, the mapping file obtaining module 301 is further configured to obtain the mapping relationship file again when the application program is updated.
Optionally, the log data further includes: operating system type, time of occurrence, application version, device information.
To sum up, the embodiment of the invention discloses a client behavior data acquisition device, which associates a page, a view and a self-defined field by establishing a mapping relationship between a value of the page attribute field, a value of the view event field and a value of the self-defined field, wherein the client can obtain a mapping relationship file and store the mapping relationship file locally, when a user behavior triggering buried point function obtains the current value of the page attribute field and the value of the view attribute field, the obtained value is matched with the value stored in the mapping relationship file, after the matching is successful, the value of the self-defined field in the mapping relationship can also be added in log data recorded by the view event triggered by the user behavior, the self-defined field is used for describing service data, and the service data and the page and the view are mapped, so that the obtained information of the buried point data is more comprehensive to meet the requirement of data analysis, and meanwhile, when the log data is uploaded to a server, only the data matched with the mapping relationship is uploaded, and the storage resource of the server is saved.
Fig. 5 is a block diagram illustrating an electronic device 600 according to an example embodiment. For example, the electronic device 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 5, electronic device 600 may include one or more of the following components: processing component 602, memory 604, power component 606, multimedia component 608, audio component 610, input/output (I/O) interface 612, sensor component 614, and communication component 616.
The processing component 602 generally controls overall operation of the electronic 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 a portion 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 used to store various types of data to support operations at the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 600, contact data, phonebook data, messages, pictures, multimedia, and so forth. The memory 604 may be implemented by any type or combination of volatile or non-volatile 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 disks.
The multimedia component 608 includes a screen that provides an output interface between the electronic device 600 and a user. 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 an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense demarcations of touch or slide actions, but also detect duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the electronic device 600 is in an operation mode, such as a photographing mode or a multimedia mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 610 is used to output and/or input audio signals. For example, the audio component 610 may include a Microphone (MIC) for receiving external audio signals when the electronic device 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be 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 keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor component 614 includes one or more sensors for providing status assessment of various aspects of the electronic device 600. For example, the sensor component 614 may detect an open/closed state of the electronic device 600, the relative positioning of components, such as a display and keypad of the electronic device 600, the sensor component 614 may also detect a change in position of the electronic device 600 or a component of the electronic device 600, the presence or absence of user contact with the electronic device 600, orientation or acceleration/deceleration of the electronic device 600, and a change in temperature of the electronic device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object 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 gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 616 is operable to facilitate wired or wireless communication between the electronic device 600 and other devices. The electronic device 600 may access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an 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 electronic device 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, micro-controllers, microprocessors or other electronic components for implementing a client behavior data collection method provided by an embodiment of the present application.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 604 comprising instructions, executable by the processor 620 of the electronic device 600 to perform the above-described method is also provided. For example, the non-transitory storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Fig. 6 is a block diagram of an electronic device 700 shown in accordance with an example embodiment. For example, the electronic device 700 may be provided as a server. Referring to fig. 6, electronic device 700 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, that are 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. In addition, the processing component 722 is configured to execute instructions to perform a client behavior data collection method provided by the embodiments of the present application.
The electronic device 700 may also include a power component 726 that is configured to perform power management of the electronic device 700, a wired or wireless network interface 750 that is configured to connect the electronic device 700 to a network, and an input output (I/O) interface 758. The electronic device 700 may operate based on an operating system, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM or the like, stored in memory 732.
The embodiment of the present application further provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the method for handling the attack behavior is implemented.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (9)
1. A client behavior data acquisition method is applied to a client, and is characterized by comprising the following steps:
acquiring a mapping relation file, wherein the mapping relation file comprises: the relation among the value of a page attribute field, the value of a view event field and the value of a custom field, wherein the page attribute field is a field which uniquely represents the page, the view event field is a field which uniquely represents the view event, and the custom field is a field related to the view event;
responding to an operation behavior of a user, and acquiring first attribute information of a page of a client and second attribute information of a view event corresponding to the page through a buried point process in the client;
and sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
2. The method according to claim 1, wherein the obtaining first attribute information of a page of the client and second attribute information of a view event corresponding to the page comprises:
responding to the operation on the page, acquiring the life cycle information of the page through a preset page monitoring function, and taking the life cycle information as first attribute information, wherein the first attribute information comprises: the method comprises the steps of (1) page creation time, page destruction time and page class names;
responding to the operation of the view, and acquiring second attribute information of the view event through a preset event listening function, wherein the second attribute information comprises: view event label, view event name.
3. The method of claim 1, further comprising:
uploading the log data to a server in a compressed file form at preset time intervals;
or when the number of the log data is larger than or equal to a preset threshold value, uploading the log data to a server in a compressed file form.
4. The method according to claim 1, wherein after the obtaining of the mapping relationship file, the method further comprises:
and analyzing the preset format of the mapping relation file, and storing the analyzed file in the local.
5. The method of claim 1, further comprising:
and when the application program is updated, the mapping relation file is obtained again.
6. The method of claim 1, wherein the log data further comprises: operating system type, application version, device information.
7. A client behavior data collection device, the device comprising:
a mapping file obtaining module, configured to obtain a mapping relationship file, where the mapping relationship file includes: the relation among the value of a page attribute field, the value of a view event field and the value of a custom field, wherein the page attribute field is a field which uniquely represents the page, the view event field is a field which uniquely represents the view event, and the custom field is a field related to the view event;
the behavior information acquisition module is used for responding to the operation behavior of a user and acquiring first attribute information of a page of a client and second attribute information of a view event corresponding to the page through a buried point process in the client;
and the matching module is used for sorting according to the mapping relation, matching the value of the first attribute information with the value of the page attribute field, matching the value of the second attribute information with the value of the view event field, storing the matched value of the page attribute field, the value of the view event field and the value of the custom field as a piece of log data under the condition of successful matching, and sending the log data to a server.
8. 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 method of any one of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210888364.2A CN115509872A (en) | 2022-07-26 | 2022-07-26 | Client behavior data acquisition method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210888364.2A CN115509872A (en) | 2022-07-26 | 2022-07-26 | Client behavior data acquisition method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115509872A true CN115509872A (en) | 2022-12-23 |
Family
ID=84501270
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210888364.2A Pending CN115509872A (en) | 2022-07-26 | 2022-07-26 | Client behavior data acquisition method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115509872A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016629A (en) * | 2023-03-22 | 2023-04-25 | 创云融达信息技术(天津)股份有限公司 | Front-end page event extraction method |
-
2022
- 2022-07-26 CN CN202210888364.2A patent/CN115509872A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116016629A (en) * | 2023-03-22 | 2023-04-25 | 创云融达信息技术(天津)股份有限公司 | Front-end page event extraction method |
| CN116016629B (en) * | 2023-03-22 | 2023-06-27 | 创云融达信息技术(天津)股份有限公司 | Front-end page event extraction method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106021072A (en) | Information display method and device | |
| CN115509872A (en) | Client behavior data acquisition method and device | |
| CN116069612A (en) | Abnormality positioning method and device and electronic equipment | |
| CN112486770A (en) | Client dotting reporting method and device, electronic equipment and storage medium | |
| CN110968492B (en) | Information processing method and device and storage medium | |
| CN112256563A (en) | Android application stability testing method and device, electronic equipment and storage medium | |
| CN114189719B (en) | Video information extraction method and device, electronic equipment and storage medium | |
| CN114428737A (en) | Communication method, device, equipment and storage medium based on micro service system | |
| CN112333233B (en) | Event information reporting method and device, electronic equipment and storage medium | |
| CN112507261A (en) | First screen time calculation method and device | |
| CN113760946A (en) | Pre-verification processing method, device, equipment and medium applied to data source migration | |
| CN113407879A (en) | Data reporting method, device and readable medium | |
| CN111782508A (en) | Automatic test method, device, electronic equipment and storage medium | |
| CN111143184B (en) | Data processing method, device and system | |
| CN113986648A (en) | Method and device for executing application program, electronic equipment and storage medium | |
| CN111343268B (en) | Method and device for downloading multimedia resources, server and electronic equipment | |
| CN112199250B (en) | Picture monitoring method and device, electronic equipment and storage medium | |
| CN109947640B (en) | Regression test-based core function coverage statistical method and device | |
| CN113191792B (en) | Task processing method, device, electronic equipment, storage medium and program product | |
| CN111538486B (en) | Layout file nesting layer number screening method and device and electronic equipment | |
| CN114710401B (en) | Abnormality positioning method and device | |
| CN113420205B (en) | Method and device for determining shared source account, terminal equipment and server | |
| CN112000841B (en) | Electronic tag data processing method and device, electronic equipment and storage medium | |
| CN114531493B (en) | Request processing method and device, electronic equipment and storage medium | |
| CN108197001B (en) | Data statistical method and device and electronic equipment |
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 |