In Reader Revenue Manager, the Rewarded ad call-to-action (CTA) lets site visitors watch a short ad to earn access to your site content. This is available for Reader Revenue Manager publishers who use Google AdSense to monetize their site.
The system uses Reader Revenue Manager to detect your current AdSense implementation.
Before you begin, make sure:
- You have an active Google AdSense account. If you don’t, sign up for AdSense.
- You correctly place AdSense code in your HTML.
- The code snippet isn’t placed by the Reader Revenue Manager on your site.
Enable the Rewarded Ad CTA with AdSense
Important: Readers will find a message with the rewarded ad option only when a rewarded ad is available from your AdSense account. If no rewarded ad is available, like due to insufficient ad demand, the message doesn’t show.
- In the Publisher Center, go to Reader Revenue Manager
Content access.
- Select the CTA you want to edit, or create a new one.
- In the message editor, add Rewarded ad as a call-to-action choice.
- When prompted for ad settings, select the option Google AdSense.
- Save your changes.
Tip: After you save the CTA, the system verifies if you correctly installed AdSense on your site. If it isn't detected, the system shows a warning message.
Troubleshoot AdSense detection
If you get a warning message that Reader Revenue Manager didn't detect your AdSense implementation, it may be due to one of the following reasons:
- AdSense code is missing: Make sure you correctly place the AdSense code in your site's HTML. You can find instructions in the AdSense Help Center.
- AdSense isn’t on the primary URL: Reader Revenue Manager only checks the primary URL you configure in your publication settings. To avoid issues, be sure to include AdSense on all pages that have the
swg.jsscript. - Lazy loading AdSense: If you use a service to lazy load your AdSense script, it can interfere with our detection system. This may cause
swg.jsto skip your script because it assumes the dependency is missing. - Reader Revenue Manager rendering service failure: In some cases, issues with the web rendering service can lead to a false-positive detection error. This often occurs on sites with poor performance. If you check all of the above and still get the warning, this could be the case.