Task processing method and device and electronic equipment

Abstract

The invention discloses a task processing method and device and electronic equipment. The method comprises the following steps: displaying one or more shops with task identifiers and shop task identifiers corresponding to the shops; a target shop in the shops triggered by a user is responded, a target shop page is displayed, the target shop page is a shop page corresponding to the target shop, and the target shop page comprises a task entry associated with a shop task page of the target shop; the shop task page of the target shop is used for displaying a task which is put for the user and is associated with the target shop. By adopting the method, the problem of low task utilization rate and completion rate in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and specifically to a task processing method, device, electronic device and storage medium. Background Art

[0002] With the continuous development of the Internet, there are more and more ways to motivate users to browse pages or place orders on online platforms through tasks. For example, some platforms set incentive tasks and allocate corresponding rights or virtual resources to users based on their completion of the incentive tasks, thereby motivating users to place orders on the platform.

[0003] In the prior art, the platform usually sets up a special task center, and users need to receive or view tasks through the special task center. When users who enter the store are willing to receive tasks, they often need to leave the main order link of the store and enter the task center to search for store-related tasks. The operation is cumbersome, resulting in low task utilization and completion rates. In addition, different brands may also have the need to launch brand-exclusive tasks. However, due to page capacity constraints, the number of tasks that can be carried by the user's task center is limited. It is difficult to display a large number of exclusive tasks of different brands to users through the task center page, resulting in low task exposure, which also leads to low task utilization and completion rates.

[0004] Therefore, how to provide users with a convenient way to receive tasks in order to improve task utilization and completion rate is a problem that needs to be solved.

[0005] The above information disclosed in the Background section is only for enhancement of understanding of the background of the present application and therefore it may contain information that does not constitute the prior art that is already known to a person of ordinary skill in the art. Summary of the invention

[0006] The task processing method provided in the embodiment of the present application solves the problem of low task utilization and completion rate in the prior art.

[0007] An embodiment of the present application provides a task processing method, including: displaying one or more stores with task identifiers and store task identifiers corresponding to the stores; in response to a user triggering a target store among the stores, displaying a target store page, wherein the target store page is a store page corresponding to the target store, and the target store page includes a task entry associated with a store task page of the target store; the store task page of the target store is used to display tasks associated with the target store that are placed for the user.

[0008] Optionally, the store with a task identifier includes a task active store associated with user active tasks for the user; wherein the user active tasks are pending tasks that have been delivered to the user but not claimed by the user and / or ongoing tasks that the user has claimed but not completed.

[0009] Optionally, the store task identifier corresponding to the store is a first task label generated according to the active user tasks of the user.

[0010] Optionally, it also includes: if the target store is an active store for the task, displaying the store task logo of the target store at the task entrance.

[0011] Optionally, displaying the store task logo of the target store at the task entrance includes: displaying the store task logo in a first entrance area at the task entrance; in response to a trigger operation on the first entrance area, loading a rights aggregation page corresponding to the user, and locating to the store task page included in the rights aggregation page.

[0012] Optionally, the store task logo is displayed in the first entrance area at the task entrance, including: displaying a second task label representing the store task logo in the first entrance area; wherein, the second task label is generated based on the user's active tasks, and the display information of the second task label includes indication information for indicating at least one of the task collection status, the current progress of the task, and the task rights and interests.

[0013] Optionally, in response to the trigger operation on the first entry area, the rights aggregation page corresponding to the user is loaded, and the store task page included in the rights aggregation page is located, including: in response to the trigger operation of the user on the first entry area, the rights aggregation page corresponding to the user is loaded, and the task page tag of the rights aggregation page is controlled to be in a selected state, and the store task page indicated by the task page tag is displayed; wherein the rights aggregation page includes one or more tab pages indicated by page tags; the task page tag is one of its page tags.

[0014] Optionally, it also includes: if the target store currently does not have any tasks to be collected for the user and the user's collected tasks have been completed, then: hiding the task entrance; or hiding the store task identifier of the target store at the task entrance, and hiding the store task page of the target store in the rights aggregation page loaded after the task entrance is triggered.

[0015] Optionally, it also includes: displaying the user's preferential information logo in the second entry area at the task entrance; in response to a trigger operation on the second entry area, loading the rights aggregation page corresponding to the user, and locating the user coupon page included in the rights aggregation page.

[0016] Optionally, it also includes: in response to the triggering operation of the task entrance, displaying the store task page; wherein, displaying the store task page includes: if the user has an ongoing task in the target store, then displaying the ongoing task and the current progress of the ongoing task on the store task page, and hiding other tasks to be collected that the target store has placed to the user; if the user does not have an ongoing task in the target store, then displaying one or more tasks to be collected that the target store has placed to the user on the store task page.

[0017] Optionally, it also includes: when the ongoing task is displayed on the store task page, an order control is displayed for the ongoing task to guide the user to place an order on the target store page; when one or more tasks to be collected that the target store delivers to the user are displayed on the store task page, a collection control for collecting the tasks to be collected is displayed for each task to be collected.

[0018] Optionally, it also includes: when displaying multiple tasks to be collected, in response to the collection operation of the collection control for the target task among the tasks to be collected, displaying the first prompt information corresponding to the multi-task collection rules, the first prompt information includes prompting the limit on the number of tasks to be collected in the same time period; in response to the user's confirmation collection operation feedback on the first prompt information, the target task is updated to an ongoing task, and the second prompt information corresponding to the successful task collection is displayed; wherein, the target task is updated to an ongoing task, including: the collection control corresponding to the target task is updated to an order control.

[0019] Optionally, it also includes: when a target task that has been successfully received is completed, hiding the target task on the store task page and displaying other tasks to be received.

[0020] Optionally, it also includes: displaying any of the following information of the task to be collected or the task in progress on the store task page: brand logo and / or store logo, task name, task description information, task activity time, task rights and interests, and task collection rules.

[0021] Optionally, the text information corresponding to the store task identifier and the task entry text information displayed at the task entry are updated according to the user ordering behavior data of the user in the target store.

[0022] Optionally, it also includes: if the user has an ongoing task in the target store, in response to the user's successful order placement information for an order in the target store that matches the task rules of the ongoing task, displaying the task rights or current task progress corresponding to the order.

[0023] An embodiment of the present application also provides a task processing method, including: recalling one or more stores that deliver tasks to users, and determining a store task identifier corresponding to the store; sending the store and the corresponding store task identifier to a client, so that the client displays the store and the corresponding store task identifier; receiving an access request for a target store among the stores sent by the client, and generating target store page data corresponding to the target store for the access request; sending the target store page data to the client, so that the target store page is rendered on the client, wherein the target store page data includes task entry information associated with the store task page of the target store.

[0024] Optionally, determining the store task identifier corresponding to the store includes: obtaining task configuration information corresponding to the store or the brand to which the store belongs; determining user attributes of the user; determining the store that delivers tasks to the user based on the task configuration information and the user attributes; obtaining the user's task record from the store's task record data, and generating the store task identifier based on the user's task record.

[0025] Optionally, determining the store task identifier corresponding to the store includes: if the user has an active user task in the store, generating the store task identifier based on the active user task; the information of the store task identifier is associated with the store and displayed on the client; wherein the active user task is a pending task that has been delivered to the user but has not been claimed by the user and / or an ongoing task that the user has claimed but has not completed.

[0026] Optionally, it also includes: obtaining order behavior data matching the ongoing task, and updating the current progress of the ongoing task based on the order behavior data; generating a store task identifier displayed at the task entrance of the client based on the ongoing task, and the information of the store task identifier displayed at the task entrance of the client is generated based on the current progress of the ongoing task.

[0027] Optionally, it also includes: generating task center page data and sending it to the client for display, so as to deliver tasks to the user through the task center page displayed on the client; wherein the number of tasks associated with the user included in the task center page data does not exceed the task quantity limit.

[0028] An embodiment of the present application also provides a task processing device, including: a store display unit, used to display one or more stores with task identifiers and store task identifiers corresponding to the stores; a store page unit, used to display a target store page in response to a user triggering a target store among the stores, wherein the target store page is a store page corresponding to the target store, and the target store page includes a task entry associated with a store task page of the target store; the store task page of the target store is used to display tasks associated with the target store that are placed for the user.

[0029] An embodiment of the present application also provides a task processing device, including: a recall unit, used to recall one or more stores that have delivered tasks to users, and determine the store task identifier corresponding to the store; a store information sending unit, used to send the store and the corresponding store task identifier to a client, so that the client displays the store and the corresponding store task identifier; a store access unit, used to receive an access request sent by the client for a target store among the stores, and generate target store page data corresponding to the target store for the access request; a store page data sending unit, used to send the target store page data to the client, so that the target store page is rendered on the client, wherein the target store page data includes task entry information associated with the store task page of the target store.

[0030] An embodiment of the present application further provides an electronic device, comprising: a memory, and a processor; the memory is used to store a computer program, and after the computer program is run by the processor, the method provided in the embodiment of the present application is executed.

[0031] The embodiment of the present application also provides a computer storage medium storing computer execution instructions, which are used to implement the method provided in the embodiment of the present application when executed by a processor.

[0032] Compared with the prior art, this application has the following advantages:

[0033] The embodiment of the present application provides a task processing method, device, electronic device and storage medium, which displays one or more stores with task identifiers and store task identifiers corresponding to the stores; in response to a user triggering a target store in the store, displays a target store page, wherein the target store page is a store page corresponding to the target store, and the target store page includes a task entry associated with the store task page of the target store; the store task page of the target store is used to display tasks associated with the target store placed for the user. By displaying the store task identifier, it is convenient for users to select stores with tasks to place orders, and the task entry is displayed on the target store page of the target store selected by the user to facilitate users to enter the target store to browse or purchase goods. It is convenient to receive the tasks placed by the store to the user and view their own tasks, thereby integrating store-related tasks into the user's order main link, and the user does not need to leave the order main link to receive or view tasks on other paths, solving the problem of low task utilization and completion rate. In addition, by displaying tasks on the store page, the problem of the task center page carrying the exclusive tasks corresponding to each store due to the page capacity constraint of the special task center page is avoided. Furthermore, after the user completes the order at the target store, he or she can view the corresponding task rights and interests, thereby increasing the user's willingness to place an order and improving the user experience.

[0034] The embodiment of the present application provides a task processing method, device, electronic device and storage medium, which determines the store task identifier corresponding to the store by recalling one or more stores that deliver tasks to the user; sends the store and the corresponding store task identifier to the client, so that the client displays the store and the corresponding store task identifier; receives the access request for the target store in the store sent by the client, and generates the target store page data corresponding to the target store for the access request; sends the target store page data to the client, so that the target store page is rendered on the client, wherein the target store page data contains the task entry information associated with the store task page of the target store. By providing the client with the store and the corresponding store task identifier for display, it is convenient for the user to select a store with a task to place an order. By providing the target store page data of the target store selected by the user to the client so that the target store page containing the task entry is displayed, it is convenient for the user to enter the target store to browse or purchase goods, so that the store-related tasks can be conveniently received and viewed as the user's tasks are viewed, thereby integrating the store-related tasks into the user's main order link, and the user does not need to leave the main order link to receive or view tasks on other paths, solving the problem of low task utilization and completion rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1is a processing flow chart of a task processing method provided in the first embodiment of the present application;

[0036] Figure 2 This is a schematic diagram of a task link integrated into a store order link provided in the first embodiment of the present application;

[0037] Figure 3 is a schematic diagram of a task processing device provided in the second embodiment of the present application;

[0038] Figure 4 is a processing flow chart of another task processing method provided in the third embodiment of the present application;

[0039] Figure 5 is a schematic diagram of another task processing device provided in the fourth embodiment of the present application;

[0040] Figure 6 It is a schematic diagram of an electronic device provided by this application. DETAILED DESCRIPTION

[0041] Many specific details are described in the following description to facilitate a full understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present application, so the present application is not limited by the specific implementation disclosed below.

[0042] The embodiments of the present application provide a variety of task processing methods, devices, electronic devices, and storage media, which are described one by one in the following embodiments.

[0043] To facilitate understanding, relevant concepts involved in the task processing method provided in the embodiment of the present application are first given.

[0044] Tasks are set up to guide users to complete activity goals. When users complete activity goals, they can get corresponding rewards. It is an incentive method. The reward that users can get when they complete the activity goals of the task is the task rights of the task. Tasks include but are not limited to brand tasks and platform tasks. Exclusive tasks configured in brand dimensions or store dimensions and corresponding to user behaviors in brands (single brand or brand combination) or stores (single store or store combination) are brand tasks. For example, the task that brand A delivers to users is: if orders in one or more stores of brand A within a certain period of time meet the activity goals of the task, a certain amount of resources can be obtained. This task is a brand task of brand A. Tasks that do not distinguish between individual brands or stores and are configured in the platform or platform venue dimensions are platform tasks. For example, the task that the platform delivers to users is: if the activity goals of the task are met by browsing specific pages of the platform within a certain period of time, a certain amount of resources can be obtained. This task is a platform task.

[0045] Task rights and interests refer to the rights and interests of users on the platform, including but not limited to: virtual resources that users can redeem when purchasing goods or services on the platform, the right to price reductions, the right of users to receive gifts, discount coupons, full-discount coupons, single product coupons, coupons, gift coupons, etc.

[0046] The task center refers to the brand tasks and / or platform tasks of the aggregation platform, which centrally displays various tasks to users in the platform dimension and supports task-related tasks such as task collection, status and task execution result viewing. The task function can be provided through the task center page, which can be a web page.

[0047] The main order link refers to the shortest path that users take to complete their ordering behavior on the network platform (also called the platform). For example, the path from loading the store list page of the platform application, the user selecting one of the stores displayed on the store list page, entering the store to browse products and selecting products to complete the order is the main order link.

[0048] The task processing method provided in this application displays the store and its corresponding task tags, displays the task entrance of the associated store task page on the store page, and provides users with task-related operation interfaces and functions in the brand dimension or store dimension, thereby integrating the task into the user's main order link, allowing users to easily receive, view, and complete tasks during the ordering process, thereby obtaining the task rights corresponding to the task, encouraging users to receive and complete tasks, and improving task utilization and completion rates.

[0049] It should be noted that the above disclosed information is only used to help understand the present application and does not mean to constitute the prior art known to ordinary technicians in the field.

[0050] The following combination Figure 1 and Figure 2 The task processing method provided in the first embodiment of the present application is described. Figure 1 The task processing method shown includes: step S101 to step S102.

[0051] Step S101, displaying one or more stores with task identifiers and the store task identifiers corresponding to the stores.

[0052] The method can be applied to a client. The so-called client can be an electronic product or an application running on an electronic product. Electronic products include but are not limited to computing devices such as mobile terminals, computers, portable terminals, and PADs. For example, the client can be an application client of a food delivery platform running on a mobile terminal, or a small program application of a mobile terminal. The client can be used to display the front-end interface, receive user behavior data, etc., and of course, it can also have certain data processing capabilities.

[0053] Specifically, the store or the brand to which the store belongs, and the platform can all place tasks to users or users who meet certain conditions, and the task execution result after the user receives the task is determined based on the user behavior data (such as order behavior data). The user behavior data is the user's order data, especially the valid order data. For example, the order data includes the order quantity or amount. Among them, the store or the brand to which the store belongs places brand tasks to users or users who meet certain conditions. The task execution result of the brand task is determined based on the user's user behavior data in the store or the store associated with the brand. When the task execution result meets the task goal of the brand task, the user can obtain the task rights and interests corresponding to the task. For example, the task one placed by store C to the user is: 20 units of virtual resources can be obtained for each order with a full payment of N yuan. For another example, the task two placed by store C to member users is: 50 units of virtual resources can be obtained for each order with a full payment of M yuan. Among them, the platform can also place platform tasks to users or users who meet certain conditions. The task execution result of the platform task is determined based on the user's user behavior data in each store participating in the platform task. When the task execution result meets the task goal of the platform task, the user can obtain the task rights and interests corresponding to the task. For example, placing 3 or more orders within a specified period can get 20 units of virtual resources. In actual applications, when there is a demand for delivery tasks, the task manager configures the delivery tasks, thereby setting the task information, including but not limited to: the store logo corresponding to the task, the task name, the task activity time, the task description information (i.e. the rule description information for users to complete the task), the delivery user group (such as designated members, ordinary users, user levels, etc.), the task picture, the task rights, etc.

[0054] In actual applications, in response to a loading instruction of a client page, a client page for displaying one or more stores recalled based on the user's user location information is loaded, and at least some of the stores are displayed on the client page. Stores that deliver tasks to the user are filtered out from the recalled stores according to store identifiers, and the stores with task identifiers are displayed on the client page as stores with task identifiers. Preferably, the store with a task identifier includes a task active store associated with a user active task for the user; wherein the user active task is a task to be received that is delivered to the user but not received by the user and / or an ongoing task that the user has received but not completed. That is, the store with a task identifier includes tasks that the user has not received and / or has received but not completed in the store. The client page includes but is not limited to store list pages, search result pages, other recommendation or shopping guide pages, and other pages for displaying store information.

[0055] This step is to display the store task identifier corresponding to the store when displaying the store, so as to facilitate the user to select the store to place an order according to the task. Preferably, the corresponding store task identifier is displayed for the task active store, and the store task identifier can be displayed in the form of a label along with the store card during implementation, wherein the store task identifier corresponding to the store is a first task label generated according to the user active task of the user. The display information of the first task label includes indication information for indicating at least one of the task collection status, the current progress of the task, and the task rights. For example, the stores recalled for the user are displayed in the store list page, and the recalled stores include task active stores. The first task label corresponding to this store is displayed in the store card of the task active store, and the first task label reflects the store task identifier of this store. Among them, the store task identifier contains information related to the user active task. During implementation, the store task identifier is generated according to the user active task of the user, and can be generated by the client or generated by the server and provided to the client. Since the user active tasks of different users in the same store may be the same or different, the store task identifier corresponding to the same store of different users can contain different content, or of course, the same content. That is, the text content of the first task label of the same store displayed on the client pages of different users may be the same or different. For example, if the active task of user 1 in store C is something like "Get 300 virtual beans for every order of 10 yuan or more", the text of the first task label generated is something like "Get 300 virtual beans for every task"; if the active task of user 2 in store C is something like "Get 500 virtual beans for every order of 40 yuan or more", the text of the first task label generated is something like "Get 500 virtual beans for every task". The task progress reflects the result of task execution.

[0056] Step S102, in response to the user triggering a target store among the stores, displaying the target store page, wherein the target store page is a store page corresponding to the target store, and the target store page includes a task entry associated with a store task page of the target store; the store task page of the target store is used to display tasks associated with the target store that are placed for the user.

[0057] Specifically, the task entrance is displayed in the marketing information area of ​​the store page of the store. The marketing information area of ​​the target store page is at the top of the target store page, so as to attract the user's attention and increase the probability of user operation. Preferably, if the target store is the task active store, the store task logo of the target store is displayed at the task entrance. The store task logo can be displayed in association with the task entrance as the task entrance copy information of the task entrance. Among them, the display of the store task logo of the target store at the task entrance includes: displaying a second task tag representing the store task logo at the task entrance; wherein the second task tag is generated according to the user's active task of the user, and the display information of the second task tag includes indication information for indicating at least one of the task collection status, the current progress of the task, and the task rights. The second task tag can be displayed at the task entrance as the task entrance copy information of the task entrance. The second task tag and the first task tag can be the same or different. Among them, for the store that delivers tasks to users but the tasks are all in the waiting state, the store page displays the second task label, which is similar to the first guidance information that displays "place an order to get x virtual beans" to guide users to receive tasks; for the stores under the same brand where users have received tasks but have not completed the tasks, the store page of each store displays the second task label, which is similar to the second guidance information that displays "place an order to get x virtual beans, already received" or "the last order has been received" to guide users to place orders; for the store that currently has no tasks to receive or has completed all received tasks, the second task label may not be displayed. Among them, similar to "already received" and "already received" can indicate the task collection status; similar to "get x virtual beans" and other information can indicate the task rights, and similar to "the last order" and other information indicate the current progress of the task. When the target store delivers multiple tasks to the user, the second task label is generated based on the received tasks among the user's active tasks, and if the received tasks have been completed, it is generated based on other unreceived tasks.

[0058] In one embodiment, after the task entrance is triggered, the rights aggregation page corresponding to the user is loaded, and the rights aggregation page includes one or more rights pages, including but not limited to: store task page, discount information page, etc. The task entrance may include one or more entry areas, and different entry areas are anchored to different rights pages of the rights aggregation page after being triggered. Among them, the store task logo of the target store is displayed at the task entrance, including: displaying the store task logo in the first entry area at the task entrance; in response to the trigger operation for the first entry area, loading the rights aggregation page corresponding to the user, and locating to the store task page included in the rights aggregation page. Among them, the store task logo is displayed in the first entry area at the task entrance, including: displaying a second task label representing the store task logo in the first entry area; wherein the second task label is generated according to the user's active task, and the display information of the second task label includes indication information for indicating at least one of the task collection status, the current progress of the task, and the task rights. The second task label is displayed in the first entry area of ​​the task entrance as at least part of the task entrance copy information of the task entrance. Wherein, in response to the trigger operation for the first entrance area, the rights aggregation page corresponding to the user is loaded, and the store task page included in the rights aggregation page is located, including: in response to the trigger operation for the first entrance area by the user, the rights aggregation page corresponding to the user is loaded, and the task page tag of the rights aggregation page is controlled to be in a selected state, and the store task page indicated by the task page tag is displayed; wherein the rights aggregation page includes one or more tabs indicated by a page tag; the task page tag is a page tag, and the store task page is a tab page. Further, it also includes: displaying the user's preferential information identification in the second entrance area at the task entrance; in response to the trigger operation for the second entrance area, the rights aggregation page corresponding to the user is loaded, and the user coupon page included in the rights aggregation page is located, and the user coupon page is a tab page. For example, the preferential information identification is red envelope preferential information, which is anchored to the user's red envelope coupon page after being triggered. The preferential information identification can be displayed in the second entrance area as the task entrance copy information of the task entrance. The preferential information identification can be displayed in the form of a tag.

[0059] In this embodiment, the specific information displayed by the client page along with the store (such as the store card) displaying the store task identifier (such as the first task label) and the store page after the user enters the store along with the task entrance displaying the store task identifier (such as the second store label) can be the same or different. The store task identifier displayed by the client page along with the store is used to attract users to enter the store, and the information of the store task identifier displayed by the store page is used to guide users to receive or view tasks. In a preferred method, the first task label and the second task label are generated according to the user's active tasks. The display information of the first and second task labels of different users of the same store may be different, or of course, they may be the same; since the task progress, task status, etc. may change over time, the first and second task labels of the same user in the same store may change over time. Task status includes waiting to be received, in progress, completed, and overdue. In progress, it can also be subdivided into states corresponding to different degrees of completion, such as the state of being about to be completed, which means that the last order is left. Then the tasks in the corresponding task status are tasks to be received, tasks in progress, completed tasks, overdue tasks, and tasks to be completed.

[0060] In specific implementation, the rights aggregation page is implemented in the form of a floating layer. When the task entrance is triggered, a floating layer including multiple rights pages is displayed, and each rights page is a tab page indicated by a page label. In response to the triggering operation of the first entrance area that displays the second label, the rights aggregation page floating layer is displayed, the task page label is controlled to be in a selected state, and the tab page indicated by the task page label is displayed, that is, the store task page corresponding to the user in the target store. When the user triggers the second entrance area, when the rights aggregation page floating layer is displayed, the discount page label is controlled to be in a selected state, and the tab page indicated by the discount page label is displayed, that is, the discount information page corresponding to the user. Preferably, the copy information corresponding to the store task identifier and the task entrance copy information displayed at the task entrance are updated according to the user order behavior data of the user in the target store.

[0061] In this embodiment, if the target store currently does not have a task to be collected for the user, and the user's collected tasks (all tasks placed for the user have been collected) have been completed or expired, that is, the user does not currently have a valid user active task in the target store, then: hide the task entrance: or hide the store task identifier of the target store at the task entrance, and hide the store task page of the target store in the equity aggregation page loaded after the task entrance is triggered. Thereby avoiding unnecessary operations by users. When the equity aggregation page is a plurality of equity pages implemented based on a tab page (Tab page), and the store task page indicated by the task page label is one of its tab pages, then the user hides the task page label and the store task page indicated by it in the equity aggregation page when the target store currently does not have a valid user active task. Of course, if the tasks placed by the target store for the user have all been collected and completed or expired, the task entrance may not be hidden, and the store task page may be displayed through the task entrance so that the user can view the completion of historical tasks.

[0062] In this embodiment, it also includes: in response to the triggering operation of the task entrance, displaying the store task page; wherein, the store task page displays the tasks placed by the target store or the brand to which the target store belongs to the user in the form of task cards. The tasks placed to the user include tasks to be collected and / or ongoing tasks in a waiting state. Specifically, displaying the store task page includes: if the user has an ongoing task in the target store, displaying the ongoing task and the current progress of the ongoing task on the store task page, and hiding other tasks to be collected placed by the target store to the user, so that the user's store task page is more concise and improves the user experience; if the user does not have an ongoing task in the target store, displaying one or more tasks to be collected placed by the target store to the user on the store task page. Wherein, when the ongoing task is displayed on the store task page, an order control for guiding the user to place an order on the target store page is displayed for the ongoing task; when one or more tasks to be collected placed by the target store to the user are displayed on the store task page, a collection control for collecting the tasks to be collected is displayed for each task to be collected. Among them, through the triggering operation of the order control, the user returns to the location of the store task page displayed before entering the store task page, so that the user can select the product to place an order. Of course, the store task page or the rights aggregation page including the store task page also includes a close page control or a return to the previous page control, so that the user can return to the store task page to place an order through the close page control or the return to the previous page control.

[0063] Further, in the case of displaying multiple tasks to be collected, in response to the collection operation of the collection control for the target task in the tasks to be collected, the first prompt information corresponding to the multi-task collection rule is displayed, and the first prompt information includes prompting the limit of the number of tasks to be collected in the same period; in response to the confirmation collection operation fed back by the user for the first prompt information, the target task is updated from the task to be collected to the ongoing task, the collection control corresponding to the target task is updated to the order control, and the second prompt information corresponding to the successful task collection is displayed. During implementation, the first prompt information is displayed through a pop-up window, and confirmation collection controls similar to "confirm" and "collect" and return controls similar to "think again" and "cancel" are displayed in the pop-up window, thereby providing the user with an opportunity to reselect the task to be collected. The second confirmation of task collection is realized through the first prompt information, thereby ensuring that the user receives a task that is more in line with expectations. Among them, updating the task to be collected to the ongoing task includes refreshing the displayed content, for example, adding the display of the corresponding task progress for the ongoing task, updating the collection control to the order control, etc. When the number of tasks to be collected in the same period is limited to 1 task, after the target task is successfully collected, other tasks to be collected in the target store are hidden, making the user's store task page more concise. Furthermore, it also includes: after the successfully collected target task is completed, the target task is hidden on the store task page and other tasks to be collected are displayed. If the user has collected and completed all the tasks placed by the target store to the user, the store task identifier (i.e., the first task tag) corresponding to the store is hidden on the client page.

[0064] In this embodiment, the following arbitrary information of the pending task or the ongoing task is displayed on the store task page: the brand logo and / or store logo, task name, task description information, task activity time, task rights and interests, and task collection rules. The above information is specifically displayed in the task card corresponding to the pending task or the ongoing task. Among them, the brand logo and / or store logo can be information in the form of images, LOGOs, text, etc. The task description information includes description information of task rules such as task progress rules and user task completion rules, such as "get x virtual beans for every order of x yuan or more", "get x virtual beans for every x orders", "currently undelivered orders are counted in task progress", and other information.

[0065] In this embodiment, if the user has an ongoing task in the target store, in response to the order success information of the order of the user in the target store that matches the task rule of the ongoing task, the task rights and interests corresponding to the order or the current task progress are displayed. The current task progress can reflect the progress update brought by the order to the task. During implementation, after the user submits the order and the order is paid, the order success information is obtained, and the order success page is displayed. The information related to the user's task is displayed on the order success page, including information about the ongoing task matching the order, such as displaying information containing task rights and interests similar to "get x rights and interests after the order is delivered", or displaying information containing task progress similar to "x orders are left to complete the task after the order is delivered, and x rights and interests can be obtained after completion". Information related to the user's task is displayed on the order success page, and also includes displaying a task viewing entrance for viewing the ongoing task matching the order. The store task page of the user in the target store is loaded through the triggering operation of the task viewing entrance. Information related to the user's task is displayed on the order success page, and also includes displaying summary information of the task rights and interests currently obtained by the user. After the task is completed, the task rights and interests can be automatically associated with the user, or the user behavior of receiving the task rights and interests of the user is received on the order success page or the store task page, and the received task rights and interests are associated with the user.

[0066] In this embodiment, if the user has received a task in the target store and the task is an ongoing task, the corresponding task entrance will be displayed in the store page of other stores of the same brand as the target store, and the ongoing task that the user has received and is in progress in the target store will be displayed in the store task page associated with the task entrance corresponding to the store page of the other store.

[0067] In this embodiment, the store and the corresponding store task identification are displayed through the store list page (or search result page or recommendation page or other shopping guide page). When the user selects the target store for ordering from the stores displaying the store task identification, the target store page for loading the target store is triggered, and the task entrance is displayed on the target store page. The user can receive the task as needed through the task entrance without jumping to the task center to receive it. After receiving the task, the user can directly return to the target store page through the control to complete the order. After completing the order, the corresponding task rights or task progress updates can be checked on the order success page. Thereby, it is not necessary to deviate from the main link of the order when receiving and viewing the task. In addition, the tasks delivered to the user are displayed on the store page, which can realize the display of tasks in brand dimension or store dimension. The number of tasks displayed depends on the number of brands and / or stores that deliver tasks to the user, and is not limited to the page capacity of the task center page.

[0068] Please refer to Figure 2, the figure shows a task link diagram integrated into the store order link, including: store list page 201, store page 202, store task page 203 before receiving the task, and store task page 204 after receiving the task. Among them, the store list page displays each store recalled by the user, and displays each store in the form of a store card. If the user has tasks to be received and / or ongoing tasks in the store, the first task label generated according to the tasks to be received and / or ongoing tasks is displayed in the store card. The figure shows that store 2 has a first task label. The user chooses to trigger store 2 to place an order, and the store page 202 of store 2 is displayed. The task entrance is displayed in the marketing information area of ​​the store page. The task entrance may include one or more entrance areas, and the entrance copy information displayed in each entrance area corresponds to the equity information displayed at the anchor position in the equity aggregation page (floating form) associated with the entrance area. For example, if the entrance area 1 is associated with the store task page corresponding to the anchor position of the equity aggregation page, the entrance area 1 displays the second task label, and the second task label is generated according to the tasks to be received and / or ongoing tasks of the user in store 2. After the entry area 1 is triggered, the rights aggregation page is loaded and the store task page is anchored. For example, "Label 3" in the figure is a task page label, which is in a selected state to display the store task page indicated by it. If store 2 or the brand to which store 2 belongs has placed a task to the user, but the user has not yet received it, as shown in the store task page 203 before receiving the task, the user has multiple tasks to be received, and a receiving control similar to "receive the task" is displayed for each task card to be received, and one of the receiving controls is triggered, such as the triggering task card 1 in the figure. After receiving the task successfully, as shown in the store task page 204 after receiving the task, the progress information and the order control similar to "go to place an order" are displayed in the task card 1. Through the order control, the user returns to the position of the store page before the task entrance, so as to place an order. Of course, when triggering one of the receiving controls, the first prompt information used to prompt the user whether to confirm to receive the task can be displayed through a pop-up window, and the store task page 204 after receiving the task is displayed after the first prompt information is fed back to confirm the receipt. In the figure, other tasks to be received are hidden after receiving the task, so that the page display content is clear and concise. Of course, other tasks to be received can also be displayed in fact, without limitation.

[0069] It is understandable that if Figure 2 The appearance, size, position, style, layout, text, etc. of the interface elements included in or similar interface display diagrams are schematic and do not constitute a limitation on the method.

[0070] It should be noted that, in the absence of conflict, the features given in this embodiment and other embodiments of the present application can be combined with each other, and steps S101 and S102 or similar terms do not limit the steps to be executed sequentially.

[0071] So far, the method provided by this embodiment has been explained. The method facilitates users to select stores with tasks to place orders by displaying store task identifiers, and displays task entrances on the target store page of the target store selected by the user, so that users can conveniently receive tasks assigned to users by the store and view their own tasks when entering the target store to browse or purchase goods, thereby integrating store-related tasks into the user's main order link, and users do not need to leave the main order link to receive or view tasks through other paths, thereby solving the problem of low task utilization and completion rate. In addition, by displaying tasks on the store page, the problem of the task center page carrying exclusive tasks corresponding to each store due to the page capacity constraints of the special task center page is avoided. Furthermore, after the user completes the order at the target store, the corresponding task rights can be viewed, thereby enhancing the user's willingness to place orders and improving the user experience.

[0072] Corresponding to the first embodiment, the second embodiment of the present application provides a task processing device. For the relevant parts, please refer to the description of the corresponding method embodiment. Figure 3 , the task processing device shown in the figure includes:

[0073] The store display unit 301 is used to display one or more stores with task identifiers and the store task identifiers corresponding to the stores;

[0074] The store page unit 302 is used to display the target store page in response to the user triggering the target store in the store, wherein the target store page is the store page corresponding to the target store, and the target store page includes a task entrance associated with the store task page of the target store; the store task page of the target store is used to display the tasks associated with the target store placed for the user.

[0075] Optionally, the store with a task identifier includes a task active store associated with user active tasks for the user; wherein the user active tasks are pending tasks that have been delivered to the user but not claimed by the user and / or ongoing tasks that the user has claimed but not completed.

[0076] Optionally, the store task identifier corresponding to the store is a first task label generated according to the active user tasks of the user.

[0077] Optionally, the store page unit 302 is specifically used to: if the target store is the task active store, display the store task logo of the target store at the task entrance.

[0078] Optionally, the store page unit 302 is specifically used to: display the store task logo in the first entrance area at the task entrance; in response to a trigger operation on the first entrance area, load the rights aggregation page corresponding to the user, and locate the store task page included in the rights aggregation page.

[0079] Optionally, the store page unit 302 is specifically used to: display a second task label representing the store task identifier in the first entrance area; wherein the second task label is generated based on the user's active tasks, and the display information of the second task label includes indication information for indicating at least one of the task collection status, the current progress of the task, and the task rights.

[0080] Optionally, the store page unit 302 is specifically used to: in response to the user's trigger operation on the first entrance area, load the rights aggregation page corresponding to the user, and control the task page tag of the rights aggregation page to be in a selected state, and display the store task page indicated by the task page tag; wherein, the rights aggregation page includes one or more tab pages indicated by page tags; the task page tag is one of its page tags.

[0081] Optionally, the store page unit 302 is specifically used to: if the target store currently does not have any tasks to be collected for the user and the tasks that the user has collected have been completed, then: hide the task entrance; or hide the store task identifier of the target store at the task entrance, and hide the store task page of the target store in the rights aggregation page loaded after the task entrance is triggered.

[0082] Optionally, the store page unit 302 is specifically used to: display the user's preferential information logo in the second entrance area at the task entrance; in response to a trigger operation on the second entrance area, load the rights aggregation page corresponding to the user, and locate the user coupon page included in the rights aggregation page.

[0083] Optionally, the store page unit 302 is specifically used to: display the store task page in response to a trigger operation of the task entry; if the user has an ongoing task in the target store, display the ongoing task and the current progress of the ongoing task on the store task page, and hide other tasks to be collected that the target store has delivered to the user; if the user does not have an ongoing task in the target store, display one or more tasks to be collected that the target store has delivered to the user on the store task page.

[0084] Optionally, the store page unit 302 is specifically used to: when the ongoing task is displayed on the store task page, display an order control for the ongoing task to guide the user to place an order on the target store page; when one or more tasks to be collected that the target store delivers to the user are displayed on the store task page, display a collection control for each task to be collected that is used to collect the task.

[0085] Optionally, the store page unit 302 is specifically used to: when displaying multiple tasks to be collected, in response to a collection operation on a collection control for a target task among the tasks to be collected, display first prompt information corresponding to a multi-task collection rule, wherein the first prompt information includes a prompt indicating a limit on the number of tasks to be collected during the same period; in response to the user's confirmation collection operation feedback on the first prompt information, the target task is updated to an ongoing task, and a second prompt information corresponding to successful task collection is displayed; wherein, the target task is updated to an ongoing task, including: the collection control corresponding to the target task is updated to an order control.

[0086] Optionally, the store page unit 302 is specifically used to: when a target task that has been successfully received is completed, hide the target task on the store task page and display other tasks to be received.

[0087] Optionally, the store page unit 302 is specifically used to display any of the following information of the to-be-collected task or the ongoing task on the store task page: brand logo and / or store logo, task name, task description information, task activity time, task rights and interests, and task collection rules.

[0088] Optionally, the text information corresponding to the store task identifier and the task entry text information displayed at the task entry are updated according to the user ordering behavior data of the user in the target store.

[0089] Optionally, the store page unit 302 is used to: if the user has an ongoing task in the target store, in response to the user's successful order information for an order in the target store that matches the task rules of the ongoing task, display the task rights or current task progress corresponding to the order.

[0090] Based on the above embodiment, the third embodiment of the present application provides another task processing method. Figure 4 The method is described below. For the same parts, please refer to the description of the corresponding parts of the above embodiments and will not be repeated here. Figure 4 The task processing method shown includes:

[0091] Step S401, recalling one or more stores that deliver tasks to the user, and determining the store task identifiers corresponding to the stores;

[0092] Step S402, sending the store and the corresponding store task identifier to the client, so that the client displays the store and the corresponding store task identifier;

[0093] Step S403, receiving an access request for a target store in the stores sent by the client, and generating target store page data corresponding to the target store according to the access request;

[0094] Step S404: sending the target store page data to the client so that the target store page is rendered on the client, wherein the target store page data includes task entry information associated with a store task page of the target store.

[0095] The method provided in this embodiment can be applied to a server. The server is mainly used to provide a store with a task identifier and determine the store task identifier corresponding thereto, and generate target store page data for the target store selected by the user to visit detected by the client, and provide the target store page data to the client to render the target store page containing the task entrance on the client. The task entrance is displayed in the store, so that the store or brand dimension can be used to display the tasks placed by the store or brand on the user.

[0096] In one embodiment, a store task identifier of a store is generated based on the user's task record in the store. Wherein, the determining of the store task identifier corresponding to the store includes: obtaining the task configuration information corresponding to the store or the brand to which the store belongs; determining the user attributes of the user; determining the store that delivers tasks to the user based on the task configuration information and the user attributes; obtaining the user's task record from the store's task record data, and generating the store task identifier based on the user's task record. In one embodiment, the determining of the store task identifier corresponding to the store includes: if the user has an active user task in the store, generating the store task identifier based on the active user task; the information of the store task identifier is associated with the store and displayed on the client; wherein the active user task is a pending task that is delivered to the user but not received by the user and / or an ongoing task that the user has received but not completed. The above embodiments can be combined with each other if there is no conflict.

[0097] In this embodiment, the user's task progress is determined based on the user's behavior data, especially the order behavior data, and the store task identifier is generated based on the user's ongoing task. Specifically, it includes: obtaining the order behavior data that matches the ongoing task, and updating the current progress of the ongoing task based on the order behavior data; generating a store task identifier displayed at the task entrance of the client based on the ongoing task, and the information of the store task identifier displayed at the task entrance of the client is generated based on the current progress of the ongoing task. Of course, if the user does not have an ongoing task in a store, but has an uncollected task to be collected, the store task identifier is generated based on the task to be collected.

[0098] In this embodiment, displaying the store and the corresponding store task identifier on the client specifically includes: generating a first task tag representing the store task identifier, and sending the first task tag and its corresponding store to the client for display.

[0099] In this embodiment, the target store page and the task entrance contained therein are displayed on the client, specifically including: generating a second task tag representing the store task identifier, using the second task tag as part of the target store page data, sending the target store page data to the client for display, and displaying the second task tag in association with the task entrance during display. For example, the second task tag is displayed as at least part of the entrance copy information of the task entrance at the task entrance, especially at the first entrance area of ​​the task entrance, and the store task page in the rights aggregation page is anchored and displayed through a trigger operation on the first entrance area.

[0100] In this embodiment, another task delivery method is also included, specifically: generating task center page data and sending it to the client for display, so as to deliver tasks to the user through the task center page displayed on the client; wherein the number of tasks associated with the user included in the task center page data does not exceed the task quantity limit.

[0101] So far, the method provided by this embodiment has been described. The method provides the client with the store and the corresponding store task identifier for display, so that the user can select the store with the task to place an order. By providing the target store page data of the target store selected by the user to the client so that the target store page containing the task entrance is displayed, it is convenient for the user to enter the target store to browse or purchase goods and conveniently receive the tasks placed by the store to the user and view his own tasks, thereby integrating the store-related tasks into the user's main order link, and the user does not need to leave the main order link to receive or view tasks through other paths, solving the problem of low task utilization and completion rate. .

[0102] Corresponding to the third embodiment, the fourth embodiment of the present application provides a task processing device. For the relevant parts, please refer to the description of the corresponding method embodiment. Figure 5 , the task processing device shown in the figure includes:

[0103] A recall unit 501 is used to recall one or more stores that deliver tasks to users, and determine store task identifiers corresponding to the stores;

[0104] The store information sending unit 502 is used to send the store and the corresponding store task identifier to the client, so that the client displays the store and the corresponding store task identifier;

[0105] A store access unit 503, configured to receive an access request for a target store in the store sent by the client, and generate target store page data corresponding to the target store according to the access request;

[0106] The store page data sending unit 504 is used to send the target store page data to the client so that the target store page is rendered on the client, wherein the target store page data includes task entry information associated with the store task page of the target store.

[0107] Optionally, the recall unit 501 is specifically used to: obtain task configuration information corresponding to the store or the brand to which the store belongs; determine the user attributes of the user; determine the store that delivers the task to the user based on the task configuration information and the user attributes; obtain the user's task record from the store's task record data, and generate the store task identifier based on the user's task record.

[0108] Optionally, the recall unit 501 is specifically used to: if the user has an active user task in the store, generate the store task identifier based on the user active task; the information of the store task identifier is associated with the store and displayed on the client; wherein the user active task is a pending task that has been delivered to the user but has not been claimed by the user and / or an ongoing task that the user has claimed but has not completed.

[0109] Optionally, the store page data sending unit 504 is specifically used to: obtain order behavior data matching the ongoing task, and update the current progress of the ongoing task according to the order behavior data; generate a store task identifier displayed at the task entrance of the client according to the ongoing task, and the information of the store task identifier displayed at the task entrance of the client is generated according to the current progress of the ongoing task.

[0110] Optionally, the device also includes a task delivery unit, which is used to: generate task center page data and send it to the client for display, so as to deliver tasks to the user through the task center page displayed on the client; wherein the number of tasks associated with the user included in the task center page data does not exceed the task quantity limit.

[0111] Based on the above embodiments, the fifth embodiment of the present application provides an electronic device. For the relevant parts, please refer to the corresponding description of the above embodiments. Figure 6 The electronic device shown in the figure includes: a memory 601 and a processor 602; the memory is used to store a computer program, and after the computer program is run by the processor, the method provided in the embodiment of the present application is executed.

[0112] Based on the above embodiments, the sixth embodiment of the present application provides a computer storage medium. For the relevant parts, please refer to the corresponding description of the above embodiments. Figure 6 The memory in the figure can be understood as the storage medium. The computer storage medium stores computer execution instructions, which are used to implement the method provided in the embodiment of the present application when executed by the processor.

[0113] It should be noted that the embodiments of the present application may involve platform operations, order transactions, etc. In actual applications, the solutions described in this article should be applied within the scope permitted by applicable laws and regulations in accordance with the applicable laws and regulations of the country where they are located.

[0114] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, the user's specific personal data should be used in the scheme described in this article within the scope permitted by applicable laws and regulations, in compliance with the applicable laws and regulations of the country where it is located (for example, the user's explicit consent, effective notification to the user, etc.).

[0115] In a typical configuration, an electronic device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory. The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0116] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0117] Although the present application is disclosed as above in the form of a preferred embodiment, it is not intended to limit the present application. Any technical personnel in this field may make possible changes and modifications without departing from the spirit and scope of the present application. Therefore, the scope of protection of the present application shall be based on the scope defined by the claims of the present application.

Claims

1. A task processing method, characterized in that: include: Display one or more stores with task identifiers and store task identifiers corresponding to the stores; In response to a user triggering a target store among the stores, a target store page is displayed, wherein the target store page is a store page corresponding to the target store, and the target store page includes a task entry associated with a store task page of the target store; the store task page of the target store is used to display tasks associated with the target store that are placed for the user.

2. The method according to claim 1, characterized in that The store with the task identifier includes a task active store associated with the user active tasks for the user; wherein the user active tasks are pending tasks that have been delivered to the user but not claimed by the user and / or ongoing tasks that have been claimed by the user but not completed.

3. The method according to claim 2, characterized in that The store task identifier corresponding to the store is a first task label generated according to the active user tasks of the user.

4. The method according to claim 2, characterized in that: Also includes: If the target store is an active store for the task, the store task logo of the target store is displayed at the task entrance.

5. The method according to claim 4, characterized in that The displaying of the store task logo of the target store at the task entrance includes: Displaying the store task logo in a first entrance area at the task entrance; In response to a trigger operation on the first entry area, the rights aggregation page corresponding to the user is loaded, and the store task page included in the rights aggregation page is located.

6. The method according to claim 5, characterized in that The displaying of the store task logo in the first entrance area at the task entrance includes: Displaying a second task label representing the store task identifier in the first entrance area; The second task label is generated according to the active user tasks of the user, and the display information of the second task label includes indication information for indicating at least one of the task claiming status, the current progress of the task, and the task rights and interests.

7. The method according to claim 5, characterized in that The step of responding to the trigger operation on the first entry area, loading the rights aggregation page corresponding to the user, and locating to the store task page included in the rights aggregation page, includes: In response to the user's triggering operation on the first entrance area, loading the rights aggregation page corresponding to the user, controlling the task page label of the rights aggregation page to be in a selected state, and displaying the store task page indicated by the task page label; Among them, the rights aggregation page includes one or more tab pages indicated by page tags; the task page tag is one of its page tags.

8. The method according to claim 5, characterized in that Also includes: If the target store currently has no pending tasks for the user and the tasks that the user has already received have been completed, then: Hide the task entry: or, The store task identifier of the target store is hidden at the task entrance, and the store task page of the target store is hidden in the rights aggregation page loaded after the task entrance is triggered.

9. The method according to claim 4, characterized in that Also includes: Displaying the user's preferential information logo in the second entrance area at the task entrance; In response to a trigger operation on the second entry area, the rights aggregation page corresponding to the user is loaded, and the user coupon page included in the rights aggregation page is located.

10. A task processing method, characterized in that: include: Recall one or more stores that deliver tasks to the user, and determine store task identifiers corresponding to the stores; Sending the store and the corresponding store task identifier to the client, so that the client displays the store and the corresponding store task identifier; receiving an access request for a target store among the stores sent by the client, and generating target store page data corresponding to the target store according to the access request; The target store page data is sent to the client so that the target store page is rendered on the client, wherein the target store page data includes task entry information associated with a store task page of the target store.

Images