CN117555764A - Data acquisition method, device, equipment and storage medium - Google Patents

Abstract

The application provides a data acquisition method, a device, equipment and a storage medium, and relates to the field of data acquisition, wherein the method is applied to the data acquisition device; the data acquisition device comprises a target application program APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event occurrence time, event occurrence place, user identification of occurrence event, and manner of occurrence event; the method comprises the following steps: acquiring a first operation event of a user on an interface of a target product; and under the condition that the first operation event is an event type in the data of the preset type, acquiring the data of the preset type through one or more embedded point codes. The method is suitable for the data acquisition process and is used for solving the problem of troublesome data use.

Description

Data acquisition method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of data acquisition, and in particular, to a data acquisition method, apparatus, device, and storage medium.

Background

The use of data generally includes: data collection, data storage, data management, and data application. The data acquisition is important, and only if the data information is timely, efficiently and accurately acquired, the service condition of a website or software can be correctly known, and a reliable decision can be made.

Data acquisition may typically be accomplished using embedded point codes. Embedded point code is a piece of code that is added in a target page or a target Application (APP).

However, for products of different business lines, it is very difficult for a data analyst to obtain data, only a single product can be queried, and using the data is cumbersome.

Disclosure of Invention

Based on the technical problems, the application provides a data acquisition method, a device, equipment and a storage medium, which can provide a unified specification of the type of the data acquired by the embedded point codes, and is convenient for inquiry and use.

In a first aspect, the present application provides a data acquisition method, the method being applied to a data acquisition device; the data acquisition device comprises a target application program APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event occurrence time, event occurrence place, user identification of occurrence event, and manner of occurrence event; the method comprises the following steps: acquiring a first operation event of a user on an interface of a target product; and under the condition that the first operation event is an event type in the data of the preset type, acquiring the data of the preset type through one or more embedded point codes.

Optionally, the data of the preset category further includes: and customizing the data.

Optionally, the event type comprises an automation event; the target APP comprises a Software Development Kit (SDK); the buried point code for collecting automation events is encapsulated in the SDK.

Optionally, the target APP includes a software development kit SDK; the field in the embedded point code for collecting the data of the preset type is packaged in the SDK.

Optionally, the data of the preset category further includes: user attributes; the user attributes are used to record the user status when an event occurs, and the historical time record of the same type of event.

Optionally, the method further comprises: under the condition that the collected data of the preset type reach the preset condition, generating a buried point log according to the collected data of the preset type and the preset format; and sending the buried point log to the data management device.

Optionally, the preset conditions include: the time length between the current time and the event occurrence time in the data of the preset type reaches a preset time length threshold; and/or the number of the data acquired by the preset type reaches a preset number threshold.

It should be understood that products of different service lines are different in terms of naming of the products and data packets in the products, so that it is very difficult for a data analyst to acquire data of the products of different service lines, only a single product can be queried, and data usage is troublesome. According to the data acquisition method, the data acquisition device can comprise a target APP, the target APP comprises one or more embedded point codes, the embedded point codes are used for acquiring data of a preset type, and the data of the preset type can (at least) comprise: event type, event time of occurrence, event place of occurrence, user identification of occurrence of event, and manner of occurrence of event. That is, the data acquisition method provided by the application can acquire data according to the embedded point code designed by the embedded point code design specification, so that the inquiry and the use are convenient.

In a second aspect, the present application provides a data acquisition device comprising a target application APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event time of occurrence, event place of occurrence, user identification of occurrence of event, and manner of occurrence of event. The data acquisition device comprises: an acquisition module and a processing module.

The acquisition module is used for acquiring a first operation event of a user on an interface of a target product.

The processing module is used for acquiring the data of the preset type through one or more embedded point codes under the condition that the first operation event is the event type in the data of the preset type.

Optionally, the data of the preset category further includes: and customizing the data.

Optionally, the event type comprises an automation event; the target APP comprises a Software Development Kit (SDK); buried point code for collecting automation events is encapsulated in the SDK.

Optionally, the target APP includes a software development kit SDK; the field in the embedded point code for collecting the data of the preset type is packaged in the SDK.

Optionally, the data of the preset category further includes: user attributes; the user attributes are used to record the user status when an event occurs, and the historical time record of the same type of event.

Optionally, the processing module is further configured to generate a buried point log according to a preset format according to the collected data of the preset type when the collected data of the preset type reaches a preset condition; and sending the buried point log to the data management device.

Optionally, the preset conditions include: the time length between the current time and the event occurrence time in the data of the preset type reaches a preset time length threshold; and/or the number of the data acquired by the preset type reaches a preset number threshold.

In a third aspect, the present application provides an electronic device comprising a processor and a memory; the memory stores instructions executable by the processor; the processor is configured to execute the instructions to cause the electronic device to implement the method of the first aspect described above.

In a fourth aspect, the present application provides a computer program product for, when run in an electronic device, causing the electronic device to perform the steps of the related method of the first aspect described above, to implement the method of the first aspect described above.

In a fifth aspect, the present application provides a readable storage medium comprising: a software instruction; the software instructions, when executed in an electronic device, cause the electronic device to implement the method according to the first aspect described above.

The advantageous effects of the second aspect to the fifth aspect described above may be described with reference to the first aspect, and will not be repeated.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a data acquisition system according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application;

fig. 3 is a schematic flow chart of a data acquisition method according to an embodiment of the present application;

fig. 4 is another flow chart of the data acquisition method provided in the embodiment of the present application;

FIG. 5 is a schematic diagram of a buried point log according to an embodiment of the present disclosure;

fig. 6 is a schematic diagram of a data acquisition device according to an embodiment of the present application.

Detailed Description

Hereinafter, the terms "first," "second," and "third," etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", or "a third", etc., may explicitly or implicitly include one or more such feature.

The use of data generally includes: data collection, data storage, data management, and data application. The data acquisition is important, and only if the data information is timely, efficiently and accurately acquired, the service condition of a website or software can be correctly known, and a reliable decision can be made.

Data acquisition may typically be accomplished using embedded point codes. Embedded point code is a piece of code that is added in a target page or a target Application (APP).

However, for products of different business lines, it is very difficult for a data analyst to obtain data, only a single product can be queried, and using the data is cumbersome.

Based on this, the embodiment of the application provides a data acquisition method, a device, equipment and a storage medium, which can provide a unified specification of the type of the data acquired by the embedded point code, and is convenient for inquiry and use.

The following description is made with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a data acquisition system according to an embodiment of the present application. As shown in fig. 1, the data acquisition system includes: the data acquisition device 100 and the data management device 200. The data acquisition device 100 and the data management device 200 may be connected by a wired network or a wireless network.

The data acquisition device 100 may be an electronic device such as a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA), or the like, which is not limited in the embodiments of the present application.

The data acquisition device 100 may include a target APP including one or more embedded point codes, each of which is used to acquire a preset type of data. The data acquisition device 200 may be used to acquire a preset variety of data using one or more embedded point codes in the target APP. The specific process may be described with reference to the data acquisition method provided in the following embodiments, and will not be described herein.

In some embodiments, the data acquisition device 100 may also be used to send acquired data to the data management device 200.

For example, the data collection device 100 may generate a buried point log from the collected data and transmit the buried point log to the data management device 200.

As described above, the data collection device 100 and the data management device 200 may be connected to each other through a wired network or a wireless network. The wired or wireless network includes one or more media or devices capable of transmitting the buried point log from the data acquisition device 100 to the data management device 200.

In some embodiments, the wired or wireless network may include one or more communication media that enable the data acquisition device 100 to send the embedded point log directly to the data management device 200. In this embodiment, the data acquisition device 100 may modulate the embedded point log according to a communication standard (e.g., a wireless communication protocol) and transmit the modulated embedded point log to the data management device 200. The one or more communication media may include wireless and/or wired communication media, such as a Radio Frequency (RF) spectrum or one or more physical transmission lines.

Alternatively, the one or more communication media may form part of a packet-based network, which may be, for example, a local area network, a wide area network, or a global network (e.g., the Internet).

Optionally, the one or more communication media may also include a router, switch, base station, or other device that facilitates communication of the data acquisition device 100 to the data management device 200.

The data management apparatus 200 may be a computing device having a computing processing function, such as a server or a computer.

The server may be a single server, or may be a server cluster formed by a plurality of servers. In some implementations, the server cluster may also be a distributed cluster. Optionally, the server may also be implemented on a cloud platform, which may include, for example, a private cloud, public cloud, hybrid cloud, community cloud (community cloud), distributed cloud, inter-cloud (inter-cloud), multi-cloud (multi-cloud), and the like, or any combination thereof. The embodiments of the present application are not limited in this regard.

The main implementation body of the data acquisition method provided in the embodiments of the present application is the data acquisition device 100 described above. As described above, the data acquisition device 100 may be an electronic device such as a mobile phone, a tablet computer, and the like. Alternatively, the data acquisition device 100 may be a processor (e.g., a central processing unit (central processing unit, CPU)) in the aforementioned electronic apparatus; alternatively, the data acquisition device 100 may be an APP in the foregoing electronic apparatus; still alternatively, the data acquisition device 100 may be a functional module or the like for executing the data acquisition method in the aforementioned electronic apparatus. The embodiments of the present application are not limited in this regard.

For simplicity of description, the following description will collectively refer to the data acquisition device 100 as an electronic device.

Fig. 2 is a schematic diagram of the composition of an electronic device according to an embodiment of the present application. As shown in fig. 2, the electronic device may include: processor 10, memory 20, communication line 30, and communication interface 40, and input-output interface 50.

The processor 10, the memory 20, the communication interface 40, and the input/output interface 50 may be connected by a communication line 30.

The processor 10 is configured to execute instructions stored in the memory 20 to implement a data acquisition method provided in the following embodiments of the present application. The processor 10 may be a CPU, a general purpose processor Network Processor (NP), a digital signal processor (digital signal processing, DSP), a microprocessor, a microcontroller (micro control unit, MCU)/a single-chip microcomputer (single chipmicrocomputer)/a single-chip microcomputer, a programmable logic device (programmable logic device, PLD), or any combination thereof. The processor 10 may also be any other apparatus having a processing function, such as a circuit, a device, or a software module, which is not limited in this embodiment. In one example, processor 10 may include one or more CPUs, such as CPU0 and CPU1 in fig. 2. As an alternative implementation, the electronic device may include multiple processors, for example, and may include processor 60 (illustrated in phantom in fig. 2) in addition to processor 10.

Memory 20 for storing instructions. For example, the instructions may be a computer program. Alternatively, memory 20 may be a read-only memory (ROM) or other type of static storage device that may store static information and/or instructions, an access memory (random access memory, RAM) or other type of dynamic storage device that may store information and/or instructions, an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or other optical storage, optical storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media, or other magnetic storage devices, etc., as examples of which are not limited in this application.

It should be noted that, the memory 20 may exist separately from the processor 10 or may be integrated with the processor 10. The memory 20 may be located inside the electronic device or outside the electronic device, which is not limited in this embodiment of the present application.

A communication line 30 for communicating information between the components comprised by the electronic device.

A communication interface 40 for communicating with other devices (e.g., the data acquisition apparatus 100 described above) or other communication networks. The other communication network may be an ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), etc. The communication interface 40 may be a module, a circuit, a transceiver, or any device capable of enabling communication.

And an input-output interface 50 for implementing man-machine interaction between the user and the electronic device. Such as enabling action interactions or information interactions between a user and an electronic device.

The input/output interface 50 may be a mouse, a keyboard, a display screen, or a touch display screen, for example. The action interaction or information interaction between the user and the electronic equipment can be realized through a mouse, a keyboard, a display screen, a touch display screen or the like.

It should be noted that the structure shown in fig. 2 does not constitute a limitation of the electronic device, and the electronic device may include more or less components than those shown in fig. 2 (for example, only the processor 10 and the memory 20), or a combination of some components, or a different arrangement of components.

The following describes a data acquisition method provided in the embodiments of the present application.

Fig. 3 is a flow chart of a data collection method according to an embodiment of the present application. As shown in fig. 3, the method includes S101 to S102.

S101, the electronic equipment acquires a first operation event of a user on an interface of a target product.

Wherein the electronic device (data acquisition apparatus 100) comprises a target APP. One or more embedded point codes may be included in the target APP. The embedded point codes are all used for collecting data of preset types. The preset kinds of data may include the following: event type, event time of occurrence, event place of occurrence, user identification of occurrence of event, and manner of occurrence of event.

It will be appreciated that an event is one way to define a buried point location, and that an event can uniquely locate a buried point location. In order to more conveniently and efficiently use the data, the service characteristics are combined at the same time, so that the classification of the events is derived. For example, the behavior of a click class may be categorized as one class of events, and the behavior of an exposure class may be categorized as another class of events.

The event type is used to indicate the kind of user behavior that occurs, such as the behavior of the click class or the behavior of the exposure class described above.

The time of occurrence of the event is used to indicate the time of occurrence of the user behavior, or may be understood as the time of generating the buried point log, which may be specifically described in the following embodiments, and will not be described herein.

In some possible embodiments, event types may include automation events and custom events. The target APP can comprise a software development kit (software development kit, SDK), the embedded point code for collecting the automation event can be packaged in the SDK, and the embedded point code can be automatically reported after being accessed into the SDK without manual definition. Custom events can be custom written by an administrator into the point code and written into the target APP.

For example, automation events may include common event types such as login (launch), exit (end), install (install), and crash (crash). Custom events may include types of events such as begin browse (pvbegin), end browse (pvend), click, expose (show), and task (task).

The event occurrence location is used to indicate a location where a user action occurs, for example, when a user action of a preset event type occurs, the electronic device may acquire a current Internet Protocol (IP) address and determine the event occurrence location according to the IP address. The process of determining the actual location according to the IP address may be described in the related art, and will not be described herein.

The identity of the user who has occurred the event is used to indicate the identity of the user who has occurred the event-type user behavior. For example, taking an electronic device as a mobile phone, the user identifier may be a mobile phone number or other code for indicating the identity of the user, etc. The embodiment of the application does not limit the specific types of the user identification.

The manner in which the event occurs is used to indicate the manner in which the user's behavior occurred. For example, the manner may include the model of the electronic device used by the user, the product version, the network type, the current AB experiment hit, and so forth. The AB experiment hit can be described in the related art, and will not be described here.

In some possible embodiments, the preset variety of data may specifically include event attributes and user attributes. The event parameters may specifically include the event type, the event occurrence time, the event occurrence place, the user identifier of the occurrence event, and the manner in which the event occurs. The user parameters may be used to record the user state at which an event (or user behavior) occurs, as well as a historical time of day record of the same type of event occurring.

Alternatively, event attributes may specifically include public and private parameters. The common parameters may specifically include the event type, the event occurrence time, the event occurrence place, the user identifier of the occurrence event, and the manner in which the event occurs. The private parameters may include custom data.

Illustratively, the private parameters may be specifically as shown in table 1 below:

TABLE 1

As shown in table 1, taking two events, i.e., a login event and an exit event as examples, the private parameters of the login event may specifically include a start type, a start source, and a session type. The private parameters of the exit event may specifically include the exit type, APP residence time, etc.

In some possible embodiments, as described above, the target APP may include a software development kit SDK therein. In this case, the fields for collecting data of a predetermined category (i.e., common parameters) in the above-mentioned buried code may be encapsulated in the SDK.

S102, under the condition that the first operation time is the event type in the data of the preset type, acquiring the data of the preset type through one or more embedded point codes.

It should be understood that products of different service lines are different in terms of naming of the products and data packets in the products, so that it is very difficult for a data analyst to acquire data of the products of different service lines, only a single product can be queried, and data usage is troublesome. In the data acquisition method provided by the embodiment of the application, the electronic device may include a target APP, the target APP includes one or more embedded point codes, the embedded point codes are all used for acquiring data of a preset type, and the data of the preset type may (at least) include: event type, event time of occurrence, event place of occurrence, user identification of occurrence of event, and manner of occurrence of event. That is, the data acquisition method provided by the embodiment of the application can acquire data according to the embedded point code designed by the embedded point code design specification, so that the inquiry and the use are convenient.

In some possible embodiments, after the data of the preset kind is collected through one or more embedded point codes, the electronic device may further generate an embedded point log according to the collected data of the preset kind, and send the embedded point log to the data management device. Fig. 4 is a schematic flow chart of another data collection method according to an embodiment of the present application. As shown in fig. 4, after S102 described above, the method may further include S201 to S202.

S201, under the condition that the collected data of the preset type reach the preset condition, the electronic equipment generates a buried point log according to the collected data of the preset type and the preset format.

In a possible implementation manner, the preset condition may specifically include: the duration between the current time and the occurrence time of the event in the data of the preset category reaches a preset duration threshold.

The preset duration threshold may be preset in the electronic device or the target APP by a manager. For example, the preset duration threshold may be 5 seconds or 5 minutes, etc. The specific numerical value of the preset duration threshold is not limited in the embodiment of the application.

In another possible implementation manner, the preset condition may specifically include: the number of the data acquired by the preset type reaches a preset number threshold.

The preset number threshold value can be preset in the electronic equipment or the target APP by a manager. For example, the preset number of pieces threshold may be 5 pieces or 10 pieces, or the like. The specific numerical value of the preset number threshold is not limited in the embodiment of the application.

In another possible implementation manner, the preset condition may specifically include: the time length between the current time and the event occurrence time in the data of the preset type reaches a preset time length threshold value, and the number of the data of the preset type acquired reaches a preset number threshold value, namely the two conditions are included simultaneously.

Optionally, before generating the buried point log, the electronic device may further restrict naming of the event attribute and the user attribute according to a preset naming rule.

Optionally, the electronic device may also constrain the entered parameter values according to a preset numerical specification prior to generating the buried point log.

Exemplary, fig. 5 is a schematic diagram of a buried point log provided in an embodiment of the present application. As shown in fig. 5, the fields recorded in the embedded point log may mainly include several fields, such as action, af_id, app_name, app_vers_ion, app id, attr_ad group, attr_ campaign, attr _create, attr_network, attrbut_id, attrbut_type, battery, and burst_id.

S202, the electronic equipment sends the buried point log to the data management device.

For example, the electronic device may transmit the embedded point log according to the agreed log channel item data management device.

The specific process of the electronic device sending the buried point log to the data acquisition device in S202 may be described with reference to fig. 1, which is not described herein.

Based on the understanding of the above embodiments, the process from designing to reporting an event may specifically include the following processes:

1. demand scenario:

at present, a content type APP needs to be dotted, and statistical analysis is performed by using the dotted buried point after online.

2. And (3) carrying out event design:

and designing the demand name, the trigger time, the reporting time and the like of the event.

By way of example, the details of the event design may be as shown in Table 2 below:

TABLE 2

As shown in table 2, taking the top page exposure as an example, the trigger time of the top page exposure may be reporting the top page, the reporting timer may be reporting the top page after entering the page, and the requirement is a conventional buried point, which may be used to record the top page exposure. Taking photo import of the top page as an example, the triggering time of photo import of the top page can be reported by clicking a photo import button, and the reporting time can be reported after clicking the button, and the requirement is used for recording the function permeability. Taking template filling of the top page as an example, the triggering time of template filling of the top page can be reported by clicking a template selection button, and the reporting time can be reported after clicking the button, and the requirement is used for recording the function permeability.

3. Development and dotting:

according to the proposed buried point requirement, a developer writes buried point codes to the buried point SDK.

4. After successful dotting:

the electronic equipment collects data of a preset type and reports the data to a log channel agreed with a data management device (or a data management system) in the form of a buried point log.

The data management device (or the data management system) can acquire the buried point log from the log channel, then strip the event according to the requirement of cleaning some data and display the event in the management system so as to achieve the purpose of automatically managing the event to the management system after reporting the event.

In some possible embodiments, in the event design, in order to enable the business personnel to efficiently define the buried points and align the requirements with the developer and the tester, the requirement development deviation caused by misalignment is reduced, and the situation of post reworking is caused, so that a explicit alignment manner between the requirement provider and the developer and between the requirement provider and the tester is required. Based on the method, the embodiment of the application can provide a functional interface capable of simulating and creating the product, product personnel can utilize the product function to construct a frame interface and interaction of the product in advance before the APP is not finished, then the simulation interface can be utilized to define the desired point location by operation, and other participants can enter the interface to know the desired buried point.

Illustratively, the functions of the functional interface that may simulate creating a product may be as shown in Table 3 below:

TABLE 3 Table 3

As shown in Table 3, the functions of the functional interface capable of simulating the creation of the product mainly comprise three parts, namely product creation, point location identification and requirement viewing.

The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of a method. To achieve the above functions, it includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. The technical aim may be to use different methods to implement the described functions for each particular application, but such implementation should not be considered beyond the scope of the present application.

In an exemplary embodiment, the embodiment of the present application further provides a data acquisition device, where the data acquisition device includes a target application APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event time of occurrence, event place of occurrence, user identification of occurrence of event, and manner of occurrence of event. Fig. 6 is a schematic diagram of a data acquisition device according to an embodiment of the present application. As shown in fig. 6, the data acquisition device may include: an acquisition module 601 and a processing module 602.

The acquiring module 601 is configured to acquire a first operation event of a user on an interface of a target product.

The processing module 602 is configured to collect, in case the first operation event is an event type in the data of the preset type, the data of the preset type through one or more embedded point codes.

In some possible embodiments, the preset kind of data further includes: and customizing the data.

In other possible embodiments, the event type includes an automated event; the target APP comprises a Software Development Kit (SDK); buried point code for collecting automation events is encapsulated in the SDK.

In still other possible embodiments, the target APP includes a software development kit SDK therein; the field in the embedded point code for collecting the data of the preset type is packaged in the SDK.

In still other possible embodiments, the preset kind of data further includes: user attributes; the user attributes are used to record the user status when an event occurs, and the historical time record of the same type of event.

In still other possible embodiments, the processing module 602 is further configured to generate, according to the collected data of the preset type and the preset format, a buried point log if the collected data of the preset type reaches the preset condition; and sending the buried point log to the data management device.

In still other possible embodiments, the preset condition includes: the time length between the current time and the event occurrence time in the data of the preset type reaches a preset time length threshold; and/or the number of the data acquired by the preset type reaches a preset number threshold.

It should be noted that the division of the modules in fig. 6 is schematic, and is merely a logic function division, and other division manners may be implemented in practice. For example, two or more functions may also be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional units.

In an exemplary embodiment, a readable storage medium is also provided, comprising software instructions that, when run on an electronic device, cause the electronic device to perform any of the methods provided by the above embodiments.

In an exemplary embodiment, the present application also provides a computer program product comprising computer-executable instructions, which, when run on an electronic device, cause the electronic device to perform any of the methods provided by the above embodiments.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer-executable instructions. When the computer-executable instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are fully or partially produced. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer-executable instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, from one website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Although the present application has been described herein in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed application, from a review of the figures, the disclosure, and the appended claims. In the claims, the word "Comprising" does not exclude other elements or steps, and the "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Although the present application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the present application. It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A data acquisition method, characterized in that the method is applied to a data acquisition device; the data acquisition device comprises a target application program APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event occurrence time, event occurrence place, user identification of occurrence event, and manner of occurrence event; the method comprises the following steps:

acquiring a first operation event of a user on an interface of the target product;

and under the condition that the first operation event is the event type in the data of the preset category, acquiring the data of the preset category through the one or more embedded point codes.

2. The method of claim 1, wherein the predetermined category of data further comprises: and customizing the data.

3. The method of claim 1, wherein the event type comprises an automated event; the target APP comprises a Software Development Kit (SDK); the embedded point code for collecting the automation event is encapsulated in the SDK.

4. The method of claim 1, wherein the target APP includes a software development kit SDK therein; and a field for acquiring the data of the preset type in the embedded point code is encapsulated in the SDK.

5. The method of claim 1, wherein the predetermined category of data further comprises: user attributes; the user attributes are used for recording the user state when the event occurs and the historical time record of the event of the same type.

6. The method according to any one of claims 1-4, further comprising:

under the condition that the collected data of the preset type reaches a preset condition, generating a buried point log according to a preset format according to the collected data of the preset type;

and sending the buried point log to a data management device.

7. The method of claim 6, wherein the preset conditions include:

the time length between the current time and the event occurrence time in the preset type of data reaches a preset time length threshold;

and/or the number of the groups of groups,

the number of the data acquired by the preset type reaches a preset number threshold.

8. A data acquisition device, which is characterized by comprising a target application program APP; the target APP comprises one or more embedded point codes; the embedded point codes are all used for collecting data of preset types; the preset kinds of data include: event type, event occurrence time, event occurrence place, user identification of occurrence event, and manner of occurrence event; the data acquisition device comprises:

the acquisition module is used for acquiring a first operation event of a user on the interface of the target product;

the acquisition module is used for acquiring the data of the preset type through the one or more embedded point codes under the condition that the first operation event is the event type in the data of the preset type.

9. An electronic device, the electronic device comprising: a processor and a memory;

the memory stores instructions executable by the processor;

the processor is configured to, when executing the instructions, cause the electronic device to implement the method of any one of claims 1-7.

10. A readable storage medium, the readable storage medium comprising: a software instruction;

when the software instructions are run in an electronic device, the electronic device is caused to implement the method of any one of claims 1-7.