CN110990743B

CN110990743B - Method and device for determining unloading rate of application program and electronic equipment

Info

Publication number: CN110990743B
Application number: CN201911221048.4A
Authority: CN
Inventors: 祝威
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Shanghai Ant Chuangjiang Information Technology Co ltd
Priority date: 2019-12-03
Filing date: 2019-12-03
Publication date: 2023-11-14
Anticipated expiration: 2039-12-03
Also published as: CN110990743A

Abstract

The specification provides a method and a device for determining an application program uninstallation rate and electronic equipment, wherein the method for determining the application program uninstallation rate comprises the following steps: obtaining a push message required to be pushed to a target application; the push message is packaged and then sent to a push server; determining the sending quantity of the push messages according to the response sent by the push server; receiving a first log file sent by a buried point component in the target application; determining the receiving quantity of the push message according to the receiving state information in the first log file; and determining the unloading rate of the target application according to the sending quantity of the push messages and the receiving quantity of the push messages. The method and the device can improve the statistical accuracy of the application program unloading rate, and the log file is reported in real time, so that the application unloading rate can be counted conveniently and rapidly, and the time delay for counting the application unloading rate is shortened.

Description

Method and device for determining unloading rate of application program and electronic equipment

[ field of technology ]

The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for determining an application program uninstallation rate, and an electronic device.

[ background Art ]

For the existing mobile operation system, after a target Application (App) performs a marketing campaign by pushing a message, a marketer cannot count how many users still keep the target App on the electronic device (for example, a smart phone or a tablet computer) used. This requires statistics of the target App's offload rate.

Taking the mobile operating system as the iOS as an example, in the prior art, an application server corresponding to the target App in the iOS is counted to determine whether the push message is successfully pushed according to the response state of the apple push notification service (Apple Push Notification service; abbreviated as: APNs hereinafter), so as to calculate the target App unloading rate. However, the above method can only roughly calculate the unloading rate of the target App, cannot accurately count how many iOS devices actually unload the target App.

[ invention ]

The embodiment of the specification provides a method, a device and electronic equipment for determining the unloading rate of an application program, so that the unloading rate of the application program is counted according to a log file reported by the application, the counting accuracy of the unloading rate of the application program is improved, the log file is reported in real time, the unloading rate of the application can be counted conveniently and rapidly, and the time delay for counting the unloading rate of the application is shortened.

In a first aspect, an embodiment of the present disclosure provides a method for determining an unloading rate of an application program, including: obtaining a push message required to be pushed to a target application; the push message is packaged and then sent to a push server; after the push server pushes the push message to the electronic equipment, determining the sending quantity of the push message according to the response sent by the push server; the target application is installed on the electronic equipment, and the target application successfully registers for push service; receiving a first log file sent by a buried point component in the target application, wherein the first log file comprises receiving state information of the target application on the push message and a user identifier using the target application; determining the receiving quantity of the push message according to the receiving state information in the first log file; and determining the unloading rate of the target application according to the sending quantity of the push messages and the receiving quantity of the push messages.

In one possible implementation manner, the determining, according to the number of sent push messages and the number of received push messages, the unloading rate of the target application includes: and calculating a difference value between the sending quantity of the push messages and the receiving quantity of the push messages, and calculating a ratio between the difference value and the sending quantity of the push messages, wherein the ratio is the unloading rate of the target application.

In one possible implementation manner, the first log file further includes status information of whether a user using the target application opens a push permission switch; after receiving the first log file sent by the embedded point component in the target application, the method further includes: determining the receiving quantity of the push messages according to the receiving state information in the first log file, and determining the quantity of the target applications of which the push permission switch is closed according to the state information of whether the user using the target application in the first log file opens the push permission switch; and determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

In one possible implementation manner, the determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications with the push permission switch closed includes: calculating a difference value between the sending number of the push messages and the number of the target applications of which the push permission switch is closed; and calculating the ratio between the received quantity of the push messages and the difference value, wherein the ratio is the unloading rate of the target application.

In one possible implementation manner, the first log file sent by the embedded point component is an extension component that sends the push message to the target application after the electronic device receives the push message, and after the extension component obtains the user identifier of the target application, the push message and the user identifier are sent to the embedded point component, and the push message and the user identifier are generated and sent by the embedded point component.

In one possible implementation manner, the method further includes: receiving a second log file sent by a buried point component in the target application, wherein the second log file is generated according to a click event of a user on the push message after the push message is clicked by the user using the target application by the target application; the second log file comprises click events of the push message by the user; determining the clicked quantity of the push message according to the second log file; and determining the reason why the target application is unloaded according to the change condition of the clicked quantity of the push message within the preset time length.

In a second aspect, an embodiment of the present disclosure provides a method for determining an unloading rate of an application program, including: the method comprises the steps that an expansion component of a target application receives push information, the target application is installed on electronic equipment, the target application successfully registers push service, the push information is sent to the electronic equipment by a push server, and then the push information is sent to the expansion component of the target application by the electronic equipment; the extension component of the target application obtains a user identifier of the target application, and sends the push message and the user identifier to the embedded point component of the target application; and the embedded point component of the target application generates a first log file according to the push message and the user identifier, and sends the first log file to an application server corresponding to the target application, so that the application server calculates the unloading rate of the target application according to the first log file.

In one possible implementation manner, after the sending the first log file to the application server corresponding to the target application, the method further includes: the target application displays the push message.

In one possible implementation manner, before the extension component of the target application receives the push message, the method further includes: after a user using the target application logs in the target application, the target application acquires and stores a user identification of the user; and the target application sends the equipment token of the electronic equipment to a push server through a front-end server to register push service.

In one possible implementation manner, after the target application displays the push message, the method further includes: the target application obtains a click event of the push message by a user using the target application; the target application sends the click event to a buried point component of the target application; and the embedded point component of the target application generates a second log file according to the click event of the user on the push message, and sends the second log file to the application server, so that the application server determines the reason why the target application is unloaded according to the second log file.

In a third aspect, an embodiment of the present disclosure provides a device for determining an unloading rate of an application program, including: the acquisition module is used for acquiring push messages to be pushed to the target application; the packaging module is used for packaging the push message and then sending the push message to a push server; the determining module is used for determining the sending quantity of the push messages according to the response sent by the push server after the push server pushes the push messages to the electronic equipment; the target application is installed on the electronic equipment, and the target application successfully registers for push service; the receiving module is used for receiving a first log file sent by a buried point component in the target application, wherein the first log file comprises the receiving state information of the target application on the push message and a user identifier using the target application; the determining module is further configured to determine a received number of the push message according to the received status information in the first log file received by the receiving module; and determining the unloading rate of the target application according to the sending quantity of the push messages and the receiving quantity of the push messages.

In one possible implementation manner, the determining module is specifically configured to calculate a difference between the number of sent push messages and the number of received push messages, and calculate a ratio between the difference and the number of sent push messages, where the ratio is an unloading rate of the target application.

In one possible implementation manner, the first log file further includes status information of whether a user using the target application opens a push permission switch; the determining module is further configured to determine, after the receiving module receives a first log file sent by a buried point component in the target application, a received number of the push messages according to receiving status information in the first log file, and determine, according to status information of whether a user using the target application in the first log file opens a push permission switch, a number of target applications in which the push permission switch is closed; and determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

In one possible implementation manner, the determining module is specifically configured to calculate a difference between the number of sent push messages and the number of target applications that the push permission switch is turned off; and calculating the ratio between the received quantity of the push messages and the difference value, wherein the ratio is the unloading rate of the target application.

In one possible implementation manner, the receiving module is further configured to receive a second log file sent by a buried point component in the target application, where the second log file is generated by the buried point component according to a click event of the user on the push message after the push message is clicked by the user using the target application and the push message is displayed by the target application; the second log file comprises click events of the push message by the user; the determining module is further configured to determine, according to the second log file, a number of clicked push messages; and determining the reason why the target application is unloaded according to the change condition of the clicked quantity of the push message within a preset time length.

In a fourth aspect, an embodiment of the present disclosure provides a device for determining an unloading rate of an application program, including: the receiving module is used for receiving push information, wherein the push information is sent to the electronic equipment by the push server and then sent to the expansion component of the target application by the electronic equipment, the target application is installed on the electronic equipment, and the target application successfully registers push service; the acquisition module is used for acquiring the user identification using the target application; the first sending module is used for sending the push message received by the receiving module and the user identification acquired by the acquiring module; the generation module is used for receiving the push message and the user identifier sent by the first sending module and generating a first log file according to the push message and the user identifier; and the second sending module is used for sending the first log file generated by the generating module to an application server corresponding to the target application so that the application server calculates the unloading rate of the target application according to the first log file.

In one possible implementation manner, the apparatus further includes: and the display module is used for displaying the push message after the second sending module sends the first log file to the application server corresponding to the target application.

In one possible implementation manner, the apparatus further includes: the storage module is used for acquiring and storing the user identification of the user after the user using the target application logs in the target application before the receiving module receives the push message; and the registration module is used for sending the device token of the electronic device to the push server through the front-end server to register the push service.

In a fifth aspect, embodiments of the present disclosure provide an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method provided in the first aspect.

In a sixth aspect, the present description embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the method provided in the first aspect.

In a seventh aspect, embodiments of the present disclosure provide an electronic device, including: at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method provided in the second aspect.

In an eighth aspect, the present description embodiments provide a non-transitory computer-readable storage medium storing computer instructions that cause the computer to perform the method provided in the second aspect.

In the above technical solution, after obtaining a push message to be pushed to a target application, the push message is encapsulated and then sent to a push server, and after the push server pushes the push message to an electronic device, the number of sent push messages is determined according to a response sent by the push server. Then, a first log file sent by a buried point component in the target application is received, the receiving quantity of the push message is determined according to the receiving state information in the first log file, and the unloading rate of the target application is determined according to the sending quantity of the push message and the receiving quantity of the push message, so that statistics on the unloading rate of the application according to the log file reported by the application can be realized, the statistical accuracy of the unloading rate of the application program is improved, the log file is reported in real time, the unloading rate of the application can be counted conveniently and rapidly, and the time delay for counting the unloading rate of the application is shortened.

[ description of the drawings ]

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

FIG. 1 is a flow chart of one embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 2 is a flow chart of another embodiment of a method for determining an application uninstallation rate according to the present disclosure;

FIG. 3 is a flow chart of yet another embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 4 is a flow chart of yet another embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 5 is a flow chart of yet another embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 6 is a flow chart of yet another embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 7 is a flow chart of yet another embodiment of a method for determining an application uninstallation rate of the present disclosure;

FIG. 8 is a flow chart of yet another embodiment of a method for determining an application uninstallation rate of the present disclosure;

FIG. 9 is a flow chart of yet another embodiment of a method of determining an application uninstallation rate of the present disclosure;

FIG. 10 is a schematic diagram illustrating an embodiment of an apparatus for determining an application uninstallation rate according to the present disclosure;

FIG. 11 is a schematic diagram illustrating another embodiment of an apparatus for determining an unloading rate of an application program according to the present disclosure;

fig. 12 is a schematic structural view of an embodiment of the electronic device of the present specification.

[ detailed description ] of the invention

For a better understanding of the technical solutions of the present specification, embodiments of the present specification are described in detail below with reference to the accompanying drawings.

It should be understood that the described embodiments are only some, but not all, of the embodiments of the present description. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present disclosure.

The terminology used in the embodiments of the description presented herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description presented herein. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

FIG. 1 is a flowchart illustrating an embodiment of a method for determining an application uninstallation rate according to the present disclosure, where, as shown in FIG. 1, the method for determining an application uninstallation rate may include:

step 101, obtaining a push message to be pushed to a target application.

The target application is an application needing to count the unloading rate; the push message to be pushed to the target application may be sent to the application server corresponding to the target application after the operator of the target application edits the push message, so that the application server corresponding to the target application may obtain the push message to be pushed to the target application.

Step 102, the push message is packaged and then sent to a push server.

Specifically, the push server may be a server having a push function, for example: apple server, this embodiment is not limited thereto.

After the application server corresponding to the target application obtains the push message to be pushed to the target application, the push message can be encapsulated, the push message is encapsulated into a message format suitable for being transmitted to the push server, and then the encapsulated push message is sent to the push server.

Step 103, after the push server pushes the push message to the electronic device, determining the number of the push messages according to the response sent by the push server.

The target application is installed on the electronic equipment, and the target application successfully registers the push service.

Specifically, after the push server pushes the push message to the electronic device, a response is sent to an application server corresponding to the target application to inform the sending state of the push message, and the application server can determine the sending quantity of the push message according to the response sent by the push server.

Step 104, receiving a first log file sent by a buried point component in the target application, where the first log file includes receiving status information of the target application on the push message and a user identifier using the target application.

In this embodiment, a buried point component is disposed in the target application, and the first log file sent by the buried point component is generated and sent by the buried point component after the electronic device receives the push message, and then sends the push message to an extension component of the target application, where the extension component obtains a user identifier using the target application, and then sends the push message and the user identifier to the buried point component.

In a specific implementation, the embedded point component may encrypt the generated first log file, and then send the encrypted first log file to an application server corresponding to the target application; in the encryption, an RSA encryption algorithm may be used, which is not limited in this embodiment.

Step 105, determining the number of received push messages according to the receiving status information in the first log file.

Specifically, the receiving status information includes a time when the target application receives the push message, a content and/or a type of the push message, and the like, so that the application server corresponding to the target application can determine the receiving quantity of the push message according to the receiving status information in the first log file.

And 106, determining the unloading rate of the target application according to the sending quantity of the push messages and the receiving quantity of the push messages.

Specifically, according to the number of sent push messages and the number of received push messages, determining the offload rate of the target application may be: and calculating a difference value between the sending quantity of the push messages and the receiving quantity of the push messages, and calculating a ratio between the difference value and the sending quantity of the push messages, wherein the ratio is the unloading rate of the target application.

In the method for determining the unloading rate of the application program, after the push message required to be pushed to the target application is obtained, the push message is packaged and then sent to a push server, and after the push server pushes the push message to the electronic device, the sending quantity of the push message is determined according to the response sent by the push server. Then, a first log file sent by a buried point component in the target application is received, the receiving quantity of the push message is determined according to the receiving state information in the first log file, and the unloading rate of the target application is determined according to the sending quantity of the push message and the receiving quantity of the push message, so that statistics on the unloading rate of the application according to the log file reported by the application can be realized, the statistical accuracy of the unloading rate of the application program is improved, the log file is reported in real time, the unloading rate of the application can be counted conveniently and rapidly, and the time delay for counting the unloading rate of the application is shortened.

FIG. 2 is a flowchart of another embodiment of a method for determining an application uninstallation rate in the present disclosure, where in this embodiment, the first log file may further include status information of whether a user using the target application opens a push permission switch; thus, as shown in fig. 2, in the embodiment shown in fig. 1 of the present specification, after step 104, the method may further include:

Step 201, determining the number of received push messages according to the received state information in the first log file, and determining the number of target applications with the push permission switch closed according to the state information of whether the user using the target application in the first log file opens the push permission switch.

Step 202, determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

Specifically, according to the number of sent push messages, the number of received push messages, and the number of target applications for which the push permission switch is turned off, determining the unloading rate of the target applications may be: calculating a difference between the number of the sent push messages and the number of the target applications for which the push permission switch is turned off; and calculating the ratio between the received number of the push messages and the difference value, wherein the ratio is the unloading rate of the target application.

Since the target application cannot receive the push message after the push permission switch is turned off, but this does not indicate that the target application is unloaded, when calculating the unloading rate of the target application, the number of target applications for which the push permission switch is turned off needs to be subtracted from the number of sending the push message, so that the unloading rate obtained by calculation can be more accurate.

FIG. 3 is a flowchart illustrating a further embodiment of a method for determining an application offload rate according to the present disclosure, where, as shown in FIG. 3, the method for determining an application offload rate may further include:

step 301, receiving a second log file sent by a buried point component in the target application, where the second log file is generated by the buried point component according to a click event of the user on the push message after the target application displays the push message and the user using the target application clicks the push message; the second log file includes a click event of the push message by the user.

Step 302, determining the number of clicked push messages according to the second log file.

Step 303, determining the reason why the target application is unloaded according to the change condition of the clicked number of the push messages within the predetermined time.

The predetermined time period may be set by itself according to system performance and/or implementation requirements, and the embodiment does not limit the length of the predetermined time period.

For example, the predetermined time period may be 7 days, and the application server corresponding to the target application may count the number of clicked push messages every day, and then determine the reason why the target application is unloaded according to the change condition of the number of clicked push messages within 7 days. Assuming that the unloading rate of the target application increases sharply on a certain day, and the number of clicked push messages on the same day decreases than that on the previous day, it is known that the unloading rate increases on the same day due to the higher frequency of push messages.

In a specific implementation, the steps 301 to 303 may be executed in parallel with the steps 104 to 106 or sequentially, and the execution order of the steps 301 to 303 and the steps 104 to 106 is not limited in the embodiment of the present disclosure, and the steps 301 to 303 may be executed after the step 103. In fig. 3, steps 301 to 303 are shown as an example after step 106.

Fig. 4 is a flowchart of still another embodiment of a method for determining an unloading rate of an application program according to the present disclosure, where, as shown in fig. 4, the method for determining an application program may include:

in step 401, an extension component of a target application receives a push message, where the target application is installed on an electronic device, and the target application successfully registers for a push service, where the push message is sent by a push server to the electronic device, and then sent by the electronic device to the extension component of the target application.

In this embodiment, an extension component is disposed in a target application, and after a push server sends a push message to an electronic device, the electronic device sends the push message to the extension component of the target application.

Step 402, the extension component of the target application obtains the user identifier of the target application, and sends the push message and the user identifier to the embedded point component of the target application.

And step 403, the embedded point component of the target application generates a first log file according to the push message and the user identifier, and sends the first log file to an application server corresponding to the target application, so that the application server calculates the unloading rate of the target application according to the first log file.

Fig. 5 is a flowchart of still another embodiment of the method for determining an application program uninstallation rate according to the present disclosure, as shown in fig. 5, in the embodiment of fig. 4 according to the present disclosure, after step 403, the method may further include:

in step 501, the target application displays the push message.

Further, after step 501, the method may further include:

in step 502, the target application obtains a click event of the push message by a user using the target application.

In step 503, the target application sends the click event to the embedded point component of the target application.

In step 504, the embedded component of the target application generates a second log file according to the click event of the user on the push message, and sends the second log file to the application server, so that the application server determines the reason why the target application is unloaded according to the second log file.

Fig. 6 is a flowchart of still another embodiment of the method for determining an application program uninstallation rate according to the present disclosure, as shown in fig. 6, in the embodiment of fig. 4 according to the present disclosure, before step 401, the method may further include:

in step 601, after a user using the target application logs in the target application, the target application obtains and stores a user identifier of the user.

In step 602, the target application sends the device token of the electronic device to the push server through the front-end server, and performs push service registration.

The method for determining the unloading rate of the application program provided in the embodiment of the present specification is described below by taking the target application as a Dana wallet and the push server as an Apple server as an example.

Fig. 7 is a flowchart of another embodiment of a method for determining an application uninstallation rate according to the present disclosure, where the present embodiment describes a procedure of push service registration by Dana wallet. As shown in fig. 7, may include:

step 701, a user using the target application logs into the Dana wallet.

In step 702, the dana wallet obtains the user identifier of the user, and caches the user identifier in an App Groups sandbox.

In step 703, dana wallet registers and reports the device token to the front-end server.

In this embodiment, the device token may be a device token of an electronic device installed with a Dana wallet, and the front-end server may be an Mpaas server.

The front-end server sends the device token to the Apple server, step 704.

In step 705, the apple server returns a response to the front end server that the push service registration was successful.

In step 706, the front-end server returns a response to the Dana wallet that the push service registration was successful.

Fig. 8 is a flowchart of yet another embodiment of a method for determining an application offload rate in the present specification, which describes a flow for sending a push message to a Dana wallet. As shown in fig. 8, may include:

in step 801, the operation of the Dana wallet sends a push message to be pushed to the Dana server.

Step 802, the dana server encapsulates the push message, and encapsulates the push message into a message format suitable for transmission to the Apple server.

In step 803, the dana server sends the encapsulated push message to the Apple server.

In step 804, the apple server pushes the push message onto the electronic device.

The electronic device is an electronic device provided with a Dana application.

In step 805, the apple server sends a response to the Dana server to inform the sending status of the push message.

Thus, the Dana server can determine the number of the push messages sent according to the response sent by the Apple server.

Step 806, the electronic device sends the push message to the expansion component of the Dana application.

In step 807, the expansion component of the Dana application obtains the user identification using the Dana wallet from the Dana application.

In step 808, the extension component of the dana application sends the push message and the user identifier to the embedded point component of the target application.

And step 809, generating a first log file by the embedded point component of the target application according to the push message and the user identifier, and sending the first log file to the Dana server.

In this way, the Dana server may determine the number of received push messages according to the reception status information in the first log file.

The Dana server may then calculate the offload rate of the Dana wallet in the manner provided by step 106 in the embodiment of fig. 1 of the present description.

In step 810, the expansion component of the Dana wallet sends the push message to the Dana wallet to display the push message.

Fig. 9 is a flowchart of another embodiment of a method for determining an application uninstallation rate according to the present disclosure, where the embodiment describes a procedure for clicking a push message by a user. As shown in fig. 9, may include:

Step 901, a user using Dana wallet clicks on a push message.

In step 902, the dana wallet sends a click event of the user on the push message to a buried point component of the target application.

Specifically, when the Dana wallet sends the click event to the buried point component, an RSA encryption algorithm may be used to encrypt the click event.

In step 903, the embedded component of the dana application generates a second log file according to the click event of the user on the push message, and sends the second log file to the application server, so that the application server determines, according to the second log file, a reason why the target application is uninstalled.

In the method for determining the unloading rate of the application program provided by the embodiment of the specification, the embedded point component of the target application responds to the push message in real time, and the generated first log file can be encrypted and then sent to the corresponding application server, so that the reliability and the safety of the data are ensured. The subsequent application server may calculate the uninstalling rate of the target application according to the first log file, and may analyze the use viewing angle of the user and the reason for uninstalling the application program, and identify whether the user is the user who reinstalls the target application for the repeated uninstallation of the card. In addition, by adopting the method provided by the embodiment of the specification, even if the target application is not opened, as long as the user installs the target application and the push switch is opened, the target application can receive the push message and perform the functions of data encryption, log reporting and the like. In addition, according to the response sent by the push server, the sending state information of the push message can be obtained, and the situation that the network-free push does not arrive can be eliminated.

Fig. 10 is a schematic structural diagram of an embodiment of an application program unloading rate determining apparatus in this embodiment, where the application program unloading rate determining apparatus in this embodiment may be used as an electronic device or a part of an electronic device to implement the application program unloading rate determining method provided in the embodiments shown in fig. 1 to 3 in this specification. In this embodiment, the electronic device may be an application server corresponding to the target application.

As shown in fig. 10, the above-mentioned apparatus for determining an application uninstallation rate may include: an acquisition module 1001, a packaging module 1002, a determination module 1003, and a reception module 1004;

the acquiring module 1001 is configured to acquire a push message that needs to be pushed to a target application; the target application is an application needing to count the unloading rate; the push message to be pushed to the target application may be sent to the application server corresponding to the target application after the operator of the target application edits the push message, so that the obtaining module 1001 may obtain the push message to be pushed to the target application.

The encapsulation module 1002 is configured to encapsulate the push message and send the encapsulated push message to a push server; specifically, the push server may be a server having a push function, for example: apple server, this embodiment is not limited thereto.

After the obtaining module 1001 obtains the push message that needs to be pushed to the target application, the encapsulation module 1002 may encapsulate the push message, encapsulate the push message into a message format suitable for transmitting to the push server, and then send the encapsulated push message to the push server.

A determining module 1003, configured to determine, according to a response sent by the push server, a sending number of the push messages after the push server pushes the push messages to the electronic device; the target application is installed on the electronic equipment, and the target application successfully registers push service; specifically, after the push server pushes the push message to the electronic device, a response is sent to the application server corresponding to the target application, so as to inform the sending state of the push message, and the determining module 1003 may determine, according to the response sent by the push server, the sending number of the push message.

A receiving module 1004, configured to receive a first log file sent by a buried point component in the target application, where the first log file includes receiving status information of the target application on the push message and a user identifier that uses the target application; in this embodiment, a buried point component is disposed in the target application, and the first log file sent by the buried point component is generated and sent by the buried point component after the electronic device receives the push message, and then sends the push message to an extension component of the target application, where the extension component obtains a user identifier using the target application, and then sends the push message and the user identifier to the buried point component.

A determining module 1003, configured to determine a number of received push messages according to the receiving status information in the first log file received by the receiving module 1004; and determining the unloading rate of the target application according to the sending number of the push messages and the receiving number of the push messages.

Specifically, the receiving status information includes a time when the target application receives the push message, a content and/or a type of the push message, and so on, so that the determining module 1003 may determine the number of received push messages according to the receiving status information in the first log file.

In this embodiment, the determining module 1003 is specifically configured to calculate a difference between the number of sent push messages and the number of received push messages, and calculate a ratio between the difference and the number of sent push messages, where the ratio is an unloading rate of the target application.

Further, the first log file further includes status information of whether the user using the target application opens the push permission switch; in this way, the determining module 1003 is further configured to determine, after the receiving module 1004 receives the first log file sent by the embedded point component in the target application, the number of received push messages according to the receiving status information in the first log file, and determine, according to the status information of whether the user using the target application in the first log file opens the push permission switch, the number of target applications in which the push permission switch is closed; and determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

In this embodiment, the determining module 1003 is specifically configured to calculate a difference between the number of sent push messages and the number of target applications for which the push permission switch is turned off; and calculating the ratio between the received number of the push messages and the difference value, wherein the ratio is the unloading rate of the target application.

The receiving module 1004 is further configured to receive a second log file sent by the embedded point component in the target application, where the second log file is generated by the embedded point component according to a click event of the user on the push message after the target application displays the push message and a user using the target application clicks the push message; the second log file comprises click events of the user on the push message;

a determining module 1003, configured to determine, according to the second log file, a number of clicked push messages; and determining the reason why the target application is unloaded according to the change condition of the clicked number of the push messages within a preset time length.

In the above-mentioned determining device for application program unloading rate, after the obtaining module 1001 obtains a push message to be pushed to a target application, the encapsulation module 1002 encapsulates the push message and sends the encapsulated push message to a push server, and after the push server pushes the push message to an electronic device, the determining module 1003 determines the sending number of the push message according to a response sent by the push server. Then, the receiving module 1004 receives the first log file sent by the embedded point component in the target application, the determining module 1003 determines the receiving number of the push message according to the receiving state information in the first log file, and determines the unloading rate of the target application according to the sending number of the push message and the receiving number of the push message, so that statistics on the unloading rate of the application according to the log file reported by the application can be realized, the statistical accuracy of the unloading rate of the application program is improved, the log file is reported in real time, statistics on the unloading rate of the application can be conveniently and rapidly performed, and the time delay for counting the unloading rate of the application is shortened.

Fig. 11 is a schematic structural diagram of another embodiment of an application program unloading rate determining apparatus in this embodiment, where the application program unloading rate determining apparatus in this embodiment may be used as an electronic device or a part of an electronic device to implement the application program unloading rate determining method provided in the embodiments shown in fig. 4 to 6 in this specification. In this embodiment, the electronic device may be an electronic device for installing a target application.

As shown in fig. 11, the above-mentioned apparatus for determining an application uninstallation rate may include: a receiving module 1101, an acquiring module 1102, a first transmitting module 1103, a generating module 1104 and a second transmitting module 1105;

the receiving module 1101 is configured to receive a push message, where the push message is sent by a push server to an electronic device, and then sent by the electronic device to an extension component of a target application, where the target application is installed on the electronic device, and the target application successfully registers for a push service.

An obtaining module 1102, configured to obtain a user identifier using the target application;

a first sending module 1103, configured to send the push message received by the receiving module 1101 and the user identifier acquired by the acquiring module 1102;

a generating module 1104, configured to receive the push message and the user identifier sent by the first sending module 1103, and generate a first log file according to the push message and the user identifier;

the second sending module 1105 is configured to send the first log file generated by the generating module 1104 to an application server corresponding to the target application, so that the application server calculates an unloading rate of the target application according to the first log file.

The functions of the receiving module 1101, the obtaining module 1102 and the first sending module 1103 may be implemented by an extension component in the target application, and the functions of the generating module 1104 and the second sending module 1105 may be implemented by a buried component in the target application.

Further, the above-mentioned apparatus for determining an application program uninstallation rate may further include: a display module 1106, a save module 1107, and a registration module 1108;

the display module 1106 is configured to display the push message after the second sending module 1105 sends the first log file to an application server corresponding to the target application.

A saving module 1107, configured to acquire and save a user identifier of a user who uses the target application after the user logs in the target application before the receiving module 1101 receives the push message;

the registration module 1108 is configured to send the device token of the electronic device to the push server through the front-end server, and perform push service registration.

FIG. 12 is a schematic diagram illustrating one embodiment of an electronic device of the present disclosure, as shown in FIG. 12, which may include at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to perform the method for determining the application program uninstallation rate provided in the embodiments shown in fig. 1 to 3 of the present specification.

The electronic device may be a server, for example: the form of the electronic device is not limited in this embodiment by the application server corresponding to the target application.

Fig. 12 shows a block diagram of an exemplary electronic device suitable for use in implementing embodiments of the present description. The electronic device shown in fig. 12 is only an example, and should not be construed as limiting the functionality and scope of use of the embodiments herein.

As shown in fig. 12, the electronic device is in the form of a general purpose computing device. Components of an electronic device may include, but are not limited to: one or more processors 410, a memory 430, and a communication bus 440 that connects the various system components (including the memory 430 and the processing unit 410).

The communication bus 440 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry Standard architecture (Industry Standard Architecture; hereinafter ISA) bus, micro channel architecture (Micro Channel Architecture; hereinafter MAC) bus, enhanced ISA bus, video electronics standards Association (Video Electronics Standards Association; hereinafter VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnection; hereinafter PCI) bus.

Electronic devices typically include a variety of computer system readable media. Such media can be any available media that can be accessed by the electronic device and includes both volatile and nonvolatile media, removable and non-removable media.

Memory 430 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) and/or cache memory. The electronic device may further include other removable/non-removable, volatile/nonvolatile computer system storage media. Although not shown in fig. 12, a magnetic disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable nonvolatile optical disk (e.g., a compact disk read only memory (Compact Disc Read Only Memory; hereinafter CD-ROM), digital versatile read only optical disk (Digital Video Disc Read Only Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to communication bus 440 by one or more data medium interfaces. Memory 430 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the present description.

A program/utility having a set (at least one) of program modules may be stored in the memory 430, such program modules including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules typically carry out the functions and/or methods of the embodiments described herein.

The electronic device may also communicate with one or more external devices (e.g., keyboard, pointing device, display, etc.), with one or more devices that enable a user to interact with the electronic device, and/or with any device (e.g., network card, modem, etc.) that enables the electronic device to communicate with one or more other computing devices. Such communication may occur through communication interface 420. Moreover, the electronic device may also communicate with one or more networks (e.g., local area network (Local Area Network; hereinafter: LAN), wide area network (Wide Area Network; hereinafter: WAN) and/or a public network, such as the Internet) via a network adapter (not shown in FIG. 12) that may communicate with other modules of the electronic device via the communication bus 440. It should be appreciated that although not shown in fig. 12, other hardware and/or software modules may be used in connection with an electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Arrays of Independent Drives; hereinafter RAID) systems, tape drives, data backup storage systems, and the like.

The processor 410 executes programs stored in the memory 430 to perform various functional applications and data processing, for example, to implement the method for determining an application program uninstallation rate provided in the embodiment shown in fig. 1 to 3 of the present specification.

Embodiments of the present disclosure also provide an electronic device that may include at least one processor; and at least one memory communicatively coupled to the processor, wherein: the memory stores program instructions executable by the processor, and the processor invokes the program instructions to perform the method for determining the application program uninstallation rate provided in the embodiments shown in fig. 4 to 6 of the present specification.

The electronic device may be an electronic device for installing a target application, and the form of the electronic device is not limited in this embodiment, and the electronic device may be implemented by using the structure shown in fig. 12, which is not described herein again.

The embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer instructions for causing a computer to execute the method for determining the application program uninstallation rate provided in the embodiments shown in fig. 1 to 3 of the present disclosure.

The embodiments of the present disclosure also provide a non-transitory computer readable storage medium storing computer instructions for causing a computer to execute the method for determining the application program uninstallation rate provided in the embodiments shown in fig. 4 to 6 of the present disclosure.

The non-transitory computer readable storage media described above may employ any combination of one or more computer readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory; EPROM) or flash Memory, an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for the present specification may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a local area network (Local Area Network; hereinafter: LAN) or a wide area network (Wide Area Network; hereinafter: WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present specification. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present specification, the meaning of "plurality" means at least two, for example, two, three, etc., unless explicitly defined otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present specification in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present specification.

Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.

It should be noted that, the terminals in the embodiments of the present disclosure may include, but are not limited to, a personal Computer (Personal Computer; hereinafter referred to as a PC), a personal digital assistant (Personal Digital Assistant; hereinafter referred to as a PDA), a wireless handheld device, a Tablet Computer (Tablet Computer), a mobile phone, an MP3 player, an MP4 player, and the like.

In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

In addition, each functional unit in each embodiment of the present specification may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.

The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a Processor (Processor) to perform part of the steps of the methods described in the embodiments of the present specification. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (hereinafter referred to as ROM), a random access Memory (Random Access Memory) and various media capable of storing program codes such as a magnetic disk or an optical disk.

The foregoing description of the preferred embodiments is provided for the purpose of illustration only, and is not intended to limit the scope of the disclosure, since any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the disclosure are intended to be included within the scope of the disclosure.

Claims

1. A method for determining an application uninstallation rate, comprising:

obtaining a push message required to be pushed to a target application;

the push message is packaged and then sent to a push server;

after the push server pushes the push message to the electronic equipment, determining the sending quantity of the push message according to the response sent by the push server; the target application is installed on the electronic equipment, and the target application successfully registers for push service;

receiving a first log file sent by a buried point component in the target application, wherein the first log file comprises receiving state information of the target application on the push message and a user identifier using the target application;

the first log file further comprises state information of whether a user using the target application opens a push permission switch or not;

after receiving the first log file sent by the embedded point component in the target application, the method further includes:

Determining the receiving quantity of the push messages according to the receiving state information in the first log file, and determining the quantity of the target applications of which the push permission switch is closed according to the state information of whether the user using the target application in the first log file opens the push permission switch;

and determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

2. The method of claim 1, wherein determining the offload rate of the target application according to the number of sent push messages, the number of received push messages, and the number of target applications for which the push permission switch is closed comprises:

calculating a first difference between the number of sent push messages and the number of target applications for which the push permission switch is turned off;

calculating a second difference between the first difference and the received number of push messages;

and calculating a ratio between the second difference value and the first difference value, wherein the ratio is the unloading rate of the target application.

3. The method of claim 1, wherein the first log file sent by the embedded point component is an extension component that sends the push message to the target application after the electronic device receives the push message, and the extension component obtains a user identifier using the target application, and then sends the push message and the user identifier to the embedded point component, and the push message and the user identifier are generated and sent by the embedded point component.

4. A method according to any one of claims 1-3, further comprising:

receiving a second log file sent by a buried point component in the target application, wherein the second log file is generated according to a click event of a user on the push message after the push message is clicked by the user using the target application by the target application; the second log file comprises click events of the push message by the user;

determining the clicked quantity of the push message according to the second log file;

and determining the reason why the target application is unloaded according to the change condition of the clicked quantity of the push message within the preset time length.

5. A method for determining an application uninstallation rate, comprising:

the method comprises the steps that an expansion component of a target application receives push information, the target application is installed on electronic equipment, the target application successfully registers push service, the push information is sent to the electronic equipment by a push server, and then the push information is sent to the expansion component of the target application by the electronic equipment;

the extension component of the target application obtains a user identifier of the target application, and sends the push message and the user identifier to the embedded point component of the target application;

The embedded point component of the target application generates a first log file according to the push message and the user identifier, and the first log file is sent to an application server corresponding to the target application, so that the application server calculates the unloading rate of the target application according to the first log file;

after the first log file is sent to the application server corresponding to the target application, the method further includes:

the target application displays the push message;

the target application obtains a click event of the push message by a user using the target application;

the target application sends the click event to a buried point component of the target application;

and the embedded point component of the target application generates a second log file according to the click event of the user on the push message, and sends the second log file to the application server, so that the application server determines the reason why the target application is unloaded according to the second log file.

6. The method of claim 5, prior to receiving a push message, the extension component of the target application further comprising:

after a user using the target application logs in the target application, the target application acquires and stores a user identification of the user;

And the target application sends the equipment token of the electronic equipment to a push server through a front-end server to register push service.

7. An apparatus for determining an application program uninstallation rate, comprising:

the acquisition module is used for acquiring push messages to be pushed to the target application;

the packaging module is used for packaging the push message and then sending the push message to a push server;

the determining module is used for determining the sending quantity of the push messages according to the response sent by the push server after the push server pushes the push messages to the electronic equipment; the target application is installed on the electronic equipment, and the target application successfully registers for push service;

the receiving module is used for receiving a first log file sent by a buried point component in the target application, wherein the first log file comprises the receiving state information of the target application on the push message and a user identifier using the target application;

the determining module is further configured to determine, after the receiving module receives a first log file sent by a buried point component in the target application, a received number of the push messages according to receiving status information in the first log file, and determine, according to status information of whether a user using the target application in the first log file opens a push permission switch, a number of target applications in which the push permission switch is closed; and determining the unloading rate of the target application according to the sending number of the push messages, the receiving number of the push messages and the number of the target applications of which the push permission switch is closed.

8. The device according to claim 7,

the determining module is specifically configured to calculate a first difference between a number of sent push messages and a number of target applications that the push permission switch is turned off; calculating a second difference between the first difference and the received number of push messages; and calculating a ratio between the second difference and the first difference, wherein the ratio is the unloading rate of the target application.

9. The apparatus of claim 7, the first log file sent by the embedded point component is an extension component that sends the push message to the target application after the electronic device receives the push message, the extension component obtains a user identification using the target application, and the push message and the user identification are sent to the embedded point component, generated and sent by the embedded point component.

10. The apparatus according to any one of claim 7 to 9,

the receiving module is further configured to receive a second log file sent by a buried point component in the target application, where the second log file is generated by the buried point component according to a click event of the user on the push message after the push message is clicked by the user using the target application and the push message is displayed by the target application; the second log file comprises click events of the push message by the user;

The determining module is further configured to determine, according to the second log file, a number of clicked push messages; and determining the reason why the target application is unloaded according to the change condition of the clicked quantity of the push message within a preset time length.

11. An apparatus for determining an application program uninstallation rate, comprising:

the receiving module is used for receiving push information, wherein the push information is sent to the electronic equipment by the push server and then sent to the expansion component of the target application by the electronic equipment, the target application is installed on the electronic equipment, and the target application successfully registers push service;

the acquisition module is used for acquiring the user identification using the target application;

the first sending module is used for sending the push message received by the receiving module and the user identification acquired by the acquiring module;

the generation module is used for receiving the push message and the user identifier sent by the first sending module and generating a first log file according to the push message and the user identifier;

the second sending module is used for sending the first log file generated by the generating module to an application server corresponding to the target application so that the application server calculates the unloading rate of the target application according to the first log file;

Wherein the apparatus further comprises:

the display module is used for displaying the push message after the second sending module sends the first log file to the application server corresponding to the target application;

the acquisition module is further used for acquiring a click event of the push message by a user using the target application;

the first sending module is further configured to send the click event;

the generating module is further configured to receive the click event sent by the first sending module, and generate a second log file according to the click event of the user on the push message;

the second sending module is further configured to send the second log file to the application server, so that the application server determines, according to the second log file, a reason why the target application is unloaded.

12. The apparatus of claim 11, further comprising:

the storage module is used for acquiring and storing the user identification of the user after the user using the target application logs in the target application before the receiving module receives the push message;

and the registration module is used for sending the device token of the electronic device to the push server through the front-end server to register the push service.

13. An electronic device, comprising:

at least one processor; and

at least one memory communicatively coupled to the processor, wherein:

the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-4.

14. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of any one of claims 1 to 4.

15. An electronic device, comprising:

at least one processor; and

at least one memory communicatively coupled to the processor, wherein:

the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 5-6.

16. A non-transitory computer readable storage medium storing computer instructions that cause the computer to perform the method of any one of claims 5 to 6.