Operation association method and device, equipment and medium
By receiving and reporting recommendation identification and operation events in the first application, the problem of low correlation accuracy between target application operations and trigger applications in the prior art is solved, and a higher precision operation association is achieved.
Patent Information
- Application Number
- CN202510612744.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2025-08-26
AI Technical Summary
The prior art cannot correlate the operations of target applications with the applications that trigger these operations by 100%, resulting in low association accuracy.
By receiving the recommendation task data and recommendation logos issued by the server, the recommendation information is displayed on the playback page of the first application, and the recommendation logo and operation event are reported to the server when the target operation instruction is received, and the target operation event is associated with the first application using the recommendation logo to avoid relying on the device identification.
Improves the accuracy of operational associations and ensures the accurate correlation of target operation events with recommended applications.
Smart Images
Figure CN120540554A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of computer technology, and in particular to operation association methods, devices, equipment, and media. Background Art
[0002] With technological advancements, it's now possible to recommend target applications within certain apps. For example, a jump button for target application B can be set on the app pages of apps A and C. After a user triggers the jump button on the app page of either app A or app C, they'll be redirected to the designated page D of target application B. Another example is a download button for target application B can be set on the app pages of apps A and C. After a user triggers the download button on the app page of either app A or app C, they'll download and install the target application B. This effectively recommends target application B within apps A and C.
[0003] Due to data isolation between apps, after executing actions targeting the target app, such as redirecting to a specific page of the target app or downloading and installing the target app's software, the target app cannot distinguish the specific app that triggered these actions. For example, after redirecting to specific page D of target app B, target app B only perceives that it has redirected to specific page D. It cannot distinguish whether the redirection to specific page D was triggered from the recommended page of app A, the recommended page of app C, or whether the user triggered it from the target app B's own app page.
[0004] Some technologies, such as device identification matching, can associate actions on target applications with the applications that trigger them. However, these technologies cannot fully associate actions on target applications with the applications that trigger them, resulting in low association accuracy. Summary of the Invention
[0005] In view of this, the present disclosure provides an operation association method, an operation association device, an electronic device, a computer-readable storage medium, and a computer program product, which can improve association accuracy.
[0006] In a first aspect, the present disclosure provides an operation association method, applied to a first application, the method comprising:
[0007] receiving recommended task data and a recommendation identifier for a second application issued by a server, wherein the recommended task data is generated based on a recommended task for the second application, and the recommendation identifier includes a task identifier of the recommended task, a time when the recommended task data was issued, and a user identifier of a target user currently logged into the first application;
[0008] Based on the recommended task data, displaying recommendation information of the second application on the playback page of the first application, where the target application component is integrated into the second application;
[0009] If a target operation instruction for the second application is received in the playback page, the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction are reported to the server, and the recommendation identifier is sent to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
[0010] In a second aspect, the present disclosure provides an operation association method, which is applied to a target application component, wherein the target application component is integrated into a second application; the method comprises:
[0011] In response to a target operation event for the second application, determining whether a recommendation identifier corresponding to the target operation event and sent by the first application is received;
[0012] If the recommendation identifier sent by the first application is received, the recommendation identifier and the target operation event are reported to the server, and the server is configured to associate the target operation event with the first application based on the recommendation identifier.
[0013] In a third aspect, the present disclosure provides an operation association device, the device comprising:
[0014] a data receiving module, configured to receive recommended task data and a recommendation identifier for a second application issued by a server, wherein the recommended task data is generated based on a recommended task for the second application, and the recommendation identifier includes a task identifier of the recommended task, a time when the recommended task data was issued, and a user identifier of a target user currently logged into the first application;
[0015] a recommendation information display module, configured to display recommendation information of the second application on the playback page of the first application based on the recommendation task data, wherein the second application integrates the target application component;
[0016] A data reporting module is used to report the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction to the server if a target operation instruction for the second application is received in the playback page, and send the recommendation identifier to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
[0017] In a fourth aspect, the present disclosure provides an operation association device, the device comprising:
[0018] a determination module, configured to determine, in response to a target operation event for the second application, whether a recommendation identifier corresponding to the target operation event and sent by the first application is received;
[0019] The data reporting module is configured to report the recommendation identifier and the target operation event to the server if the recommendation identifier is received from the first application. The server is configured to associate the target operation event with the first application based on the recommendation identifier.
[0020] In a fifth aspect, the present disclosure provides an electronic device comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the above method by executing the computer instructions.
[0021] In a sixth aspect, the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the above method.
[0022] In a seventh aspect, the present disclosure provides a computer program product, comprising computer instructions, where the computer instructions are used to enable a computer to execute the above method.
[0023] In some embodiments of the present disclosure, after receiving the recommended task data and recommendation identifier for the second application sent by the server, the first application can display the recommendation information of the second application on the playback page of the first application based on the recommended task data, and when receiving the target operation instruction for the second application on the playback page, the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction can be reported to the server, and the recommendation identifier can be sent to the target application component, so that when the target operation event of the second application is executed, the target application component can report the recommendation identifier and the target operation event to the server, and the server associates the target operation event with the first application based on the recommendation identifier. Since the recommendation identifier is generated based on the task identifier of the recommended task, the issuance time of the recommended task data, and the user identifier of the target user who is currently logged into the first application, there is no need to rely on the device identifier to associate the target operation event with the first application, so the problem of the device identifier not being able to be fully obtained can be avoided, thereby improving the association accuracy. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the related technologies, the following briefly introduces the drawings required for use in the specific embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0025] Figure 1 It is a schematic diagram of the operational association of some technologies;
[0026] Figure 2 is a flowchart of an operation association method provided by some embodiments of the present disclosure;
[0027] Figure 3 is an interactive schematic diagram of an operation association method provided by some embodiments of the present disclosure;
[0028] Figure 4 is a flowchart of an operation association method provided by other embodiments of the present disclosure;
[0029] Figure 5 is a schematic diagram of a module of an operation association device provided by some embodiments of the present disclosure;
[0030] Figure 6 is a schematic diagram of a module of an operation association device provided by some embodiments of the present disclosure;
[0031] Figure 7 It is a structural diagram of an electronic device provided by some embodiments of the present disclosure. DETAILED DESCRIPTION
[0032] To make the purpose, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present disclosure.
[0033] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0034] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below.
[0035] Herein, unless explicitly stated otherwise, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.
[0036] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.
[0037] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the type, scope of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and authorization should be obtained from relevant users in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.
[0038] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to the software or hardware such as the electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.
[0039] As an optional but non-limiting implementation, in response to receiving an active request from a relevant user, a prompt message may be sent to the relevant user in the form of a pop-up window, in which the prompt message may be presented in text form. Furthermore, the pop-up window may also include a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.
[0040] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0041] See also Figure 1 , which is a schematic diagram of the operational association of some technologies. Figure 1 In the example, both application A and application B can display a recommendation page for application C, and one or more target operations for application C can be recommended on the recommendation page. The target operation may include but is not limited to downloading and installing the application software of application C, registering as a user on the registration page of application C, activating the target function provided by application C on the function activation page of application C, watching a specified novel or video provided by application C, etc. In response to the recommendation button on the recommendation page being triggered by the user, it means that the user accepts the target operation recommended on the recommendation page and intends to perform the target operation in application C. The so-called intention means that the user has the intention to perform the target operation, but it is also possible that the target operation will not be performed. In the case where the recommendation button on the recommendation page is triggered, if the target operation occurs in application C, it means that application A or application B successfully recommends the target operation for application C; if the recommendation button on the recommendation page is triggered, if the target operation does not occur in application C, it means that application A or application B fails to recommend the target operation for application C.
[0042] In order to associate the target operation occurring in application C with the application that successfully recommended the target operation, some technical solutions are as follows:
[0043] 1) For either Application A or Application B, after the user triggers the Recommend button on the application's recommendation page, Application A or B may generate a triggering operation event. The device identifier of the device hosting Application A or B, combined with the triggering operation event, is then sent to the server for storage. The triggering operation event may include, but is not limited to, the target operation intended by the user, the time when the Recommend button on the recommendation page was triggered, the user identifier corresponding to the user logging into the application, and the application identifier corresponding to the application that generated the triggering operation event.
[0044] 2) When a target operation occurs in application C, application C generates a target operation event and combines the device identifier of the device where application C is running with the target operation event, sending it to the server for storage. The target operation event may include, but is not limited to, the target operation performed by the user in application C, the time when the target operation was performed, the user identifier corresponding to the user who logged into application C, and the application identifier of application C.
[0045] 3) Because application A or B and application C that successfully recommended the target operation are typically located on the same device, the server can first match the received combined data based on the device identifier. After finding two sets of combined data with the same device identifier, the server can further locate the application that successfully recommended the target operation based on the application identifier, target operation, and other information in the combined data, and then associate the found application with the target operation of application C.
[0046] for example Figure 1 In the example, assuming that the recommendation button on the recommendation page of application A is triggered by the user, application A can generate a trigger operation event, and the trigger operation event carries the application ID of application A, the time when the recommendation button in application A was triggered by the user, the target operation that the user intends to perform, etc. After generating the trigger operation event, application A can send the combination of the trigger operation event and the device ID to the server for storage. After the target operation occurs in application C, application C can generate a target operation event, and the target operation event carries the target operation performed by the user, the time when the user performed the target operation, the application ID of application C, etc. After generating the target operation event, application C can send the combination of the target operation event and the device ID to the server for storage. Based on the device ID, the server can successfully match the two sets of data sent by application A and application C. Then, based on the application ID, target operation, etc. in the two sets of data, it can determine that the user performed the target operation in application C based on the recommendation of application A, that is, application A is the application that successfully recommended the target operation. Therefore, the target operation in application C can be associated with application A.
[0047] exist Figure 1 In the technical solution shown, the device identification cannot be obtained 100%, so the target operation occurring in application C cannot be 100% associated with the application that successfully recommends the target operation, resulting in a problem of low association accuracy.
[0048] In view of this, the present disclosure provides an operation association method that can solve the above-mentioned problems, thereby improving the association accuracy. The operation association method can be applied to a first application, or can be applied to an electronic device that runs the first application. The electronic device may include but is not limited to a tablet computer, a laptop computer, a desktop computer, etc. In the first application, a second application may be recommended, or one or more operations for the second application may be recommended. The operations for the second application may include but are not limited to downloading and installing the application software of the second application, performing user registration on the registration page of the second application, activating the target function provided by the second application on the function activation page of the second application, and watching a specified novel or video provided by the second application. A target application component may be integrated in the second application. The target application component is used to communicate with the first application.
[0049] See also Figure 2 and Figure 3 . Figure 2 A flowchart of an operation association method provided for some embodiments of the present disclosure. Figure 3 An interactive schematic diagram of an operation association method provided for some embodiments of the present disclosure.
[0050] Figure 2 In the example, the operation association method may include the following steps:
[0051] Step S201: Receive recommended task data and a recommendation identifier for a second application sent by a server.
[0052] Specifically, Figure 3 The server in the example can be a recommendation management platform for the first application. On the server, one or more recommendation tasks for the second application can be configured. Different recommendation tasks can be used to recommend different operations for the second application. For example, recommendation tasks A1, A2, and A3 for the second application can be configured on the server, where recommendation task A1 is used to recommend downloading and installing the application software of the second application, recommendation task A2 is used to recommend user registration on the registration page of the second application, and recommendation task A3 is used to recommend browsing the novel M in the second application.
[0053] The server can send recommended task data to the first application based on a pre-configured recommendation strategy. The recommended task data can be generated based on the recommended task to be performed, and can specifically include the target action to be recommended for the second application and the recommended form of the target action. The recommended form can include, but is not limited to, the layout of the recommended page, such as page size, page color, and page font.
[0054] The recommendation strategy may include, but is not limited to, the timing of sending recommended task data and the logic for selecting recommended tasks to be executed. For example, the recommendation strategy may include sending recommended task data to the first application at predetermined intervals. The recommended task data sent in two consecutive bursts are generated based on different recommended tasks.
[0055] The recommendation identifier uniquely identifies the current recommended task data delivery operation. This identifier can be different for different recommended task data delivery operations. For example, the first time recommended task data is delivered based on recommended task A1, the recommendation identifier might be AAA1; the second time recommended task data is delivered based on recommended task A1, the recommendation identifier might be AAA2; and the third time recommended task data is delivered based on recommended task A2, the recommendation identifier might be AAA3.
[0056] In this embodiment, the recommendation identifier may include the task identifier of the recommended task, the time of issuing the recommended task data, and the user identifier of the target user currently logged into the first application. The combination of task identifier + issuing time + user identifier can usually be unique. For example, for user H who logs into the first application, it is assumed that the recommended task data generated based on the recommended task A1 are issued at the first time point and the second time point respectively. For these two data issuing operations, since the first time point and the second time point are different, even if the two issued are the same recommended task data and the user identifier is the same. The two data issuing operations can still be distinguished through the recommendation identifier. Identifying different data issuing operations based on the task identifier, the time of issuing the recommended task data, and the user identifier of the target user currently logged into the first application can effectively ensure the uniqueness of the recommendation identifier, and the generation logic of the recommendation identifier is relatively simple. Of course, the recommendation identifier can also be generated based on other logic besides the task identifier, the issuing time, and the user identifier. The present disclosure does not limit the generation logic of the recommendation identifier.
[0057] In this embodiment, in addition to sending recommended task data and a recommendation identifier to the first application based on a pre-configured recommendation strategy, the server may also send recommended task data and a recommendation identifier to the first application in response to a data acquisition request sent by the first application. That is, before receiving the recommended task data and the recommendation identifier sent by the server, the first application may send a data acquisition request to the server. The data acquisition request includes the user identifier of the target user currently logged into the first application. After the server generates a recommendation identifier based on the user identifier, it may send the recommended task data and the recommendation identifier to the first application in response to the data acquisition request.
[0058] Furthermore, in the data acquisition request, the first application may specify the task identifier of the target recommended task. After generating the recommended task data based on the target recommended task, the server may send the recommended task data to the first application. Of course, the first application may not specify the task identifier of the target recommended task. The server may determine the recommended task for generating the recommended task data based on the recommendation strategy. Alternatively, the first application may carry the application operation currently occurring in the first application in the data acquisition request. The server may determine the recommended task for generating the recommended task data based on the application operation in the data acquisition request. For example, after the user logs in to the first application, the login event may be carried in the data acquisition request. Based on the login event, the server may generate the recommended task data based on the recommended task A1. For another example, after the user performs operation N in the first application, the operation N may be carried in the data acquisition request. Based on operation N, the server may generate the recommended task data based on the recommended task A2.
[0059] This disclosure does not limit the generation logic of the recommended task data.
[0060] Step S202: Display recommendation information of the second application on the play page of the first application based on the recommendation task data.
[0061] The recommendation information may include, but is not limited to, the target action to be recommended for the second application, the presentation format of the recommendation page, etc. After the recommendation information of the second application is displayed on the playback page of the first application, the user can learn about the functions of the second application while using the first application, and can then decide whether to accept the recommendation of the first application, download and install the second application, or use the relevant functions of the second application.
[0062] In step S203, if a target operation instruction for the second application is received in the playback page, the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction are reported to the server, and the recommendation identifier is sent to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
[0063] Specifically, recommendation buttons can be displayed on the playback page of the first application. In response to these recommendation buttons being triggered by the user, it can be indicated that a target operation instruction for the second application has been received. When the target operation instruction is received, it means that the user accepts the recommendation of the first application and intends to perform the target operation recommended by the first application for the second application. In this case, the first application can communicate with the target application component in the second application and send the recommendation identifier to the target application component. At the same time, the first application can also generate a trigger operation event and send a combination of the trigger operation event and the recommendation identifier to the server. The trigger operation event may include the target operation for the second application that the user intends to perform, the time point when the target operation instruction is received, the application identifier of the first application, etc.
[0064] In this embodiment, since the recommendation identifier includes a recommended task identifier, the target application component can identify the target operation that the user intends to perform on the second application based on the recommendation identifier after receiving the recommendation identifier. Furthermore, the target application component can detect whether the target operation on the second application occurs. After detecting that the target operation on the second application occurs, it indicates that the target operation is triggered by the recommendation of the first application. The target application component can generate a target operation event and send the target operation event and the recommendation identifier to the server. The target operation event may include the target operation that the user has performed on the second application, the time point when the user performs the target operation, the application identifier of the second application, etc.
[0065] Since the recommendation identifier is unique, after receiving the data sent by the first application and the second application, the server can find the matching data combination based on the recommendation identifier, and then associate the target operation event with the first application. Figure 1 The description is not repeated here.
[0066] In summary, in some embodiments of the present disclosure, after receiving the recommended task data and recommendation identifier for the second application sent by the server, the first application can display the recommendation information of the second application on the playback page of the first application based on the recommended task data, and when receiving the target operation instruction for the second application on the playback page, the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction can be reported to the server, and the recommendation identifier can be sent to the target application component, so that when the target operation event of the second application is executed, the target application component can report the recommendation identifier and the target operation event to the server, and the server associates the target operation event with the first application based on the recommendation identifier. Since the recommendation identifier is generated based on the task identifier of the recommended task, the issuance time of the recommended task data, and the user identifier of the target user who is currently logged into the first application, there is no need to rely on the device identifier to associate the target operation event with the first application, so the problem of the device identifier not being able to be fully obtained can be avoided, thereby improving the association accuracy.
[0067] In some embodiments, when the target operation instruction instructs downloading and installing the application software of the second application, sending the recommendation identifier to the target application component includes:
[0068] When the installation of the second application software is complete, display a prompt indicating whether to start the second application;
[0069] If an instruction to start the second application is received, the second application is triggered to start, and the recommendation identifier is sent to the target application component.
[0070] Specifically, when the second application is started, the target application component may be triggered to upload the recommendation identifier to the server, thereby completing the operation association and preventing data omission.
[0071] In some embodiments, when the target operation instruction instructs downloading and installing the application software of the second application, the recommended task data also includes a target link; triggering the launch of the second application includes:
[0072] The target link is sent to the target application component, and the target application component is used to trigger the start of the second application based on the target link, and make the application page of the second application jump to the page pointed to by the target link.
[0073] Specifically, the target link may be a target page link of the second application, such as a homepage link of the first application, or a login page link of the first application.
[0074] After the target link is sent to the target application component, the target application component can jump to the page pointed to by the target link. At this time, it means that the second application is successfully started.
[0075] In some embodiments, the method of the present disclosure further comprises:
[0076] If no instruction to start the second application is received, the recommendation identifier is saved locally;
[0077] When it is detected that the second application is in the startup state, the locally stored recommendation identifier is sent to the target application component.
[0078] and Figure 2 Corresponding to the method, the present disclosure also provides an operation association method applied to the target application component. Figure 4 , which is a flowchart of the operation association method provided in some other embodiments of the present disclosure. Figure 4 In , the operation association methods include:
[0079] Step S401: In response to a target operation event for a second application, it is determined whether a recommendation identifier corresponding to the target operation event sent by a first application is received.
[0080] Step S402: If the recommendation identifier sent by the first application is received, the recommendation identifier and the target operation event are reported to the server. The server is configured to associate the target operation event with the first application based on the recommendation identifier.
[0081] In some embodiments, when the target operation event is a start operation event for the second application, the method further includes:
[0082] If a recommendation identifier corresponding to the start operation event is received from the first application, a target link is also received from the first application;
[0083] The second application is triggered to start, and the application page of the second application is redirected to the page pointed to by the target link.
[0084] In some embodiments, when the target operation event is a start operation event for the second application, the method further includes:
[0085] If the recommendation identifier corresponding to the start operation event sent by the first application is not received, sending a prompt message to the first application indicating that the second application has been started;
[0086] If a recommendation identifier corresponding to the start operation event is received from the first application after the prompt message is sent, the start operation event and the received recommendation identifier are reported to the server.
[0087] Figure 4 Methods and Figure 2 Similar, I won’t go into details here.
[0088] See also Figure 5 , which is a module diagram of the operation association device provided in some embodiments of the present disclosure. Figure 5 , the operation-related device includes:
[0089] The data receiving module 501 is used to receive the recommended task data and recommendation identifier for the second application sent by the server. The recommended task data is generated based on the recommended task for the second application. The recommendation identifier includes the task identifier of the recommended task, the time when the recommended task data is sent, and the user identifier of the target user who is currently logged in to the first application.
[0090] The recommendation information display module 502 is used to display the recommendation information of the second application on the play page of the first application according to the recommendation task data, where the target application component is integrated into the second application.
[0091] The data reporting module 503 is used to report the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction to the server if a target operation instruction for the second application is received in the playback page, and send the recommendation identifier to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
[0092] In some embodiments, when the target operation instruction instructs downloading and installing the application software of the second application, the data reporting module 503 is specifically configured to:
[0093] When the installation of the second application software is complete, display a prompt indicating whether to start the second application;
[0094] If an instruction to start the second application is received, the second application is triggered to start, and the recommendation identifier is sent to the target application component.
[0095] In some embodiments, when the target operation instruction instructs downloading and installing the application software of the second application, the recommended task data also includes a target link; the data reporting module 503 is specifically configured to:
[0096] The target link is sent to the target application component, and the target application component is used to trigger the start of the second application based on the target link, and make the application page of the second application jump to the page pointed to by the target link.
[0097] In some embodiments, the data reporting module 503 is specifically configured to:
[0098] If no instruction to start the second application is received, the recommendation identifier is saved locally;
[0099] When it is detected that the second application is in the startup state, the locally stored recommendation identifier is sent to the target application component.
[0100] In some embodiments, before receiving the recommended task data and recommendation identifier sent by the server, the data receiving module 501 is specifically configured to:
[0101] A data acquisition request is sent to the server, where the data acquisition request includes the user identifier of the target user currently logged into the first application. The server is configured to respond to the data acquisition request and issue the recommended task data and the recommendation identifier.
[0102] See also Figure 6 , which is a module diagram of the operation association device provided in some embodiments of the present disclosure. Figure 6 , the operation-related device includes:
[0103] The determination module 601 is configured to determine, in response to a target operation event for a second application, whether a recommendation identifier corresponding to the target operation event and sent by the first application is received.
[0104] The data reporting module 602 is configured to report the recommendation identifier and the target operation event to the server upon receiving the recommendation identifier sent by the first application. The server is configured to associate the target operation event with the first application based on the recommendation identifier.
[0105] In some embodiments, when the target operation event is a start operation event for the second application, the determination module 601 is further configured to:
[0106] If a recommendation identifier corresponding to the start operation event is received from the first application, a target link is also received from the first application;
[0107] The second application is triggered to start, and the application page of the second application is redirected to the page pointed to by the target link.
[0108] In some embodiments, when the target operation event is a start operation event for the second application, the determination module 601 is further configured to:
[0109] If the recommendation identifier corresponding to the start operation event sent by the first application is not received, sending a prompt message to the first application indicating that the second application has been started;
[0110] If a recommendation identifier corresponding to the start operation event is received from the first application after the prompt message is sent, the start operation event and the received recommendation identifier are reported to the server.
[0111] The configuration device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.
[0112] The operation association device disclosed in the present invention has the same beneficial effects as the above-mentioned operation association method, which will not be described in detail here.
[0113] The present disclosure also provides an electronic device having the above Figure 5 or Figure 6 The operation-related device shown.
[0114] See also Figure 7 , is a schematic diagram of the structure of an electronic device provided by some embodiments of the present disclosure. Figure 7As shown, the electronic device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display graphical information of a GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 7 A processor 10 is taken as an example.
[0115] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.
[0116] The memory 20 stores instructions that can be executed by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.
[0117] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on the use of the electronic device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0118] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.
[0119] The electronic device further includes a communication interface 30 for the electronic device to communicate with other devices or a communication network.
[0120] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.
[0121] A portion of the present disclosure may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present disclosure through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes but is not limited to a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium can be any available computer-readable storage medium or communication medium that can be accessed by the computer.
[0122] Although the embodiments of the present disclosure have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.
Claims
1. An operation association method, characterized in that: Applied to the first application, the method includes: receiving recommended task data and a recommendation identifier for a second application issued by a server, wherein the recommended task data is generated based on a recommended task for the second application, and the recommendation identifier includes a task identifier of the recommended task, a time when the recommended task data was issued, and a user identifier of a target user currently logged into the first application; Based on the recommended task data, displaying recommendation information of the second application on the playback page of the first application, where the target application component is integrated into the second application; If a target operation instruction for the second application is received in the playback page, the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction are reported to the server, and the recommendation identifier is sent to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
2. The method according to claim 1, characterized in that When the target operation instruction instructs downloading and installing the application software of the second application, sending the recommendation identifier to the target application component includes: When the application software of the second application is installed, displaying prompt information indicating whether to start the second application; If an instruction to start the second application is received, the second application is triggered to start, and the recommendation identifier is sent to the target application component.
3. The method according to claim 2, characterized in that When the target operation instruction instructs downloading and installing the application software of the second application, the recommended task data further includes a target link; The triggering and starting the second application includes: The target link is sent to the target application component, and the target application component is used to trigger the start of the second application based on the target link, and make the application page of the second application jump to the page pointed to by the target link.
4. The method according to claim 1, wherein Before receiving the recommended task data and the recommendation identifier sent by the server, the method further includes: A data acquisition request is sent to the server, where the data acquisition request includes a user identifier of a target user currently logged into the first application. The server is configured to issue the recommended task data and the recommendation identifier in response to the data acquisition request.
5. An operation association method, characterized in that: Applied to a target application component, the target application component being integrated into a second application; the method comprising: In response to a target operation event for the second application, determining whether a recommendation identifier corresponding to the target operation event and sent by the first application is received; If the recommendation identifier sent by the first application is received, the recommendation identifier and the target operation event are reported to the server, and the server is configured to associate the target operation event with the first application based on the recommendation identifier.
6. The method according to claim 5, characterized in that When the target operation event is a start operation event for the second application, the method further includes: If a recommendation identifier corresponding to the start operation event is received from the first application, further receiving a target link sent by the first application; Triggering the start of the second application and causing the application page of the second application to jump to the page pointed to by the target link.
7. An operation association device, characterized in that: The device comprises: a data receiving module, configured to receive recommended task data and a recommendation identifier for the second application issued by the server, wherein the recommended task data is generated based on the recommended task for the second application, and the recommendation identifier includes a task identifier of the recommended task, a time when the recommended task data was issued, and a user identifier of a target user currently logged into the first application; a recommendation information display module, configured to display recommendation information of the second application on the playback page of the first application based on the recommendation task data, wherein the second application integrates the target application component; A data reporting module is used to report the recommendation identifier and the triggering operation event that triggers the generation of the target operation instruction to the server if a target operation instruction for the second application is received in the playback page, and send the recommendation identifier to the target application component. The target application component is used to report the recommendation identifier and the target operation event to the server when the target operation event of the second application is executed. The server is used to associate the target operation event with the first application based on the recommendation identifier.
8. An operation association device, characterized in that: The device comprises: a determination module, configured to determine, in response to a target operation event for a second application, whether a recommendation identifier corresponding to the target operation event and sent by the first application is received; The data reporting module is configured to report the recommendation identifier and the target operation event to the server if the recommendation identifier is received from the first application. The server is configured to associate the target operation event with the first application based on the recommendation identifier.
9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the operation association method according to any one of claims 1 to 4, or the operation association method according to any one of claims 5 to 6, by executing the computer instructions.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the operation association method according to any one of claims 1 to 4, or to execute the operation association method according to any one of claims 5 to 6.
11. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the operation association method according to any one of claims 1 to 4, or to execute the operation association method according to any one of claims 5 to 6.