The Courier Blog
The real cost of notifications at scale
The sticker price of a notification platform is never the real price. Cost scales with both message volume and user count, and the biggest expense is often the one nobody invoices: owning and running whatever you built yourself. Here's a clear way to model what notifications cost at scale and the levers that actually control it.
Build and launch a hosted preference center that looks great on web and mobile
Courier's redesigned Preferences Editor and hosted preference center let you build, preview, and launch a branded notification preference center with no frontend code, plus new bulk APIs to migrate preferences.
Email open tracking and consent: the new rules in Europe
Regulators in Europe are treating the email open-tracking pixel like a cookie, which means it needs consent before it fires. Here's what changed, who's actually in scope, what compliance requires, and how to keep sending while gating tracking on consent, including how to wire it up in Courier.
The Future-Proof Multichannel Notification System: Built for Humans and AI Agents
Multichannel delivery is now table stakes. In an AI world, future-proof means a notification system both your team and AI agents can build and run.
You can build anything now. That's exactly why you shouldn't build this.
AI made building software cheap, so the temptation is to build everything. But owning infrastructure is a permanent draw on your scarcest resource, attention. The value lives at two ends, the systems everything runs on and the product only you can make; the move is to build less, buy the opinionated platform, and let an agent operate it.
Push Notifications vs In-App Messages: Key Differences and When to Use Each
Push notifications reach users outside your app; in-app messages engage them inside it. Learn the key differences, when to use each, and how to run push, in-app inbox, email, and SMS from one Courier API.
Email sender requirements: a developer's guide to the Gmail, Yahoo, and Outlook rules
Gmail, Yahoo, and Outlook have converged on one set of sender rules, and they've stopped being polite about enforcement. Here's what every developer sending email needs to have in place, provider by provider, plus where the rest of the market is heading.
I redid every cover image on our blog in an afternoon with Claude, Ideogram, and Contentful
I refreshed 81 blog covers, two years of posts, in a single afternoon. Claude Code orchestrated the pipeline, Ideogram generated the art, and the Contentful MCP moved every post in and out. Here is the stack, and why it only took an afternoon.
Experiments: A/B test your messages inside Journeys
Experiments bring A/B testing into Journeys. On any send node, run 2 to 10 message variants, split traffic by weight, and Courier buckets each recipient deterministically, keeping them in the same variant across sends. Compare sent, delivered, open, and click rates per variant, then promote the one you want, without leaving your journey or bolting on a separate testing tool.