Method, device and equipment for burying point processing and storage medium

Abstract

The embodiment of the invention relates to a point burying processing method and device, equipment and a storage medium. The method provided by the invention comprises the following steps: in response to detection of change of burying point configuration information for a target application program, determining change content of the burying point configuration information; and utilizing the burying point component to update the burying point event of the target application program based on an updating strategy related to the change content in the running process of the target application program. In this way, the point burying event can be automatically updated when the configuration information of the target application program changes, manual intervention is not needed in the process, and timeliness and accuracy of updating of the point burying event are ensured.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein generally relate to the field of computer technology, and more specifically, to a method, apparatus, device, and storage medium for embedding data. Background Technology

[0002] Event tracking is a data collection method that works by embedding program code at the operational nodes where data needs to be collected. This code captures, processes, and sends user behavior or event data at those nodes. This data is then transmitted to the backend for analysis and processing. In this way, businesses can obtain detailed information about user behavior, such as clicks, browsing time, and purchase conversion rates. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for event tracking is provided, comprising: in response to detecting a change in event tracking configuration information for a target application, determining the content of the change in the event tracking configuration information; and using an event tracking component, updating the event tracking events of the target application during the operation of the target application based on an update strategy related to the content of the change.

[0004] In a second aspect of this disclosure, an apparatus for event tracking is provided, comprising: a change content determination module configured to determine the change content of the event tracking configuration information in response to detecting a change in event tracking configuration information for a target application; and an event tracking update module configured to update the event tracking of the target application during the operation of the target application using event tracking components, based on an update strategy related to the change content.

[0005] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.

[0006] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to implement the method of the first aspect.

[0007] In a fifth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions that, when executed by a processor, implement the method according to a first aspect of this disclosure.

[0008] It should be understood that the content described in this content section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 A schematic diagram of an example environment according to an embodiment of the present disclosure is shown;

[0011] Figure 2 A flowchart illustrating an example process of a method for embedding data according to some embodiments of the present disclosure is shown;

[0012] Figure 3 An example flowchart of updating event tracking points according to some embodiments of this disclosure is shown;

[0013] Figure 4 A schematic structural block diagram of an apparatus for embedding data processing according to some embodiments of the present disclosure is shown; and

[0014] Figure 5 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown. Detailed Implementation

[0015] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0016] It should be noted that the headings of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and embodiments of any type may be included under any section / subsection. Furthermore, embodiments described in any section / subsection may be combined in any way with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0017] In the description of embodiments of the disclosure, the term "comprising" and similar terms thereof are understood to encompass open-ended inclusion, i.e., "comprising but not limited to". The term "based on" is understood to mean "based at least in part on". The term "one embodiment" or "the embodiment" is understood to mean "at least one embodiment". The term "some embodiments" is understood to mean "at least some embodiments". The following can also include other explicit and implicit definitions. The terms "first", "second", etc. can refer to different or same objects. The following can also include other explicit and implicit definitions.

[0018] In some embodiments of the disclosure, data of users, acquisition and / or use of data, etc. can be involved. These aspects comply with corresponding laws and regulations and relevant provisions. In some embodiments of the disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user is aware of and confirms. Accordingly, when implementing various embodiments of the disclosure, the type of data or information that can be involved, the scope of use, the scenario of use, etc. should be notified to the user and authorized by the user in a proper manner according to relevant laws and regulations. The specific notification and / or authorization manner can vary according to the actual situation and application scenario, and the scope of the disclosure is not limited in this respect.

[0019] In the specification and embodiments of the disclosure, if personal information processing is involved, it will be processed on the premise of legality (for example, obtaining the consent of the subject of personal information, or being necessary for the performance of a contract, etc.), and only within the prescribed or agreed range. The user refuses to process personal information other than the necessary information required for the basic function, which does not affect the user's use of the basic function.

[0020] As briefly described above, based on the point-in-time technology, the behavior or event data of the user on the corresponding application program can be captured, processed and sent. However, in the traditional point-in-time scheme, the point-in-time event is often realized by hard coding, which requires the developer to manually add point-in-time logic in the code. However, this method not only lacks flexibility, but also any change needs to be re-deployed to take effect, which undoubtedly increases the difficulty and complexity of maintenance.

[0021] Therefore, some embodiments of the disclosure provide a scheme for point-in-time processing. According to the scheme, first, in response to detecting that the point-in-time configuration information for the target application program changes, the change content of the point-in-time configuration information is determined; then, using the point-in-time component, during the running process of the target application program, the point-in-time event of the target application program is updated based on the update strategy related to the change content.

[0022] The solution of the present disclosure can automatically update the event of the embedded point based on the embedded point component when the configuration information of the target application program changes, which does not need manual code editing, ensuring the flexibility and efficiency of the update of the event of the embedded point. In addition, since the target program can always remain in a running state during the update of the event of the embedded point, the efficiency of the update of the event of the embedded point is greatly improved, and the difficulty and complexity of maintenance are reduced.

[0023] Various example implementations of the solution will be described in detail below in conjunction with the accompanying drawings.

[0024] Figure 1 A schematic diagram of an example environment 100 according to an embodiment of the present disclosure is shown. Referring to Figure 1 , the example environment 100 can include a terminal device 110, a terminal device 160, and an electronic device 120.

[0025] In the example environment 100, the terminal device 110 has installed therein an application 130 for interacting with the electronic device 120. An administrator 140 can interact with the application 130 via the terminal device 110 and / or its attached devices. The terminal device 160 has installed therein a target application program 170, and the administrator 140 can add, modify, or delete the event of the embedded point for the target application program 170 by means of the electronic device 120.

[0026] As an example, the administrator 140 can provide an access request for the embedded point configuration information related to the target application program 170 to the application 130 to edit the embedded point configuration information. After completing the editing of the embedded point configuration information, the administrator 140 can save the latest embedded point configuration information. At this time, the electronic device 120 can detect that the embedded point configuration information has changed, and based on the change content of the embedded point configuration information, use the embedded point component to update the event of the embedded point of the target application program 170 based on the update strategy related to the change content during the running of the target application program 170.

[0027] In addition, the terminal device 110 can present an interface 150 of the application 130. A configuration page of the embedded point configuration information can be presented in the interface 150.

[0028] In some embodiments, terminal device 110 (or terminal device 160) may be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, terminal device 110 (or terminal device 160) may also support any type of user-facing interface (such as "wearable" circuitry).

[0029] Electronic device 120 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Electronic device 120 may include, for example, computing systems / servers, such as mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0030] A communication connection can be established between electronic device 120 and terminal device 110 (or terminal device 160). The communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth connections, mobile network connections, Universal Serial Bus connections, Wi-Fi connections, etc., and the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, electronic device 120 and terminal device 110 (or terminal device 160) can achieve signaling interaction through the communication connection between them.

[0031] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0032] Figure 2 A flowchart of an example process 200 for a method of embedding data processing according to some embodiments of the present disclosure is shown. Process 200 can be implemented at an electronic device 120.

[0033] Reference Figure 2 In box 210, electronic device 120, in response to detecting a change in the tracking configuration information for target application 170, determines the content of the change in the tracking configuration information.

[0034] In some embodiments, the target application 170 can refer to any application that can apply the embedding technology. As an example, the target application 170 can be a web application and a mobile application, etc.

[0035] In some embodiments, the embedding configuration information can refer to the configuration information used to edit the embedding event (e.g., edit the data collection point and its related collection parameters, etc.). As an example, the embedding configuration information can define when, where and how to collect the user behavior data.

[0036] In some embodiments, in order to efficiently store and manage the embedding configuration information, the electronic device 120 can configure a suitable database to store the embedding configuration information and manage the data related thereto. As an example, the database can be MySQL, PostgreSQL or MongoDB, etc. As an example, the embedding configuration information and the data related thereto can be stored in a reasonable manner. For example, the storage manner includes but is not limited to an event table and an attribute table, etc., so as to meet the business requirements and ensure the efficiency of data operation.

[0037] In some embodiments, the change of the embedding configuration information can be triggered based on the editing operation of the administrator 140 on the embedding configuration information, or can be triggered based on the updating operation of the electronic device 120 on the embedding configuration information.

[0038] In some embodiments, the change content of the embedding configuration information can indicate adding a new embedding event for the target application 170, deleting or modifying an existing embedding event (e.g., modifying the collection frequency, data type, etc.), etc.

[0039] It should be noted that according to actual needs, the change content of the embedding configuration information can also indicate more content, which can be specifically according to actual needs, and the embodiments of the present disclosure will not be enumerated one by one.

[0040] Figure 3 An example 300 flowchart of updating the embedding event according to some embodiments of the present disclosure is shown.

[0041] Referring to Figure 3 In block 301, the electronic device 120 obtains an access request initiated by the administrator 140 for the embedding configuration information 320.

[0042] In block 302, the electronic device 120 verifies the permission of the initiator of the access request in response to detecting the access request for the embedding configuration information 320.

[0043] At block 303, the electronic device 120 determines whether the authority of the initiator of the access request is verified. If yes, at block 304, the electronic device 120 allows the administrator 140 to access the configuration information 320 of the embedded point. If not, at block 305, the electronic device 120 denies the administrator 140 to access the configuration information 320 of the embedded point.

[0044] In some embodiments, the electronic device 120 can verify the authority of the access request in any suitable manner. As an example, the electronic device can verify the authority of the access request based on an open authorization manner. Specifically, the electronic device verifies the authority of the access request based on an access token associated with the access request, wherein the access token is issued to the initiator of the access request based on the authorization of the administrator of the configuration information 320 of the embedded point to the initiator of the access request.

[0045] In some embodiments, the administrator 140 needs to obtain an access token by authenticating with the service provider of the configuration information 320 of the embedded point before initiating the access request. The initiator of the access request needs to attach the access token when initiating the access request. The electronic device 120 can verify the validity of the access token and determine whether to allow the administrator 140 to access the configuration information 320 of the embedded point according to the authority scope defined in the token. In this way, the username and password of the administrator 140 are not required in the above-mentioned verification process, thereby preventing information leakage.

[0046] In other embodiments, the electronic device 120 can also verify the authority of the access request in other manners. For example, the electronic device 120 can implement the authority verification by using a network token.

[0047] As an example, when using the network token to verify the authority, the electronic device 120 can provide the administrator 140 with a token containing the identity information of the administrator 140 and a validity period, and sign the token with a private key. That is, the initiator of the access request attaches the token when sending the access request. The electronic device 120 can verify the signature of the token using a public key after receiving the access request, to ensure the authenticity and integrity of the token. Once the token is verified, the electronic device 120 can determine whether the requester has the authority to access the configuration information 320 of the embedded point according to the identity information of the administrator 140 in the token.

[0048] In some embodiments, the electronic device 120 can implement fine-grained access control based on an access control list. In this way, the administrator can set very specific authorities for the administrator 140 or user groups. For example, the authorities can be set for specific resources, tables or functions, instead of simply allowing or denying access to the entire system or a large range of resources.

[0049] In some embodiments, the electronic device 120 can use Secure Sockets Layer / Transport Layer Security to better encrypt and protect data during transmission, thereby effectively preventing data from being stolen or tampered with.

[0050] In some embodiments, the electronic device 120 can intercept and record the operations of the administrator 140 based on middleware or an interceptor. This records detailed information such as the operator, operation time, and operation content, facilitating subsequent auditing and tracking.

[0051] In some embodiments, given that the log volume may be very large, the electronic device 120 can store and manage these logs based on a log management system. This not only enables efficient storage and retrieval of log information but also allows for in-depth data analysis, helping to uncover potential security issues.

[0052] In some embodiments, the electronic device 120 may manage and support the aforementioned authorization process for access requests based on any appropriate security framework.

[0053] Based on the above approach, the embodiments of this disclosure provide a robust access control mechanism. By strictly controlling access to and modification of the event tracking configuration information 320, it ensures that only authorized personnel can perform related operations, thereby reducing the risk of data leakage and misoperation. Furthermore, the aforementioned access control mechanism also ensures that the analysis and display functions related to the data collected from event tracking are only visible to authorized administrators 140, thus protecting data security and privacy while also improving controllability and management efficiency.

[0054] In some embodiments, the electronic device 120 can present a configuration page related to the event tracking configuration information 320 to the administrator 140 via an interface 150. As an example, the configuration page may display content such as operation buttons and forms, allowing the administrator 140 to easily perform operations such as adding, editing, and deleting event tracking points. In this way, the administrator 140 does not need to have in-depth knowledge of the code structure or event tracking technical details. Event tracking points can be easily set up and adjusted through simple drag-and-drop configuration.

[0055] In box 306, electronic device 120 determines that the tracking configuration information 320 has changed in response to the detection of a change event for the tracking configuration information 320 being published in the target middleware associated with the target application 170, wherein the change event is published to the target middleware based on the detection of a save instruction for the tracking configuration information 320.

[0056] As described above, the administrator 140 can edit the configuration information 320 of the embedded points through the interface 150. Once the editing is completed and saved, a change event will be issued in the target middleware, so that the latest configuration information 320 of the embedded points is immediately synchronized to the electronic device 120. Then, the electronic device 120 can add new embedded point events or delete or modify existing embedded point events based on the changed configuration information 320 of the embedded points. This process realizes the hot loading of the configuration information 320 of the embedded points, thereby greatly improving the efficiency and flexibility of the update of the embedded point events.

[0057] In some embodiments, the target middleware comprises at least one of the following: a message queue or a distributed cache.

[0058] In some embodiments, to realize the real-time synchronization and hot loading of the configuration information 320 of the embedded points, the electronic device 120 can use one or more of the message queue and the distributed cache technology. In this way, the change event of the configuration information 320 of the embedded points can be quickly spread. At the same time, these two ways are beneficial to the dynamic listening and response of the electronic device 120 to the change event of the configuration information 320 of the embedded points, so that the embedded point events can be updated without restarting the target application 170.

[0059] In some embodiments, in terms of resource management of the target middleware, the electronic device 120 can solve the resource competition problem that may occur in the hot loading process of the configuration information 320 of the embedded points through, for example, version control and queue consumer mode.

[0060] In this way, the embodiments of the present disclosure significantly improve the real-time performance of the configuration information 320 of the embedded points through real-time synchronization and hot loading technology. This means that the new configuration of the administrator 140 on the configuration information 320 of the embedded points can take effect immediately, avoiding the problem of long waiting for deployment and release of the administrator 140, so that the new embedded point data collection work can be started quickly.

[0061] In some embodiments, the electronic device 120 can use multiple threads to improve the performance and response speed of the target middleware. To ensure the stability and efficiency of the target middleware in the multi-threaded environment, the electronic device 120 can use, for example, thread-safe data structures, distributed locks, optimistic locks, and configuration update queues to ensure thread safety in the update process of the configuration information 320 of the embedded points, thereby effectively preventing resource competition problems and ensuring that the electronic device 120 is still stable and efficient in a high-concurrency scenario.

[0062] At block 307, the electronic device 120 obtains historical interaction behaviors of the target user (e.g., the user 180) with respect to the target application 170. Then, among the historical interaction behaviors, the electronic device 120 determines target historical interaction behaviors that are not monitored by the existing set of second event instrumentation events of the target application 170. Subsequently, the electronic device 120 updates the instrumentation configuration information 320 based on the target historical interaction behaviors, where the updated instrumentation configuration information 320 indicates at least adding event instrumentation events related to the target historical interaction behaviors for the target application.

[0063] In some embodiments, the electronic device 120 can utilize appropriate tools to capture various interaction behaviors of the target user on the target application to obtain the historical interaction behaviors. As an example, the electronic device 120 can provide an interface to customize the capture targets to ensure comprehensive recording of the behaviors.

[0064] Next, the electronic device 120 can aggregate the collected historical interaction behavior data through, e.g., data lakes and data warehouses, and perform necessary data cleaning and format conversion to ensure consistency and usability of the data. The data can be selectively presented to the administrator 140 as needed.

[0065] Then, the electronic device 120 can extract meaningful features from the data processed as described above, such as temporal features (e.g., time of occurrence and duration of behaviors, etc.), behavioral features (e.g., specific operations such as clicks, swipes, and page visits, etc.), and contextual features (e.g., current page, device type of the target user, and geographic location, etc.), etc., as needed to gain a deeper understanding of the historical interaction behaviors.

[0066] In some embodiments, the electronic device 120 can utilize a machine learning model to identify various features extracted by the above-described process to discover the target historical interaction behaviors that are not covered by the existing event instrumentation events. As an example, the machine learning model can be constructed based on at least one of anomaly detection, clustering algorithms, isolation forest, local outlier factor, etc.

[0067] In some embodiments, for the target historical interaction behaviors identified by the machine learning model, human review can be further utilized to ensure that the final target historical interaction behaviors are valuable and not covered by the existing event instrumentation events.

[0068] Finally, the electronic device 120 can present the above-described target historical interaction behaviors to the administrator 140, and update the instrumentation configuration information 320 in an automated or semi-automated manner to add or change the existing event instrumentation events so that the changed event instrumentation events can cover the target historical interaction behaviors.

[0069] At block 220, the electronic device 120 updates the instrumented events of the target application 170 based on the update policy related to the changed content during the running of the target application 170 by using the instrument component.

[0070] In some embodiments, the update policy can include adding new instrumented events, modifying the data collection rules of existing instrumented events, or deleting instrumented events that are no longer needed, etc.

[0071] In some embodiments, the instrument component has the ability to add new instrumented events, modify the data collection rules of existing instrumented events, or delete instrumented events that are no longer needed for the target application 170 without affecting the running of the target application 170, thereby achieving automatic configuration of instrumented events. This automatic configuration capability makes the instrumented event update process no longer dependent on the hard coding of developers, thereby reducing maintenance costs. In addition, since the update of instrumented events can be achieved without re-deploying the target application 170, the flexibility and timeliness of instrumented event configuration are greatly improved.

[0072] In some embodiments, the electronic device 120 adds a first set of instrumented events related to the newly added instrumented events for the target application 170 in response to determining that the changed content at least indicates the newly added instrumented events. Or the electronic device 120 modifies the data collection rules related to a second set of instrumented events already existing in the target application 170 based on the change manner related to the changed existing instrumented events in response to determining that the changed content at least indicates the changed existing instrumented events.

[0073] In some embodiments, when the electronic device 120 receives the changed content and determines that the changed content at least indicates the newly added instrumented events, the electronic device 120 can add a first set of instrumented events in the target application 170. These first instrumented events can be configured to collect new user data or other related data.

[0074] If the electronic device 120 determines that the received changed content contains change indications for existing instrumented events, the electronic device 120 can further analyze the specific content of the changes. As an example, the electronic device 120 can modify the data collection rules of a second set of instrumented events based on the change manner related to the changed existing instrumented events. As an example, the change manner can involve data collection frequency, data collection type, or data processing logic, etc.

[0075] In some embodiments, the change manner related to the changed existing instrumented events at least indicates a change to at least one of the following in the data collection rules: collection frequency or data format of collected data. Based on real-time monitoring results, the data collection strategy, including collection frequency, data format, etc., can be intelligently adjusted, thereby being able to maximize the accuracy and real-time performance of the data.

[0076] In some embodiments, the electronic device 120 obtains user data (e.g., user 180’s behavior data on the program 170) and device data, which can refer to data of the device (e.g., the mobile terminal 160) on which the target application 170 is installed. Based on the obtained user data and device data, the electronic device 120 adaptively updates the configuration information 320 of the embedded points to adjust the collection rules of the existing embedded point events.

[0077] As an example, if a certain user behavior suddenly increases, the electronic device 120 can increase the data collection frequency of this behavior to obtain more detailed information. As another example, if the system resource usage of the mobile terminal 160 approaches the limit, the electronic device 120 can reduce the frequency or accuracy of data collection to reduce the device burden of the mobile terminal 160.

[0078] In this way, the electronic device 120 can dynamically adjust the data collection rules by monitoring the user data and device data in real time, thereby realizing automatic and intelligent embedded point data collection. In this way, the electronic device 120 can ensure the accuracy and real-time performance of the embedded point data collection, while optimizing the performance to avoid resource waste. In addition, such an embedded point data collection method can adapt to different business scenarios and environments and realize stable operation, thereby effectively solving the problem of fixed and rigid data collection methods in the traditional embedded point data collection process.

[0079] In some embodiments, when the target user accesses the target application 170, at block 308, in response to detecting that the user behavior of the target user on the target application 170 meets the trigger condition of the embedded point event, the electronic device 120 collects embedded point data related to the triggered embedded point event.

[0080] In some embodiments, the electronic device 120 can store and report the collected embedded point data, thereby providing a basis for subsequent data analysis. As an example, the reported embedded point data can be collected and analyzed in depth. These embedded point data not only reveal the usage habits of the target user on the target application 170, but also point out the possible problems and improvement space in the target application 170.

[0081] At block 309, based on the collected embedded point data, the electronic device 120 can generate visual reports. These reports can visually and intuitively show the key indicators of the target user and the performance of the target application 170.

[0082] In some embodiments, the administrator 140 can quickly understand the running status of the target application 170 by viewing these visual reports. This provides strong decision support for the administrator 140, helping them better optimize the product and improve the user experience.

[0083] In some embodiments, one or more of the above can be implemented based on a microservice or distributed architecture (e.g., containerization technology).

[0084] As an example, based on a microservice architecture, the method for the processing of the embedding in the embodiments of the present disclosure can be split into a plurality of small, independent services. Each service focuses on a specific business function, and this refinement helps to improve maintainability and scalability.

[0085] As an example, based on a distributed architecture, one or more functions in the method for the processing of the embedding in the embodiments of the present disclosure can handle tasks in parallel, thereby speeding up the processing of the embedding data.

[0086] As can be clearly understood from the foregoing various embodiments, the embodiments of the present disclosure can automatically update the embedding events based on the embedding component when the configuration information of the target application program changes, and this process does not require manual code editing, ensuring the flexibility and efficiency of the updating of the embedding events. In addition, since the target program can always remain in a running state during the updating of the embedding events, the efficiency of the updating of the embedding events is greatly improved, and the difficulty and complexity of maintenance are reduced.

[0087] The embodiments of the present disclosure also provide a corresponding apparatus for implementing the above method or process. Figure 4 A schematic structural block diagram of an apparatus 400 for the processing of the embedding according to some embodiments of the present disclosure is shown. The apparatus 400 can be implemented as or included in the electronic device 120. The various modules / components in the apparatus 400 can be implemented by hardware, software, firmware, or any combination thereof.

[0088] With reference to Figure 4 , the apparatus 400 includes a change content determination module 410 and an embedding event updating module 420. The change content determination module 410 is configured to, in response to detecting that the embedding configuration information 320 for the target application program 170 has changed, determine the change content of the embedding configuration information 320. The embedding event updating module 420 is configured to, using the embedding component, update the embedding events of the target application program 170 based on an updating strategy related to the change content during the running of the target application program 170.

[0089] In some embodiments, the embedding event updating module 420 is further configured to, in response to determining that the change content at least indicates the addition of an embedding event, add a first set of embedding events related to the added embedding event to the target application program 170; or in response to determining that the change content at least indicates the change of an existing embedding event, change a data collection rule related to a second set of embedding events already existing in the target application program 170 based on a change manner related to the change of the existing embedding event.

[0090] In some embodiments, the change manner related to the change of the existing embedded point event at least indicates a change to at least one of the following in the data collection rule: a collection frequency; or a data format of the collected data.

[0091] In some embodiments, the apparatus 400 further comprises an adaptive updating module. The adaptive updating module is configured to: obtain a historical interaction behavior of the target user related to the target application; determine, in the historical interaction behavior, a target historical interaction behavior that is not monitored by a second set of embedded point events already existing in the target application 170; and update the embedded point configuration information 320 based on the target historical interaction behavior, wherein the updated embedded point configuration information 320 at least indicates adding an embedded point event related to the target historical interaction behavior for the target application.

[0092] In some embodiments, the apparatus 400 further comprises an authentication module. The authentication module is configured to: in response to detecting an access request for the embedded point configuration information 320, verify a permission of an initiator of the access request, and wherein the verification comprises: verifying the permission of the access request based on an access token related to the access request, wherein the access token is issued to the initiator of the access request based on an authorization of the initiator of the access request by a manager of the embedded point configuration information 320.

[0093] In some embodiments, the apparatus 400 further comprises a synchronization module. The synchronization module is configured to: in response to detecting that a change event for the embedded point configuration information 320 is published in a target middleware associated with the target application 170, determine that the embedded point configuration information 320 is changed, wherein the change event is published in the target middleware based on detecting a save instruction for the embedded point configuration information 320.

[0094] In some embodiments, the target middleware comprises at least one of: a message queue; or a distributed cache.

[0095] Figure 5 A block diagram of an electronic device 500 in which one or more embodiments of the disclosure can be implemented is shown. The electronic device 500 may, for example, be used to implement the electronic device 120 as shown in Figure 1 It should be understood that the electronic device 500 shown is merely an example which should not limit the function and scope of the embodiments described herein. Figure 5 The electronic device 500 shown is merely an example and should not limit the function and scope of the embodiments described herein.

[0096] Reference is made to Figure 5The electronic device 500 is in the form of a general electronic device. Components of the electronic device 500 can include, but are not limited to, one or more processors or processing units 510, a memory 520, a storage device 530, one or more communication units 540, one or more input devices 550, and one or more output devices 560. The processing unit 510 can be a real or virtual processor and is capable of executing various processing in accordance with programs stored in the memory 520. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve parallel processing capability of the electronic device 500.

[0097] The electronic device 500 typically includes a number of computer storage media. Such media can be any available media that is accessible by the electronic device 500 and includes both volatile and non-volatile media, removable and non-removable media. The memory 520 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory), or some combination thereof. The storage device 530 can be a removable or non-removable media and can include machine-readable media such as a flash drive, a magnetic disk drive, or any other media that can be used to store information and / or data and that can be accessed by the electronic device 500.

[0098] The electronic device 500 can further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 5 FIG. 5, a magnetic disk drive for reading from or writing to a removable, non- volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk (e.g., a CD-ROM) can be provided. In such instances, each can be connected to the bus by one or more data media interfaces. The memory 520 can include a computer program product 525 having one or more program modules configured to carry out the various methods or actions of the various embodiments of the present disclosure.

[0099] The communication unit 540 enables communication with other electronic devices over communication media. Additionally, functionality of the components of the electronic device 500 can be implemented in a single computing cluster or a plurality of computer machines that are capable of communicating over a communication connection. As such, the electronic device 500 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network nodes in a networked environment.

[0100] The input device 550 can be one or more input devices, such as a mouse, a keyboard, a trackball, etc. The output device 560 can be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 500 can also communicate with one or more external devices (not shown), such as storage devices, display devices, etc., one or more devices that enable a user to interact with the electronic device 500, or any devices (e.g., a network card, a modem, etc.) that enable the electronic device 500 to communicate with one or more other electronic devices, as desired via the communication unit 540. Such communication can be carried out via an input / output (I / O) interface (not shown).

[0101] According to an example implementation of the present disclosure, a computer readable storage medium is provided having computer executable instructions stored thereon, where the computer executable instructions are executed by a processor to implement the method described above. According to an example implementation of the present disclosure, a computer program product is also provided that is tangibly stored on a non-transitory computer readable medium and includes computer executable instructions, where the computer executable instructions are executed by a processor to implement the method described above.

[0102] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0103] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0104] The computer readable program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0105] The computer program product of the present disclosure can be a computer program product, which is a machine-readable medium (media) having instances of the software embodied thereon, such as computer software, firmware, wireless application protocol (WAP), middleware or microcode. For example, a computer program product can be a floppy disk, a CD-ROM, a DVD, a Blu-ray Disc™, a flash drive, a memory stick, a magnetic tape, or a hard disk drive. The machine-readable medium can be a single medium, or multiple media, of the same or different type. The computer program product can be one or more computer program components embodied in medium and / or transmission signals. The computer program product can have one or more computer program components embodied in medium and / or transmission signals.

[0106] The implementations of the disclosure have been described above with the intent to be illustrative rather than limiting. Although the implementations of the disclosure have been described with regard to one or more implementations, it will be recognized that a variety of modifications and changes can be made to these implementations without departing from the broader spirit and scope of the implementations as set forth in the preceding disclosure. For example, certain aspects of the implementations can be performed using hardware, software, and / or firmware, or any combination thereof. The above-described implementations should therefore be regarded as merely illustrative, and not as narrowing the scope of the disclosure, which is defined by the appended claims and their equivalents.

Claims

1. A method for embedding data points, comprising: In response to detecting a change in the event tracking configuration information for the target application, the content of the change in the event tracking configuration information is determined; as well as Using the event tracking component, during the operation of the target application, the event tracking events of the target application are updated based on the update strategy related to the changed content.

2. The method according to claim 1, wherein, using a tracking component, during the operation of the target application, the tracking events of the target application are updated based on an update strategy related to the changed content, including at least one of the following: In response to determining that the change at least indicates a new event, add a first set of event tracking related to the new event tracking to the target application; or In response to determining that the change content at least indicates a change to an existing event tracking point, the data collection rules related to a second set of existing event tracking points in the target application are changed based on the change method associated with the change to the existing event tracking point.

3. The method of claim 2, wherein the change method related to the change of the existing tracking event indicates at least one of the following changes in the data collection rules: sampling frequency; or The data format of the collected data.

4. The method according to claim 1, further comprising: Acquire historical interaction behavior of the target user related to the target application; Among the historical interaction behaviors, target historical interaction behaviors that are not monitored by a set of second tracking events already present in the target application are identified; as well as Based on the target historical interaction behavior, the event tracking configuration information is updated, wherein the updated event tracking configuration information at least indicates that event tracking related to the target historical interaction behavior is added to the target application.

5. The method according to claim 1, further comprising: In response to detecting an access request for the event tracking configuration information, the permissions of the initiator of the access request are verified, and the verification includes: The permissions of the access request are verified based on the access token associated with the access request, wherein the access token is issued to the initiator of the access request based on the authorization granted to the initiator of the access request by the administrator of the event tracking configuration information.

6. The method according to claim 1, further comprising: In response to the detection of a change event for the event tracking configuration information being published in the target middleware associated with the target application, it is determined that the event tracking configuration information has been changed, wherein the change event is published to the target middleware based on the detection of a save instruction for the event tracking configuration information.

7. An apparatus for embedded point processing, comprising: The change content determination module is configured to determine the change content of the tracking configuration information in response to detecting a change in the tracking configuration information for the target application; as well as The embedded point event updating module is configured to utilize the embedded point component to update the embedded point event of the target application based on an updating strategy related to the change content during running of the target application.

8. An electronic device, comprising: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit cause the electronic device to perform the method according to any one of claims 1 to 6.

9. A computer readable storage medium having stored thereon a computer program, the computer program being executable by a processor to implement the method according to any one of claims 1 to 6.

10. A computer program product comprising computer executable instructions that, when executed by a processor, implement the method according to any one of claims 1 to 6.

Images