Unfilled Recovery In App Implementation Overview [Beta version]
Last edited: 2024/01/22
Step | Publisher’s actions | Yieldbird’s actions | Expected duration |
1. Inventory selection | - Deciding which ad units will be replaced by Unfilled Recovery
- Note: We only support standard display ad sizes; no rich media / non-standard sizes | Optional: supporting the publisher in selecting the ad units | 1-2 days |
2. App registration and MCM setup
(learn more) | - Providing necessary details for MCM invitation:
1. GAM ID
2. Email address used to set up the account
3. Company name
- Accepting invitation to MCM | - Registering the apps in Yieldbird’s GAM
- Sending the invitation to Google’s MCM program (Manage Inventory)
- Monitoring the MCM connection process | <1 week |
3. App-ads.txt implementation | - Adding our app-ads.txt | - Providing the app-ads.txt script | < 1 week |
4. Technical setup
(learn more) | - Implementing the methods in the code of the app | - Supporting the publisher in the process | < 1 week |
5. Ongoing cooperation | Invoicing Yieldbird with the amounts shown in the reporting dashboard | Reporting the revenues generated by Unfilled Recovery | ongoing |
Technical requirements:
- Fill rate < 70% on the ad slots where Unfilled Recovery should be implemented
- No backfills in Publisher’s GAM that do not allow for any unfilled impressions to manifest, e.g. house campaigns, campaigns on priority 12 with rate card 0 etc.
- Android operating system; we currently do not support iOS
- No rich media or non standard ad sizes