AI Personalization System for Email Newsletters in Media
Mass mailings with identical content for the entire database are an outdated approach: open rates of 15–20%, and subscriber churn reaching 5–8% per month. Our engineers observe that media outlets lose up to 70% of engagement potential by ignoring behavioral signals. We build a personalization pipeline based on LLM and event streaming that lifts open rates to 35–50%: reader profile → article scoring → subject line generation via a large language model. Technically, this is a chain involving Apache Kafka for events, Redis for profiles, and batch processing 1–2 hours before send. As a result, each subscriber receives a digest relevant to their interests, reducing churn by 2–3 times and saving up to 40% of the email marketing budget by cutting non-targeted sends.
What Data Is Critical for Personalization?
A quality profile requires at least 10–15 read articles. We collect events: views, time on page, likes, shares. Below this threshold, we use category-based personalization by selecting sections based on recent interests. Data is stored in Redis with a TTL of 30 days; topics are weighted with exponential decay. Without sufficient history, the algorithm switches to a fallback to not degrade the experience.
Why Mass Mailings Lose to Personalization?
Uniform digests ignore behavioral signals: which section a reader opens more often, which topics they skip. LLM personalization accounts for content freshness, editorial score, and even time of day. Compare:
| Metric | Mass Mailing | Personalized Digest |
|---|---|---|
| Open rate, % | 15–20 | 35–50 |
| Click-through rate, % | 2–5 | 8–15 |
| Monthly churn, % | 5–8 | 2–4 |
| Time spent reading | 30–60 s | 2–5 min |
After implementing personalization, open rate increased from 18% to 41% in three months, notes the technical director of one of our clients.
How We Build the Personalization Pipeline?
Step 1. Reader profiling. Collect events via Apache Kafka: views, likes, time on article. Store in Redis with TTL 30 days. Topics are weighted with exponential decay. For each reader, we form a 1536-dimensional embedding based on viewing history.
Step 2. Article scoring. For each unread article, we calculate a combined score:
- Topic match (50%)
- Freshness (30%) — newer articles score higher
- Editorial score (20%)
Step 3. Subject line generation. Use Claude 3.5 Sonnet with a few-shot prompt. The model receives the top three articles and reader interests, and outputs a headline of up to 55 characters in Russian. Example code:
from anthropic import Anthropic
def generate_personalized_digest(user_profile, available_articles, n_articles=5):
llm = Anthropic()
read_ids = user_profile.get('read_ids', set())
unread = [a for a in available_articles if a['id'] not in read_ids]
topics = user_profile.get('topics', {})
scored = []
for article in unread:
topic_score = topics.get(article.get('topic', 'general'), 0.05)
freshness = max(0, 1.0 - article.get('hours_old', 24) / 48)
quality = article.get('editorial_score', 0.7)
scored.append({**article, 'score': topic_score*0.5 + freshness*0.3 + quality*0.2})
top_articles = sorted(scored, key=lambda x: -x['score'])[:n_articles]
article_titles = [a['title'] for a in top_articles]
response = llm.messages.create(
model="claude-3-5-sonnet-20241022",
max_tokens=80,
messages=[{
"role": "user",
"content": f"Write a compelling email subject line for a news digest in Russian.\nArticles: {article_titles[:3]}\nReader's main interests: {list(topics.keys())[:3]}\nMax 55 chars. No clickbait."
}])
return {'articles': top_articles, 'subject': response.content[0].text.strip()}
The personalization trigger threshold is 10–15 read articles. Otherwise, category-based personalization (section selection) is used without article-level targeting. If needed, we fine-tune the model on a corpus of editorial materials using LoRA.
What Results Does Personalization Deliver?
Personalized digests are 2–3 times more effective than mass mailings on key metrics. We conduct A/B testing for each model, fixing lift at p99 latency under 200 ms. Our team's experience in MLOps and NLP allows rapid adaptation of the pipeline to any editorial team. Savings on non-targeted sends reach 30–40% while maintaining content quality.
| Method | Required Data | Latency | Cold Start |
|---|---|---|---|
| Collaborative filtering | Rating history | High | Problem |
| Content-based filtering | Profiles, metadata | Medium | Partial |
| LLM personalization (ours) | Behavior + NLP | Low (batch) | None |
What Is Included in the Turnkey Solution
- Solution architecture with block diagram
- Pipeline code in Python using LangChain and Redis
- Integration with CRM and ESP via REST API
- Documentation and team training
- 3-month warranty and support for releases
Timeline and Cost
Implementation time: from 2 to 6 weeks depending on integration complexity. Cost is calculated individually after an audit of the current stack. We will assess your project free of charge — get a consultation through the form on our website.
How to Get Started?
Tell us about your subscriber base, current metrics, and goals. We will prepare a proposal with an exact scope of work and a timeline. Contact us — we will help raise your open rate up to 50%.