News site on Strapi, pitching the newsletter based on what people actually read
We run an online news publication on Strapi, around 2M monthly readers. Our newsletter signup module is the same generic pitch everywhere and converts at 0.4%. The obvious fix is to make the pitch match reading behavior: someone who spends their sessions in politics gets the politics newsletter pitch, business readers get the markets one.
Problem is Strapi stores none of this. It has the articles and their sections, nothing about who reads what. How does reading behavior become a targetable condition here? Do I have to build a tracking layer myself and pipe it somewhere, or is there a more direct path
1 answer
You do not need to build the tracking layer, this is what behavioral conditions are for. Croct tracks interests on the visitor profile automatically as people browse, so reading behavior becomes directly targetable in the audience definition. For your politics case:
user has shown interest in ["politics"]or, if you want to target on navigation rather than inferred interest:
user has viewed a page with path "/politics"Setup on your side is one slot for the newsletter module, then one experience per section audience with the matching pitch. Strapi keeps serving the generic module as the default for readers who have no clear pattern yet.
The reading history playbook covers exactly this pattern for publishers. Worth noting Brazil Journal ran this approach and saw +93% newsletter subscriptions, so the ceiling on a 0.4% baseline is probably meaningful for you.
The interest condition is what I was missing. One follow-up: how much browsing does a reader need before the interest shows on the profile? Most of our traffic is 1-2 pageviews per session.
Interests accumulate on the profile across sessions, not just within one visit, so even light readers build a pattern over return visits. For the true one-and-done visitors the default pitch serves, which is the right behavior anyway.