Best Practise
Following each of the main points below will help you get the most out of your Rewarded Video integration.
CMP Integration & User Consent
Why is a CMP integration with enabled vendor management essential to collect GDPR & CCPA compliant user consents to increase fill rates?
Implementing a Consent Management Platform (CMP) is crucial for maximizing ad fill rates and ensuring demand partners actively bid on your inventory. A CMP facilitates compliance with data protection regulations, such as the General Data Protection Regulation (GDPR) in the European Union and the California Consumer Privacy Act (CCPA) in the United States. Without a compliant CMP and without requesting consent from affected GDPR & CCPA users, both fill rate and eCPM will be impacted significantly or no ads will be delivered at all.
Importance of Vendor Management in Your CMP
Enabling vendor management within your CMP is essential. This feature allows you to control which advertising partners can access user data, ensuring that only trusted vendors participate in the bidding process. Proper vendor management enhances transparency and trust, leading to higher fill rates and better eCPM.
Key Regions Where CMP Implementation Is Critical
Implementing a CMP is particularly important in regions with stringent data protection laws, including:
European Union (EU): Under the GDPR, user consent is mandatory for data processing activities, including targeted advertising.
United States (US): The CCPA requires businesses to obtain user consent before collecting personal information for advertising purposes.
By integrating a CMP with robust vendor management capabilities, you ensure compliance with these regulations, maintain user trust, and optimize your ad monetization strategy.
Avoid CMPs That Only Offer Cookie Management
When choosing a Consent Management Platform (CMP), it’s essential to look beyond basic cookie management. Some CMPs focus solely on managing cookies, which is not sufficient for effective advertising monetization. Ensure that your CMP includes Vendor Management capabilities to manage and enable demand partners effectively.
To optimize your setup:
Request a detailed introduction to Vendor Management from your CMP provider.
Contact our Account Managers to receive a curated list of the most relevant vendors to enable in your CMP solution.
By focusing on comprehensive Vendor Management, you can maximize ad demand, increase fill rates, and comply with data privacy regulations effectively.
SDK Initialization
When should you initialize the SDK?
To provide a seamless experience and avoid user frustration, it’s essential to initialize the SDK at an appropriate time. This ensures the rewarded video is ready to play when users reach the relevant point in your app or game. Follow these recommendations:
Early Initialization: Initialize the SDK as early as possible, such as when the user opens your app or game. This proactive approach ensures the SDK is ready well before users reach the video placement.
Contextual Initialization: If initializing at app launch isn't feasible, do it when the user is nearing the section where the video will be displayed. This minimizes wait times and ensures a smoother experience.
Avoid Delayed Initialization: Never initialize the SDK only when the video button is already visible to the user. SDK initialization can take a few seconds, and users expect immediate responses. Delays at this stage can lead to frustration and disrupt the overall user experience.
Ad Requests
When should you make an Ad Request?
It is a much better user experience to make ad requests before the user interacts with the video play button. Here’s why:
Improved User Experience Pre-loading ads ensures they are ready to play instantly when the user clicks the button, eliminating waiting times and providing a seamless experience.
Ensure Availability By making the ad request in advance, you can verify whether an ad is available (a "fill") before even displaying the button to the user. If no ad is available, the button can remain hidden, avoiding any user confusion or dissatisfaction.
Logical Button Display Build a logic in your app or game to display the play button only if an ad is ready to be shown. For example:
Make the ad request in advance (e.g., during app initialization or when the user is approaching the rewarded video placement).
Display the button only if an ad is available, ensuring users can always watch a video upon clicking.
Check the availability of the ad (whether there is a "fill") when the user clicks on the button. If there is a no fill or the ad expired, re-request an ad.
Avoid Delays in Ad Loading: When an ad request is initiated upon the button click, the user must wait for the ad to load. Depending on the network speed and server response time, this delay can disrupt the flow of the app or game and frustrate the user.
Avoid Risk of No Fill: There is always a possibility of receiving a "no fill" response from the ad network, meaning no ad is available to show. If this occurs after the user has already clicked the button, they might feel misled or disappointed, as they were expecting to watch an ad and earn a reward. This can lead to a negative perception of the app or game.
Callbacks
Why should you choose Client-Side Callbacks over Server-to-Server Callbacks?
For scenarios where speed and user satisfaction are critical—such as rewarding users after a video ad— client-side callbacks are the superior choice.
Immediate User Feedback: Client-side callbacks provide instant feedback to the user. When a rewarded video ends, the user immediately sees their reward, maintaining engagement and avoiding frustration caused by delays.
No Network Dependency: Unlike S2S callbacks, client-side callbacks do not rely on external server communications. This eliminates risks associated with server downtime, network instability, or latency.
Enhanced User Experience: Users expect immediate rewards after completing a task. Delays caused by S2S callbacks may lead to complaints, reduced trust, and a negative impression of the app.
Simpler Implementation: Client-side callbacks are easier to implement as they do not require complex server infrastructure or robust handling for network issues.
Avoid Delays in Callbacks: Rewarding users after a video has been watched should be instant. Avoid delays when using server-to-server callbacks and use client-side callbacks instead.
Last updated