A paywall shows the start of an article and asks readers to subscribe to read the rest. In UniSignIn it is made of three parts: a plan with premium access, a Content Wall experience, and an Orchestration that shows the wall to readers without a plan.
Connect Stripe: see Stripe.
Create a plan with premium access: in Commerce → Products, create a subscription product and add a plan. Turn on Enable Premium Content Access so subscribers to this plan can read premium content. See Commerce.
Show plans in the Account Center: in the Account Center experience, turn on subscriptions and choose the plans readers can buy.
Create a Content Wall experience: in Audience Operation → Experience, create a Content Wall:
.article-content.No for a hard paywall, Yes for a soft one readers can dismiss.{{unisignin-button}} to add Sign Up and Login buttons for readers who already subscribe, see Placeholders.Create an Orchestration: in Audience Operation → Orchestration:
Subscription Status does not equal active, so subscribers never see the wall.A metered paywall lets readers open a number of free articles each month, then shows the paywall.
Mark your articles: UniSignIn counts a page as an article when it has <meta property="og:type" content="article">. Most CMSs add this to article pages already.
Set the meter in the Orchestration: in the User Profile rules, add Article view of the month greater than 3. Readers see 3 free articles, and the paywall from the 4th article of the month.
Keep subscribers out: keep the rule Subscription Status does not equal active in the same Orchestration.
Other meters you can use in the same way:
| Rule | Resets |
|---|---|
Article view of the day | every day |
Article view of the week | every week |
Article view of the month | every calendar month |
Article view in total | never |
Articleview of the session | when the reader's visit ends |
The meter is counted in the reader's browser, so it starts again on a new device or after the reader clears their browser data. Where GDPR applies, the meter only counts for readers who consent to storing information on their device (TCF purpose 1).
Combine the meter with other rules to decide who sees the wall and when, for example:
Referrer domains (last 30 days)Active days (last 30 days) greater than or equal to 3See Orchestration and Segments for all rules.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.