What Are Push Notifications? The Definitive Guide for 2026

Push notifications are one of the most powerful — and most misunderstood — communication channels in the digital world. Every day, billions of push messages land on lock screens, notification centers, and browser windows across the globe. They drive engagement, recover abandoned carts, deliver breaking news, and keep users connected to the apps and services they rely on.

But what exactly is a push notification? How does the technology work behind the scenes? And how should businesses use push notifications effectively without alienating their audience?

This definitive guide answers all of those questions. Whether you're a product manager evaluating push for the first time, a developer building notification infrastructure, or a marketer looking to optimize your messaging strategy, this is the only resource you need to understand push notifications from the ground up.

What Is a Push Notification? Definition Explained

A push notification is a short, clickable message sent from an application (mobile app, web app, or desktop app) to a user's device — even when the user is not actively using that application. Unlike pull-based communication (where the user has to open an app or check an inbox), push notifications are delivered proactively by the server to the client device in real time.

Here's a simple push notifications definition: push notifications are server-initiated messages delivered to a user's device through the operating system's native notification system, appearing on lock screens, notification trays, or browser prompts without requiring the app to be open.

The key characteristics that distinguish push notifications from other messaging channels include:

• Real-time delivery — messages arrive within seconds of being sent
• Device-level visibility — they appear on the lock screen or notification center, not buried in an inbox
• No app open required — users receive them even when the app is backgrounded or closed
• Opt-in model — users must grant permission before receiving notifications (especially on iOS and web)
• Actionable — notifications can include buttons, deep links, images, and interactive elements

Push notifications bridge the gap between the app experience and the idle screen. They are the only channel that can reach users instantly, at the OS level, without requiring the user to take any prior action like opening an email client or checking a messaging app.

A Brief History of Push Notifications

Understanding what push notifications are today requires a look at how they evolved over the past two decades.

2003–2008: The Precursors

Before smartphones, push technology existed in rudimentary forms. BlackBerry's push email service (2003) was one of the first widely adopted push systems — emails arrived on the device instantly instead of requiring manual refresh. SMS also served as a primitive "push" channel, but lacked the app-level context and interactivity we associate with modern push notifications.

2009: Apple Launches APNs

In June 2009, Apple introduced the Apple Push Notification service (APNs) alongside iPhone OS 3.0. This was the landmark moment for push notifications as we know them. For the first time, third-party developers could send messages directly to a user's iPhone lock screen without the app being open. APNs established the opt-in permission model that remains the standard today.

2010: Google Responds with C2DM (Later GCM, Now FCM)

Google launched Cloud to Device Messaging (C2DM) for Android in 2010, later evolving it into Google Cloud Messaging (GCM) in 2012 and finally Firebase Cloud Messaging (FCM) in 2016. Unlike iOS, Android initially allowed push notifications by default — users didn't need to explicitly opt in, which led to higher reach but also more notification fatigue on the platform.

2013–2015: Rich Notifications and Actionable Buttons

Apple and Google both expanded notification capabilities significantly during this period. iOS 8 (2014) introduced actionable notifications with custom buttons, and iOS 10 (2016) brought rich notifications with images, GIFs, and custom UI. Android kept pace with expanded notifications, inline replies, and notification channels.

2015: Web Push Enters the Scene

The W3C Push API and Notification API standards enabled web push notifications, allowing websites to send notifications to desktop and mobile browsers. Google Chrome led adoption, followed by Firefox and Edge. This opened push notifications beyond native apps to any website with a service worker.

2018–2021: Permission Tightening and Notification Management

As notification overload became a real user problem, both platforms responded. iOS 12 introduced Notification Grouping and Deliver Quietly options. Android 8.0 (Oreo) added Notification Channels, giving users granular control. Browsers began restricting web push permission prompts to combat spam.

2022–2026: AI-Powered Personalization and iOS Web Push

Apple finally brought web push notifications to iOS with Safari 16.4 in 2023, closing a major gap. Meanwhile, the industry shifted toward AI-driven send-time optimization, personalized content generation, and intelligent frequency capping. In 2025–2026, large language models began powering notification copywriting and predictive engagement models became standard in leading push platforms.

How Do Push Notifications Work? Technical Architecture

Understanding how push notifications work requires knowing the three-part architecture that powers every push message: the app publisher's server, the platform notification service, and the user's device.

The Three-Part Architecture

[Your App Server] → [Platform Push Service] → [User's Device]
        ↓                     ↓                       ↓
   Composes the          Routes the message       OS displays the
   message + targets     to the right device      notification

Here's what happens step by step when a push notification is sent:

1. Registration — When a user installs your app (or visits your website and grants permission), the device registers with the platform push service (FCM, APNs, or the browser push service) and receives a unique device token (also called a registration token or push subscription).

2. Token storage — Your app sends this device token to your backend server, which stores it alongside the user's profile.

3. Message composition — When you want to send a notification, your server composes a payload (title, body, image URL, deep link, custom data) and sends it to the platform push service along with the target device token(s).

4. Routing and delivery — The platform push service validates your credentials, queues the message, and routes it to the correct device over a persistent connection.

5. Display — The device OS receives the message, wakes the app's notification handler if needed, and displays the notification according to the payload and the user's notification settings.

FCM (Firebase Cloud Messaging) — Android & Web

Firebase Cloud Messaging (FCM) is Google's cross-platform messaging solution and the primary push infrastructure for Android apps and most web push implementations.

Key technical details:

• Protocol: HTTP v1 API (recommended) or legacy XMPP/HTTP
• Max payload size: 4,096 bytes (4 KB)
• Delivery: Best-effort delivery with priority levels (high priority for time-sensitive messages, normal priority for less urgent)
• Topics: Supports pub/sub topic messaging for broadcasting to user segments
• Upstream messaging: Devices can send messages back to the server
• Platforms: Android, iOS, Web (Chrome, Firefox, Edge, Opera)

FCM is free to use with no message limits, which makes it the default choice for many developers. However, FCM has a critical limitation: it requires Google Play Services, which means it doesn't work reliably on Chinese-market Android devices (Huawei, Xiaomi, OPPO, vivo) where Google services are unavailable.

APNs (Apple Push Notification service) — iOS, macOS, watchOS

APNs is Apple's proprietary push notification delivery system for all Apple platforms.

Key technical details:

• Protocol: HTTP/2-based APNs provider API
• Max payload size: 4,096 bytes (4 KB) for regular notifications, 5,120 bytes (5 KB) for VoIP notifications
• Delivery: Uses persistent, encrypted connections (TLS 1.2+) between your server and APNs
• Token-based auth: Supports JWT-based authentication (recommended) or certificate-based
• Priority: 10 (immediate) or 5 (power-conscious delivery, batched by the OS)
• Feedback service: Reports invalid tokens so you can clean your database

APNs is known for strict rate limiting and aggressive battery optimization. Notifications can be coalesced or deprioritized if the system determines they are not time-sensitive.

Web Push Protocol — Browsers

Web push notifications are built on open standards, primarily:

• W3C Push API — allows service workers to receive push messages
• Web Push Protocol (RFC 8030) — defines how application servers communicate with push services
• VAPID (RFC 8292) — Voluntary Application Server Identification, for authenticating your server
• Payload encryption (RFC 8291) — end-to-end encryption of push payloads

Each browser vendor operates its own push service (Google for Chrome, Mozilla for Firefox, Microsoft for Edge), but they all follow the same protocol. This means your server can send web push notifications to any compliant browser using a single implementation.

Max payload size for web push: 4,078 bytes (varies slightly by browser)

Chinese OEM Push Channels

A critical consideration for apps targeting Chinese or global markets is the fragmented Android push landscape in China. Since Google Play Services are unavailable on most Chinese Android devices, FCM notifications simply don't reach these users. Instead, each major manufacturer operates its own push service:

• Huawei Push Kit (HMS)
• Xiaomi MiPush
• OPPO Push
• vivo Push
• Honor Push
• Meizu Push

To achieve reliable delivery in China, you need to integrate each OEM channel individually — or use a push notification service that unifies all these channels under a single API, routing messages through the correct channel based on the user's device manufacturer.

Types of Push Notifications

Not all push notifications serve the same purpose. Understanding the different types helps you build a notification strategy that delivers value rather than annoyance.

1. Transactional Push Notifications

Transactional notifications are triggered by a user's specific action and deliver information the user expects or needs. These have the highest acceptance rates because users perceive them as useful and relevant.

Examples:

• Order confirmation and shipping updates
• Payment receipts and invoices
• Password reset codes and 2FA verification
• Ride arrival alerts (Uber, Lyft)
• Flight status changes
• Login alerts from new devices

Transactional notifications typically see open rates of 75–90% because they carry immediate, personal relevance.

2. Marketing Push Notifications

Marketing notifications are proactive messages designed to drive engagement, retention, or revenue. They are sent at the brand's initiative rather than triggered by a specific user action.

Examples:

• Flash sales and limited-time promotions
• New content or feature announcements
• Re-engagement campaigns ("We miss you! Here's 20% off")
• Seasonal or holiday campaigns
• Cross-sell and upsell recommendations

Marketing pushes see lower open rates (typically 3–8%) than transactional messages, but they remain one of the most cost-effective channels for re-engagement. The key is restraint — over-sending marketing pushes is the fastest path to opt-outs.

3. Triggered (Behavioral) Push Notifications

Triggered notifications are automated messages sent in response to specific user behaviors or events. They sit between transactional and marketing — they're proactive like marketing pushes but contextually relevant like transactional ones.

Examples:

• Abandoned cart reminders
• Browse abandonment ("Still looking at those sneakers?")
• Inactivity reminders (7-day dormancy triggers)
• Milestone celebrations ("You've completed 100 workouts!")
• Price drop alerts on wishlisted items
• Geofence-triggered offers ("Welcome back to downtown — 15% off your next coffee")

Triggered notifications outperform generic marketing pushes by 3–10x because they're contextual and timely. They're the backbone of modern mobile engagement strategies.

4. Informational / Content Push Notifications

These notifications deliver content updates, news, or information the user has expressed interest in.

Examples:

• Breaking news alerts
• Score updates for followed sports teams
• Weather warnings
• Stock price alerts
• New episode or content releases
• Social activity notifications ("John commented on your post")

5. System and Utility Notifications

System notifications communicate important technical or account information.

Examples:

• App update available
• Storage running low
• Subscription renewal reminders
• Terms of service changes
• Security alerts

Push Notifications Across Platforms: iOS vs Android vs Web

The push notification experience varies significantly across platforms. Understanding these differences is essential for delivering a consistent, optimized experience.

iOS Push Notifications

• Permission required: Yes — users must explicitly opt in via a system dialog. You get one chance to show this prompt (unless the user resets permissions manually), so timing matters enormously.
• Notification styles: Banners, alerts, badges, sounds, and lock screen notifications
• Rich content: Images, GIFs, video thumbnails, audio, and custom UI via Notification Content Extensions
• Action buttons: Up to 4 custom action buttons per notification category
• Grouping: Automatic and custom thread-based grouping (iOS 12+)
• Focus modes: iOS 15+ allows users to filter notifications by Focus mode (Work, Personal, Sleep), which can suppress your notifications
• Notification Summary: iOS 15+ batches non-time-sensitive notifications into scheduled summaries
• Live Activities: iOS 16.1+ allows persistent, updating notifications on the lock screen (sports scores, delivery tracking)
• Average opt-in rate: 50–55% (varies by app category)

Android Push Notifications

• Permission required: Starting with Android 13 (API 33), apps must request the POST_NOTIFICATIONS runtime permission. Prior to Android 13, notifications were enabled by default.
• Notification channels: Android 8.0+ requires apps to create notification channels, giving users granular control over notification types (e.g., mute marketing but keep transactional)
• Rich content: Images, progress bars, large text, inbox style, big picture, messaging style, and fully custom layouts
• Action buttons: Up to 3 action buttons per notification
• Inline reply: Users can type replies directly in the notification shade
• Priority levels: Min, Low, Default, High, Max — affecting how prominently the notification appears
• Foreground services: Notifications can persist for ongoing tasks (music playback, navigation)
• Average opt-in rate: 81–85% (higher than iOS due to the historically default-on model)

Web Push Notifications

• Permission required: Yes — browsers show a permission prompt. Modern browsers (Chrome 80+, Firefox, Edge) have tightened prompt behavior to combat notification spam.
• Appearance: Desktop banner notifications (corner of screen), mobile browser notifications (similar to app push)
• Rich content: Title, body, icon, badge, image, action buttons (up to 2), and vibration patterns
• Service worker required: Web push relies on service workers to receive and display notifications even when the browser tab is closed
• HTTPS required: Web push only works on secure origins
• iOS Safari support: Available since iOS/iPadOS 16.4 (March 2023), but only for websites added to the Home Screen as web apps
• Average opt-in rate: 7–15% (significantly lower than native apps, due to browser UI friction and user skepticism)

Platform Comparison Table

Feature	iOS	Android	Web
Opt-in required	Always	Android 13+	Always
Average opt-in rate	50–55%	81–85%	7–15%
Max payload size	4 KB	4 KB (FCM)	~4 KB
Rich media	✅ Full	✅ Full	✅ Limited
Action buttons	Up to 4	Up to 3	Up to 2
Notification grouping	✅	✅	Limited
Silent/background push	✅	✅	✅
Scheduled delivery	✅ (server-side)	✅ (server-side)	✅ (server-side)

Push Notification Opt-In Best Practices

Your entire push strategy lives or dies on the opt-in. If users decline permission, you've lost the channel entirely (especially on iOS). Here are proven best practices for maximizing opt-in rates.

1. Use a Pre-Permission Prompt (Soft Ask)

Never trigger the native OS permission dialog cold. Instead, show an in-app "soft ask" screen first that explains the value of enabling notifications. If the user says "Not now" on the soft ask, you can try again later. If they decline the native prompt, you can't easily re-ask.

Example soft ask flow:

"Never miss a flash sale! Turn on notifications to get personalized deals before they sell out." [Enable Notifications] [Maybe Later]

Only users who tap "Enable Notifications" see the actual system prompt. This strategy can increase opt-in rates by 40–60% compared to cold prompting.

2. Time the Ask Right

Don't ask for notification permission on first launch or before the user has experienced your app's core value. Wait until the user has completed a meaningful action — placed their first order, added items to a wishlist, followed a topic — then ask.

Research consistently shows that prompting after the user demonstrates intent (session 2–3, or after a key event) yields significantly higher opt-in rates.

3. Explain the Value Clearly

Be specific about what the user will get. "Turn on notifications" is weak. "Get alerts when items on your wishlist drop in price" is compelling. Tailor the value proposition to what the user has actually done in the app.

4. Offer Granular Control

If your platform supports it (Android notification channels, or your own in-app preference center), let users choose which types of notifications they want. Users who feel in control are far less likely to disable notifications entirely.

5. Respect Frequency

The number-one reason users disable push notifications is receiving too many. Start conservatively (2–4 per week for marketing pushes) and increase only if engagement metrics support it. Monitor your opt-out rate per message — a spike means you're over-sending.

6. Provide Easy Opt-Out

Make it easy for users to manage their notification preferences within your app. A visible notification settings screen reduces the chance they'll go nuclear and disable all notifications at the OS level.

Key Push Notification Metrics

Measuring push notification performance goes beyond open rates. Here are the metrics every team should track.

Delivery Rate

Definition: The percentage of sent notifications that are successfully delivered to the device.

Formula: (Notifications Delivered / Notifications Sent) × 100

Benchmark: 95–99% for well-maintained token databases. Low delivery rates indicate stale tokens, uninstalled apps, or platform-specific issues (like missing Chinese OEM channel support).

Open Rate (Click-Through Rate)

Definition: The percentage of delivered notifications that users tap to open.

Formula: (Notifications Opened / Notifications Delivered) × 100

Benchmarks:

• Transactional: 75–90%
• Triggered/behavioral: 8–20%
• Marketing: 3–8%
• Overall industry average: 5–15%

Opt-In Rate

Definition: The percentage of users who grant notification permission.

Formula: (Users Opted In / Total Users Prompted) × 100

Benchmarks: iOS: 50–55%, Android: 81–85%, Web: 7–15%

Opt-Out (Unsubscribe) Rate

Definition: The percentage of opted-in users who disable notifications over a given period.

Formula: (Users Who Disabled Notifications / Total Opted-In Users) × 100

Benchmark: Healthy opt-out rate is below 1% per month. Above 3% signals a problem with content, frequency, or relevance.

Conversion Rate

Definition: The percentage of users who complete a desired action (purchase, sign-up, feature usage) after tapping a notification.

Formula: (Conversions from Push / Notifications Opened) × 100

This is the metric that ties push directly to business value. Track it end-to-end using deep links and attribution.

Revenue Per Push

Definition: The average revenue generated per push notification sent.

Formula: Total Revenue Attributed to Push / Total Notifications Sent

This metric is especially important for e-commerce and subscription apps where push directly drives monetization.

Time-to-Open

Definition: The average time between notification delivery and user tap.

Benchmark: Most push opens happen within 1 hour of delivery, with the median around 7–15 minutes. This metric helps you optimize send times.

Push Notification Best Practices for 2026

Beyond opt-in strategy, here are the best practices for running a world-class push notification program.

Personalize Everything

Generic, broadcast-style pushes are increasingly ineffective. In 2026, users expect personalization. Use behavioral data, purchase history, preferences, and real-time context to tailor every message. Even basic personalization — using the user's first name or referencing their last action — can boost open rates by 20–30%.

Optimize Send Time

Don't blast notifications at 9 AM to your entire user base. Use send-time optimization (STO) to deliver each notification at the time each individual user is most likely to engage, based on their historical interaction patterns. Most modern push notification platforms offer STO as a built-in feature.

Use Rich Media

Rich push notifications with images, GIFs, and action buttons consistently outperform plain-text messages. Include relevant visuals and make the CTA clear with action buttons. On supported platforms, consider using expanded layouts to tell a richer story.

A/B Test Relentlessly

Test everything: titles, body copy, images, CTAs, send times, and deep link destinations. Even small improvements in CTR compound dramatically at scale. Run tests on 10–20% of your audience, then send the winning variant to the rest.

Implement Frequency Capping

Set maximum notification limits per user per day and per week. A common approach is no more than 1 marketing push per day and 5 per week, with transactional notifications uncapped. Adjust based on your data.

Deep Link to Relevant Content

Every notification should deep link the user to the exact screen or content referenced in the message — not the app's home screen. A notification about a flash sale on sneakers should open the sneakers sale page, not the app's main landing page.

Segment Your Audience

Segment users by behavior, demographics, lifecycle stage, and engagement level. New users, power users, dormant users, and at-risk churners should all receive different messages at different frequencies. One-size-fits-all push campaigns underperform segmented ones by 3–5x.

The Future of Push Notifications: 2026 and Beyond

Push notifications continue to evolve rapidly. Here are the trends shaping the channel's future.

AI-Powered Content Generation

Large language models are now being used to generate and optimize push notification copy at scale. Instead of a marketer writing one message for an entire segment, AI generates personalized variants for each user based on their behavior, preferences, and communication style. Early adopters report 15–25% improvements in engagement.

Predictive and Preemptive Notifications

AI models can predict user needs before they arise. An airline app might send a gate-change notification before the user even checks their flight status. A fitness app might send a motivational push at the exact moment a user historically starts losing their workout streak. Predictive push transforms notifications from reactive to proactive.

Richer Interactive Experiences

Notifications are becoming mini-apps. Apple's Live Activities, Android's ongoing notification updates, and interactive web notifications allow users to take complex actions without ever opening the app. Expect this trend to accelerate — ordering a coffee, approving a transaction, or RSVPing to an event, all from the notification shade.

Privacy-First Personalization

With increasing privacy regulations (GDPR, CCPA, India's DPDP Act) and the deprecation of third-party tracking, push personalization is shifting to first-party and zero-party data. The most effective push strategies in 2026 rely on data users have voluntarily provided — preferences, interests, and in-app behavior — rather than cross-app tracking.

Cross-Channel Orchestration

Push notifications increasingly work as part of an omnichannel orchestration strategy rather than in isolation. A user who ignores a push notification might receive a follow-up email 24 hours later, then an in-app message on their next visit. Modern engagement platforms coordinate across push, email, SMS, in-app, and WhatsApp to maximize reach without over-messaging.

Edge Computing and Faster Delivery

Edge computing is reducing push notification delivery latency, especially for real-time use cases like live sports, financial trading alerts, and ride-sharing ETAs. By processing and routing notifications closer to the end user, delivery times are dropping from seconds to sub-second ranges.

How to Get Started with Push Notifications

If you're ready to implement push notifications for your app or website, here's a practical roadmap:

1. Choose your infrastructure — Decide whether to build on raw platform APIs (FCM, APNs, Web Push) or use a managed push notification service that handles multi-platform delivery, analytics, and segmentation out of the box.

2. Integrate the SDK — Add the push SDK to your mobile app or service worker to your website. Handle device token registration and storage.

3. Design your opt-in flow — Implement a soft-ask pre-permission screen with a clear value proposition. Time it to appear after the user has experienced your core value.

4. Define your notification types — Categorize your notifications (transactional, marketing, triggered) and create Android notification channels accordingly.

5. Build your segmentation — Set up user segments based on behavior, demographics, and lifecycle stage. Start simple and refine over time.

6. Launch with transactional first — Begin with high-value transactional notifications (order updates, account alerts) to build user trust, then layer in triggered and marketing messages.

7. Measure and iterate — Track delivery rate, open rate, conversion rate, and opt-out rate from day one. A/B test everything and let data guide your strategy.

Frequently Asked Questions

What is a push notification in simple terms?

A push notification is a short message that pops up on your phone, tablet, or computer from an app or website — even when you're not using it. Think of it as a tap on the shoulder from an app, alerting you to something important like a new message, a sale, or a delivery update.

What is the difference between a push notification and a text message (SMS)?

SMS messages are sent via cellular networks to a phone number, cost money per message, and don't require an app. Push notifications are sent over the internet to a specific device through an app, are free to send (no per-message carrier fees), and require the user to have the app installed and permission granted. Push notifications also support rich media (images, buttons, deep links) that SMS cannot.

Do push notifications use data or cost the user money?

Push notifications use a negligible amount of mobile data (a few kilobytes per notification). They do not cost the user any additional money beyond their normal data plan. For the sender, push delivery through FCM and APNs is free — the cost is in the infrastructure to manage targeting, segmentation, and analytics.

Can I send push notifications without an app?

Yes — web push notifications allow you to send notifications to users through their web browser without a native mobile app. Users simply need to visit your website and grant notification permission. However, web push has lower opt-in rates and more limited capabilities compared to native app push.

Why am I not receiving push notifications?

Common reasons include: notification permissions are disabled in your device settings, the app's notifications are turned off, Do Not Disturb or Focus mode is active, the app has been force-closed (on some Android devices), battery optimization is killing the background process, or the app hasn't been updated. Check Settings > Notifications on your device to verify permissions.

What is a good push notification open rate?

Open rates vary widely by notification type and industry. Transactional notifications see 75–90% open rates. Triggered behavioral notifications average 8–20%. Marketing pushes average 3–8%. An overall open rate above 5–10% is considered healthy for a mixed push program. Focus on improving relevance and timing rather than chasing a single benchmark.

How many push notifications should I send per day?

There is no universal answer, but research and industry best practices suggest limiting marketing push notifications to 1 per day and 3–5 per week. Transactional notifications (order updates, security alerts) can be sent as needed since users expect them. The right frequency depends on your app category, user expectations, and — most importantly — your opt-out rate data.

Are push notifications bad for battery life?

Individual push notifications have minimal battery impact. The platform push services (FCM, APNs) use a single persistent connection shared across all apps, so receiving a notification doesn't require waking up a separate connection for each app. However, notifications that trigger heavy background processing (like downloading large attachments or syncing data) can affect battery life.

What is the difference between push notifications and in-app messages?

Push notifications reach users when they're outside the app — on the lock screen or in the notification tray. In-app messages appear only when the user is actively using the app. Push is better for re-engagement and time-sensitive alerts; in-app messaging is better for onboarding, feature discovery, and contextual guidance while the user is already engaged.

Can push notifications be sent to iOS and Android at the same time?

Yes, but the technical implementation differs. iOS uses APNs and Android uses FCM, so your server needs to integrate with both services. Most push notification platforms abstract this complexity, allowing you to compose one notification and send it cross-platform with a single API call, automatically handling the platform-specific payload formatting and delivery.

Conclusion

Push notifications remain one of the most direct, immediate, and effective channels for engaging users in 2026. From transactional alerts that users rely on to AI-personalized marketing messages that drive revenue, the push notification channel continues to grow in both capability and sophistication.

The fundamentals haven't changed: deliver the right message, to the right person, at the right time. But the tools to execute on that promise — intelligent segmentation, send-time optimization, rich media, and cross-platform delivery — have never been more powerful.

Whether you're just starting with push or optimizing an existing program at scale, success comes down to respecting the user's attention, delivering genuine value with every message, and relentlessly measuring and iterating on your results.