The part where you configure the number of free stories that could be read by end users(both guests/registered users) on the website before they get the paywall popup. 

You could toggle the paywall by clicking on the switch next to the appropriate field available in the right corner. We can also set the duration in which the paywall limit would be reset. 

Example: 

If we set 5 stories in 2 days in the settings, It means the end user can read 5 free stories in two days. If the user exhausts the set limit in 2 days, they can read free content after 2 days of reading the first free story. 

Access level: We can choose the access level set in the CMS -> Bulk action on the metered paywall settings->access level as well:

Story registration wall

A registration wall can now be configured for stories that are behind a login for Anonymous users when they reach the prescribed Story limit for a time period.
Steps to set this up:
- In Accesstype go to 'Configure' -> 'Metered Paywall Settings'
- Toggle on 'Stories behind login' for Anonymous users.
- Add the required story limit and time period.
- Save the changes.
In Bold, while publishing the story, set the 'Access level' as 'Login'

For stories that are behind subscriptions, we can choose between a Registration wall and a Paywall to be displayed for Anonymous users by checking the respective radio button. Once the configured limit for stories is reached, they will be shown the wall that has been configured here.

Remodelled Metered Paywall

The metered paywall settings has been remodelled to set the different access level conditions and a separate set of rules has been set for anonymous and logged in users.

Adding the number field component

This will set a minimum value of 0 for all number fields possible in AccessType.

What’s new

Moving metering settings to CF edge worker

We have shifted our decision-making mechanism to the edge. The decision-making mechanism incorporates metering logic (if applicable to the publisher) and adhere to the specifications of Authorisation endpoint for amp-subscriptions.

Improvements

1. Modify metering rule

With the updated metering rule, if access level is not set in AccessType, then it either allows all story for metering or no story for metering.

2. Optimise numbers of purge API calls

We have optimised the number of purge API calls now, in which not more than two purge API calls is allowed in a subscription purchase journey.

3. Updating Paper trail

Added more details to trace the deletions of Subscriber Wallets in database.

Meter Paywall - We can configure to display paywall to all non subscribed users by defining the number of stories they get to see in a week/month/year. Control the access to the content and convert prospective users to your customers.