Reader Revenue Manager allows you to engage your readers with call-to-actions (CTAs) for newsletters, registrations and surveys. While standard CTAs appear as pop-up overlays, Inline CTAs are embedded directly within your article content.
Inline CTAs provide a less intrusive experience for your readers. While you should expect a lower interaction rate compared to pop-up CTAs, data shows that users who do engage with Inline CTAs are significantly more likely to complete the desired action. This typically results in higher-quality conversions.
Before you begin
- Supported types: You can use Inline CTAs for newsletters, registrations and surveys. Currently, rewarded ads are not supported for inline delivery.
- Funnel requirement: To make an Inline CTA live, you must first add it, to an active funnel in the Publisher Center.
Implementation steps
- Add the CMS code snippet (Required for non-Site Kit users): Before adding an Inline CTA, your website must have the primary Reader Revenue Manager code snippet installed in the <head> of each page. For detailed instructions, refer to Add a code snippet to your site.
- This step is not required for WordPress publishers who have already onboarded using Site Kit.
- Configure your CTA: In the Publisher Center, set up your newsletters, registrations, and surveys CTAs.
- Add to Funnel and activate: Ensure the CTA is part of a funnel and is set to live. CTAs will remain in "Draft" status and won't appear until they are added to a funnel and made to live in the setup page.
- Retrieve the snippet: Find your unique code snippet in the 'Inline CTA' section of the CTA configuration page.
- Embed the code: Copy the code snippet and paste it into your website’s HTML where you want the CTA to appear.
- WordPress users: Use the Custom HTML block to insert the snippet.
Optional: Disable pop-up CTAs
If you prefer to show only the Inline CTA and hide the standard pop-up on a specific page, add the following parameter to your RRM code snippet: autoPromptType: "none".
Example
JavaScript<script async type="application/javascript"
src="https://news.google.com/swg/js/v1/swg-basic-qual.js"></script>
<script>
(self.SWG_BASIC = self.SWG_BASIC || []).push( basicSubscriptions => {
basicSubscriptions.init({
type: "NewsArticle",
isPartOfType: ["Product"],
isPartOfProductId: "PUB_ID:PRODUCT_ID",
clientOptions: { theme: "light", lang: "en" },
autoPromptType: "none",
});
});
</script>
Troubleshooting & tips
- Quote marks: Ensure your code uses standard straight quotes (") rather than "curly" or smart quotes, which can prevent the code from parsing correctly.
- Frequency capping: Inline CTAs are currently set as "auto-uncapped" and will persist on the page until the user completes the action. For example, signs up or registers.
- Performance expectations: Because Inline CTAs are less intrusive, expect a lower Click-Through Rate (CTR) compared to pop-ups. However, data shows that users who interact with Inline CTAs are significantly more likely to complete the payment or registration process.
- Performance strategy: We recommend showing both types of CTA, pop-up and inline, on the same page to maximize engagement.