The reader is on the page now.
Front pages, recommendations and paywalls all decide in the moment a reader arrives. Signals keeps the attributes those surfaces read current while the session is still running, keyed on reader, session or article.
- Entities
- reader · session · article · section
- Read from
- front page · recommender · paywall
- Runs in
- your cloud · AWS · GCP · Azure
- Served in
- 6ms p50 in-region
Three problems a subscriber profile cannot solve.
The same front page for everyone
The real estate goes to whatever was picked this morning, not to what this reader has spent the last ten minutes on.
Recommendations that repeat what was ignored
A title shown thirty-five times and never clicked is still in the rail, because the model only sees yesterday.
A paywall that cannot see intent
The meter counts articles. It does not know this session looks like a subscriber.
Four surfaces, one set of definitions.
No replatform. One SDK call.
Signals sits beside the CMS, the recommender and the warehouse you already run. It adds the live attributes none of them keep current.
Start with one attribute.
Define it, read it in your own product, and see it change while you click around. 14 days, no card, no sales call.