Reader Revenue Manager allows you to engage your readers with calls to action (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 Centre.
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 Centre, set up your newsletters, registrations and surveys CTAs.
- Add to funnel and activate: Ensure that 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 and tips
- Quote marks: Ensure that 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 maximise engagement.