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_limit and type_of_paywall apply 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.

Please authenticate to join the conversation.

Upvoters
Status

In Progress

Board
πŸ’‘

Pelcro Product

ETA
Sep 28, 2026
Date

5 days ago

Author

Rana Haleem

Subscribe to post

Get notified by email when there are changes.