Kyle Seyler
October 23, 2025

Transactional, product, and marketing notifications are specialized message types used for communicating with users across modern applications. As developers and product teams, understanding these notification types is essential to build effective user experiences and meet legal requirements.
In this article, I'll introduce transactional, product, and marketing notifications, and discuss their purposes, similarities, and differences to give you a better understanding. Whether you're using Courier or another notification platform, getting these fundamentals right is critical for compliance and user trust.
Transactional notifications are automated messages triggered by specific user actions or system events. These notifications provide essential information that users expect and need about their account activity or transactions.
Transactional notifications are not limited to financial transactions. The term refers to any notification that confirms or updates users about an action they initiated or an event affecting their account. Common examples include password resets, order confirmations, payment receipts, security alerts, API key generation, subscription renewals, appointment confirmations, and invoice notifications.
The transactional notification workflow consists of 4 steps:
These notifications are sent in real-time or near real-time to ensure users receive updates when they need them most. For example, when you reset your password, the system immediately sends a verification email. When a payment fails, you get an alert within seconds so you can update your payment method.
Product notifications (also called lifecycle or engagement notifications) are messages designed to help users understand, adopt, and get value from your product. These notifications are educational and feature-focused, guiding users through the product experience.
Unlike transactional notifications that respond to user actions, product notifications proactively drive engagement by introducing new features, providing usage tips, and helping users discover functionality they might otherwise miss. Common examples include new feature announcements, onboarding guidance, usage tips, milestone celebrations, and feature discovery prompts.
Product notifications are typically triggered by user behavior patterns, product events, or time-based rules:
For example, if a user hasn't activated a key feature after 7 days, the system might send a tooltip or modal explaining its value. When you ship a major feature update, you announce it through in-app banners to all relevant users.
Marketing notifications (also called promotional notifications) are messages designed to drive sales, conversions, or business growth through promotional campaigns. These notifications highlight offers, discounts, events, and opportunities that encourage users to take commercial actions.
Marketing notifications always require explicit user opt-in and must include unsubscribe options per FTC CAN-SPAM requirements. They're typically sent to broad segments of users rather than being triggered by individual user actions. Common examples include sale announcements, discount codes, webinar invitations, newsletter content, upgrade promotions, and seasonal campaigns.
Marketing notifications follow a campaign-based workflow:
These notifications can be one-time broadcasts or part of automated marketing sequences. For example, a sale notification goes to all opted-in users, while an abandoned cart reminder is triggered by specific user behavior but still promotional in nature.
Yes, it's highly recommended. Separating transactional and marketing email through multi-tenant infrastructure prevents poor marketing performance from affecting delivery of your critical transactional messages. Many companies use separate IP addresses and subdomains for each type. Courier's transactional notification solution allows you to manage all three notification types with proper separation and routing.
No. According to the FTC, adding any promotional content to a transactional notification can reclassify it as a marketing message that requires opt-in. The FTC states that if "a recipient reasonably interpreting the subject line would likely conclude that the message contains an advertisement" or if "the transactional or relationship content does not appear, in whole or in substantial part, at the beginning of the body of the message," it becomes a commercial message. Keep transactional notifications purely informational.
It depends on the content. A notification that says "Your cart expires in 24 hours" without promotional elements could be considered transactional (informing about system behavior). However, "Complete your purchase and save 15%" is clearly marketing since the primary purpose is commercial advertisement, which requires opt-in under CAN-SPAM.
Generally no for tooltips, modals, and banners that are part of the product interface. However, mobile push notifications typically do require explicit opt-in, even when they're announcing product features rather than promotions. Building an in-app notification center gives users control over their preferences without requiring separate opt-in for each message type.
Ask yourself: "Is the primary goal to help the user use a feature they already have access to, or to convince them to buy something?" If it's education about existing functionality, it's product. If it's promoting an upgrade, sale, or conversion, it's marketing.
Transactional: Email and SMS work well for most cases. SMS is preferred for time-sensitive items like two-factor authentication codes. Push notifications work for mobile-first applications. Courier's channel settings let you route each notification type through the optimal channel.
Product: In-app notifications (modals, tooltips, banners) are most effective since users are actively engaged. Email and push can supplement for users who aren't currently in the product.
Marketing: Email is the primary channel for most marketing campaigns. SMS and push require more careful use due to their intrusive nature and stricter opt-in requirements.
Courier provides a unified platform for managing all three notification types with proper separation and compliance. You can read the documentation to learn more, or send test notifications to see how easy it is to get started with reliable, compliant notification infrastructure.
In this article, I introduced transactional, product, and marketing notifications with their purposes and compared them to each other. Transactional notifications are essential for service delivery and account updates. Product notifications drive feature adoption and engagement. Marketing notifications promote commercial offers and drive revenue. Understanding when to use each type is critical for building notification systems that users trust, engage with, and that comply with legal requirements.

Expo Push Notifications: The Complete Implementation Guide (SDK 52+)
Expo push notifications are alerts sent from a server to a user's phone, even when the app isn't open. To set them up, install the expo-notifications library, ask the user for permission, and get a unique push token for their device. Your server sends a message to Expo's push service with that token, and Expo delivers it through Apple or Google. Push notifications only work on real phones, not simulators. Local notifications are different — they're scheduled by the app itself for things like reminders. You can also route Expo push through services like Courier to add email, SMS, and Slack fallbacks.
By Kyle Seyler
February 24, 2026

Best Email API Providers for Developers in 2026: SendGrid vs Postmark vs Mailgun vs SES vs Resend
Your email provider sticks with you longer than most technical decisions. Courier handles notification infrastructure for thousands of teams, so we went deep on the six email providers that show up most: SendGrid, Postmark, Mailgun, Amazon SES, Resend, and SMTP. This guide covers real API primitives, actual code from each provider's docs, Courier integration examples with provider overrides, and an honest read on where each developer experience holds up and where it breaks down. We also asked Claude to review every API and tell us which one it would wire up first. The answer surprised us.
By Kyle Seyler
February 23, 2026

A Resilient Notification Strategy for Regulated Industries
Notification compliance isn't a legal checklist—it's an infrastructure problem. In 2026, Reg E deadlines, HIPAA content rules, and TCPA consent requirements dictate your system architecture. This guide breaks down the engineering constraints of regulated notifications for fintech, healthcare, and insurance. Learn why hard-coded deadlines fail, how "alert without disclosing" works in practice, and why the smart escalation pattern (Push → SMS → Email) is the only way to satisfy both user urgency and regulatory documentation. Build systems that absorb complexity, not application code that breaks every time a state law changes.
By Kyle Seyler
February 11, 2026
© 2026 Courier. All rights reserved.