Mintegral's Retention & Key Action Optimizer
1. Brief introduction
1.1 Applicable scenario
Mintegral's Retention & Key Action Optimizer helps acquire high-quality users at scale by leveraging automatic algorithm optimization rather than manual bid-adjustment on sub-source level.
﻿
1.2 Key capability
This feature supports optimization goals based on Day1 Retention and Key Action.
Day1 Retention refers to the next day after the installation happens.
Key Action refers to the key events that are highly related to the quality index and advertisement performance, which can be customized, for instance, ‘level 5 of the game’.
﻿
2. Requirement
2.1 Testable range
This optimization feature is currently available for CPI campaigns only.
﻿
2.2 Requirement for epb (event postback)
The epb must be returned (if not, your campaigns can't participate in the optimization). It is recommended to return all networks' data for algorithm’s better learning. Good to control the epb return delay of Key Action within 72 hours.
*Note: Currently Mintegral only supports the optimization of events that can be sent back to Mintegral within 72 hours, where 72 hours refers to the time window from user installation --> event generation --> successfully be sent back to Mintegral.
﻿
●If the optimized event can be sent back to Mintegral in a large proportion within 72h after installation, then the more samples we get here, the algorithm can learn this event efficiently, and the event rate will be obviously improved;
●If the proportion of the event sent back to Mintegral within 72 hours is very small, that is, the event may not be generated and sent back until the fourth and fifth days, the number of samples available in the algorithm will be very small, and it will be difficult to optimize, so it is difficult to improve the event rate.
﻿
2.3 Threshold for the events of Day1 Retention & Key Action 
Now Day 1 Retention & Key Action Optimizer just supports setup on a new offer. Only when your new offer meets the following conditions, the optimization model can complete data accumulation and enter algorithm-optimization stage smoothly.
﻿
●Your product needs to accumulate 60 events in the past 7 days 
●Your new offer needs to accumulate 150 installs in the past 7 days
●Your new offer needs to be launched for 3 days  
Note*: Before accumulating enough data, your new offer can be considered no different from the normal one, so it’s necessary to improve its scale first and reach the threshold, and then enter the algorithm-optimization stage.
﻿
2.4 Key Action customization
Your customized Key Action must be highly related to campaign quality assessment. The conversion rate from install to that Key Action preferably falls somewhere in the range of 30%-50% by our recommendation.
﻿
2.5 Threshold for Daily budget
The daily budget should be no less than [CPI*40 ÷ estimated conversion rate of selected Key Action].
﻿
3. Expected performance
During the first 5 days after the launch, the Mintegral algorithm works on data accumulation and model optimization, and there might be a fluctuation in quality performance. If the amount of your selected Key Action/Day1 Retention cannot reach the algorithm-optimization threshold (see 2.3), you need to bump  CPI to increase scale.
Note*: After the optimization goal's configuration, there might be a fluctuation in scale as the algorithm prioritizes targeting the audience meeting the goal and decreasing the acquisition of users below the goal.
﻿
4. During optimization and ramp-up stage
●Please avoid payout decreases, budget decreases, campaign pauses, or removal of good performing creatives.
●In case the campaign quality meets the optimization goal, it's recommended to increase CPI to expand scale.
●In case of failing the optimization goal, reach out to your account manager to help more.
﻿
5. Access to the optimizer feature
Feel free to contact your account manager to apply for access to the optimizer feature, and provide information, including but not limited to the campaign/offer name, the optimization goal, the current Day1 retention rate, and the rate of selected Key Action.
﻿
6. Event Postback Guidance
﻿https://alidocs.dingtalk.com/i/p/ZR2PmK51081zvpO7l2AmoRr7n6rR2Xdb﻿