Reader Revenue Manager problems

Thanks for getting in touch @emga, and indeed the feedback too. See below answers to your comments:

1- On paywalled content there is no button for users to subscribe now and this makes the subscription not easy for the users that’s make the funnel not work well and decreases the subscribers

If you’d like to share your site URL I’d be happy to review your set up, and some details in relation to no subscribe option appearing. Depending on how you set up your paywall, there are different options other than a subscribe button, such as free trial prompts, access for new readers etc. You can share your site URL privately using this form if preferred.

2- On paywalled content if we want to add a CTA call to action it doesn’t work good cos of if the users click on the button and come back to the page or post the content becomes unlocked it becomes open and users can read all the post or page

If you share an example of a URL with this behavior I’d be happy to check. As above, there are prompts that can be configured that don’t necessary block content (ie. Open access – screenshot). It’s possible that the CTA can be clicked on or ignored, and the content does become visible with particular configuration.

3- Why is the content only for one country why it’s can’t to be for all countries or specified countries like apps in the Play Store

I’m sure there are various reasons as to why Reader Revenue Manager is being rolled out in different countries at different times, such as regional regulation, payment limitations etc.

Note that we can only assist with Site Kit specific queries, but for such questions regarding Reader Revenue Manager as a service, there are Help and Feedback options from within the dashboard at https://publishercenter.google.com/reader-revenue-manager. If you share you’re Site Health information above, I can hopefully assist with any Site Kit queries, while also reviewing your Reader Revenue Manager prompts.

Thank you!

Thanks for the additional information on this @emga.

In the first case, where you mention there is no button for users to subscribe and where you share a screenshot, I’m unable to replicate such an issue. In my case from various tests, either a subscribe button appears or the option for a free trial (depending on how you set it up). Can you share a URL with this behavior, or ideally your Site Health information so I can inspect your set up?

In the second case, where you have a Paywall but also a custom CTA, with the custom CTA set to appear first, I can replicate the same and it’s a good point you raise. I’ll raise this with the Site Kit team based on your findings. The message stating “CTAs appearing on paywalled content cannot be dismissed by your readers.” seems to be true if you dismiss the CTA, as it reappears once more however, in my case – as with your own, if I click on the CTA button for a link to another website, the CTA is dismissed and the content is visible. I suspect that this is intentional, as such a CTA would allow users to see content only after visiting a related site or page. While this isn’t a Site Kit issue as such, I’m going to bring this up in discussion with the the Reader Revenue Manager team to confirm this is expected behavior. Thank you for sharing your findings.

Back to your original point, please do share your site URL with a paywall and I’ll inspect this to see what’s happening in relation no option to subscribe.

Thanks for the update @emga. I have been testing this and while I couldn’t recreate the exact same message as one of your user encounters, and I did test all prompts and different scenarios. What I suspect, is that the messaging can appear slightly differently across regions, or Google translate may be applied at browser level. Based on the content of the prompt. it sounds like a reader registration prompt. Can you recreate it yourself, or is this from one user?

In relation to your original query regarding a CTA when clicked, this could potentially be a CTA to direct users to a sister or related site, with content unlocked as a reward. This is expected behavior, but I will pass on your feedback as I can see how the messaging can be confusing.