Web Push Overview

Full Verion Knowledge Center guide for Web Push.

Quick summary (30 sec)

Full Verion Knowledge Center guide for Web Push.

Web Push — member screen guide
Web Push — member screen guide
Web Push — create / configure (annotated)
Web Push — create / configure (annotated)
Web Push — status & metrics callouts
Web Push — status & metrics callouts

What is it?

Web Push lets consented subscribers receive browser notifications for campaigns. It requires domain setup, VAPID keys, and explicit user opt-in — never silent spam.

Why use it?

Web Push needs VAPID keys, install snippet, consented subscribers, then campaigns (title, message, destination, quota).

When to use — and when not

  • Use when your goal matches this channel’s delivery model.
  • Use after websites/profile basics are complete.
  • Do not use if the plugin is OFF for your account/network.

How it works in Verion

Install snippet per verified site; create campaign with send quota under the daily cap; never spam non-consented users.

Requirements

  • Active Verion member account with email verified when required.
  • Sufficient related credit balance.
  • Website verified when the feature depends on inventory.
  • Plugin enabled by the operator when gated.

Who it is for

  • Publishers
  • Advertisers
  • Agencies operating Verion workspaces

Step-by-step

  1. Open Web Push from the member menu.
  2. Confirm credits and verification prerequisites.
  3. Create or select inventory/creative for this feature.
  4. Configure targeting and caps carefully.
  5. Launch, then monitor delivery daily.

Screen options explained

  • List view: status, spend/earn, and quick actions.
  • Create/edit form: required fields blocked until valid.
  • Help (?): opens this Knowledge Center overview.

Best practices

  • Start small, measure, then scale.
  • Reconcile credit burn against Analytics.

Common mistakes

  • Launching before verification.
  • Ignoring zero-delivery warnings.

FAQ

What is Web Push?

Web Push lets consented subscribers receive browser notifications for campaigns. It requires domain setup, VAPID keys, and explicit user opt-in — never silent spam.

Troubleshooting

No subscribers collecting

Confirm VAPID keys, HTTPS site, and the opt-in prompt is not blocked.

Campaign sends zero

Check send quota, daily cap, and that subscribers still have permission.

Was this helpful?