WEB PUSH

Web Push Notifications That Bring Visitors Back

Turn permission into a return visit. Send web push notifications from your website, then bring subscribers straight to the story, product, or update they wanted.

PERMISSION FIRST

Give visitors a reason to subscribe

Invite people to follow useful updates at a meaningful moment. Web push notifications start with browser permission; your website decides when to explain the value and ask.

BEYOND THE OPEN TAB

Stay useful after visitors leave

Deliver a system notification when the site is closed, where the browser can wake its service worker. Support varies by browser, operating system, permission, and device state.

A CLEAR NEXT STEP

Open the page that matters

Connect web push notifications to a relevant destination. Keep a saved article, booking, or product one click away, with access checks handled by your website.

DELIVERY VISIBILITY

See what happened after sending

Review message records, delivery, and clicks. Use the official analytics and troubleshooting tools to distinguish accepted sends from what subscribers actually receive.

MADE FOR YOUR USERS

Web push notifications for everyday moments

One relevant update. One clear destination.

Publishers

A new story worth returning for

Send a subscribed reader to the latest edition, with topic preferences owned by your publication.

CHOOSE WITH CONFIDENCE

Plan your web push notifications integration

Connect notification delivery to your application rules.

Capabilities and implementation requirements
Your requirementHow it is deliveredWhat to plan for
Permission & identityRegister subscribed recipients through the platform SDK.Your app owns consent, preferences, and account-device mapping.
SendingUse the supported console or server APIs.Your backend controls business triggers, timing, and duplicate suppression.
Opening an updateHandle a notification click and its destination.Validate payloads and account access before showing private content.
Delivery insightInspect available message records and engagement reports.Accepted sends do not guarantee receipt; features depend on the plan and channel.

FROM SETUP TO FIRST SEND

Get started with web push notifications

Configure the channel, connect a test recipient, and follow the complete integration guide.

  1. 01

    Create your application

    Enable the channel in the Push console and configure your application.

    Open Push Console
  2. 02

    Connect a test recipient

    Follow the Web Push guide for browser permissions, registration, and service worker configuration.

    Follow the Integration Guide
  3. 03

    Send and open a test

    Check delivery and the destination on your own devices before a broader rollout.

    Test Your Integration

BUDGET BEFORE YOU BUILD

Web push notifications Pricing & Trial

Choose a plan for your web push notifications audience.

WEB PUSH TRIAL

Free$0 · 7 + 7 day trial

Test Web Push features with the trial shared queue.

View Plan Details

WEB PUSH STANDARD

$199per month

Includes 10,000 monthly active users and a dedicated queue.

Compare Push Plans

YOUR APPLICATION

Contact usVolume pricing & delivery requirements

Discuss audience size, channels and queue requirements. App and Web plans have separate allowances and overage pricing.

Contact us

TEST YOUR INTEGRATION

Try web push notifications in your own application

BUILD WITH TENCENT RTC PUSH

Make your first message useful.

Follow the official quick start, register a test recipient, and send a notification from the console. The illustration shows a possible application experience.

Open the Quick Start

YOUR QUESTIONS, ANSWERED

Web push notifications FAQs

Discuss your project

How do web push notifications work?

A visitor grants permission and subscribes through a supported browser. Your server sends the notification; the browser displays it according to permission, platform support, and device state.

Can web push notifications arrive after the site closes?

Yes, on supported environments when the service worker can be awakened. A closed page does not guarantee delivery: browser settings, operating system restrictions, and network state still apply.

Do subscribers need to install a mobile app?

Desktop website subscribers do not need your native app. Mobile browser requirements differ, so verify the supported browser and operating system combination in the Web Push guide.

Can I send data-only web push notifications offline?

The documented offline channel supports notification messages, not transparent data-only messages. Choose the supported system notification, online in-app message, or combined strategy for your integration.

How are web push notifications priced?

Web Push has its own trial and paid plan. The Standard plan includes 10,000 MAU at $199 per month; additional MAU cost $0.0099 per user per month. Confirm current terms before purchasing.

How do I add web push notifications to a website?

Use the Web Push registration and sending guides, with a supported browser and the required service worker. Ask permission after explaining what the visitor will receive.

Can web push notifications reach visitors after they close the page?

Delivery depends on browser support, permission, subscription validity and whether the browser can wake the service worker. Test the actual device and browser states you intend to support.

BUILD YOUR NEXT USER CONNECTION

Start building with web push notifications