π Problem Statement
As an editor, I cannot choose where inside an article the paywall appears, which limits me to all-or-nothing gating per article.
π‘ User Story
As an editor, I want to insert a subscriber-only break at any point in an article, so that non-subscribers read only the content above it.
As a publisher admin, I want only articles containing a break to be gated, so that free stories stay open without meter rules.
π― Definition of Done (DoD)
β Given an article contains a subscriber break marker, when a non-entitled user loads the page, then content below the marker is withheld and the embedded paywall renders at the marker.
β Given an entitled subscriber loads a marked article, when the page renders, then the full article displays with no paywall.
β Given an article contains no marker, when any user loads the page, then no paywall renders.
β Given a search crawler requests a marked article, when the page renders, then the full article body is served, preserving current crawler-bypass behaviour.
β Given an editor publishes an article, when they place the break in the CMS editor, then no Pelcro dashboard configuration is required per article.
β This change will impact UI, SDK, and API, specifically Pelcro Elements embedded paywall rendering, JS-SDK content gating, and paywall product configuration.
β This solution will include the following limitations: one break per article; marker authoring requires a CMS-side plugin or shortcode; client-side content withholding only unless server-side truncation is scoped separately; no A/B testing of break position; interaction with metered paywalls out of scope.
Please authenticate to join the conversation.
Backlog
Pelcro Product
7 days ago

Rana Haleem
Get notified by email when there are changes.
Backlog
Pelcro Product
7 days ago

Rana Haleem
Get notified by email when there are changes.