CN110502415B

CN110502415B - Buried point setting method, device and equipment

Info

Publication number: CN110502415B
Application number: CN201910795819.4A
Authority: CN
Inventors: 刘少伟; 高元胜; 徐嘉亮; 董畅; 徐唐; 沈仁奎; 邓鑫鑫
Original assignee: Beijing Mind Creation Information Technology Co ltd
Current assignee: Beijing Mind Creation Information Technology Co ltd
Priority date: 2019-08-27
Filing date: 2019-08-27
Publication date: 2023-11-28
Anticipated expiration: 2039-08-27
Also published as: CN110502415A

Abstract

The embodiment of the specification discloses a buried point setting method, a buried point setting device and buried point setting equipment. The scheme of the point burying device comprises the following steps: acquiring initial embedded point configuration information of a designated version of a control to be processed; acquiring a buried point setting instruction input by an operation user; responding to the buried point setting instruction, and setting the initial buried point configuration information of the appointed version to obtain an updated buried point configuration file of the appointed version; and sending the updated embedded point configuration file of the appointed version so as to facilitate the target application client end of the appointed version carried on the user terminal equipment to set the embedded point of the control to be processed by the updated embedded point configuration file.

Description

Buried point setting method, device and equipment

The present application relates to the field of computer data processing technologies, and in particular, to a method, an apparatus, and a device for setting a buried point.

Background

With the rapid development of terminal technology, various applications have gained rapid popularity. The user generates a lot of behavior data during the use of various applications, and the buried point setting method is applied because the behavior data is important in analyzing the software products and registered users. At present, embedding points of all controls in an application client are usually set through a code embedding point method. The code embedding is to implant codes for collecting user behavior data into a control requiring statistical data in an application client so as to realize the embedding acquisition function. When the embedded point setting method changes the embedded point of the control, a professional is required to modify the application program of the application client, and the operation is complex, time-consuming and labor-consuming.

Disclosure of Invention

In view of the above, the embodiments of the present application provide a method, an apparatus, and a device for setting a buried point, which are used for solving the problem that a method for setting a buried point is required to be provided with more convenient operation.

In order to solve the above technical problems, the embodiments of the present specification are implemented as follows:

the buried point setting method provided by the embodiment of the specification comprises the following steps:

the method comprises the steps that a server obtains initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version;

acquiring a buried point setting instruction input by an operation user;

responding to the buried point setting instruction, setting the initial buried point configuration information, and obtaining an updated buried point configuration file;

transmitting the updated embedded point configuration file so as to facilitate the designation carried on the user terminal equipment

And the target application client of the version sets the embedded point of the control to be processed based on the updated embedded point configuration file.

The method for setting the buried point, provided in the embodiment of the present disclosure, is applied to a terminal device, where a target application client of a specified version is carried on the terminal device, and includes:

Acquiring triggering operation of the target application client;

determining an application version of the target application client to obtain a designated version;

acquiring the embedded point configuration file of the appointed version from a cloud server;

and setting the buried point of the target application client according to the buried point configuration file.

The embodiment of the present disclosure provides a buried point setting device, which is applied to a server, and includes:

the first acquisition module is used for acquiring initial buried point configuration information of the control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version;

the second acquisition module is used for acquiring a buried point setting instruction input by an operation user;

the setting module is used for responding to the buried point setting instruction and setting the initial buried point configuration information to obtain an updated buried point configuration file;

and the sending module is used for sending the updated embedded point configuration file so as to facilitate the target application client of the appointed version carried on the user terminal equipment to set the embedded point of the control to be processed based on the updated embedded point configuration file.

The embodiment of the present disclosure provides a buried point setting device, which is applied to a terminal device, where a target application client of a specified version is carried on the terminal device, and the buried point setting device includes:

the first acquisition module is used for acquiring triggering operation of the target application client;

the determining module is used for determining the application version of the target application client to obtain a designated version;

the second acquisition module is used for acquiring the embedded point configuration file of the appointed version from the cloud server;

and the setting module is used for setting the buried point of the target application client according to the buried point configuration file.

The embodiment of the present specification provides a buried point setting device, including:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to:

acquiring initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version;

Acquiring a buried point setting instruction input by an operation user;

and sending the updated embedded point configuration file so that the target application client of the appointed version carried on the user terminal equipment can set the embedded point of the control to be processed based on the updated embedded point configuration file.

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

acquiring triggering operation of a target application client of a designated version carried on the embedded point setting equipment;

A computer readable storage medium provided in embodiments of the present specification stores computer executable instructions that when executed by a processor implement the steps of:

acquiring a buried point setting instruction input by an operation user;

acquiring triggering operation of a target application client of a designated version carried on terminal equipment;

The above-mentioned at least one technical scheme that this description embodiment adopted can reach following beneficial effect:

when the point embedding setting is required to be carried out on the to-be-processed control in the target application client of the appointed version, an operation user can enable the server to generate and send an updated point embedding configuration file by inputting a point embedding setting instruction for modifying initial point embedding configuration information of the to-be-processed control, so that the target application client of the appointed version carried on the user terminal equipment sets the point embedding of a plurality of controls including the to-be-processed control based on the updated point embedding configuration file. According to the embedded point setting scheme, an operating user does not need to modify an application program of a target application client of a designated version, the embedded point setting of a control to be processed in the target application client of the designated version can be completed, the requirement of an embedded point setting method on an operator is reduced, and meanwhile the operation complexity of the embedded point setting method is reduced. And because one embedded point configuration file can be maintained for each version of application client, the influence on other versions of application clients caused by setting embedded points of the application client of a designated version can be avoided, and the version compatibility problem is reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

fig. 1 is a schematic flow chart of a method for setting a buried point according to a first embodiment of the present disclosure;

FIG. 2 is a schematic diagram of a buried debug page according to a first embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a buried point debug page displaying control information reported by test terminal equipment;

fig. 4 is a schematic flow chart of a buried point setting method according to a second embodiment of the present disclosure;

FIG. 5 is a schematic structural view of a buried point setting device corresponding to the method of FIG. 1 according to a third embodiment of the present disclosure;

fig. 6 is a schematic structural diagram of a buried point setting device corresponding to the method of fig. 4 according to a fourth embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

Fig. 1 is a schematic flow chart of a method for setting a buried point according to an embodiment of the present disclosure. From the program perspective, the execution subject of the flow may be a program for setting a buried point, which is installed on a server.

As shown in fig. 1, the process may include the steps of:

step 101: the method comprises the steps that a server obtains initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version.

In the present description embodiment, the control (i.e., user interface design element) is a visual component in the application interface of the target application program. By setting the corresponding control on the target application program, the appearance and the behavior of the application interface of the target application program can reach the expected effect, and the user can interact with the application program through the control. In actual practice, the controls include, but are not limited to, buttons, search boxes, selectable item lists, and the like. The controls in the target application client are matched with unique control identifications so as to facilitate the subsequent burying point setting of the controls.

In the embodiment of the present disclosure, the code for embedding the point does not need to be embedded in the application program of the target application client, and the application program of the target application client is configured to perform embedding point data acquisition according to the embedding point configuration file. Specifically, when the target application client sets the embedded point, the embedded point configuration file needs to be analyzed, and the embedded point of the control is set according to the association relationship among the control, the embedded point and the embedded point acquisition information in the analyzed embedded point configuration information, so that the required embedded point acquisition information is acquired after the control is triggered.

In practical applications, the file type of the embedded point configuration file may be set according to practical requirements, for example, the embedded point configuration file may be in JSON (JavaScript ObjectNotation) format. The target application client may be any application client that needs to set a buried point, for example, a payment application client, a browsing application client, a chat application client, etc.

In this embodiment of the present disclosure, an example description is given of one piece of embedding point configuration information in an embedding point configuration file, where the embedding point configuration information is used to set an embedding point with an embedding point identifier of "s_event-day_estoreydetail_vip_buy" for a control identified as "saybook database activity_activity_database_new_tv_operation_buyvipagain" so as to acquire embedding point acquisition information such as log_id, log_type, log_name, and log_interface. The embedded point configuration information is as follows:

In the embodiment of the present disclosure, the target application client with a specified version is a target application client with one application version in an operating system, and application programs of the target application clients with different application versions are different. For example, the target application client of the specified version may be a payment application client of version number 5.6.0 applicable to the android operating system, and at this time, the payment application client of version number 5.6.0 applicable to the iOS operating system is a different application client from the target application client of the specified version. Or, the payment application client with the version number 5.6.0 applicable to the iOS operating system and the payment application client with the version number 5.6.1 applicable to the iOS operating system also belong to two application clients with different versions.

In practical applications, the operating user should already know in advance the control information to be processed when executing step 101, where the control information to be processed is used to indicate what type of control (i.e. the control to be processed) in the target application client of what version (i.e. the designated version) needs to be subjected to the embedded point setting. The current embedded point configuration file of the target application client of the appointed version indicated by the control information to be processed can be determined to be the initial embedded point configuration file. The initial embedded point configuration file contains the association relationship among all embedded point identifiers, embedded point acquisition information and control identifiers of all embedded points currently set by the target application client of the appointed version, and the initial embedded point configuration file can also contain all embedded point identifiers, embedded point acquisition information and control identifiers related to the association relationship. At this time, the server may determine the initial embedded point configuration information of the control to be processed according to the control information to be processed and the initial embedded point configuration file.

In the embodiment of the specification, a corresponding embedded point configuration file is configured for each version of target application client, that is, one embedded point configuration file corresponds to one application version of target application client in one operating system, so that the problem of version compatibility of the application client after embedded point modification can be avoided, limiting conditions for embedded point setting can be reduced, the embedded point setting method is simplified, and requirements for operators are reduced.

Step 102: and acquiring a buried point setting instruction input by an operation user.

In this embodiment of the present disclosure, after obtaining initial embedded point configuration information of a control to be processed, a server may generate an embedded point debug page including control information of the control to be processed and the initial embedded point configuration information. For step 102, specifically, a buried point setting instruction input by the operation user on the buried point debug page may be obtained.

Fig. 2 is a schematic diagram of a buried point debugging page according to the first embodiment of the present disclosure, as shown in fig. 2, where the buried point debugging page includes a designated version information display area 201 of a target application client, an initial buried point configuration information display area 202 of a control to be processed, and a newly added buried point setting area 203. In fig. 2, the initial buried point configuration information display area 202 of the control to be processed is displayed with: a control identifier "paybutton" of the control to be processed, a buried point identifier "mailian 1" of a buried point currently having an association with the control "paybutton" to be processed, and a "delete" operation option 2021; the user can input a buried point setting instruction for instructing deletion of the association relationship between the to-be-processed control "paybutton" and the buried point "main 1" by clicking the "delete" operation option 2021. The newly added buried point setting area 203 shows: a control to be processed identification input area 2031, a point to be embedded identification input area 2032, and a "submit" operation option 2033; the user can input a pinch point setting instruction for instructing establishment of an association relationship between the control "pay button" and the pinch point "main 2" by clicking the "submit" operation option 2033.

Step 103: and responding to the buried point setting instruction, and setting the initial buried point configuration information to obtain an updated buried point configuration file.

In the embodiment of the present disclosure, the updated embedded point configuration file may have a plurality of implementation manners.

Mode one: and replacing the initial buried point configuration information corresponding to the control to be processed in the initial buried point configuration file by using the modified initial buried point configuration information of the control to be processed, wherein the whole initial buried point configuration file after information replacement can be used as an updated buried point configuration file. The user terminal device stores the updated embedded point configuration file after receiving the updated embedded point configuration file in the implementation mode, and deletes the old embedded point configuration file stored in the user terminal device. In the implementation mode, the user terminal equipment only needs to execute simple file pulling and file replacing operations, so that the method is safe and reliable.

Mode two: and using the modified initial embedded point configuration information of the control to be processed as an updated embedded point configuration file. After receiving the updated embedded point configuration file in the implementation manner, the user terminal device can use the updated embedded point configuration file to replace embedded point configuration information corresponding to the control to be processed in the old version embedded point configuration file stored in the user terminal device. The implementation mode can reduce the resource consumption of the user terminal equipment when the updated embedded point configuration file is required to be pulled as much as possible, and avoid the waste of network resources.

Step 104: and sending the updated embedded point configuration file so that the target application client of the appointed version carried on the user terminal equipment can set the embedded point of the control to be processed based on the updated embedded point configuration file.

In the embodiment of the present specification, step 104 may specifically include: uploading the updated embedded point configuration file to a cloud server, so that the user terminal equipment can automatically acquire the updated embedded point configuration file from the cloud server when the carried target application client of the designated version is started. In the implementation manner, because the user terminal device can automatically pull the updated embedded point configuration file from the cloud server when the target application client is started, no additional operation is required to be performed by a user, the user operation steps in the process of embedding point change in the target application client can be simplified, the problem of long embedded point change period caused by that the user does not update the version of the target application client in the prior art can be solved, and the embedded point change period is shortened.

In the embodiment of the specification, the server may respond to an operation user input a buried point setting instruction, where the buried point setting instruction is used to set buried point configuration information of a control to be processed in a target application client of a specified version; generating an updated buried point configuration file, and sending the updated buried point configuration file to user terminal equipment so as to enable a target application client of a designated version carried on the user terminal equipment to set a buried point based on the updated buried point configuration file; according to the scheme, the embedded point setting of the control in the target application client can be completed without modifying the application program of the target application client, so that the requirement of the embedded point setting method on operators can be reduced, and meanwhile, the operation complexity of the embedded point setting method can be reduced.

Based on the method in fig. 1, the examples of the present specification also provide some specific implementations of the method, as described below.

In the present embodiment, for step 101: there are various implementations for the server to obtain the initial embedded point configuration information of the control to be processed.

The first implementation manner is as follows: when the operating user knows that the icon and the triggering mode of the to-be-processed control are displayed in the application interface of the target application client of the designated version, but the operating user cannot determine the control identifier of the to-be-processed control, step 101 may specifically include:

the method comprises the steps that a server obtains control information of a control which is operated by a user on test terminal equipment for the last time, wherein the control information is reported by the test terminal equipment in response to triggering operation of a control to be processed in a target application test client of a designated version. And acquiring the initial embedded point configuration file of the appointed version. And determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file.

In the embodiment of the present specification, the application interface of the target application test client of the specified version is the same as that of the target application client of the specified version used by the general user. The difference is that when a control in an application interface of a target application testing client of a designated version is triggered, reporting information generated is control information, wherein the control information comprises: control identification and control basic information; the report information generated after the application interface of the target application client of the appointed version used by the common user is triggered is buried point data, and the buried point data does not contain a control identification.

Therefore, when the operation user knows the icon of the to-be-processed control but does not know the control identification of the to-be-processed control, the operation user can trigger the target application of the appointed version to test the to-be-processed control in the client side, so that the server obtains the control information of the to-be-processed control, and further the control identification of the to-be-processed control is determined. And determining the embedded point configuration information corresponding to the control identification of the control to be processed in the initial embedded point configuration file as the initial embedded point configuration information.

Fig. 3 is a schematic diagram of a buried point debugging page displaying control information reported by a test terminal device. Assume that a user identifier corresponding to a test terminal device of an operator is "123", and a target application test client of a specified version is mounted on the test terminal device. As shown in fig. 3, the operating user inputs the designated version information of the target application client in the first area 301, and inputs the monitoring user identifier "123" in the second area 302, and the operating option "stop refreshing" 303 indicates that the server is collecting control information reported by the terminal device with the user identifier "123". At this time, the control information 304 displayed by the embedded point debugging page is the control information of the control which is operated by the user on the test terminal device last time; the control information 304 includes a control identifier and control basic information, where the control basic information may be set according to actual requirements, and this is not limited in this specification. The embedded point debugging page also displays embedded point configuration information corresponding to the control information 304, so that embedded point setting of the control indicated by the control information 304 is facilitated.

The second implementation mode is as follows: when the operating user knows the control identifier of the control to be processed, step 101 may specifically include:

the method comprises the steps that a server obtains control information of a to-be-processed control input by an operation user, wherein the to-be-processed control is a control in a target application client of a designated version; acquiring an initial buried point configuration file of the appointed version; and determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file.

In this embodiment of the present disclosure, the control information of the to-be-processed control input by the operation user includes a control identifier of the to-be-processed control, and at this time, the embedded point configuration information corresponding to the control identifier of the to-be-processed control in the initial embedded point configuration file may be determined as the initial embedded point configuration information.

In this embodiment of the present disclosure, after determining, by the server, initial embedded point configuration information corresponding to the control information in the initial embedded point configuration file, the method may further include: and generating a buried point debugging page containing the control information and the initial buried point configuration information. In practical applications, the schematic diagram of the embedded debug page may refer to fig. 2 or fig. 3, and will not be described herein.

In the embodiment of the present specification, when the initial buried point configuration information includes: the association relationship among the control mark to be processed, the buried point mark and the buried point acquisition information is that the buried point setting instruction is used for indicating to cancel the buried point set by the control to be processed, and the initial buried point configuration information is set in response to the buried point setting instruction, which specifically comprises: and deleting the association relation contained in the initial buried point configuration information to cancel the buried point set for the control to be processed. At this time, the updated embedded point configuration file does not contain embedded point identifiers having association relation with the control identifiers to be processed. Therefore, after the user terminal device sets the buried point based on the updated buried point configuration file, the buried point for the control to be processed will not be set.

In the embodiment of the present specification, when the initial buried point configuration information includes: the association relationship among the control mark to be processed, the first buried point mark and the first buried point acquisition information is that the buried point setting instruction is used for indicating that when the buried point set by the control mark to be processed is changed, the initial buried point configuration information is set in response to the buried point setting instruction, and the method specifically comprises the following steps: changing a first buried point identifier in the initial buried point configuration information into a second buried point identifier, wherein the first buried point identifier and the second buried point identifier are different buried point identifiers; and/or changing the first buried point acquisition information in the initial buried point configuration information into the second buried point acquisition information, wherein the first buried point acquisition information and the second buried point acquisition information are different buried point acquisition information so as to change the buried point and/or the buried point acquisition information of the control to be processed.

In practical applications, the buried point acquisition information is used for indicating data required to be acquired by the buried point. For example, when a buried point is set for a payment button, buried point acquisition information having an association relationship with the payment button may be used to indicate acquisition of commodity identification, commodity link, seller identification, transaction amount, amount due, payment method, and the like. The data indicated by the buried point acquisition information may be set according to actual requirements, which is not limited in the embodiment of the present specification.

In practical application, the buried point acquisition information corresponding to different buried point identifiers is usually different, so that the change of the buried point of the control to be processed can be realized by modifying the buried point identifier with an association relation with the control to be processed. Or when all the embedded point acquisition information corresponding to the existing embedded point identification does not meet the requirement, the embedded point acquisition information corresponding to the embedded point identification with the association relation with the control identification to be processed can be modified, or one embedded point identification is newly established, the embedded point acquisition information corresponding to the newly established embedded point identification is set as the required embedded point acquisition information, and the association relation among the control identification to be processed, the newly established embedded point identification and the embedded point acquisition information corresponding to the newly established embedded point identification is established, so that the change of the embedded point of the control to be processed is realized.

In the embodiment of the present disclosure, when the initial buried point configuration information does not include: the association relationship among the control identification to be processed, the buried point identification and the buried point acquisition information is that the buried point setting instruction is used for indicating that when the buried point is set for the control to be processed, the initial buried point configuration information is set in response to the buried point setting instruction, which specifically can include: and adding the association relation among the control identification to be processed, the designated buried point identification and the designated buried point acquisition information into the initial buried point configuration information so as to set buried points for acquiring the designated buried point acquisition information for the control to be processed.

In the embodiment of the specification, various implementation manners for setting the buried point are provided, and an operation user can input a buried point setting instruction based on a buried point setting page shown in fig. 2 or 3, so that the method is visual, convenient and practical.

Fig. 4 is a schematic flow chart of a buried point setting method according to a second embodiment of the present disclosure. From a program perspective, the execution subject of the flow may be an application program of a target application client of a specified version that is mounted on the user terminal device.

As shown in fig. 4, the process may include the steps of:

Step 401: and acquiring triggering operation of the target application client of the appointed version.

In the embodiment of the present specification, step 401 may specifically include: and when the target application client is in the exit state, acquiring a starting operation of the target application client.

The target application client being in the exit state means that the application program of the target application client is in an un-running state, that is, the application program of the target application client is not running in the background of the terminal device or in the foreground of the terminal device. In practical application, the user may close the target application client by clicking an "exit application" button in the target application client, where the target application client is in an exit state. Or the user can make the application program of the target application client run in the background of the terminal device, and when the terminal device judges that the duration of the application program of the target application client running in the background exceeds a preset value, or when the CPU occupancy rate of the terminal device exceeds a preset threshold, the target application client is controlled to change from the background running state to the exit state. According to the implementation mode, when the target application client is started, the embedded point configuration file is pulled from the cloud server, so that the real-time performance of embedded point updating can be guaranteed, the accuracy of embedded point data reporting can be guaranteed, and the problem of embedded point data confusion and error caused by embedded point updating in the operation process of the target client is avoided.

Step 402: and determining the application version of the target application client to obtain the appointed version.

In the embodiment of the present disclosure, the target application client of the specified version corresponds to the target application client of one application version in one operating system, and the application programs of the target application clients of different application versions are different. The specified version includes: operating system information of the terminal device and version information of an application program of a target application client mounted in the terminal device. For example, the specified version may be android 5.6.0.

Step 403: and acquiring the embedded point configuration file of the appointed version from the cloud server.

In the embodiment of the present specification, step 403 may specifically include: generating a buried point configuration file acquisition request, wherein the configuration file acquisition request is used for requesting to acquire the buried point configuration file of the appointed version of the target application client; sending the embedded point configuration file acquisition request to a cloud server; and receiving the embedded point configuration file fed back by the cloud server.

The embedded point configuration file of the specified version, which is obtained from the cloud server, may be generated by using the embedded point setting method of the embodiment. In practical applications, only the last updated embedded point configuration file of a designated version is usually stored in the cloud server. Therefore, a user who does not use the target application client for a long time can directly acquire the latest embedded point configuration file of the appointed version when the target application client is started again, and multiple old embedded point configuration files related in the process of generating the latest embedded point configuration file are not needed to be downloaded one by one, so that the method is convenient and quick.

Step 404: and setting the buried point of the target application client according to the buried point configuration file.

In an embodiment of the present disclosure, the embedded point configuration information in the embedded point configuration file includes: the control identification, the buried point identification and the buried point acquisition information are related; the setting the embedded point of the target application client according to the embedded point configuration file may specifically include:

replacing an old version embedded point configuration file of the target application client pre-stored in the terminal equipment by using the embedded point configuration file; and setting the buried point of the designated control in the target application client as the buried point indicated by the buried point identifier with the association relation with the control identifier of the designated control according to the buried point configuration file, so as to acquire buried point acquisition information with the association relation with the control identifier of the designated control when the designated control is triggered.

In practical application, when the embedded point configuration file obtained from the cloud server is different from the old version embedded point configuration file pre-stored in the terminal device, the embedded point set based on the embedded point configuration file obtained from the cloud server is also different from the embedded point set based on the old version embedded point configuration file pre-stored in the terminal device.

In this embodiment of the present disclosure, when a buried point of a target application client of a specified version needs to be set, a new version of buried point configuration file of the specified version may be generated in advance by using the buried point setting method in the first embodiment, and the new version of buried point configuration file is uploaded to the cloud server. When a target application client in the terminal equipment is started, automatically acquiring a buried point configuration file of a designated version (namely a new version buried point configuration file) from a cloud server; and setting the buried point of the target application client according to the buried point configuration file. The version updating operation of the target application client is not required to be executed by the user, so that the user operation can be reduced, and the user experience is improved. And when a user starts a target application program, the embedded point updating can be performed, the embedded point updating instantaneity is good, and the problem of overlong embedded point changing period caused by the fact that the user does not execute version upgrading operation can be solved. Meanwhile, as each version of application client corresponds to one embedded point configuration file, the version compatibility problem generated after the embedded point configuration file of the appointed version is modified can be reduced, and therefore the user experience is improved.

Based on the same thought, the third embodiment of the present disclosure further provides an apparatus corresponding to the method in fig. 1. Fig. 5 is a schematic structural diagram of a buried point setting device corresponding to the method in fig. 1 according to the third embodiment of the present disclosure. As shown in fig. 5, the apparatus applied to a server may include:

The first obtaining module 501 is configured to obtain initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version.

The second obtaining module 502 is configured to obtain a buried point setting instruction input by an operation user.

And a setting module 503, configured to set the initial buried point configuration information in response to the buried point setting instruction, so as to obtain an updated buried point configuration file.

And the sending module 504 is configured to send the updated embedded point configuration file, so that the target application client of the specified version carried on the user terminal device sets the embedded point of the control to be processed based on the updated embedded point configuration file.

The first obtaining module 501 may specifically be configured to: acquiring control information of a control which is operated by a user on test terminal equipment for the last time, wherein the control information is reported by the test terminal equipment in response to the triggering operation of a control to be processed in a target application test client of a designated version; acquiring an initial buried point configuration file of the appointed version; and determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file.

Alternatively, the first obtaining module 501 may specifically be configured to: acquiring control information of a control to be processed input by an operation user, wherein the control to be processed is a control in a target application client of a designated version; acquiring an initial buried point configuration file of the appointed version; and determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file.

The first acquisition module 501 may also be configured to: and generating a buried point debugging page containing the control information and the initial buried point configuration information. Correspondingly, the second obtaining module 502 may be configured to: and acquiring a buried point setting instruction input by an operation user in the buried point debugging page.

When the initial buried point configuration information includes: the association relationship among the control identifier to be processed, the buried point identifier and the buried point acquisition information, and the buried point setting instruction is used for indicating to cancel the buried point set on the control to be processed, the setting module 503 may be specifically used for: and deleting the association relation contained in the initial buried point configuration information to cancel the buried point set for the control to be processed.

When the initial buried point configuration information includes: the association relationship among the control to be processed identifier, the first buried point identifier and the first buried point acquisition information, and the buried point setting instruction is used for indicating that when the buried point set by the control to be processed is changed, the setting module 503 may be specifically used for: changing a first buried point identifier in the initial buried point configuration information into a second buried point identifier, wherein the first buried point identifier and the second buried point identifier are different buried point identifiers; and/or changing the first buried point acquisition information in the initial buried point configuration information into the second buried point acquisition information, wherein the first buried point acquisition information and the second buried point acquisition information are different buried point acquisition information so as to change the buried point and/or the buried point acquisition information of the control to be processed.

When the initial buried point configuration information does not include: the association relationship among the control identifier to be processed, the buried point identifier and the buried point acquisition information, and the buried point setting instruction is used for indicating that when the buried point is set for the control to be processed, the setting module 503 may be specifically used for: and adding the association relation among the control identification to be processed, the designated buried point identification and the designated buried point acquisition information into the initial buried point configuration information so as to set buried points for acquiring the designated buried point acquisition information for the control to be processed.

The sending module 504 may be specifically configured to upload the updated embedded point configuration file to a cloud server, so that when the user terminal device starts up the carried target application client of the specified version, the updated embedded point configuration file is obtained from the cloud server. Wherein one of the embedded point profiles corresponds to a target application client of an application version in an operating system.

Based on the same thought, the fourth embodiment of the present disclosure further provides an apparatus corresponding to the method in fig. 4. Fig. 6 is a schematic structural diagram of a buried point setting device corresponding to the method of fig. 4 according to a fourth embodiment of the present disclosure. As shown in fig. 5, the apparatus is applied to a terminal device, where a target application client of a specified version is carried on the terminal device, and may include:

A first obtaining module 601, configured to obtain a trigger operation on the target application client.

And the determining module 602 is configured to determine an application version of the target application client, and obtain a specified version.

A second obtaining module 603, configured to obtain the embedded point configuration file of the specified version from the cloud server.

And the setting module 604 is configured to set the buried point of the target application client according to the buried point configuration file.

The first obtaining module 601 may be specifically configured to obtain a start operation of the target application client when the target application client is in an exit state.

The second obtaining module 603 may be specifically configured to generate a buried point configuration file obtaining request, where the configuration file obtaining request is used to request to obtain a buried point configuration file of the specified version of the target application client; sending the embedded point configuration file acquisition request to a cloud server; and receiving the embedded point configuration file fed back by the cloud server.

The embedded point configuration information in the embedded point configuration file comprises: the control identification, the buried point identification and the buried point acquisition information are related; the setting module 604 may be specifically configured to replace an old version of the embedded point configuration file of the target application client pre-stored in the terminal device with the embedded point configuration file; and setting the buried point of the designated control in the target application client as the buried point indicated by the buried point identifier with the association relation with the control identifier of the designated control according to the buried point configuration file, so as to acquire buried point acquisition information with the association relation with the control identifier of the designated control when the designated control is triggered.

Based on the same thought, the fifth embodiment of the present specification also provides a buried point setting device corresponding to the method in fig. 1.

This buries some setting equipment includes: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to:

acquiring initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version; acquiring a buried point setting instruction input by an operation user; responding to the buried point setting instruction, setting the initial buried point configuration information, and obtaining an updated buried point configuration file; and sending the updated embedded point configuration file so that the target application client of the appointed version carried on the user terminal equipment can set the embedded point of the control to be processed based on the updated embedded point configuration file.

Based on the same idea, the sixth embodiment of the present specification also provides a buried point setting device corresponding to the method in fig. 4.

acquiring triggering operation of a target application client of a designated version carried on the embedded point setting equipment; determining an application version of the target application client to obtain a designated version; acquiring the embedded point configuration file of the appointed version from a cloud server; and setting the buried point of the target application client according to the buried point configuration file.

Based on the same idea, a seventh embodiment of the present disclosure further provides a computer readable storage medium corresponding to the method in fig. 1, where the computer readable storage medium stores computer executable instructions, where the computer executable instructions when executed by a processor implement the following steps:

Based on the same idea, an eighth embodiment of the present disclosure further provides a computer readable storage medium corresponding to the method in fig. 4, where the computer readable storage medium stores computer executable instructions, where the computer executable instructions when executed by a processor implement the following steps:

acquiring triggering operation of a target application client of a designated version carried on terminal equipment; determining an application version of the target application client to obtain a designated version; acquiring the embedded point configuration file of the appointed version from a cloud server; and setting the buried point of the target application client according to the buried point configuration file.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-transitory computer readable storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to portions of the description of method embodiments being relevant.

The apparatus, the device, the nonvolatile computer readable storage medium and the method provided in the embodiments of the present disclosure correspond to each other, and therefore, the apparatus, the device, and the nonvolatile computer storage medium also have similar advantageous technical effects as those of the corresponding method, and since the advantageous technical effects of the method have been described in detail above, the advantageous technical effects of the corresponding apparatus, device, and nonvolatile computer storage medium are not described herein again.

In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose logic function is determined by the user programming the device. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented by using "logic compiler" software, which is similar to the software compiler used in program development and writing, and the original code before the compiling is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but not just one of the hdds, but a plurality of kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), lava, lola, myHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic controllers, and embedded microcontrollers, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, atmelAT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in the same piece or pieces of software and/or hardware when implementing the present application.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims

1. A buried point setting method, characterized by comprising:

the method comprises the steps that a server obtains initial embedded point configuration information of a control to be processed; the control to be processed is a control in a target application client of a designated version, and the initial embedded point configuration information is information in an initial embedded point configuration file of the designated version; the server acquires initial embedded point configuration information of a control to be processed, and specifically comprises the following steps: the method comprises the steps that a server obtains control information of a control which is operated by a user on test terminal equipment for the last time, wherein the control information is reported by the test terminal equipment in response to triggering operation of a control to be processed in a target application test client of a designated version; acquiring an initial buried point configuration file of the appointed version; determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file;

The target application client of the appointed version is a target application client of an application version in an operating system;

acquiring a buried point setting instruction input by an operation user;

2. The method of claim 1, wherein the server obtains initial embedded point configuration information of the control to be processed, specifically comprising:

the method comprises the steps that a server obtains control information of a to-be-processed control input by an operation user, wherein the to-be-processed control is a control in a target application client of a designated version;

acquiring an initial buried point configuration file of the appointed version;

and determining initial buried point configuration information corresponding to the control information in the initial buried point configuration file.

3. The method of claim 1 or 2, wherein after determining the initial buried point configuration information corresponding to the control information in the initial buried point configuration file, further comprises:

Generating a buried point debugging page containing the control information and the initial buried point configuration information;

the obtaining the buried point setting instruction input by the operation user specifically includes:

and acquiring a buried point setting instruction input by an operation user in the buried point debugging page.

4. The method according to any one of claims 1-2, wherein when the initial buried point configuration information includes: the control identification to be processed, the buried point identification and the buried point acquisition information are related, and the buried point setting instruction is used for indicating that when the buried point set for the control to be processed is canceled,

the responding to the buried point setting instruction sets the initial buried point configuration information, and specifically includes:

and deleting the association relation contained in the initial buried point configuration information to cancel the buried point set for the control to be processed.

5. The method according to any one of claims 1-2, wherein when the initial buried point configuration information includes: the control mark to be processed, the first buried point mark and the first buried point acquisition information are related, and the buried point setting instruction is used for indicating that when the buried point set by the control mark to be processed is changed,

changing a first buried point identifier in the initial buried point configuration information into a second buried point identifier, wherein the first buried point identifier and the second buried point identifier are different buried point identifiers; and/or changing first buried point acquisition information in the initial buried point configuration information into second buried point acquisition information, wherein the first buried point acquisition information and the second buried point acquisition information are different buried point acquisition information; and changing the buried point of the control to be processed and/or the buried point acquisition information.

6. The method of any of claims 1-2, wherein when the initial buried point configuration information does not include: the control identification to be processed, the buried point identification and the buried point acquisition information are related, and the buried point setting instruction is used for indicating that when the buried point is set for the control to be processed,

and adding the association relation among the control identification to be processed, the designated buried point identification and the designated buried point acquisition information into the initial buried point configuration information so as to set buried points for acquiring the designated buried point acquisition information for the control to be processed.

7. The method of claim 1, wherein the sending the updated buried point configuration file specifically comprises:

uploading the updated embedded point configuration file to a cloud server, so that the user terminal equipment can acquire the updated embedded point configuration file from the cloud server when the carried target application client of the designated version is started.

8. The method of claim 1, wherein one of the embedded point profiles corresponds to a target application client of an application version in an operating system.

9. The buried point setting method is characterized by being applied to terminal equipment, wherein the terminal equipment is carried with a target application client of a designated version, and the method comprises the following steps:

acquiring triggering operation of the target application client;

acquiring the embedded point configuration file of the appointed version from a cloud server; the buried point profile generated according to the method of claim 1;

the cloud server only stores the last updated embedded point configuration file of the appointed version;

10. The method of claim 9, wherein the obtaining a trigger operation for the target application client specifically comprises:

and when the target application client is in the exit state, acquiring a starting operation of the target application client.

11. The method of claim 10, wherein the obtaining the specified version of the embedded point configuration file from the cloud server specifically comprises:

generating a buried point configuration file acquisition request, wherein the configuration file acquisition request is used for requesting to acquire the buried point configuration file of the appointed version of the target application client;

sending the embedded point configuration file acquisition request to a cloud server;

and receiving the embedded point configuration file fed back by the cloud server.

12. The method of claim 11, wherein the buried point configuration information in the buried point configuration file comprises: the control identification, the buried point identification and the buried point acquisition information are related; setting the embedded point of the target application client according to the embedded point configuration file specifically includes:

replacing an old version embedded point configuration file of the target application client pre-stored in the terminal equipment by using the embedded point configuration file;

And setting the buried point of the designated control in the target application client as the buried point indicated by the buried point identifier with the association relation with the control identifier of the designated control according to the buried point configuration file, so as to acquire buried point acquisition information with the association relation with the control identifier of the designated control when the designated control is triggered.

13. A buried point setting device, characterized by being applied to a server, comprising:

14. The buried point setting device is characterized by being applied to terminal equipment, wherein a target application client of a designated version is carried on the terminal equipment, and the buried point setting device comprises:

15. A buried point setting apparatus, characterized by comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

Acquiring a buried point setting instruction input by an operation user;

16. A buried point setting apparatus, characterized by comprising:

at least one processor; the method comprises the steps of,

a memory communicatively coupled to the at least one processor; wherein,

17. A computer readable storage medium storing computer executable instructions that when executed by a processor perform the steps of:

acquiring a buried point setting instruction input by an operation user;

18. A computer readable storage medium storing computer executable instructions that when executed by a processor perform the steps of: