Delivery processing method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a delivery processing method and device, electronic equipment and a storage medium, and the method comprises the steps: carrying out the delivery account matching according to a target account condition in a target delivery strategy and the account data of each delivery account, and determining a target delivery account meeting the target account condition; sending a target delivery task to the target delivery account, wherein the target delivery task is used for executing the target delivery strategy; if a task receiving instruction returned by the target delivery account is received, determining task progress information of the target delivery task according to delivery data and task index information of the target delivery account in a process that the target delivery account performs content delivery according to the delivery operation guidance information in a task period; sending task progress information to the target delivery account; according to the method provided by the invention, on-line delivery operation guidance and automatic progress determination of the delivery account are realized, and the delivery guidance efficiency is improved.

Description

Technical Field

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

[0002] Optimizers use the delivery account on the delivery side to deliver and optimize ads. In related technologies, in order to optimize the effect of ad delivery, users on the delivery media side mainly communicate with optimizers on the delivery side offline before delivery optimization. For example, users on the delivery media side send delivery guidance information to optimizers on the delivery side through other instant messaging or online documents. This method that relies on offline communication is time-consuming and the delivery optimization efficiency is not high. Summary of the invention

[0003] In view of the above problems, the embodiments of the present application propose a delivery processing method, device, electronic device and storage medium to solve the problem that the related technology relies on offline communication for delivery optimization, which is time-consuming and has low delivery optimization efficiency.

[0004] According to one aspect of an embodiment of the present application, a delivery processing method is provided, the method comprising: matching delivery accounts according to target account conditions in a target delivery strategy and account data of each delivery account, and determining a target delivery account that meets the target account conditions; the target delivery strategy also includes delivery operation guidance information, task period and task indicator information; sending a target delivery task to the target delivery account, the target delivery task being used to execute the target delivery strategy; if a task acceptance instruction returned by the target delivery account is received, during the task period, when the target delivery account delivers content according to the delivery operation guidance information, determining task progress information of the target delivery task according to the delivery data of the target delivery account and the task indicator information; and sending the task progress information to the target delivery account.

[0005] According to one aspect of an embodiment of the present application, a delivery processing device is provided, including: an account matching module, used to match delivery accounts according to target account conditions in a target delivery strategy and account data of each delivery account, and determine a target delivery account that meets the target account conditions; the target delivery strategy also includes delivery operation guidance information, task period and task indicator information; a task sending module, used to send a target delivery task to the target delivery account, the target delivery task is used to execute the target delivery strategy; a task progress determination module, used to determine the task progress information of the target delivery task according to the delivery data of the target delivery account and the task indicator information during the task period when the target delivery account delivers content according to the delivery operation guidance information if a task acceptance instruction returned by the target delivery account is received; and a progress information sending module, used to send the task progress information to the target delivery account.

[0006] In some embodiments, the delivery operation guidance information includes at least one delivery guidance action, and the task indicator information includes sub-task indicator information corresponding to each delivery guidance action; the sub-task indicator information includes the compliance conditions corresponding to the indicator parameters; the task progress information includes the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task; the task progress determination module includes: a first acquisition unit, which is used to obtain the actual parameter value of the target delivery account under the indicator parameter corresponding to each delivery guidance action during the task period when the target delivery account delivers according to each delivery guidance action; a first determination unit, which is used to determine the task action progress corresponding to each delivery guidance action according to the compliance conditions corresponding to the indicator parameter corresponding to each delivery guidance action and the actual parameter value corresponding to the indicator parameter; a second determination unit, which is used to determine the task execution progress of the target delivery task according to the task action progress corresponding to each delivery guidance action.

[0007] In some embodiments, the delivery guidance action includes multiple secondary guidance actions; the first acquisition unit includes: a second acquisition unit, used to obtain, during the task period, sub-delivery data corresponding to each secondary guidance action of the target delivery account under the delivery guidance action; a statistical unit, used to perform statistics based on the sub-delivery data corresponding to multiple secondary guidance actions of the target delivery account under the delivery guidance action, to obtain the actual parameter value of the indicator parameter corresponding to the delivery guidance action of the target delivery account.

[0008] In some embodiments, the delivery operation guidance information includes multiple delivery guidance actions, and the delivery operation guidance information also includes action weights corresponding to each of the delivery guidance actions; the second determination unit is configured to: according to the action weights corresponding to each of the delivery guidance actions, perform weighted processing on the task action progress corresponding to the multiple delivery guidance actions respectively, to obtain the task execution progress of the target delivery task.

[0009] In some embodiments, the target delivery strategy also includes an effect measurement strategy; the delivery processing device also includes: an effect measurement result determination module, which is used to measure the effect of the target delivery task according to the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the end time of the task period of the target delivery account and the effect measurement strategy, and determine the effect measurement result of the target delivery task; an effect measurement result sending module, which is used to send the effect measurement result of the target delivery task to the target delivery account.

[0010] In some embodiments, the effect measurement strategy includes a positive measurement condition defined by an effect indicator parameter, and the first delivery effect data includes a first numerical value corresponding to a sub-effect indicator parameter for determining the effect indicator parameter; the second delivery effect data includes a second numerical value corresponding to the sub-effect indicator parameter; an effect measurement result determination module includes: a third determination unit, used to determine the numerical value corresponding to the effect indicator parameter in the reference period according to the first numerical value corresponding to the sub-effect indicator parameter in the first delivery effect data; a fourth determination unit, used to determine the numerical value corresponding to the effect indicator parameter at the end time of the task period according to the second numerical value corresponding to the sub-effect indicator parameter in the second delivery effect data; and a fifth determination unit, used to determine the effect measurement result of the target delivery task according to the numerical value corresponding to the effect indicator parameter in the reference period, the numerical value corresponding to the effect indicator parameter at the end time of the task period, and the positive measurement condition.

[0011] In some embodiments, the delivery processing device also includes: a splitting module, used to split the effect indicator parameters in the positive measurement conditions to determine the sub-effect indicator parameters corresponding to the effect indicator parameters; a data source determination module, used to determine the data source corresponding to the sub-effect indicator parameters; a first value acquisition module, used to obtain the first value corresponding to the sub-effect indicator parameter in the reference period from the data source corresponding to the sub-effect indicator parameter; a second value acquisition module, used to obtain the second value corresponding to the sub-effect indicator parameter at the end time of the task period from the data source corresponding to the sub-effect indicator parameter.

[0012] In some embodiments, the delivery processing device also includes: a first feedback information receiving module, used to receive first feedback information sent by the target delivery account for the target delivery task, the first feedback information is sent by the client where the target delivery account is located in response to a trigger operation on a first feedback entry; the client where the target delivery account is located responds to the effect measurement result of the target delivery task being a negative effect, and displays the first feedback entry in the task display page corresponding to the target delivery task.

[0013] In some embodiments, the account matching module includes: an attribute value determination unit, which is used to determine the attribute value of each delivery account under each attribute in the attribute set based on the account data of each delivery account; and a matching unit, which is used to determine the target delivery account whose attribute value meets the target account condition based on the attribute value of each delivery account under each attribute in the attribute set.

[0014] In some embodiments, the delivery processing device also includes: a basic attribute determination module, which is used to determine the basic attributes corresponding to each delivery account based on the basic information of each delivery account; and an attribute set determination module, which is used to combine the basic attributes corresponding to each delivery account with the pre-configured common attributes respectively to determine the attribute set corresponding to each delivery account.

[0015] In some embodiments, the target delivery strategy further includes a mutually exclusive condition; the task sending module is configured to: if it is determined that the mutually exclusive condition is not met, send the target delivery task to the target delivery account.

[0016] In some embodiments, the delivery processing device also includes: a second feedback information receiving module, used to receive second feedback information sent by the target delivery account for the target delivery task, the second feedback information is sent by the client where the target delivery account is located in response to a triggering operation on a second feedback entry; the client where the target delivery account is located responds to the target delivery task not being completed at the end time of the task period, and displays the second feedback entry in the task display page corresponding to the target delivery task.

[0017] In some embodiments, the delivery processing device further includes: a task cancellation module, configured to cancel the target delivery task for the target delivery account if a task abandonment request for the target delivery task is received from the target delivery account during the task period.

[0018] According to one aspect of an embodiment of the present application, an electronic device is provided, including: a processor; a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the delivery processing method as described above is implemented.

[0019] According to one aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor, the delivery processing method as described above is implemented.

[0020] According to one aspect of an embodiment of the present application, a computer program product is provided, including computer instructions, which implement the above delivery processing method when executed by a processor.

[0021] In this application, account matching is performed based on the target account conditions in the target delivery strategy, the target delivery account that meets the target account conditions is determined, and the target delivery task for executing the target delivery strategy is sent to the target delivery account. Since the target delivery strategy includes delivery operation guidance information, delivery operation guidance for the delivery account is achieved through online channels. When the target delivery account accepts the target delivery task, the progress is calculated according to the delivery data of the target delivery account during the task period and the task indicator information in the target delivery strategy, and the task progress information of the target delivery task is determined, so that the progress of the target delivery task is automatically determined. After that, the task progress information is sent to the target delivery account, so that the user on the delivery account side can know the task execution progress of the target delivery task, and the effective interaction with the delivery account is guaranteed. Especially in the case of facing a large number of delivery accounts, this application can issue target delivery tasks to multiple delivery accounts that meet the target account conditions, and can achieve delivery guidance for multiple delivery accounts. Compared with the delivery guidance through offline communication in the related technology, the scheme of this application can improve the efficiency of delivery guidance for delivery accounts and reduce time consumption.

[0022] In the scheme of providing delivery guidance through offline methods, the user on the delivery account side needs to manually configure the task indicator information and report it to the server before the progress can be determined. This method requires the user on the delivery account side to perform more manual operations. In the present application, the target delivery strategy includes task indicator information. During the task period, the server can automatically calculate the progress based on the task indicator information and the delivery data of the target delivery account, thereby automatically determining the progress of the target delivery task and reducing user manual operations. Moreover, since there is no need for the delivery account side to report the task indicator information, the interaction between the delivery account side and the server is reduced. When the number of delivery accounts facing the service on the server side is large, the response pressure on the server can be greatly reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1A It is a schematic diagram of an application scenario of the present application according to an embodiment of the present application.

[0025] Figure 1B It is a schematic diagram of an application scenario shown according to another embodiment of the present application.

[0026] Figure 2 It is a flowchart of a delivery processing method according to an embodiment of the present application.

[0027] Figure 3 It is a schematic diagram of a task display page in a delivery client according to an embodiment of the present application.

[0028] Figure 4 It is a schematic diagram of a task abandonment page according to an embodiment of the present application.

[0029] Figure 5 It is a schematic diagram of a task display page in a delivery client according to another embodiment of the present application.

[0030] Figure 6 It is a schematic diagram of a task display page in a delivery client according to another embodiment of the present application.

[0031] Figure 7 It is a flow chart showing actual parameter values ​​of indicator parameters corresponding to a delivery guidance action according to an embodiment of the present application.

[0032] Figure 8 It is a schematic diagram showing the display of effect measurement results on a task display page according to an embodiment of the present application.

[0033] Fig. 9 It is a schematic diagram showing the display of effect measurement results on a task display page according to another embodiment of the present application.

[0034] Fig.10 It is a flow chart showing the measurement of delivery effect of delivery tasks according to an embodiment of the present application.

[0035] Fig.11 It is a flowchart of querying after splitting effect indicator parameters according to an embodiment of the present application.

[0036] Fig.12It is a schematic diagram of determining effect measurement results based on effect delivery strategies and parameter values ​​of various effect delivery indicators according to an embodiment of the present application.

[0037] Fig.13 is a schematic diagram of a task display page according to another embodiment of the present application.

[0038] Fig.14 It is a flowchart showing a method of determining a set of attributes for each investment account according to an embodiment of the present application.

[0039] Fig.15 The figure is a flowchart of account matching according to an embodiment of the present application.

[0040] Fig.16 It is a schematic diagram of the account condition configuration control in the delivery configuration page according to an embodiment of the present application.

[0041] Fig.17 It is a schematic diagram of configuring account conditions in a delivery configuration page according to an embodiment of the present application.

[0042] Fig.18 It is a schematic diagram of a delivery configuration page according to an embodiment of the present application.

[0043] Fig.19 It is a schematic diagram of configuring an effect delivery strategy in a delivery configuration page according to an embodiment of the present application.

[0044] Fig. 20 It is a schematic diagram of a delivery configuration page according to an embodiment of the present application.

[0045] Fig.21 It is a schematic diagram of configuring mutually exclusive conditions in a delivery configuration page according to an embodiment of the present application.

[0046] Fig. 22 It is a schematic diagram of customizing columns in a display page according to an embodiment of the present application.

[0047] Fig.23 It is a block diagram of a delivery processing device according to an embodiment of the present application.

[0048] Fig.24 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION

[0049] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0050] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0051] It should be noted that the "multiple" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0052] Figure 1A is a schematic diagram of an application scenario of the present application according to an embodiment of the present application, such as Figure 1A As shown, the application scenario includes a delivery configuration terminal 110, a delivery management server 120 and a delivery terminal 130, wherein the delivery configuration terminal 110 and the delivery terminal 130 can be terminals such as desktop computers, laptops, tablet computers, smart phones, etc. that can display and interact with pages, and the delivery management server 120 can be a physical server or a cloud server. The delivery management server 120 is connected to the delivery configuration terminal 110 and the delivery terminal 130 for communication.

[0053] The user on the delivery configuration side 110 can configure the delivery strategy on the delivery configuration page displayed on the delivery configuration side 110. After that, the delivery configuration side 110 sends the configured delivery strategy to the delivery management server 120, and the delivery management server 120 can perform delivery processing according to the method provided in this application.

[0054] The delivery management server 120 can execute step 121, delivery account matching, that is, matching the target account conditions in the target delivery strategy with each delivery account, and determining the target delivery account that meets the target account conditions. After that, the delivery management server executes step 122 to send the target delivery task. The user on the delivery end 130 side can choose to accept the target delivery task or reject the target delivery task in the display page. If the user chooses to accept the target delivery task, the delivery end 130 sends an acceptance instruction for the target delivery task to the delivery management server 120; thereafter, the delivery management server 120 executes the following steps: step 123, receiving the acceptance instruction for the target delivery task; step 124, determining the task progress information of the target delivery task; step 125, sending the task progress information of the target delivery task. The task display page of the delivery end 130 can display the task progress information of the target delivery task accordingly. The specific implementation process of the above steps 121-step 125 is described below.

[0055] In the present application, the delivery management server 120 and the delivery end 130 are connected, and can interact through a program interface, so that the delivery task can directly reach the advertiser at the delivery end, avoiding the advertiser accepting delivery tasks and delivering advertisements across systems.

[0056] Figure 1B is a schematic diagram of an application scenario according to another embodiment of the present application, such as Figure 1B As shown, after the delivery strategy is created, the delivery strategy is stored in the database, and on the other hand, a target delivery task is generated based on the task period in the delivery strategy and the matching target delivery account; then, the target delivery task is sent to the delivery client (i.e., the client running on the delivery end). The user on the delivery client side (i.e., the advertiser) can choose to accept the target delivery task or reject the target delivery task. If the advertiser chooses to accept the target delivery task, the target delivery task can be executed and the advertisement can be delivered.

[0057] In some embodiments, the target delivery tasks may be stored in a database. To cope with high QPS (Queries Per Second) scenarios on the delivery side and the service provider side, the delivery strategies and delivery tasks in the database may be synchronized to the search engine.

[0058] The implementation details of the technical solution of the embodiment of the present application are described in detail below:

[0059] Figure 2 is a flowchart of a delivery processing method according to an embodiment of the present application. The method can be executed by an electronic device with processing capabilities, for example, as Figure 1A The server, cloud server, etc. of the delivery management server 120. Figure 2 As shown, the method at least includes steps 210 to 240, which are described in detail as follows:

[0060] Step 210, matching the delivery accounts according to the target account conditions in the target delivery strategy and the account data of each delivery account, and determining the target delivery account that meets the target account conditions; the target delivery strategy also includes delivery operation guidance information, task period and task indicator information.

[0061] The target delivery strategy refers to the delivery strategy for the current account to be matched. The target delivery strategy can be one of a preset delivery strategy set, and each delivery strategy in the delivery strategy set can be matched to a delivery account according to the method of this application. The delivery strategy is used to provide delivery guidance to a delivery account, or to provide a delivery account with a direction for optimizing delivery operations. The delivery strategy can be configured by a user on the delivery management platform side in the strategy configuration interface.

[0062] A delivery account refers to an account of a user on the advertiser's side on the delivery management platform. The user on the advertiser's side can manage the content to be delivered (such as advertisements) based on the delivery account. For example, the user can configure targeting information, bids, delivery media (i.e., the advertising display locations, etc.) for the content to be delivered.

[0063] The target account condition refers to the account condition in the target delivery strategy. The account condition is used to automatically match the delivery account for the target delivery strategy. The target delivery account refers to the delivery account that meets the target account condition. It can be understood that the target delivery account that meets the target account condition can be one or more. In the case of multiple target delivery accounts, each target delivery account is processed according to the following process.

[0064] In some embodiments, the target account condition is defined by the attribute value range corresponding to one or more attributes. Assuming that the target account condition is the attribute value range defined for attribute A, if the attribute value of a delivery account under attribute A is within the attribute value range defined for attribute A in the target account condition, it can be determined that the delivery account meets the target account condition. In the case where the target account condition is defined by the attribute value range corresponding to multiple attributes, the target account condition defines the logical relationship between the attribute value ranges corresponding to different attributes, such as logical AND, logical OR, logical NOT, etc. An attribute of a delivery account can also be called a label of the delivery account.

[0065] In the case where the target account condition is defined by the attribute value range corresponding to one or more attributes, the attribute information of each delivery account can be determined based on the account data of each delivery account, and the attribute information includes the attribute value of the delivery account under each attribute, and the target delivery account that meets the target account condition is determined based on the attribute value range corresponding to the attribute defined by the target account condition and the attribute value of each delivery account under each attribute. Specifically, the attribute value of each attribute defined by the target account condition in the attribute information of the delivery account is obtained, and it is determined whether the obtained attribute value is within the attribute value range defined for the attribute in the target account condition. If it is, it is determined that the attribute value of the delivery account under the attribute meets the attribute value range defined for the attribute by the target account condition; if the attribute values ​​of all the attributes defined in the target account condition in the attribute information of the delivery account meet the attribute value range defined in the target account condition, then the delivery account is determined to be the target delivery account that meets the target account condition.

[0066] The attributes of the delivery account include, for example, the company name, registered capital, service provider, industry (e.g., primary industry, secondary industry, etc.) of the company to which the delivery account belongs, optimization goals (e.g., shallow optimization goals, deep optimization goals) specified in the advertising plan of the delivery account, account balance of the delivery account, whether the delivery account is an active account within the preset time from the current time, delivery consumption of the delivery account for the specified delivery content (e.g., product B) within the specified time period, the ratio between the delivery effect of the delivery account for the specified delivery content within the specified time period and the promotion target consumption, average daily delivery consumption within the preset time from the current time (e.g., average daily consumption in the last three days), etc. It is worth mentioning that the above attributes of the delivery account are only illustrative examples and cannot be considered as limiting the scope of use of this application.

[0067] In some embodiments, an account matching model can be used to determine whether a placement account meets the target account condition based on the target account condition and the attribute information corresponding to each placement account. The account matching model can be constructed by a neural network (e.g., a fully connected network, a recurrent network, etc.). The attribute information corresponding to the placement account includes the attribute value of the placement account under each attribute.

[0068] Specifically, the attribute value range limited for each attribute in the target account condition can be vectorized to obtain the feature vector corresponding to the target account condition; and the attribute value under each attribute in the attribute information corresponding to the delivery account to be matched can be vectorized to obtain the attribute feature vector corresponding to the delivery account; then, the feature vector corresponding to the target account condition and the attribute feature vector corresponding to the delivery account are input into the account matching model, and the account matching model performs deep feature extraction and fusion according to the feature vector corresponding to the target account condition and the attribute feature vector corresponding to the delivery account, and performs classification, and outputs the matching label between the delivery account and the target account condition, and the matching label is used to indicate the matching degree between the delivery account and the target account condition, or to indicate whether the delivery account meets the target account condition. If it is determined based on the matching label that the delivery account meets the target account condition, the delivery account is correspondingly determined as the target delivery account. Among them, the network layer used for feature extraction in the account matching model can process the input features based on the attention mechanism, so that it can be ensured that the account matching model can effectively refer to the correlation between different features in the input information during the processing process.

[0069] In order to ensure the accuracy of the matching degree classification of the account matching model, the account matching model can be trained first through training data. The training data includes multiple training samples and label information corresponding to each training sample. A training sample includes a sample account condition and attribute information corresponding to a sample delivery account. The label information corresponding to the training sample is used to indicate whether the sample delivery account in the training sample meets the sample account condition. The account matching model is trained according to the following process: for each training sample, a sample feature vector corresponding to the sample account condition is obtained, and an attribute feature vector corresponding to the sample delivery account is obtained, wherein the sample feature vector corresponding to the sample account condition is obtained by vectorizing the sample account condition, and the attribute feature vector corresponding to the sample delivery account is obtained by vectorizing the attribute information corresponding to the sample delivery account; the account matching model predicts the matching degree according to the sample feature vector corresponding to the sample account condition and the attribute feature vector corresponding to the sample delivery account, and outputs the matching degree label between the sample delivery account and the sample account condition; the prediction loss is calculated according to the matching degree label between the sample delivery account and the sample account condition, and the label information corresponding to the training sample from which the sample delivery account and the sample account condition are derived; the parameters of the account matching model are adjusted inversely according to the prediction loss until the training end condition is met. The training end condition may be that the number of iterations of the account matching model reaches a threshold, or that the loss function of the account matching model converges, or that the prediction accuracy of the account matching model is higher than an accuracy threshold.

[0070] Through the above training process, the account matching model can learn the relationship between the sample delivery account and the sample account conditions, as well as the relationship between the attributes involved in the sample feature vector and the attributes involved in the attribute feature vector based on the attribute feature vector corresponding to the sample delivery account and the sample feature vector corresponding to the sample account conditions, and thus accurately predict the matching degree.

[0071] In some application scenarios, the attributes involved in the attribute information maintained for the delivery account may change, for example, the personalized basic attributes maintained for the delivery account may change, or the personalized basic attributes maintained for different delivery accounts may be different, while the attributes involved in the target account conditions in the target delivery strategy remain relatively unchanged. There may be an attribute involved in the attribute information of the delivery account (assuming it is attribute A) that is not involved in the target account conditions, but another attribute involved in the target account conditions (assuming it is attribute B) has a high correlation with attribute A, for example, attribute A is the average daily consumption of the delivery account in the past three days, and attribute B is the average daily consumption of the delivery account in the past five days. In the case where the attributes involved in the attribute information of the delivery account change, if the target account conditions limit A certain attribute (such as attribute B mentioned above) is not involved in the attribute information of the delivery account, but the attribute information of the delivery account involves another attribute A that is highly correlated with attribute B. In this case, the value of attribute B is searched from the attribute information of the delivery account, and the judgment is made in combination with the attribute value range specified by the target account condition for attribute B, which is easy to lead to misjudgment of the matching degree between the delivery account and the target account condition. In this case, the matching degree between the delivery account and the target account condition is predicted by the account matching model. Since the account matching model can fully explore the correlation between the attribute information of the delivery account and the attributes specified in the target account condition, it can effectively solve the above-mentioned problem of misjudgment caused by the fact that some attributes involved in the target account condition are not involved in the attribute information of the delivery account.

[0072] The task period refers to the time period for executing the target delivery strategy, which can be configured according to actual needs during the process of configuring the target delivery strategy. The task period indicates the duration of executing the target delivery strategy. The start time of the task period can be a specified time or a specified relative time. For example, the time when the user on the delivery account side operates according to the delivery operation guidance information can be used as the start time of the task period, and the time interval between the target delivery account sending the task acceptance instruction and the specified time can be used as the start time of the task period.

[0073] The delivery operation guidance information is used to indicate delivery guidance actions, which refer to operations related to content (e.g., advertisement) delivery and can be triggered on the client where the delivery account is located. Delivery guidance actions include operations such as changing the delivery position and / or delivery media platform configured by the user corresponding to the delivery account, updating the delivery material configured by the user corresponding to the delivery account, updating the delivery bid type configured by the user corresponding to the delivery account, changing the delivery form (e.g., video+text form, image+text form) configured by the user corresponding to the delivery account, etc. The delivery guidance actions indicated by the delivery operation guidance information in a delivery strategy can be one or more, which are not specifically limited here.

[0074] The task indicator information is used to indicate the goal to be achieved by executing the target delivery strategy. In some embodiments, the task indicator information may include the parameter range set by the indicator parameter, or the reaching condition set for the indicator parameter. The indicator parameter may also be referred to as the task indicator, and the indicator parameters include, for example, the number of advertisements, the lead marking rate, the account recharge, the number of video creatives, the number of creatives, the number of materials, the click-through rate, etc., which are not specifically limited here.

[0075] In some embodiments, the task indicator information may include subtask indicator information set for each delivery guidance action, and the subtask indicator information includes a parameter range set for the indicator parameter, wherein the goals to be achieved by executing different delivery guidance actions can be limited by different indicator parameters or by different parameter ranges of the same indicator parameter. For example, if the delivery operation guidance information in the target delivery strategy includes two delivery guidance actions (delivery guidance action K1 and delivery guidance action K2), the task indicator information may include a goal set for delivery guidance action K1 and a goal set for delivery guidance action K2, wherein the goal set for delivery guidance action K1 is, for example, that the number of online advertisements reaches a first threshold value Z1; and the goal set for delivery guidance action K2 is, for example, that the number of materials used in advertisements reaches a second threshold value Z2.

[0076] Step 220: Send the target delivery task to the target delivery account, where the target delivery task is used to execute the target delivery strategy.

[0077] After the target delivery task is sent to the target delivery account, the target delivery task details can be displayed on the client where the target delivery account is located. The target delivery task details include at least the task period, task description, and delivery guidance actions in the delivery operation guidance information in the target delivery strategy. Further, after the target delivery account receives the target delivery task, the user on the target delivery account side can choose to accept the target delivery task or reject the target delivery task.

[0078] Step 230: if the task acceptance instruction returned by the target delivery account is received, during the task period, the target delivery account delivers content according to the delivery operation guidance information, and the task progress information of the target delivery task is determined according to the delivery data and task indicator information of the target delivery account.

[0079] As described above, the user on the target delivery account side can choose to accept the target delivery task or reject the target delivery task. If it is detected that the task acceptance operation is triggered in the display page corresponding to the target delivery task, the target delivery account (or the client where the target delivery account is located) sends a task acceptance instruction to the delivery management server. The task acceptance operation can be a click, touch, slide, etc. operation triggered by the task acceptance control, which is not specifically limited here.

[0080] If the user on the target delivery account side chooses to accept the target delivery task, the user on the target delivery account side can operate according to the delivery operation guidance information in the target delivery strategy. Correspondingly, during the task period, the media platform can deliver content based on the information after the target delivery account has operated according to the delivery operation guidance information. On this basis, the delivery management server can collect the delivery data of the target delivery account, and determine the task progress information of the target delivery task by combining the delivery data of the target delivery account and the task indicator information.

[0081] The delivery data of the target delivery account refers to the data related to content delivery generated after the target delivery account operates in accordance with the delivery operation guidance information during the task period. The delivery data may include, for example, the number of advertisements delivered in each advertising position (delivery position) after operating in accordance with the delivery operation guidance information during the task period, as well as the conversion information of different delivery positions (such as the number of clicks, the number of application downloads, the number of orders, etc.), the total consumption of the account, the number of materials used for content delivery in each delivery position, etc.

[0082] The task progress information of the target delivery task is used to reflect the task execution progress of the target delivery task. Based on the delivery data of the target delivery account and the target defined by the task indicator information, the task execution progress of the target delivery task executed by the target delivery account can be determined. If it is determined through the delivery data of the target delivery account that the target indicated by the task indicator information has been achieved, the task execution progress of the target delivery task can be determined to be 100%.

[0083] Since the delivery data of the target delivery account obtained at different time points during the task period may be different, in order to more accurately reflect the completion of the target delivery account for the target delivery task, the delivery data of the target delivery account can be periodically obtained at a preset interval during the task period, and then the task progress information of the target delivery task at different time points can be calculated based on the delivery data and task indicator information of the target delivery account obtained at different time points.

[0084] In some embodiments, the task indicator information may include the compliance conditions corresponding to the indicator parameters set for each delivery guidance action, and correspondingly, the delivery data of the target delivery account includes the parameter information of the target delivery account for the indicator parameters corresponding to each delivery guidance action. The delivery management server may create a periodic task for the target delivery account in response to the task acceptance instruction returned by the target delivery account, and the periodic task is used to obtain the parameter information of the target delivery account under the indicator parameters corresponding to each delivery guidance action according to the preset interval duration (the parameter information is, for example, the numerical value of the indicator parameter), and the duration of two consecutive executions of the periodic task is the preset interval duration. The task information of the periodic task includes the target delivery account, the indicator parameters corresponding to the delivery guidance action, and the data source information corresponding to the indicator parameters. The data source information corresponding to the indicator parameters is used to indicate the data source of the parameter information of the indicator parameters, and the data source information corresponding to the indicator parameters may include the network address of the data source.

[0085] On this basis, the target delivery account and indicator parameters can be used as request input parameters, and the network address of the data source corresponding to the indicator parameters can be used as the address of the accessed party to perform request encapsulation, and a template request for the indicator parameters of the target delivery account can be obtained. A template request can be constructed for each indicator parameter. Thereafter, when the execution of a periodic task is triggered based on the interval duration, the template request is called, and a request for the indicator parameters is initiated to obtain the parameter information of the target delivery account for the indicator parameters, and the task execution progress of the target delivery task is calculated. In this embodiment, in response to the task acceptance instruction returned by the target delivery account, a periodic task is created, and a template request is obtained based on the task information encapsulation of the periodic task. In this way, in the task period corresponding to the target delivery task, when the execution of the periodic task is triggered, the template request is reused to obtain the latest parameter information of the target delivery account for each indicator parameter, without the need to repeat the request encapsulation every time the acquisition is required, which can improve the data acquisition efficiency.

[0086] In some embodiments, if the indicator parameter is a composite parameter, that is, the value of the indicator parameter needs to be calculated through other metadata, and the indicator parameter is not directly stored in the database, the delivery management server can determine the splitting information corresponding to the indicator parameter in the parameter splitting information set, wherein the parameter splitting information set includes splitting information corresponding to multiple composite parameters, and the splitting information includes metadata corresponding to the composite parameter, and the association relationship between the metadata corresponding to the composite parameter and the composite parameter, and the association relationship can also be understood as a calculation method for calculating the composite parameter through metadata.

[0087] In this case, a periodic task is created for the target delivery account according to the metadata corresponding to the indicator parameters and the data source information of the metadata; and for each metadata, the target delivery account and metadata are used as request input parameters, and the network address of the data source corresponding to the metadata is used as the accessed party address, and the request is encapsulated to obtain a template request for the metadata of the target delivery account. Afterwards, in the process of triggering the execution of the periodic task, the metadata information is obtained by calling the template request for the metadata, and the value of the indicator parameter is calculated according to the association between the metadata and the indicator parameter and the latest metadata information, and then the task progress information of the target delivery task is determined based on the value of the indicator parameter and the corresponding compliance condition of the indicator parameter.

[0088] In some embodiments, a composite identifier may be added in advance for the indicator parameter involved, and the composite identifier is used to indicate whether the indicator parameter is a composite parameter, and the composite identifier includes a first identifier for indicating that the indicator parameter is a composite parameter and a second identifier for indicating that the indicator parameter is not a composite parameter. In some embodiments, a composite identifier may be added to the indicator parameter according to the parameter splitting information set. If there is splitting information corresponding to an indicator parameter (assuming it is an indicator parameter P) in the parameter splitting information set, a first identifier is added to the indicator parameter P; otherwise, a second identifier is added to the indicator parameter P. On this basis, the delivery management server may determine whether the indicator parameter is a composite parameter according to the composite identifier of the indicator parameter involved in the task indicator information in the target delivery strategy. If the indicator parameter is a composite parameter, the template request is encapsulated in units of the metadata of the indicator parameter according to the above embodiment; if the indicator parameter is not a composite parameter, the template request is encapsulated in units of the indicator parameter according to the above embodiment.

[0089] In some embodiments, after receiving the task acceptance instruction returned by the target delivery account, the delivery management service end can obtain the operation log of the target delivery account to determine whether the user on the target delivery account side operates according to the delivery guidance action in the delivery operation guidance information based on the operation log of the target delivery account. After determining that the user on the target delivery account side operates according to the delivery guidance action in the delivery operation guidance information, it is confirmed that the task period corresponding to the target delivery task has been entered, that is, the task period in the target delivery strategy, or the time recorded in the operation log indicating that the user on the target delivery account side operates according to the delivery guidance action in the delivery operation guidance information is used as the start time of the task period corresponding to the target delivery task. After confirming that the task period corresponding to the target delivery task has been entered, the delivery data of the target delivery account can be periodically obtained according to the above-mentioned embodiment, and the task progress information of the target delivery task can be calculated accordingly. In this embodiment, after determining that the user on the target delivery account side operates according to the delivery guidance actions in the delivery operation guidance information, the calculation of the task progress information of the target delivery task is started. In this way, the accuracy of the calculated task progress information can be guaranteed, and the situation where the task progress information calculated based on the delivery data of the target delivery account cannot reflect the execution progress of the target delivery task when the user on the target delivery account side does not operate according to the delivery guidance actions in the delivery operation guidance information is avoided.

[0090] It should be noted that in the specific implementation of the present application, the relevant data involved in the delivery account (such as the attribute values ​​of the delivery account under each attribute mentioned above), the operation log of the delivery account and other related data, when applied to the specific products or technologies of the embodiments of the present application, need to obtain user permission or consent, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions, and carry out subsequent data use and processing within the scope of authorization of laws, regulations and personal information subjects.

[0091] In some embodiments, the delivery data of the target delivery account includes parameter information of the indicator parameters indicated by the task indicator information, and the task indicator information includes the compliance conditions for the indicator parameters, which may include the minimum threshold value of the indicator parameters. In this case, the quotient of the numerical value indicated by the parameter information of the indicator parameter and the minimum threshold value can be calculated as the task progress of the target delivery task.

[0092] In some embodiments, the task indicator information may include compliance conditions set respectively for at least two indicator parameters, and a logical operation relationship between at least two compliance conditions, such as a logical AND, a logical OR, etc. In this case, the reference progress of each indicator parameter can be determined respectively for the parameter information corresponding to each indicator parameter and the minimum threshold in the compliance condition corresponding to the indicator parameter. For example, the quotient of the value indicated by the parameter information corresponding to an indicator parameter and the minimum threshold in the compliance condition corresponding to the indicator parameter can be used as the reference progress of the indicator parameter; then, the task progress of the target delivery task is determined based on the reference progress corresponding to the at least two indicator parameters and the logical operation relationship between the at least two compliance conditions.

[0093] In some embodiments, if the logical operation relationship between at least two conditions for reaching the target is a logical AND, the reference progress corresponding to the at least two indicator parameters can be multiplied to obtain the task progress of the target delivery task. If the logical operation relationship between at least two conditions for reaching the target is a logical OR, the maximum reference progress among the reference progress corresponding to the at least two indicator parameters can be used as the task progress of the target delivery task.

[0094] It is understandable that if the user on the target delivery account side chooses to reject the target delivery task, the corresponding target delivery account sends a task rejection instruction to the delivery management server, and the delivery management server does not need to periodically calculate the task progress information of the target delivery task under the target delivery account. In some embodiments, if the delivery management server receives a task rejection instruction returned by the target delivery account, it can accumulate the number of task rejections for the target delivery account and use the accumulated number of task rejections as the data basis for candidate delivery strategy optimization.

[0095] Step 240: Send task progress information to the target delivery account.

[0096] The task progress information can be displayed on the task display page of the target delivery task in the client where the target delivery account is located, so that the user on the target delivery account side can know the task completion status of the target delivery task in a timely manner.

[0097] Figure 3 is a schematic diagram of a task display page in a delivery client according to an embodiment of the present application. Figure 3The task display page 310 of the delivery task "2022-New Customer-XX Optimization Strategy" is shown in the figure. The task display page 310 shows the detailed information of the task, which includes the task description and task action. The task description includes the task period, task classification, and description information; the content of the task action part may include the delivery operation guidance information in the delivery strategy. The task display page 310 also includes a task progress display area 311 and a task status display area 312. The task progress display area 311 is used to display the task execution progress of the delivery task. Figure 3 The task execution progress shown in FIG. 3 is 17%. The task status display area 312 is used to display the status of the delivery task, such as being executed, abandoned, not started, etc.

[0098] The task display page 310 also includes a task abandonment control 313. If the user triggers the task abandonment control 313, the delivery client sends a task abandonment request to the delivery management server. The task abandonment request is used to request to abandon the execution of the corresponding delivery task.

[0099] In some embodiments, the client where the delivery account is located can display an abandon task control in the task display page during the task period corresponding to the delivery task and when the task progress information corresponding to the delivery task indicates that the delivery task has not been completed; conversely, if the task period corresponding to the delivery task ends, or the task progress information corresponding to the delivery task indicates that the delivery task has been completed, the abandon task control will not be displayed in the task display page to avoid the user accidentally triggering the abandon task control and sending an invalid task abandon request.

[0100] In some embodiments, if the user triggers the abandon task control 313 in the task display page 310, the task abandon page 410 may be displayed on the client, such as Figure 4 As shown, the task abandonment page 410 can be used by the user to input the reason for abandoning the delivery task. After that, the reason for abandoning the delivery task is encapsulated into the task abandonment request. After receiving the task abandonment request, the delivery management server can cancel the target delivery task for the corresponding delivery account and record the reason for abandoning the delivery task in the task delivery request, so as to optimize the delivery strategy based on the reason for abandoning the delivery task and the delivery strategy corresponding to the delivery task. It is worth mentioning that Figure 4 The optional reasons for abandoning the delivery task shown in are merely illustrative examples, and in other embodiments, other optional reasons may also be provided.

[0101] In some embodiments, after step 230, the method further includes: during the task period, if a task abandonment request for the target delivery task is received from the target delivery account, canceling the target delivery task for the target delivery account.

[0102] After canceling the target delivery task for the target delivery account, the subsequent delivery management server does not need to maintain the task progress information of the target delivery task for the target delivery account. In some embodiments, the delivery management server can also respond to the task abandonment request and accumulate the number of delivery task abandonments of the target delivery account. The number of delivery task abandonments can be used as a data reference for whether to send delivery tasks to the target delivery account in the future. For example, if the number of delivery task abandonments of the target delivery account exceeds the first number threshold, or the number of delivery task abandonments of the target delivery account within the preset first time period exceeds the second number threshold, it is determined not to send the delivery task to the target delivery account.

[0103] In some embodiments, during the task period, if a task abandonment request for the target delivery task is received from the target delivery account, after the target delivery task is canceled for the target delivery task, the method also includes: during the task period, if a task abandonment request for the target delivery task is received from the target delivery account, the task progress information for the target delivery task is restored and maintained for the target delivery account; that is, the delivery management server continues to determine the task progress information of the target delivery task based on the delivery data and task indicator information of the target delivery account during the task period, and sends the task progress information of the target delivery task to the target delivery account.

[0104] That is, after the client where the delivery account is located sends a task abandonment request for the delivery task, a cancel abandonment task control may be displayed in the task display page corresponding to the delivery task, and the user may send a cancel abandonment task request to the delivery management server by triggering the cancel abandonment task control. In some embodiments, to avoid user mis-triggering, the cancel abandonment task control is not displayed in the task display page corresponding to the target delivery task in the client where the delivery account is located when the task abandonment request is not sent to the delivery management server and / or the end time of the task period of the target delivery task is reached.

[0105] In this application, account matching is performed based on the target account conditions in the target delivery strategy, the target delivery account that meets the target account conditions is determined, and the target delivery task for executing the target delivery strategy is sent to the target delivery account. Since the target delivery strategy includes delivery operation guidance information, delivery operation guidance for the delivery account is achieved through online channels. When the target delivery account accepts the target delivery task, the progress is calculated according to the delivery data of the target delivery account during the task period and the task indicator information in the target delivery strategy, and the task progress information of the target delivery task is determined, so that the progress of the target delivery task is automatically determined. After that, the task progress information is sent to the target delivery account, so that the user on the delivery account side can know the task execution progress of the target delivery task, and the effective interaction with the delivery account is guaranteed. Especially in the case of facing a large number of delivery accounts, this application can issue target delivery tasks to multiple delivery accounts that meet the target account conditions, and can achieve delivery guidance for multiple delivery accounts. Compared with the delivery guidance through offline communication in the related technology, the scheme of this application can improve the efficiency of delivery guidance for delivery accounts and reduce time consumption.

[0106] In the scheme of providing delivery guidance through offline methods, the user on the delivery account side needs to manually configure the task indicator information and report it to the server (i.e., the delivery management server mentioned above) before the progress can be determined. This method requires the user on the delivery account side to perform more manual operations. In the present application, the target delivery strategy includes task indicator information. During the task period, the server can automatically calculate the progress based on the task indicator information and the delivery data of the target delivery account, thereby automatically determining the progress of the target delivery task, reducing user manual operations. Moreover, since there is no need for the delivery account side to report the task indicator information, the interaction between the delivery account side and the server is reduced. When the number of delivery accounts served by the server is large, the response pressure on the server can be greatly reduced.

[0107] In the related art, in the scheme where the user at the delivery management end provides delivery guidance to the optimizer at the delivery end in an offline manner, the delivery management platform cannot determine the progress of the delivery guidance, and the user at the delivery end cannot know the progress of the delivery guidance. In the present application, when the target delivery account accepts the target delivery task, the task progress information of the target delivery task is determined based on the delivery data of the target delivery account during the task period and the task indicator information in the target delivery strategy, and the task progress information is sent to the target delivery account, thereby realizing automatic calculation of the progress of the target delivery task of the delivery guidance.

[0108] In some embodiments, the delivery operation guidance information includes at least one delivery guidance action, the task indicator information includes subtask indicator information corresponding to each delivery guidance action; the subtask indicator information includes the achievement condition corresponding to the indicator parameter; the task progress information includes the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task; in this embodiment, step 230 includes the following steps A1 to A2, which are described in detail as follows:

[0109] Step A1, during the task period, when the target delivery account performs delivery according to each delivery guidance action, the actual parameter value of the target delivery account under the indicator parameter corresponding to each delivery guidance action is obtained.

[0110] The subtask indicator information corresponding to the delivery guidance action is used to indicate the content delivery target set for each delivery guidance action. Among them, the content delivery targets set for different delivery guidance actions can be the same or different. The compliance condition corresponding to the indicator parameter in the subtask indicator information refers to the content delivery target set for the corresponding delivery guidance action, which can be the parameter range set for the indicator parameter. Among them, the indicator parameters in the subtask indicator information corresponding to different delivery guidance actions can be the same or different. Indicator parameters include the number of advertisements, lead marking rate, account recharge, number of video creatives, number of creatives, number of materials, etc. mentioned above.

[0111] The task action progress corresponding to the delivery guidance action is used to reflect the completion progress of the content delivery target set for each delivery guidance action.

[0112] In some embodiments, after sending a target delivery task to a target delivery account, the client corresponding to the target delivery account can be used to detect whether the user on the target delivery account side operates according to each delivery guidance action in the target delivery task. If it is determined that the operation is performed according to the delivery guidance action, the relevant delivery information of the delivery content that meets the delivery guidance action is determined from the delivery data corresponding to the target delivery account. Then, based on the relevant delivery information of the delivery content that meets the delivery guidance action, indicator parameter statistics are performed to obtain the actual parameter values ​​of the target delivery account under the indicator parameters corresponding to each delivery guidance action.

[0113] In some embodiments, after receiving the task acceptance instruction returned by the target delivery account, the operation log of the target delivery account can be obtained, and the operation log is used to determine whether the user on the target delivery account has performed operations in accordance with the delivery guidance actions. If it is determined that the operations have been performed in accordance with the delivery guidance actions, the actual parameter values ​​of the target delivery account under the indicator parameters corresponding to each delivery guidance action are obtained.

[0114] For example, if a delivery guidance action indicates that content is delivered on delivery slots I, II, and III, and the indicator parameter configured for the delivery guidance action is the number of ad clicks, then in step A1, the delivery information related to the content delivered by the target delivery account on delivery slots I, II, and III (i.e., the delivery information related to the delivered content that satisfies the delivery guidance action) can be obtained, and then the number of ad clicks is counted based on the obtained relevant delivery information to obtain the number of ad clicks at the current time, i.e., the actual parameter value of the indicator parameter of the number of ad clicks. In a specific embodiment, the delivery information related to the delivered content can be obtained from the library table and data interface of the delivery end, or the library table in the public data warehouse, and the delivery log data table.

[0115] Step A2, determining the progress of the task action corresponding to each delivery guidance action according to the achievement condition corresponding to the indicator parameter corresponding to each delivery guidance action and the actual parameter value corresponding to the indicator parameter.

[0116] In some embodiments, if the subtask indicator information corresponding to a delivery guidance action includes a compliance condition corresponding to an indicator parameter, the compliance condition of the indicator parameter corresponding to each delivery guidance action defines a lower limit value (or minimum threshold) of the indicator parameter, that is, if the lower limit value is reached, it can be regarded that the task action progress of the delivery guidance action is 100%. Therefore, in step A2, for a delivery specified action, the ratio between the actual parameter value of the indicator parameter corresponding to the delivery guidance action and the lower limit value of the indicator parameter corresponding to the delivery guidance action can be used as the task action progress corresponding to the delivery guidance action.

[0117] In some embodiments, if the sub-task indicator information corresponding to a delivery guidance action includes compliance conditions corresponding to multiple indicator parameters and the logical operation relationship between the compliance conditions corresponding to the multiple indicator parameters, the reference progress corresponding to each indicator parameter is calculated for the delivery guidance action, and the reference progress corresponding to an indicator parameter can be equal to the ratio of the actual parameter value of the indicator parameter to the lower limit value of the compliance condition corresponding to the indicator parameter; then, based on the logical operation relationship between the compliance conditions corresponding to the multiple indicator parameters, the task action progress corresponding to the delivery guidance action is determined according to the reference progress corresponding to the multiple indicator parameters; if the logical operation relationship between the compliance conditions corresponding to the multiple indicator parameters is logical AND, the reference progress corresponding to the multiple indicator parameters can be multiplied, and the product result can be used as the task action progress corresponding to the delivery guidance action; if the logical operation relationship between the compliance conditions corresponding to the multiple indicator parameters is logical OR, the maximum reference progress among the reference progresses corresponding to the multiple indicator parameters can be used as the task action progress corresponding to the delivery guidance action.

[0118] Step A3, determining the task execution progress of the target delivery task according to the task action progress corresponding to each delivery guidance action.

[0119] In some embodiments, if the delivery operation guidance information includes a delivery guidance action, the task action progress corresponding to the delivery guidance action can be used as the task execution progress of the target delivery task.

[0120] In some embodiments, if the delivery operation guidance information includes multiple delivery guidance actions, the average of the task action progress corresponding to the multiple delivery guidance actions can be calculated, and the calculated average can be used as the task execution progress of the target delivery task.

[0121] In some embodiments, the delivery operation guidance information includes multiple delivery guidance actions, and the delivery operation guidance information also includes action weights corresponding to each delivery guidance action; in this embodiment, step A3 includes: performing weighted processing according to the task action progress corresponding to the multiple delivery guidance actions and the action weights corresponding to each delivery guidance action to obtain the task execution progress of the target delivery task.

[0122] The action weight corresponding to each delivery guidance action in the delivery operation guidance information may be configured by the user as the strategy producer during the delivery strategy configuration process. The action weights corresponding to different delivery guidance actions may be the same or different.

[0123] For example, if the target delivery strategy includes two delivery guidance actions, namely delivery guidance action P1 and delivery guidance action P2; the subtask indicator information corresponding to delivery guidance action P1 is: create 10 new advertisements during the task period; the subtask indicator information corresponding to delivery guidance action P2 is: recharge 10,000 yuan during the task period; among them, the action weight configured for delivery guidance action P1 and the action weight configured for delivery guidance action P2 are both 50%. At time point T1 during the task period, it is determined that according to delivery guidance action P1, 5 new advertisements are created, and according to delivery guidance action P2, 1,000 yuan is recharged. At this time point T1: the task action progress corresponding to delivery guidance action P1 is: 5 / 10=50%; the task action progress corresponding to delivery guidance action P2 is: 1000 / 10000=10%; the task execution progress corresponding to the target delivery task is: 50%*50%+10%*50%=30%.

[0124] The task execution progress corresponding to the target delivery task can be used to measure the degree of cooperation of the user on the delivery client side with respect to the delivery guidance action and the delivery quality. It can be understood that the higher the task execution progress corresponding to the target delivery task, the higher the delivery quality of the delivery guidance action in the target delivery task for content delivery.

[0125] In some embodiments, when the task progress information includes the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task, the corresponding delivery client displays the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task in the task display page for the target delivery task. Figure 5 and Figure 6 is a schematic diagram of a task display page in a delivery client according to another embodiment of the present application. Figure 5 and Figure 6 As shown, the task display page includes not only a task progress display area 311 but also an action progress display area 314 for each delivery guidance action. The action progress display area 314 is used to display the progress of the task action corresponding to the delivery guidance action.

[0126] In some embodiments, the task progress information may also include the progress of the advertising task, and the task indicator information may also include the advertising delivery indicator. In this case, the advertising delivery indicator data corresponding to the target delivery account may be obtained during the task period, and the advertising task progress may be calculated based on the advertising delivery indicator data and the advertising delivery indicator. For example, the advertising delivery indicator data may include the number of advertisements delivered per day, and the advertising delivery indicator may be the target number of advertisements; the average number of advertisements per day of the target delivery account during the task period may be calculated based on the advertising delivery indicator data, and the ratio of the average number of advertisements per day to the target number of advertisements may be used as the advertising task progress.

[0127] In some embodiments, the delivery guidance action includes multiple secondary guidance actions; step A1 includes the following steps B1 and B2:

[0128] Step B1, during the task period, obtain the sub-delivery data corresponding to each secondary guidance action under the delivery guidance action of the target delivery account.

[0129] In the case where the delivery guidance action includes multiple secondary guidance actions, the delivery guidance action does not have specific action content, but the delivery guidance action is represented by the action contents of multiple secondary guidance actions under the delivery guidance action.

[0130] Secondary guidance actions include: automatic expansion, bidding type, industry delivery end, delivery position, delivery position & creative form, automatic placement, creative label, DPA (Dynamic Product Ads) product name, DPA customer original product logo, standard product, setting the SPU (Standard Product Unit) logo of the object to be delivered, setting the first-level category name of the product to be delivered, the second-level category name of the product, etc., which are not specifically limited here.

[0131] In the case where the delivery guidance action includes multiple secondary guidance actions, after detecting and determining that the user on the delivery client side operates according to the secondary guidance action, the sub-delivery data obtained after the operation according to the secondary guidance action is obtained, that is, the sub-delivery data corresponding to the secondary guidance action. In some embodiments, the sub-delivery data corresponding to each secondary guidance action can be obtained from the corresponding delivery data source based on the network address of the delivery data source corresponding to each secondary guidance action.

[0132] Step B2, statistics are collected based on the sub-delivery data corresponding to the multiple secondary guidance actions under the delivery guidance action of the target delivery account, to obtain the actual parameter value of the indicator parameter corresponding to the delivery guidance action of the target delivery account.

[0133] In this embodiment, the subtask indicator information is configured in units of delivery guidance actions. Therefore, when a delivery guidance action includes multiple secondary guidance actions, the multiple secondary guidance actions under the delivery guidance action share the same subtask indicator information. On this basis, based on the sub-delivery data corresponding to each secondary guidance action, the indicator parameters corresponding to the delivery guidance action to which the secondary guidance action belongs are counted, and the actual parameter values ​​of the indicator parameters corresponding to the delivery guidance action of the target delivery account are obtained.

[0134] For example, if a delivery guidance action includes two secondary guidance actions, namely secondary guidance action X1 and secondary guidance action X2, wherein secondary guidance action X1 indicates to deliver advertisements on delivery positions P1 to P3; secondary guidance action X2 indicates to deliver commodities under the primary category of commodities, and the indicator parameter in the subtask indicator information of the delivery guidance action is the click volume, on this basis, the sub-delivery data after the operation according to the secondary guidance action X1 can be obtained, and the sub-delivery data after the operation according to the secondary guidance action X2 can be obtained, and then the overall click volume is counted to obtain the actual parameter value of the indicator parameter of the click volume. For example, the sub-delivery data corresponding to the two secondary guidance actions can be intersected or unioned to obtain the actual parameter value of the indicator parameter.

[0135] Figure 7 FIG. 1 is a flow chart showing the actual parameter value statistics for the indicator parameter corresponding to the delivery guidance action according to an embodiment of the present application. Figure 7 As shown in the figure, after sending the target delivery task to the target delivery account, the delivery management server creates a scheduled task for closed-loop management, that is, it updates the task progress in real time according to the delivery data on the delivery client side. Figure 7As shown, if it is determined that the downgrade switch in the delivery management server is in the on state, it is processed according to the processing logic in the downgrade path; if it is determined that the downgrade switch in the delivery management server is in the off state, in the closed-loop management process, it is diverted according to the secondary guidance action in the target delivery task, and the advertisements that meet the conditions (i.e., delivery content) are queried, that is, the sub-delivery data corresponding to each secondary guidance action is obtained. The advertisements to be queried are received from multiple upstream data sources through the anti-corrosion layer, and then the quantity is counted to obtain the actual parameter values ​​of the indicator parameters corresponding to the delivery guidance action of the target delivery account, and then the actual parameter values ​​of the indicator parameters corresponding to the delivery guidance action that are counted are used to update the task action progress and the task execution progress.

[0136] Since the data paths of different secondary guidance actions may be different, in this embodiment, the data are diverted according to the secondary guidance action, and different data paths are separated according to the secondary guidance action. In this way, the corresponding sub-delivery data can be obtained from the upstream data source (i.e., the delivery data source) corresponding to the secondary guidance action.

[0137] When requesting the upstream data source, an anti-corrosion layer is passed in the middle. This anti-corrosion layer can isolate the differences between the demand-side interface (i.e., the interface on the delivery management server side) and the interface on the upstream data source side, and perform interface difference conversion in the anti-corrosion layer. The anti-corrosion layer provides a stable interface to the demand side. In this way, if the interface on the data source side changes, only the logic of the interface difference conversion in the anti-corrosion layer needs to be changed without changing the demand-side interface. The anti-corrosion layer can realize the convergence of interface changes in the anti-corrosion layer and will not spread to the demand-side interface.

[0138] In the above embodiment, multiple secondary guidance actions under the delivery guidance action are split, and each secondary delivery guidance action is managed in a closed loop, so that after the user on the target delivery account side operates according to the secondary delivery guidance action, the sub-delivery data under each secondary delivery operation guidance is obtained in real time, normalized, and the task action progress of each delivery guidance action is calculated.

[0139] In this embodiment, a secondary delivery guidance action can be regarded as a task requirement, and a secondary delivery guidance action can be further abstracted into a filter described by attributes (field), operators (operators), and data values ​​(values). For example, the secondary guidance action that the bid type includes automatic bidding and manual bidding can be abstracted as: attribute-bid type; operator-includes; data value-manual bidding, automatic bidding; according to this method, each delivery guidance action can be abstracted into a filter, which has good scalability. In this way, based on the filter corresponding to the secondary delivery guidance action, it can be detected whether the user on the client side corresponding to the delivery account operates according to the secondary delivery guidance action.

[0140] In some embodiments, the target delivery strategy also includes an effect measurement strategy; after step 240, the method further includes the following steps C1 and C2:

[0141] Step C1, based on the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the end time of the task period and the effect measurement strategy, measure the effect of the target delivery task to determine the effect measurement result of the target delivery task.

[0142] The first delivery effect data refers to the delivery effect data corresponding to the target delivery account in the reference period; the second delivery effect data refers to the delivery effect data corresponding to the target delivery account at the end time of the task period.

[0143] The effect measurement strategy is used to measure the effect of delivery after the delivery operation guidance information in the target delivery strategy is operated. In the present application, the effect measurement strategy uses the delivery effect data of the reference period as a reference, and combines the delivery effect data corresponding to the end time of the task period to measure the quality of the delivery operation guidance information in the target delivery strategy, or measures the delivery effect after the delivery operation guidance information in the target delivery strategy is operated. Among them, the effect measurement strategy can indicate a time period as a reference, that is, a reference period, such as the previous delivery cycle before executing the target delivery task, such as the start time of the task period corresponding to the target delivery task, etc.

[0144] Table 1 below shows some of the effect measurement strategies by way of example:

[0145] Table 1

[0146]

[0147] The effect measurement strategies listed in Table 1 above are only illustrative examples and cannot be considered as limiting the scope of use of this application. The main accounting customer in Table 1 above refers to the customer who conducts integrated settlement. For example, if a customer opens multiple business licenses, but is actually one customer, the same settlement customer to which the multiple business licenses belong is called the main accounting customer.

[0148] In some embodiments, the effect measurement strategy in the target delivery strategy can also be obtained by performing logical operations on multiple sub-effect measurement strategies, such as logical AND, logical NOT, logical OR, etc. For example, the effect measurement strategy A in Table 1 and the effect measurement strategy B are logically ANDed, and the obtained new effect measurement strategy is used as the effect measurement strategy in a delivery strategy.

[0149] The effect measurement strategy includes positive measurement conditions defined by effect indicator parameters, such as click-through rate, conversion rate, average daily consumption per account, account consumption growth rate, and month-on-month increase in total account consumption. Positive measurement conditions refer to the conditions that need to be met for the effect measurement result to be a positive result. On the contrary, if it is determined that the positive measurement conditions in the effect measurement strategy are not met based on the first delivery effect data and the second delivery effect data, the effect measurement result is determined to be a negative result. If the effect measurement result of the target delivery task is a positive result, it indicates that the delivery effect is significantly improved after the target delivery task is executed; if the effect measurement result is a negative result, it indicates that the delivery effect is not significantly improved after the target delivery task is executed, or the delivery effect cannot be improved. It is worth mentioning that the effect indicator parameters in the effect measurement strategy can be one or more. For example, in the above effect measurement strategy A, the effect indicator parameters include the account consumption growth rate of the completed task and the main account customer X agent account consumption growth rate.

[0150] In some embodiments, the effect measurement strategy may indicate the effect indicator parameters that need to be compared. On this basis, the first delivery effect data includes a first value of the effect indicator parameter, and the second delivery effect data includes a second value of the effect indicator parameter. Then, based on the first value and the second value of the effect indicator parameter, it is determined whether the positive measurement conditions in the effect measurement strategy are met. If so, the effect measurement result is determined to be a positive result; otherwise, if not, it is determined to be a negative result.

[0151] In some embodiments, the effect measurement strategy includes a positive measurement condition defined by an effect indicator parameter, the first delivery effect data includes a first value corresponding to a sub-effect indicator parameter used to determine the effect indicator parameter; the second delivery effect data includes a second value corresponding to the sub-effect indicator parameter; in this embodiment, step C1 includes the following steps D1 to D3:

[0152] Step D1, determining the value corresponding to the effect indicator parameter in the reference period according to the first value corresponding to the sub-effect indicator parameter in the first delivery effect data.

[0153] The sub-effect indicator parameters corresponding to the effect indicator parameters can be obtained by splitting the effect indicator parameters. In practice, the delivery management server may not directly store the information of the effect indicator parameters in the effect measurement strategy, but needs to obtain it through further calculations of the parameters in the delivery effect data. In other words, the effect indicator parameters are composite parameters. Therefore, in this case, the effect indicator parameters can be split to determine the sub-effect indicator parameters of the effect indicator parameters, which can also be called the metadata of the effect indicator parameters. Moreover, the sub-effect indicator parameters obtained by splitting are also data stored in the delivery management server or other databases. This makes it easy to directly read the values ​​of the sub-effect indicator parameters from the delivery management server or other databases.

[0154] In some embodiments, split information may be configured and stored in advance for the effect indicator parameter as a composite parameter, and the split information corresponding to the effect indicator parameter includes a sub-effect indicator parameter corresponding to the effect indicator parameter, and a calculation method for determining the effect indicator parameter according to the sub-effect indicator parameter corresponding to the effect indicator parameter. On this basis, before step C1, the sub-effect indicator parameter corresponding to the effect indicator parameter may be determined according to the split information corresponding to the effect indicator parameter, and the first value of the sub-effect indicator parameter for the target delivery account in the reference period and the second value of the sub-effect indicator parameter for the target delivery account at the end time of the task period may be obtained from the data source corresponding to the sub-effect indicator parameter.

[0155] After obtaining the first numerical values ​​corresponding to multiple sub-effect indicator parameters, the value of the effect indicator parameter can be calculated based on the relationship between the sub-effect indicator parameters and the effect indicator parameter, such as the calculation method in the splitting information of the effect indicator parameter, according to the first numerical values ​​corresponding to the multiple sub-effect indicator parameters, that is, the value corresponding to the effect indicator parameter in the reference period.

[0156] Step D2, determining the value corresponding to the effect indicator parameter at the end time of the task period according to the second value corresponding to the sub-effect indicator parameter in the second delivery effect data.

[0157] Similarly, after obtaining the second numerical value corresponding to the sub-effect indicator parameter, the value of the effect indicator parameter can be calculated based on the relationship between the sub-effect indicator parameter and the effect indicator parameter according to the second numerical value corresponding to the sub-effect indicator parameter, that is, the value corresponding to the effect indicator parameter at the end time of the task period.

[0158] Step D3, determining the effect measurement result of the target delivery task according to the value of the effect indicator parameter corresponding to the reference period, the value of the effect indicator parameter corresponding to the end time of the task period, and the positive measurement condition.

[0159] If the positive measurement conditions are met based on the values ​​corresponding to the effect indicator parameters in the reference period and the values ​​corresponding to the effect indicator parameters at the end time of the task period, then the effect measurement result of the target delivery task is determined to be a positive result; conversely, if it is determined that the positive measurement conditions are not met, then the effect measurement result of the target delivery task is determined to be a negative result.

[0160] In some embodiments, before step D3, the method further includes the following steps E1 to E4:

[0161] Step E1, splitting the effect indicator parameter in the positive measurement condition to determine the sub-effect indicator parameter corresponding to the effect indicator parameter.

[0162] In step E1, the effect indicator parameter is split to determine the sub-effect indicator parameter used to determine the effect indicator parameter, and the sub-effect indicator parameter can also be called metadata of the effect indicator parameter. Moreover, the information corresponding to the split sub-effect indicator parameter can also be directly read.

[0163] In some embodiments, the effect indicator parameter may be split according to the splitting information corresponding to the effect indicator parameter to determine a plurality of sub-effect indicator parameters corresponding to the effect indicator parameter.

[0164] In other embodiments, keyword recognition may be performed on the names corresponding to the effect indicator parameters, and a splitting strategy corresponding to the keywords in the names of the effect indicator parameters may be matched, and then the effect indicator parameters may be split according to the determined splitting strategy to determine the sub-effect indicator parameters corresponding to the effect indicator parameters. In a specific embodiment, the keywords in the names corresponding to the effect indicator parameters may be identified by text semantic recognition or regular expression matching.

[0165] Keywords in the names of effect indicator parameters include, for example, "proportion", "ratio", "growth rate", "decline rate", "growth range", "change range", etc. A corresponding splitting strategy can be pre-configured for each keyword, and the splitting strategy indicates the way to split the effect indicator parameter, as well as the calculation method between the effect indicator parameter and the sub-effect indicator parameter. For example, for an effect indicator parameter whose name includes "growth rate" and "decline rate", the splitting strategy corresponding to the keyword can indicate that the effect indicator parameter is split into two sub-effect indicator parameters, and the calculation method is: the difference between 1 and the target ratio is the value of the effect indicator parameter, and the target ratio is the ratio of the two sub-effect indicator parameters. The name of the sub-effect indicator parameter can be determined according to the content before the keyword in the name of the effect indicator parameter. In a specific embodiment, if the names of multiple sub-effect indicator parameters determined by splitting an effect indicator parameter are different only in the words representing time, the multiple sub-effect indicator parameters can be regarded as one sub-effect indicator parameter. For example, the effect indicator parameter "growth rate of consumption of accounts that complete tasks" mentioned above has the keyword "growth rate" and can be split into two sub-effect indicator parameters according to the splitting strategy corresponding to the keyword: the consumption of the account that completes the task before the task period and the consumption of the account that completes the task during the task period. It can be seen that the difference between the names of the two sub-effect indicator parameters is only the different words representing time, one is "before the task period" and the other is "during the task period". Therefore, the two sub-effect indicator parameters can be regarded as one sub-effect indicator parameter, namely: the consumption of the account that completes the task; in this way, it is convenient to use different times as request input parameters in the future to obtain the value corresponding to the end time of the task period of the sub-effect indicator parameter, and to obtain the value corresponding to the sub-effect indicator parameter in the reference period. Of course, the above splitting strategies corresponding to keywords are only illustrative examples. In other embodiments, other splitting strategies can also be configured.

[0166] Step E2, determining the data source corresponding to the sub-effect indicator parameter.

[0167] The data source corresponding to the sub-effect indicator parameter refers to the source of the value of the sub-effect indicator parameter. In some embodiments, the data source corresponding to the sub-effect indicator parameter can be determined based on the data path corresponding to each sub-effect indicator parameter. When determining the data source corresponding to each sub-effect indicator parameter, the sub-effect indicator parameter and the data source identifier (e.g., network address, data table identifier, etc.) of the data source corresponding to the sub-effect indicator parameter can be associated and stored, so that it is convenient to quickly read the parameter value of the sub-effect indicator parameter from the data source corresponding to the sub-effect indicator parameter.

[0168] Step E3: acquiring a first value corresponding to the sub-effect indicator parameter in a reference period from a data source corresponding to the sub-effect indicator parameter.

[0169] In step E3, the reference period is taken as a request input parameter, and a first value corresponding to the sub-effect indicator parameter in the reference period is obtained from a data source corresponding to the sub-effect indicator parameter.

[0170] Step E4, obtaining a second value corresponding to the sub-effect indicator parameter at the end time of the task period from a data source corresponding to the sub-effect indicator parameter.

[0171] In step E4, the end time of the task period is used as a request input parameter, and a second value corresponding to the end time of the sub-effect indicator parameter at the task period is obtained from a data source corresponding to the sub-effect indicator parameter.

[0172] Based on the above steps E1 to E4, the first values ​​and the second values ​​of the plurality of sub-effect indicator parameters may be obtained in parallel, which serve as the data basis for subsequently determining the effect measurement result.

[0173] Step C2: Sending the effect measurement result of the target delivery task to the target delivery account.

[0174] Afterwards, the client where the target delivery account is located can display the effect measurement result of the target delivery task in the task display page corresponding to the target delivery task, so that the user can intuitively know the impact of executing the target delivery task on the delivery effect of the delivery account.

[0175] In the related art, in the scheme of providing delivery guidance to the optimizer at the delivery end in an offline manner, it is impossible to effectively measure the effect of the delivery guidance information, and it is impossible to determine the effect after operating according to the delivery guidance. In the present application, after the task period ends, the effect of the target delivery task is automatically measured based on the effect measurement strategy in the target delivery strategy, the first delivery effect data of the target delivery account in the reference period, and the second delivery effect data corresponding to the end time of the task, so as to realize the automatic delivery effect measurement of the delivery operation guidance information in the target delivery strategy, and the effect measurement result obtained by the effect measurement can reflect the delivery effect of the content delivery according to the delivery operation guidance information in the target delivery strategy, thereby effectively solving the problem that the delivery effect cannot be determined in the offline optimization guidance scheme in the related art. In addition, the obtained effect measurement result for the target delivery task can be stored on the delivery service end as the data basis for the subsequent optimization and updating of the target delivery strategy (such as the delivery operation guidance information, task indicator information, etc.) corresponding to the target delivery task.

[0176] Figure 8 is a schematic diagram showing the display of effect measurement results on a task display page according to an embodiment of the present application, such as Figure 8As shown, in the task display page, the content corresponding to the task income is displayed: "Income results: Compared with before the task, the average daily consumption of the account increased by 19% during the task period, which is higher than the overall level of customers." This is the effect measurement result of the target delivery task. It can be seen that Figure 8 The result of this effect measurement is positive.

[0177] In some embodiments, the parameter values ​​of the effect indicator parameters at various time points (e.g., every day) in the reference period and the parameter values ​​of the effect indicator parameters at various time points (e.g., every day) in the task period for the target delivery account may also be sent to the target delivery account along with the effect measurement results, and the change trend graphs of the effect indicator parameters in the reference period and in the task period may be displayed on the task display page, for example Figure 8 In this way, users can intuitively understand the changes in the effect indicator parameters during the reference period and during the task period.

[0178] Fig. 9 is a schematic diagram showing the display of effect measurement results on a task display page according to another embodiment of the present application. Fig. 9 The "income results: compared with before the task, the average daily consumption of the account decreased by 11% during the task period, which is lower than the overall level of customers. There may be other influencing factors. You can go to the feedback center for feedback" is the effect measurement result of the target delivery task. It can be seen that Fig. 9 The effect measurement result is negative.

[0179] In some embodiments, after step C2, the method further includes: receiving first feedback information sent by the target delivery account for the target delivery task, the first feedback information being sent by the client where the target delivery account is located in response to a triggering operation on a first feedback entry; the client where the target delivery account is located responds to the effect measurement result of the target delivery task being a negative effect, and displays the first feedback entry in the task display page corresponding to the target delivery task.

[0180] In this embodiment, when the effect measurement result of the target delivery task is a negative effect, a first feedback entry is displayed in the task display page corresponding to the target delivery task. The first feedback entry refers to an entry for providing feedback on the effect measurement result of the target delivery task. Fig. 9 The area where the "Feedback Center" is located is the first feedback entrance 910. The user can trigger the first feedback entrance, enter the effect measurement result feedback subpage, enter the feedback content in the effect measurement result feedback subpage, and then send the first feedback information to the delivery management server based on the input feedback content. In the subsequent process, the delivery management server can send the first feedback information fed back by the target delivery account for the target delivery task to the delivery configuration end, so that the user of the delivery configuration end can analyze the cause or further optimize the delivery strategy based on the first feedback information.

[0181] This application combines the page operation guidance form on the delivery account side (i.e., the delivery end) to issue the target delivery task for executing the target delivery strategy to the target delivery account that meets the target account conditions in the target delivery strategy. Furthermore, it can also be displayed on the operation page of the delivery end in the form of a system reminder, as well as the account in other applications bound by the user on the delivery account side. In addition, in this application, the target delivery task is managed in a closed loop, and the task execution progress of the target delivery task can be updated in real time according to the delivery data of the target delivery account and the task indicator information in the target delivery strategy, and the delivery effect is measured and feedback is performed after the task period ends. In this way, the online interaction between the delivery account side and the delivery service side is realized, which can improve the efficiency of delivery guidance. Moreover, in this application, the closed-loop management of the task execution progress is performed only when the delivery account side accepts the target delivery task. Therefore, for the user on the delivery end, it can choose to accept or reject the target delivery task according to actual needs.

[0182] In addition, in the present application, if the task execution progress is not completed after the task period of the target delivery task ends, a feedback entrance is provided in the task display page of the delivery end, and a feedback entrance is also provided when the effect measurement result is not a negative result, thereby facilitating users on the delivery side to provide information feedback through online channels, and the feedback information can be used for subsequent delivery strategy optimization.

[0183] Furthermore, in this application, the delivery account is automatically matched based on the target account conditions in the target delivery strategy, and the target delivery task for executing the target delivery strategy is issued to the target delivery account that meets the target delivery conditions, so that the target delivery strategy for delivery guidance is automatically issued to the delivery account. The solution of this application can improve the interaction efficiency between the delivery service end and the delivery end, and update the task completion progress and the effect measurement results of the delivery task, increase the interaction between optimizers and strategy producers, and intuitively present the operation guidance and the effect data of the execution progress and execution results, so as to finally realize the efficient communication closed loop of the media for the delivery operation guidance.

[0184] In some embodiments, when the delivery management service provides services to a large number of delivery accounts, delivery effects of multiple delivery tasks can be measured in batches. Fig.10 FIG. 1 is a flow chart showing how to measure the delivery effect of a delivery task according to an embodiment of the present application. Fig.10As shown, the delivery tasks to be measured for delivery effects can be first obtained from the database; then, the report server is called to obtain the relevant data of the sub-effect delivery parameters corresponding to each delivery task (such as the first delivery effect data and the second delivery effect data mentioned above) and passed into the analysis engine. After that, the analysis engine can load the effect measurement strategy corresponding to each delivery task from the configuration center, and measure the delivery effect of each delivery task in combination with the relevant data of the sub-effect delivery parameters corresponding to each delivery task, and determine the effect measurement results of each delivery task.

[0185] In some embodiments, the effect measurement strategy may be pre-configured to a measurement strategy configuration center, so that the effect measurement strategy may be updated and modified in real time to adapt to different business scenarios and demand changes.

[0186] Fig.11 FIG. 1 is a flowchart of querying after splitting effect indicator parameters according to an embodiment of the present application, such as Fig.11 As shown, the effect indicator parameters in the effect measurement strategy are first split to determine multiple sub-effect indicator parameters, and then the parameter values ​​of the sub-effect indicator parameters are queried to determine the effect measurement results of the delivery task. Fig.11 In the corresponding embodiment, it is assumed that the effect measurement strategy in the target delivery strategy is: effect measurement strategy E & effect measurement strategy F. Among them, effect measurement strategy E is: the month-on-month increase in total consumption of accounts that complete tasks > the month-on-month increase in total consumption of customers in the same industry. Fig.11 As shown, specifically including:

[0187] Step 1110, splitting effect indicator parameters;

[0188] The effect indicator parameters are split for effect measurement strategy E and effect measurement strategy F respectively. For example, the two effect indicator parameters involved in effect measurement strategy E are split into four sub-effect indicator parameters, that is, the effect indicator parameter "the total consumption of the account that completed the task increased month-on-month" is split into the consumption of the delivery account during the task period and the consumption of the delivery account before the task period; the effect indicator parameter "the total consumption of customers in the same industry increased month-on-month" is split into: the consumption of customers in the same industry during the task period and the consumption of customers in the same industry before the task period.

[0189] Step 1120: Summarize sub-effect indicator parameters.

[0190] Summarize all sub-effect indicators involved in the effect measurement strategy in the target delivery strategy and calculate them uniformly. This way, duplicate sub-effect indicator parameters can be filtered out to prevent duplicate calculations and facilitate the implementation of sub-effect indicators. For example, Figure 7The sub-effect indicator parameters split out from the effect indicator parameters involved in effect measurement strategy E and the effect indicator parameters involved in effect measurement strategy F include the consumption of the delivery account during the task period and the consumption of the delivery account before the task period. By summarizing them, duplicate sub-effect indicator parameters can be filtered out to ensure that only one of each sub-effect indicator parameter is retained, thus avoiding repeated queries.

[0191] Step 1130: Determine the query object, query range, and request method corresponding to the sub-effect indicator parameter. In step 1130, each sub-effect indicator parameter is classified according to the query object, query range, and query indicator.

[0192] Table 2 below shows the query object and query range corresponding to each sub-effect indicator parameter in the effect measurement strategy E.

[0193] Table 2

[0194]

[0195]

[0196] In Table 2, each category is regarded as an independent enumeration class. A request method can be provided for each category (query range, query cycle, and query index). The request method provided for each category is shown in Table 3 below:

[0197] Table 3

[0198]

[0199] After step 1130, a query request can be assembled through the query object class request method (e.g., getObjects), the query period class request method (getStartDate, getEndDate), and the query indicator information defined on each sub-effect indicator parameter, and sent to the report server. Data related to the sub-effect indicator parameter can be obtained by calling the relevant interface of the report service.

[0200] After obtaining the data related to the sub-effect indicator parameters, the data can be processed and analyzed in combination with the effect measurement strategy in the target delivery strategy to determine the effect measurement result of the target delivery task. Fig.12 FIG. 1 is a schematic diagram showing how to determine the effect measurement result based on the effect delivery strategy and the parameter values ​​of each effect delivery indicator according to an embodiment of the present application. Fig.12As shown, the delivery effect is measured for the target delivery account belonging to the platform e-commerce industry, as well as the delivery tasks that have been stopped and whose corresponding status is completed. If the consumption is greater than 500 or the exposure is greater than 10,000, the effect measurement result is determined to be a positive result; if the consumption is not greater than 500 or the exposure is not greater than 10,000, the effect measurement result is determined to be a negative result. Fig.12 The information in the dotted box on the right is the data related to the target delivery account, such as the attribute values ​​of the target delivery account under multiple attributes (for example, the attribute value under the industry is platform e-commerce, and the attribute value under the channel center attribute is region), the status information of the target delivery account for the target delivery task (for example, whether to stop delivery, task status, whether to abandon, etc.), and the delivery effect data of the target delivery account (for example, consumption is 830, exposure is 12000).

[0201] In some embodiments, after step 240, the method further includes: receiving second feedback information sent by the target delivery account for the target delivery task, the second feedback information is sent by the client where the target delivery account is located in response to a triggering operation on a second feedback entry; the client where the target delivery account is located displays the second feedback entry in the task display page corresponding to the target delivery task in response to the target delivery task not being completed at the end time of the task period.

[0202] In this embodiment, after the end time of the task period is reached, if it is determined that the task progress information indicates that the target delivery task is not completed, a second feedback entry is displayed in the task display page for the target delivery task in the client where the target delivery account is located. The user can trigger the second feedback entry to provide feedback to the delivery management server on the reason why the target delivery task was not completed, that is, send the second feedback information to the delivery management server. Fig.13 is a schematic diagram of a task display page according to an embodiment of the present application. Fig.13 As shown, after reaching the end time of the task period Fig.13 The delivery task shown is not completed (the task execution progress is 30%), and the second feedback entry 1310 is displayed in the task display page 310, that is, Fig.13 'Uncompleted Feedback' control.

[0203] After receiving the second feedback information sent by the target delivery account for the target delivery task, the delivery management server may send the second feedback information to the delivery configuration terminal to facilitate subsequent users of the delivery configuration terminal to optimize the delivery strategy.

[0204] In some embodiments, step 210 includes: determining the attribute value of each delivery account under each attribute in the attribute set according to the account data of each delivery account; and determining the target delivery account whose attribute value meets the target account condition according to the attribute value of each delivery account under each attribute in the attribute set.

[0205] Among them, the account data of the delivery account may include basic information of the delivery account and delivery-related information of the delivery account. Therefore, attributes can be extracted from the basic information of the delivery account and the delivery-related information of the delivery account to obtain the attribute values ​​of the delivery account under each attribute in the attribute set. An attribute in the attribute set can also be called a label. Attributes such as the company name, industry, registered capital, account balance of the delivery account, whether the delivery account is an active account within a preset time from the current time, delivery consumption of the delivery account for specified delivery content (such as product B) within a specified time period, etc. are not specifically limited here.

[0206] In some embodiments, an attribute set may be preset, and then based on the attributes in the attribute set, attribute values ​​are extracted from corresponding account data for each delivery account to obtain an attribute set including attribute values ​​corresponding to each delivery account.

[0207] In some embodiments, since the contents included in the account data of different delivery accounts may be different, in this case, the basic attributes corresponding to each delivery account can be determined based on the basic information of each delivery account; the basic attributes corresponding to each delivery account are combined with the pre-configured common attributes to determine the attribute set corresponding to each delivery account.

[0208] The basic attributes corresponding to each delivery account can be understood as the individual attributes or individual labels of the delivery account. In this way, the attribute set corresponding to each delivery account includes the individual attributes of the delivery account and the common attributes shared by different delivery accounts. The basic attributes change less frequently, while the common attributes change more frequently. When the common attributes change, the attribute set corresponding to each delivery account can be updated accordingly.

[0209] According to the attribute values ​​of each delivery account under each attribute in the attribute set, the target account conditions in the target delivery strategy can be matched to determine the target delivery account whose attribute value meets the target account conditions. In some embodiments, if there are multiple target delivery accounts determined, it is necessary to send target delivery tasks to multiple target delivery accounts in the future so that multiple target delivery accounts all execute the target delivery tasks. When multiple delivery accounts execute the same target delivery task, they can be regarded as a task group.

[0210] Fig.14 FIG. 1 is a flow chart showing a method of determining a set of attributes of each investment account according to an embodiment of the present application. Fig.14As shown, the performance table, advertising table, consumption table, and industry table can be used as the data basis, and the attribute value of the delivery account can be determined by performing attribute analysis through the analysis engine. For example, the basic attributes can include attributes under the categories of regional account attributes, KA account attributes, and financial reminder account attributes. Fig.14 The basic attributes shown in are only illustrative examples. In addition, based on the performance table, advertising table, consumption table, and industry table, the performance table is converted into a performance common table, the advertising table is converted into an advertising common table, the consumption table is converted into a consumption common table, and the industry table is converted into a consumption industry table, so as to be referenced multiple times in subsequent processes. Thereafter, the analysis engine extracts common attributes based on the performance common table, the advertising common table, the consumption common table, and the consumption industry table to obtain a common table including common attributes, and then performs row and column conversion to obtain a common attribute set; finally, the basic attributes of the delivery account are combined with the attributes in the common attribute set to obtain the attribute set of the delivery account. Since the common table including common attributes is processed by column-to-row conversion, if new common attributes are added, the code does not need to be modified, thereby improving the efficiency of adding new common attributes. Fig.14 The data basis for extracting attribute values, namely, the performance table, the advertising table, the consumption table, and the industry table are merely illustrative examples. In other embodiments, other data related to the delivery account may also be used as the data basis for extracting attribute values.

[0211] Fig.15 is a flow chart of a delivery processing method according to an embodiment of the present application, such as Fig.15 As shown, it includes the following steps 1510 to 1560, which are described in detail as follows:

[0212] Step 1510, attribute value extraction. In this step, the attribute values ​​of each delivery account under multiple attributes are extracted. In some embodiments, the attribute set corresponding to the delivery account can be predetermined, and then the attribute value of each attribute in the attribute set of the delivery account is extracted from the account data of the delivery account.

[0213] In some other embodiments, step 1510 includes the following 1)-4):

[0214] 1) Determine the delivery account for which the attribute value is to be extracted. In some embodiments, a task account condition for sending the delivery task can be pre-set, and then the delivery account that meets the task account condition is determined as the delivery account for which the attribute value needs to be extracted.

[0215] In other embodiments, the delivery effect data of each delivery account within a preset time period (for example, the most recent month) can also be counted, and delivery effect analysis can be performed based on the delivery effect data of the delivery account, such as analyzing the value of the target delivery index (target delivery index such as exposure quantity, exposure rate, number of clicks, number of conversions, etc., which are parameters reflecting the delivery effect of the content). If the delivery effect of a delivery account is determined to be poor (for example, the target index is less than the index threshold) according to the target index corresponding to the delivery account, or the delivery target set by the delivery account cannot be achieved, the delivery account can be determined to be the delivery account for which the attribute value is to be extracted. In other embodiments, the delivery account from which the delivery strategy request is received can also be determined as the delivery account for which the attribute value is to be extracted. For ease of description, the delivery account for which the attribute value is to be extracted is referred to as the first delivery account.

[0216] 2) Obtain the attribute values ​​of the first delivery account under each attribute according to the account data of the first delivery account. The account data of the first delivery account may come from a plurality of different data sources, such as the registration information of the delivery account, the historical delivery data of the delivery account, the historical delivery channel information of the delivery account, and other data related to content delivery. In this process, attribute values ​​may be extracted based on the basic attributes and common attributes in the attribute set of the first delivery account. The attribute values ​​of the basic attributes may be recorded in a separate basic attribute data table, and the attribute values ​​of the common attributes may be recorded in another data table. Since the common attributes change frequently, for example, the common attributes may be changed as needed in practice, the data table storing the attribute values ​​of the common attributes may be processed by column-to-row conversion. In this way, if a new common attribute is added to the data table later, the code does not need to be modified, and the efficiency of adding new common attributes is high.

[0217] 3) The attribute values ​​of the first delivery account under each attribute are stored. Specifically, the data partition, delivery account identifier, attribute, and attribute value may be stored in a four-tuple format for subsequent use, wherein the data partition indicates the storage address of the four-tuple.

[0218] 4) Write the quadruple into the distributed data warehouse and store it in the database for subsequent query.

[0219] Step 1520, load the policy engine.

[0220] The policy engine is loaded from the policy execution rule set. The policy engine is an abstraction of one or more policy execution rules in the policy execution rule set, that is, the policy engine can process according to the processing logic defined by the policy execution rules. The policy execution rules can be written by developers or configured by non-developers (such as operators) at the delivery configuration end. In some embodiments, the policy execution rules in the policy execution set can also be modified at the delivery configuration end.

[0221] Step 1530, loading the delivery strategy. In this step, the delivery strategy can be loaded from the delivery strategy library into the policy engine. The delivery strategy in the delivery strategy library can be imported by the developer or configured by the operator at the delivery configuration end. The delivery strategy loaded into the policy engine can be used as the target delivery strategy in this application.

[0222] Step 1540: Account matching: In this step, a target delivery account that meets the target account condition is determined based on the target account condition in the target delivery strategy and the attribute value of the delivery account under each attribute.

[0223] In some embodiments, account matching can be performed using the account matching model described above. The specific process is described above and will not be repeated here.

[0224] In other embodiments, the delivery management server may perform account matching according to the following process ①-⑤:

[0225] ① Combine the attribute value of a delivery account under the basic attribute and the attribute value under the common attribute into a fact data F1, and add the fact data of each delivery account to the data set M.

[0226] ② Obtain the delivery strategy to be matched with the account. The delivery strategy to be matched may be one or more. In some embodiments, the delivery strategy may be recorded in the form of a four-tuple, which includes: delivery strategy identifier, strategy version, action group ID, and account condition; wherein the action group ID is used to uniquely identify multiple delivery guidance actions included in the delivery operation guidance information in the delivery strategy.

[0227] ③ Obtain the account conditions in the delivery strategy and load the account conditions into the strategy engine.

[0228] ④ The data in the data set M is marked according to the account conditions by the policy engine, and the marked data is recorded as F11. In this process, the delivery accounts that meet the account conditions in the data set M are marked. The marking information may include the delivery strategy identifier, strategy version, action group ID, and account conditions in the four-tuple from which the account conditions come. The marking information can be recorded as Si (i is a natural number); there may be multiple marking information S1~Sn in this process; the marked data in the data set M is added to the new data set M1.

[0229] ⑤ Traverse all the data in the data set M1. If the data has tag information, generate a delivery task according to the tag information corresponding to the data, and send the delivery task to the corresponding delivery account in the subsequent process.

[0230] Step 1550, call the task interface to initiate the delivery task.

[0231] In this step, the task interface provided by the task system can be called to send the target delivery task to the target delivery account. The task system can be deployed on the delivery management server. Afterwards, the user on the target delivery account side can choose to accept the target delivery task or reject the target delivery task. If the user on the target delivery account side chooses to accept the target delivery task, the delivery management server can determine the progress of the target delivery task according to the above process, and after reaching the end time of the task period of the target delivery task, measure the effect of the target delivery task according to the effect measurement strategy in the target delivery strategy.

[0232] In some embodiments, after a target delivery task is initiated for a target delivery account, the target delivery task is correspondingly stored in a task library.

[0233] Step 1560, sending feedback information.

[0234] When the task system (delivery management server) receives feedback information (feedback information such as the first feedback information and the second feedback information mentioned above) sent by the target delivery account, the task system sends the feedback information to the delivery strategy library to associate the feedback information with the corresponding delivery strategy for storage as the data basis for subsequent optimization and update of the delivery strategy.

[0235] The account matching process as above does not require manual participation. The delivery management server automatically matches accounts based on the delivery strategy and the attribute values ​​of the delivery account under the attributes, and automatically initiates the delivery task after the matching is completed. In a specific embodiment, the rules can be defined using mvel syntax, and the account conditions can be loaded and filtered through the policy engine to determine the delivery accounts that meet the account conditions.

[0236] In some embodiments, before step 210, the method further includes: receiving a target delivery strategy sent by a delivery configuration end. The delivery configuration end refers to a client for configuring a delivery strategy. A user of the delivery configuration end can configure a delivery strategy on a delivery configuration page, and then send the delivery strategy to a delivery management server. After receiving the target delivery strategy, the delivery management server can perform delivery processing according to the method in this application.

[0237] The target account conditions, delivery operation guidance information, task period and task indicator information, and effect measurement strategy in the target delivery strategy can all be configured and generated on the delivery configuration side.

[0238] The delivery configuration page provides account condition configuration controls, allowing users to configure target account conditions in delivery strategies through the account condition configuration controls. Fig.16 is a schematic diagram of an account condition configuration control in a delivery configuration page according to an embodiment of the present application. Fig.16 The "Configure Account Search Label" control 1610 is an account condition configuration control. If the user triggers the "Configure Account Search Label" control 1610, the target account condition configuration can be performed. Fig.17 is a schematic diagram showing how to configure account conditions in a delivery configuration page according to an embodiment of the present application. Fig.17 In the , the conditions defined by multiple user-finding tags are account conditions. Among them, a user-finding tag is an attribute. Fig.17 In the example, you can first select a tag category, and then configure one or more household search tags under the selected tag category. Under the household search tag, you can select a specific household search tag and the tag value (i.e., attribute value) corresponding to the household search tag.

[0239] In the delivery configuration page, you can customize account conditions by combining multiple attributes to automatically match the delivery accounts issued by the delivery strategy, accurately locate the delivery tasks to the delivery accounts, and complete the automatic account search for the delivery tasks.

[0240] In addition, the delivery configuration page can also be used to configure delivery operation guidance information, task period and task indicator information. Fig.18 is a schematic diagram of a delivery configuration page according to an embodiment of the present application, such as Fig.18 As shown, in the delivery configuration page, you can configure delivery guidance actions (for example Fig.18 The configuration contents for each delivery guidance action include: weight (i.e., action weight mentioned above), task indicator (i.e., indicator parameter mentioned above), task indicator type, whether to include secondary action (i.e., whether to include secondary guidance action), secondary action (i.e., secondary guidance action mentioned above), and compliance condition (i.e., compliance condition corresponding to indicator parameter).

[0241] Furthermore, the effect measurement strategy can also be configured on the delivery configuration page. Fig.19 is a schematic diagram of configuring an effect delivery strategy in a delivery configuration page according to an embodiment of the present application. Fig.19 In the Task Effect Measurement Method section, you can select the task effect measurement method, and then select the effect measurement strategy under the corresponding task effect measurement method, such as Fig.19 The two effect measurement strategies E&F and G&H&I&J displayed in the positive judgment mode on the selected area side, among which the sub-effect measurement strategies in the optional effect measurement strategies, such as sub-effect measurement strategy E and sub-effect measurement strategy F, can be configured according to actual needs.

[0242] In this embodiment, the distributed delivery tasks are measured through the configured effect measurement strategy, thereby achieving measurement configuration. When it is determined that there are multiple delivery accounts that meet the target account conditions in the target delivery strategy, multiple target delivery accounts executing the target delivery task can be regarded as a task group. In this case, the effect of each target delivery task and task group in the task group can be measured based on the effect measurement strategy, and the proportion of positive effect measurement results in the task group can be counted, and the process indicators of the effect measurement process can be displayed in the task display page of the client (the process indicators are the effect indicator parameters mentioned above). For example, if an effect measurement strategy is: during the task period, the average daily consumption of completed task accounts> the average daily consumption of uncompleted task accounts, then the process indicators include: the average daily consumption of completed task accounts and the average daily consumption of uncompleted tasks.

[0243] In some embodiments, when the effect measurement strategy is associated with multiple sub-effect measurement strategies through logical relationships, the effect measurement of the target delivery task can be performed on multiple sub-effect measurement strategies in parallel, and then the sub-effect measurement results corresponding to the multiple sub-effect measurement strategies are used to determine the final effect measurement result according to the logical relationship between the multiple sub-effect measurement strategies. For example, if the effect measurement strategy is: sub-effect measurement strategy A & sub-effect measurement strategy B; after the effect measurement is performed through sub-effect measurement strategy A and sub-effect measurement strategy B, if the sub-effect measurement result determined based on sub-effect measurement strategy A is a positive result, and the sub-effect measurement result determined based on sub-effect measurement strategy B is a positive result, the final effect measurement result is determined as a positive result.

[0244] Fig. 20 is a schematic diagram of a delivery configuration page according to an embodiment of the present application, such as Fig. 20As shown, the delivery configuration page also includes a task period option 2030, under which the user can configure the time period of the task period in the delivery strategy; the delivery configuration page can also limit advertisers, for example, Fig. 20 Advertiser-restricted options 2010 (i.e. Fig. 20 In the "Advertiser UID Limitation Option" (in the "Advertiser UID Limitation" option), specify the scope of the delivery strategy for delivery account matching, that is, subsequent account matching for this delivery strategy will only be performed in the delivery account corresponding to the specified advertiser UID. In addition, the delivery configuration page also includes a Feedback Center option 2020, under which you can configure whether to display the "Feedback Center" control, that is, the first feedback entry 910 mentioned above, in the task display page of the delivery client; if you choose to display the Feedback Center under the Feedback Center option 2020, then in the task display page of the delivery client, when the measurement result of the delivery task is a negative result, the first feedback entry 910 will be displayed. Conversely, if you choose not to display the Feedback Center under the Feedback Center option 2020, then in the task display page of the delivery client, when the measurement result of the delivery task is a negative result or a positive result, the first feedback entry 910 will not be displayed.

[0245] In some embodiments, the target delivery strategy further includes mutually exclusive conditions; in this embodiment, step 220 includes: if it is determined that the mutually exclusive conditions are not met, sending the target delivery task to the target delivery account.

[0246] Mutually exclusive conditions refer to the exclusion conditions for the delivery accounts to which delivery strategies are issued. By combining mutually exclusive conditions to locate the delivery accounts to which delivery tasks need to be issued, the accuracy of delivery tasks can be improved. If the target delivery account that meets the target account conditions also meets the mutually exclusive conditions, it is determined that the target delivery task will not be issued to the target delivery account; conversely, if the target delivery account that meets the target account conditions does not meet the mutually exclusive conditions, the target delivery task will be sent to the target delivery account.

[0247] Among them, the mutually exclusive conditions in the target delivery strategy can be configured in the delivery configuration page of the delivery client. Fig.21 is a schematic diagram showing configuration of mutually exclusive conditions in a delivery configuration page according to an embodiment of the present application. Fig.21 The configuration content under the mutually exclusive rule in the policy is the mutually exclusive condition, where the mutually exclusive type can include:

[0248] 1) The ongoing task is not issued; this type of mutual exclusion further includes:

[0249] Task type mutual exclusion: Eliminate tasks by task type. After selecting a task type, the ongoing tasks of this task type will no longer be issued for this delivery task.

[0250] Strategy ID mutual exclusion: Check whether the configured mutually exclusive strategy ID is mutually exclusive with the delivery task being carried out when the delivery task is issued;

[0251] Total number of policy IDs issued (quarter): limits the number of times that the configured mutually exclusive policy IDs can be issued within a natural quarter;

[0252] 2) Time limit for delivery: limit the time for delivery of delivery tasks. Support delivery by week limit, select a certain day, and only deliver tasks on that day;

[0253] For example, if you select the release week limit and select Monday, it means that the task will be released only on Monday and not on other days.

[0254] 3) No delivery after N rejections in this quarter: If a delivery task is rejected N times by delivery account A in this quarter, the delivery task will no longer be delivered to delivery account A.

[0255] 4) No delivery after being rejected N times in three quarters: If a delivery task is rejected N times in the past three quarters, the delivery task will no longer be delivered.

[0256] 5) No delivery after N consecutive rejections in this quarter: Within this quarter, after N consecutive rejections, the delivery task will no longer be delivered.

[0257] It is worth mentioning that the above-listed mutually exclusive types are only illustrative examples. In other embodiments, the configurable mutually exclusive types may include more or fewer types, which are not specifically limited here. Figure 16-Figure 21 This is merely an illustrative example of the configurable content in the delivery configuration page. In other embodiments, the delivery configuration page may include more or less configurable content.

[0258] By configuring the account conditions and mutually exclusive conditions in the delivery strategy on the delivery configuration page, it is easy to automatically match the delivery account for the delivery strategy and automatically issue the delivery task. Moreover, even if a new delivery strategy is added, there is no need to release a new version. It is transparent to the business and only requires technical personnel to configure the rules.

[0259] In some embodiments, in the display page of the delivery client, a lot of content can be presented, for example, multiple pages with different data granularities can be presented, and the development workload is large. Moreover, there are many common functions in different pages, such as: filtering fields, switching calibers, field sorting, downloading data, drilling down jumps, etc.; in addition, business requirements have fast iteration versions, involving field changes, adding sorting, adding filter items, data range changes, etc.; to solve the above problems, the elements in the display page of the client (such as the delivery client, configuration client) can be componentized. The front-end componentization can be achieved through the following three aspects:

[0260] 1. Disassemble the front-end business components:

[0261] 1) Summarize the common functions of the dashboard and split them into multiple business components, such as toolbar, batch operation, filtering, downloading, etc.;

[0262] 2) Customize the configuration of each business component.

[0263] The configuration of business components may include the components to be used (such as input boxes, drop-down selections, tree components, etc.), component style properties, component interaction properties, layout styles, user input validation rules, linkages between form items (for example, component B is displayed only when component A=1), etc.

[0264] Configure cloud management.

[0265] Specifically, you can use the cloud-based page configuration management platform to maintain multi-scenario configurations such as list pages and form pages. By managing and maintaining pages in the cloud, you can modify the page configuration at any time in the cloud, and it will take effect on the page in real time, without having to change the code and release a new version, which is faster.

[0266] Configure the adapter.

[0267] 1) Read the cloud configuration of the list page, and parse multiple component configurations from one configuration, such as filter items, tables, custom columns, etc. Specifically, you can define a key for each configuration item, each configuration item corresponds to a front-end component (such as "input policy title"), and then split them up one by one for parsing.

[0268] 2) Compatible mapping of business component configurations of two versions. That is, if the same page is used in two different systems, but the data sources used by the two systems are different, different configurations can be loaded in different systems to generate the page components required by the system.

[0269] In the above embodiments, by componentizing the front end, on the one hand, the R&D efficiency can be improved. It has been verified that the R&D efficiency can be improved by 70%. Moreover, the front end is highly configurable, and the efficiency of developing and modifying the dashboard is improved. On the other hand, the cost of small demand iteration is low, almost 0. It can adapt to high-frequency changes in table fields, filter items, custom columns and other functions. It only needs to change the configuration, without changing the code release, which is highly efficient. In addition, filter items can be saved or shared with one click, as well as custom columns, which can improve the user experience. Fig. 22 FIG. 1 is a schematic diagram showing a custom column in a display page according to an embodiment of the present application. Fig. 22 As shown, you can check the columns that need to be presented on the page in the sub-page of custom columns.

[0270] The following describes an apparatus embodiment of the present application, which can be used to execute the method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned method embodiment of the present application.

[0271] Fig.23 is a block diagram of a delivery processing device according to an embodiment of the present application. The delivery processing device can be configured in an electronic device to implement the delivery processing provided by the present application, such as Fig.23 As shown, the delivery processing device includes: an account matching module 2310, which is used to match delivery accounts according to the target account conditions in the target delivery strategy and the account data of each delivery account, and determine the target delivery account that meets the target account conditions; the target delivery strategy also includes delivery operation guidance information, task period and task indicator information; a task sending module 2320, which is used to send the target delivery task to the target delivery account, and the target delivery task is used to execute the target delivery strategy; a task progress determination module 2330, which is used to determine the task progress information of the target delivery task according to the delivery data and task indicator information of the target delivery account during the task period when the target delivery account delivers content according to the delivery operation guidance information if a task acceptance instruction returned by the target delivery account is received; and a progress information sending module 2340, which is used to send the task progress information to the target delivery account.

[0272] In some embodiments, the delivery operation guidance information includes at least one delivery guidance action, and the task indicator information includes sub-task indicator information corresponding to each delivery guidance action; the sub-task indicator information includes the compliance conditions corresponding to the indicator parameters; the task progress information includes the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task; the task progress determination module 2330 includes: a first acquisition unit, which is used to obtain the actual parameter value of the target delivery account under the indicator parameters corresponding to each delivery guidance action during the task period when the target delivery account delivers according to each delivery guidance action; a first determination unit, which is used to determine the task action progress corresponding to each delivery guidance action according to the compliance conditions corresponding to the indicator parameters corresponding to each delivery guidance action, and the actual parameter value corresponding to the indicator parameter; a second determination unit, which is used to determine the task execution progress of the target delivery task according to the task action progress corresponding to each delivery guidance action.

[0273] In some embodiments, the delivery guidance action includes multiple secondary guidance actions; the first acquisition unit includes: a second acquisition unit, used to obtain sub-delivery data corresponding to each secondary guidance action of the target delivery account under the delivery guidance action during the task period; a statistical unit, used to perform statistics based on the sub-delivery data corresponding to multiple secondary guidance actions of the target delivery account under the delivery guidance action, to obtain the actual parameter value of the indicator parameter corresponding to the delivery guidance action of the target delivery account.

[0274] In some embodiments, the delivery operation guidance information includes multiple delivery guidance actions, and the delivery operation guidance information also includes action weights corresponding to each delivery guidance action; the second determination unit is configured to: according to the action weights corresponding to each delivery guidance action, perform weighted processing on the task action progress corresponding to the multiple delivery guidance actions respectively, to obtain the task execution progress of the target delivery task.

[0275] In some embodiments, the target delivery strategy also includes an effect measurement strategy; the delivery processing device also includes: an effect measurement result determination module, which is used to measure the effect of the target delivery task based on the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the end time of the task period of the target delivery account, and the effect measurement strategy, and determine the effect measurement result of the target delivery task; an effect measurement result sending module is used to send the effect measurement result of the target delivery task to the target delivery account.

[0276] In some embodiments, the effect measurement strategy includes a positive measurement condition defined by an effect indicator parameter, the first delivery effect data includes a first numerical value corresponding to a sub-effect indicator parameter used to determine the effect indicator parameter; the second delivery effect data includes a second numerical value corresponding to the sub-effect indicator parameter; the effect measurement result determination module includes: a third determination unit, used to determine the numerical value corresponding to the effect indicator parameter in the reference period according to the first numerical value corresponding to the sub-effect indicator parameter in the first delivery effect data; a fourth determination unit, used to determine the numerical value corresponding to the effect indicator parameter at the end time of the task period according to the second numerical value corresponding to the sub-effect indicator parameter in the second delivery effect data; a fifth determination unit, used to determine the effect measurement result of the target delivery task according to the numerical value corresponding to the effect indicator parameter in the reference period, the numerical value corresponding to the effect indicator parameter at the end time of the task period, and the positive measurement condition.

[0277] In some embodiments, the delivery processing device also includes: a splitting module, used to split the effect indicator parameters in the positive measurement conditions and determine the sub-effect indicator parameters corresponding to the effect indicator parameters; a data source determination module, used to determine the data source corresponding to the sub-effect indicator parameters; a first value acquisition module, used to obtain the first value corresponding to the sub-effect indicator parameter in the reference period from the data source corresponding to the sub-effect indicator parameter; a second value acquisition module, used to obtain the second value corresponding to the sub-effect indicator parameter at the end time of the task period from the data source corresponding to the sub-effect indicator parameter.

[0278] In some embodiments, the delivery processing device also includes: a first feedback information receiving module, used to receive first feedback information sent by the target delivery account for the target delivery task, the first feedback information is sent by the client where the target delivery account is located in response to a trigger operation on the first feedback entry; the client where the target delivery account is located responds to the effect measurement result of the target delivery task being a negative effect, and displays the first feedback entry in the task display page corresponding to the target delivery task.

[0279] In some embodiments, the account matching module 2310 includes: an attribute value determination unit, which is used to determine the attribute value of each delivery account under each attribute in the attribute set based on the account data of each delivery account; and a matching unit, which is used to determine the target delivery account whose attribute value meets the target account condition based on the attribute value of each delivery account under each attribute in the attribute set.

[0280] In some embodiments, the delivery processing device also includes: a basic attribute determination module, which is used to determine the basic attributes corresponding to each delivery account based on the basic information of each delivery account; and an attribute set determination module, which is used to combine the basic attributes corresponding to each delivery account with the pre-configured common attributes respectively to determine the attribute set corresponding to each delivery account.

[0281] In some embodiments, the target delivery strategy further includes mutually exclusive conditions; the task sending module 2320 is configured to: if it is determined that the mutually exclusive conditions are not met, send the target delivery task to the target delivery account.

[0282] In some embodiments, the delivery processing device also includes: a second feedback information receiving module, which is used to receive second feedback information sent by the target delivery account for the target delivery task, the second feedback information is sent by the client where the target delivery account is located in response to a trigger operation on the second feedback entry; the client where the target delivery account is located responds to the target delivery task not being completed at the end time of the task period, and displays the second feedback entry in the task display page corresponding to the target delivery task.

[0283] In some embodiments, the delivery processing device further includes: a task cancellation module, which is used to cancel the target delivery task for the target delivery account if a task abandonment request for the target delivery task is received from the target delivery account during the task period.

[0284] Fig.24 The structure diagram of the computer system suitable for implementing the electronic device of the embodiment of the present application is shown. It should be noted that: Fig.24 The computer system 2400 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application. Figure 1A The delivery management server in is used to execute the delivery processing method provided by this application.

[0285] like Fig.24 As shown, computer system 2400 includes a central processing unit (CPU) 2401, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 2402 or the program loaded from the storage part 2408 to the random access memory (RAM) 2403, such as executing the method in the above embodiment. In RAM 2403, various programs and data required for system operation are also stored. CPU 2401, ROM 2402 and RAM 2403 are connected to each other through bus 2404. Input / output (I / O) interface 2405 is also connected to bus 2404.

[0286] The following components are connected to the I / O interface 2405: an input section 2406 including a keyboard, a mouse, etc.; an output section 2407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 2408 including a hard disk, etc.; and a communication section 2409 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 2409 performs communication processing via a network such as the Internet. A drive 2410 is also connected to the I / O interface 2405 as needed. A removable medium 2411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 2410 as needed so that a computer program read therefrom is installed into the storage section 2408 as needed.

[0287] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 2409, and / or installed from the removable medium 2411. When the computer program is executed by the central processing unit (CPU) 2401, various functions defined in the system of the present application are executed.

[0288] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0289] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0290] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0291] As another aspect, the present application further provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist independently without being assembled into the electronic device. The above computer-readable storage medium carries computer-readable instructions, and when the computer-readable storage instructions are executed by a processor, the method in any of the above embodiments is implemented.

[0292] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method in any of the above embodiments.

[0293] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0294] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0295] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0296] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A delivery processing method, characterized in that: include: Matching the delivery accounts according to the target account conditions in the target delivery strategy and the account data of each delivery account, and determining the target delivery account that meets the target account conditions; The target delivery strategy also includes delivery operation guidance information, task period and task indicator information; Sending a target delivery task to the target delivery account, wherein the target delivery task is used to execute the target delivery strategy; If a task acceptance instruction returned by the target delivery account is received, during the task period, when the target delivery account delivers content according to the delivery operation guidance information, the task progress information of the target delivery task is determined according to the delivery data of the target delivery account and the task indicator information; The task progress information is sent to the target delivery account.

2. The method according to claim 1, characterized in that: The delivery operation guidance information includes at least one delivery guidance action, the task indicator information includes subtask indicator information corresponding to each delivery guidance action; the subtask indicator information includes the compliance conditions corresponding to the indicator parameters; the task progress information includes the task action progress corresponding to each delivery guidance action and the task execution progress for the target delivery task; In the process of the target delivery account delivering content according to the delivery operation guidance information during the task period, determining the task progress information of the target delivery task according to the delivery data of the target delivery account and the task indicator information, including: In the process of the target delivery account delivering according to each delivery guidance action during the task period, obtaining the actual parameter value of the target delivery account under the indicator parameter corresponding to each delivery guidance action; Determine the progress of the task action corresponding to each of the delivery guidance actions according to the achievement conditions corresponding to the indicator parameters corresponding to each of the delivery guidance actions and the actual parameter values ​​corresponding to the indicator parameters; The task execution progress of the target delivery task is determined according to the task action progress corresponding to each delivery guidance action.

3. The method according to claim 2, characterized in that The delivery guidance action includes a plurality of secondary guidance actions; In the process of the target delivery account delivering according to each delivery guidance action during the task period, obtaining the actual parameter value of the target delivery account under the indicator parameter corresponding to each delivery guidance action includes: During the task period, obtaining the sub-delivery data corresponding to each secondary guidance action under the delivery guidance action of the target delivery account; According to the sub-delivery data corresponding to a plurality of secondary guidance actions under the delivery guidance action of the target delivery account, statistics are performed to obtain the actual parameter value of the indicator parameter corresponding to the delivery guidance action of the target delivery account.

4. The method according to claim 2 or 3, characterized in that: The delivery operation guidance information includes a plurality of delivery guidance actions, and the delivery operation guidance information also includes an action weight corresponding to each of the delivery guidance actions; Determining the task execution progress of the target delivery task according to the task action progress corresponding to each delivery guidance action includes: According to the action weight corresponding to each of the delivery guidance actions, weighted processing is performed on the task action progresses respectively corresponding to the plurality of delivery guidance actions to obtain the task execution progress of the target delivery task.

5. The method according to claim 1, characterized in that The target delivery strategy also includes an effect measurement strategy; After sending the task progress information to the target delivery account, the method further includes: According to the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the target delivery account at the end time of the task period and the effect measurement strategy, the effect of the target delivery task is measured to determine the effect measurement result of the target delivery task; The effect measurement result of the target delivery task is sent to the target delivery account.

6. The method according to claim 5, characterized in that The effect measurement strategy includes a positive measurement condition defined by an effect indicator parameter, the first delivery effect data includes a first value corresponding to a sub-effect indicator parameter used to determine the effect indicator parameter; the second delivery effect data includes a second value corresponding to the sub-effect indicator parameter; The step of measuring the effect of the target delivery task according to the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the target delivery account at the end time of the task period, and the effect measurement strategy, and determining the effect measurement result of the target delivery task includes: Determine, according to the first value corresponding to the sub-effect indicator parameter in the first delivery effect data, the value corresponding to the effect indicator parameter in the reference period; Determine, according to the second value corresponding to the sub-effect indicator parameter in the second delivery effect data, the value corresponding to the effect indicator parameter at the end time of the task period; The effect measurement result of the target delivery task is determined according to the value of the effect indicator parameter corresponding to the reference period, the value of the effect indicator parameter corresponding to the end time of the task period, and the positive measurement condition.

7. The method according to claim 6, characterized in that Before measuring the effect of the target delivery task according to the first delivery effect data corresponding to the target delivery account in the reference period, the second delivery effect data corresponding to the target delivery account at the end time of the task period and the effect measurement strategy, and determining the effect measurement result of the target delivery task, the method further includes: Splitting the effect indicator parameter in the positive measurement condition to determine the sub-effect indicator parameter corresponding to the effect indicator parameter; Determine the data source corresponding to the sub-effect indicator parameter; Acquire, from a data source corresponding to the sub-effect indicator parameter, a first value corresponding to the sub-effect indicator parameter in the reference period; A second value of the sub-effect indicator parameter corresponding to the end time of the task period is obtained from a data source corresponding to the sub-effect indicator parameter.

8. The method according to any one of claims 5 to 7, characterized in that After sending the effect measurement result of the target delivery task to the target delivery account, the method further includes: Receive first feedback information sent by the target delivery account for the target delivery task, where the first feedback information is sent by the client where the target delivery account is located in response to a triggering operation on a first feedback entry; in response to an effect measurement result of the target delivery task being a negative effect, the client where the target delivery account is located displays the first feedback entry in a task display page corresponding to the target delivery task.

9. The method according to claim 1, characterized in that: The step of matching the delivery accounts according to the target account conditions in the target delivery strategy and the account data of each delivery account to determine the target delivery account that meets the target account conditions includes: Determine the attribute value of each of the attributes in the attribute set for each of the placement accounts according to the account data of each placement account; According to the attribute value of each delivery account under each attribute in the attribute set, a target delivery account whose attribute value meets the target account condition is determined.

10. The method according to claim 9, characterized in that Before determining the attribute value of each of the attributes in the attribute set for each of the investment accounts according to the account data of each investment account, the method further includes: Determine the basic attributes corresponding to each of the investment accounts according to the basic information of each of the investment accounts; The basic attributes corresponding to each delivery account are respectively combined with the pre-configured common attributes to determine the attribute set corresponding to each delivery account.

11. The method according to claim 1, characterized in that: The target delivery strategy also includes mutually exclusive conditions; The sending the target delivery task to the target delivery account includes: If it is determined that the mutually exclusive condition is not satisfied, the target delivery task is sent to the target delivery account.

12. The method according to claim 1, characterized in that After sending the task progress information to the target delivery account, the method further includes: Receive second feedback information sent by the target delivery account for the target delivery task, where the second feedback information is sent by the client where the target delivery account is located in response to a triggering operation on a second feedback entry; in response to the target delivery task being not completed at the end time of the task period, the client where the target delivery account is located displays the second feedback entry in a task display page corresponding to the target delivery task.

13. The method according to claim 1, characterized in that If a task acceptance instruction returned by the target delivery account is received, during the task period, the target delivery account delivers content according to the delivery operation guidance information, after determining the task progress information of the target delivery task according to the delivery data of the target delivery account and the task indicator information, the method further includes: During the task period, if a task abandonment request for the target delivery task is received from the target delivery account, the target delivery task is canceled for the target delivery account.

14. A delivery processing device, characterized in that: include: An account matching module is used to match the delivery accounts according to the target account conditions in the target delivery strategy and the account data of each delivery account, and determine the target delivery account that meets the target account conditions; The target delivery strategy also includes delivery operation guidance information, task period and task indicator information; A task sending module, used for sending a target delivery task to the target delivery account, wherein the target delivery task is used for executing the target delivery strategy; A task progress determination module, configured to determine the task progress information of the target delivery task according to the delivery data of the target delivery account and the task indicator information during the task period when the target delivery account delivers content according to the delivery operation guidance information if a task acceptance instruction returned by the target delivery account is received; The progress information sending module is used to send the task progress information to the target delivery account.

15. An electronic device, characterized in that: include: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 13 is implemented.

16. A computer-readable storage medium having computer-readable instructions stored thereon, characterized in that: When the computer-readable instructions are executed by a processor, the method according to any one of claims 1 to 13 is implemented.

17. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by a processor, the method according to any one of claims 1 to 13 is implemented.

Images