Consumer Data Platform/CDP
🔍 Problem Statement
As a publisher, I experience paywall targeting as a fixed attribute list set inside each individual paywall, which results in audiences I cannot express — anonymous readers with more than five page views in the last 30 days, for instance — receiving the same meter and gate as everyone else.
💡 User Story
As a publisher, I want to define paywall targeting as a Pelcro segment rather than per-paywall attributes, so that an audience is described once and reused across paywalls.
As a publisher, I want every attribute available in today's paywall targeting to also exist as a segment condition, so that deprecating paywall-level targeting costs me no capability I have now.
As a publisher, I want to select a segment when I create a paywall, so that the paywall applies only to readers in that segment. [TBD: one segment per paywall, or several]
As a publisher, I want to build segments over anonymous visitors from referral source and page-view frequency, so that I can target readers I know nothing else about.
🎯 Definition of Done (DoD)
✔ Given the segment builder, when a publisher creates a segment, then every attribute usable in paywall targeting today — country, platform, tag, URL, adblock — is available as a condition.
✔ Given a paywall, when a publisher configures targeting, then they select a segment, and the per-paywall attribute fields are deprecated in the UI.
✔ Given a reader in a targeted segment, when they load an article, then that paywall's
frequency_limitandtype_of_paywallapply instead of the untargeted paywall.✔ Given each segment condition type, we should make sure the data will be available and can be evaluated client-side at paywall time.
✔ Given a paywall is displayed, when Paywall Displayed is logged, then the matched segment ID and applied meter limit are recorded.
✔ This solution will include the following limitations: anonymous identity is per-browser and resets on cookie clear; activity events are logged-in only and retained 3 months; geo is country-level at decision time; per-segment products, plans and campaigns out of scope.
Log in to comment and vote
Comments1
An Anonymous User
Sep 29
•Merged request
•5 votes
Dynamic wall
🔍 Problem Statement
Pelcro's paywall is static — it shows the same content gate to every visitor regardless of engagement level, referral source, or user behaviour. Publishers cannot tailor the paywall experience dynamically to maximise conversions and reduce reader friction.
💡 User Story
As a publisher, I want a dynamic paywall that adjusts its behaviour based on reader engagement, referral source, or other signals, so that I can optimise the balance between content access and subscription conversion.
🎯 Definition of Done (DoD)
A feature is done when:
✔️ Given a configurable rule set, when a reader encounters the paywall, then the paywall behaviour (e.g. number of free articles, gate type, messaging) adapts based on the defined rules — and the admin can create, edit, and prioritise these rules from the dashboard.