Open book surrounded by push icons, illustrating a push notification glossary Open book surrounded by push icons, illustrating a push notification glossary

Push Notification Glossary: 50 Terms Explained

A push notification glossary of 50 terms in plain English, from Push API, service worker and VAPID to segments, drips and CTR.

A push notification glossary explains the terms behind web and app push, from the Push API, service worker and VAPID keys to opt-in rate, segment and drip campaign. Below are 50 push notification terms in plain English, grouped by topic, so you can read vendor docs, compare tools and talk to developers without guessing what a word means.

I put this together because push tools love jargon, and half of it means slightly different things from one vendor to the next. Where a term has a formal definition, I link the spec or official docs.

What are the core push notification terms?

These are the basics everyone meets first. Each definition is short enough to quote on its own.

  • Push notification: a message sent from a server to a user’s device that appears outside the app or website, even when it isn’t open.
  • Web push notification: a push notification delivered to a browser through the Push API and a service worker, with no app install needed.
  • App push notification: a push sent to an installed mobile app through FCM (Android) or APNs (iOS).
  • Browser notification: any alert a website shows through the browser’s Notifications API; web push is one kind.
  • Desktop notification: a notification shown on a computer’s operating system, from a website or an installed app.
  • Mobile web push: web push shown on a phone, usually through Chrome or another browser on Android.
  • Subscriber: a browser or device that has granted permission and holds an active push subscription.
  • Opt-in: the act of allowing notifications, usually by clicking Allow on the browser prompt.
  • Opt-out (unsubscribe): turning notifications off, usually in browser or app settings.
  • Push notification service (provider): the software or company you use to collect subscribers and send campaigns, such as OneSignal or a self-hosted panel.

For how these fit together, see web push vs browser vs desktop notifications.

What are the technical web push terms?

These terms come from the web standards that make push work. Developers use them daily, and marketers meet them during setup.

  • Push API: the W3C browser API that lets a site subscribe to and receive push messages (MDN).
  • Notifications API: the browser API that displays a notification and asks for permission (MDN).
  • Service worker: a background script registered for your site that receives push messages and shows notifications when no tab is open.
  • Push subscription: the endpoint URL and encryption keys a browser creates when the user opts in.
  • Endpoint: the unique URL at the browser vendor’s push service that your server sends messages to.
  • Push service: the browser vendor’s delivery server, for example the one Chrome uses through FCM.
  • Web Push protocol: the IETF standard for sending messages to a push service (RFC 8030).
  • VAPID: Voluntary Application Server Identification, a key pair that proves which server is sending (RFC 8292).
  • Payload encryption: the end-to-end encryption of message content so push services can’t read it (RFC 8291).
  • TTL (time to live): how long the push service should keep trying to deliver a message to an offline device.
  • Urgency: a header that hints how important a message is, which helps devices save battery.
  • FCM (Firebase Cloud Messaging): Google’s messaging service used for Android app push and Chrome web push (Firebase docs).
  • APNs (Apple Push Notification service): Apple’s delivery service for iOS, iPadOS and macOS notifications.
  • Manifest (web app manifest): a JSON file that describes a web app; on iPhone, a site must be added to the Home Screen for web push.
  • PWA (progressive web app): a website that can be installed and behave like an app, including push.

Deeper reads: what VAPID keys are and why web push needs a service worker.

What are the permission and prompt terms?

These cover how you ask for permission, which shapes your whole list.

  • Native prompt: the browser’s own permission dialog, which only the browser can show.
  • Soft prompt (pre-prompt): your own box or bell shown first, explaining what you’ll send before triggering the native prompt.
  • Bell (widget): a small floating icon visitors can click to subscribe later.
  • Opt-in rate: the share of visitors shown a prompt who subscribe; definitions vary by tool.
  • Permission state: granted, denied or default (not yet asked) for a site.
  • Quiet permission UI: a muted prompt Chrome shows for sites with low acceptance rates (Chromium blog).
  • Re-prompt: showing a soft prompt again later to someone who dismissed it, never the native prompt after a denial.

See how to ask visitors to allow notifications and web push opt-in rate.

What are the campaign and message terms?

These are the parts of a single notification and the ways you send it.

  • Campaign: one notification sent to an audience, manually or on a schedule.
  • Title: the bold first line of a notification.
  • Body (message): the shorter text under the title.
  • Icon: the small image, usually your logo.
  • Large image (hero image): a bigger picture shown on supported browsers, mainly Chrome on Windows and Android.
  • Badge: a small monochrome icon Android shows in the status bar.
  • Click URL (landing URL): the page that opens when someone clicks the notification.
  • CTA button (action): an extra button inside the notification with its own link; support varies by browser.
  • Scheduled push: a campaign set to send at a future time.
  • Template: a saved notification layout you reuse.

What are the automation and targeting terms?

These terms describe sending the right message to the right people without doing it by hand.

  • Segment: a group of subscribers filtered by rules such as country, device, browser or subscribed page.
  • Segmentation: the practice of building and using segments.
  • Automation (triggered push): a notification sent automatically when an event happens.
  • Welcome push: an automatic message sent right after someone subscribes.
  • Drip campaign: a timed sequence of pushes sent over days or weeks.
  • Push on publish: an automatic notification when a new blog post goes live, common with WordPress.
  • Retargeting: sending a follow-up to people who clicked or ignored an earlier campaign.
  • Frequency capping: limiting how many pushes one subscriber gets in a period.

More on two of these: welcome push notifications and drip push campaigns.

What are the analytics terms?

These are the numbers you’ll see in a push dashboard. Note that each vendor counts slightly differently, so compare like with like.

TermPlain meaning
SentMessages your server handed to push services
DeliveredMessages confirmed as received, where the tool can measure it
ClickedNotifications that were clicked
CTR (click-through rate)Clicks divided by sent or delivered, depending on the tool
Expired subscriberA subscription the push service reports as no longer valid

For benchmarks and how to read them, see push notification metrics.

Where does LaraPush fit?

LaraPush is a self-hosted web push panel, so you’ll meet most of these terms in its dashboard: prompts and bells, segments, Welcome Push, Push on Publish, scheduled campaigns, CTA buttons, and per-campaign sent, delivered and click stats. Drip Campaigns and AutoMagic Push come with the Pro plan. The trade-offs: you install it on your own VPS, a licence covers one server, and there is no free plan. See features, pricing and the best push notification services and tools.

Frequently asked questions

What is the difference between a push notification and a web push notification?

Push notification is the umbrella term for any server-sent alert. A web push notification is delivered to a browser through the Push API and a service worker, so it works without installing an app. App push goes to installed mobile apps through FCM or APNs.

What does VAPID mean in push notifications?

VAPID stands for Voluntary Application Server Identification. It is a public and private key pair that identifies your server to the browser’s push service, defined in RFC 8292. Subscriptions are tied to the VAPID public key used when they were created.

What is a soft prompt?

A soft prompt is your own message, box or bell shown before the browser’s native permission dialog. It explains what you’ll send and how often, and it only triggers the native prompt when the visitor agrees.

What is a push notification segment?

A segment is a group of subscribers filtered by rules such as country, device, browser, subscription date or the page they subscribed on. Sending to segments keeps messages relevant and reduces unsubscribes.

What does CTR mean for push notifications?

CTR is click-through rate: clicks divided by notifications sent or delivered. Tools use different bases, so check which one your dashboard uses before comparing numbers with benchmarks.

Leave a Reply

Your email address will not be published. Required fields are marked *