Skip to main content
Web push reaches a person in their browser. There is no app to build and nothing for the recipient to install. They click Allow once on your storefront and you can notify them afterwards, even when your site is closed. Senderz runs push itself. There is no third-party push vendor to sign up for, and push costs no SMS credits.
Push has to be switched on for your workspace before you can use it, and there is no setup screen for it. Contact support and ask for web push. Until it is on, the Push step in the automation builder stays locked and the push sign-up block does nothing on your storefront.

​
Where push can be sent from

Push is an automation channel. There is no push campaign. Campaigns are email or SMS only.

A Push step in an automation

The one way to send push to your contacts. Add a Push step to any automation, attach a push template, and set the step Live.

A popup that collects subscriptions

The Push subscribe block asks the visitor for browser permission and records the subscription against the contact.
Test sends exist, but only through the API. There is no test button on the contact profile, and the campaign test path refuses push with a message pointing at the push test endpoint instead.

​
Collecting a subscription

A visitor subscribes from a popup on your storefront.
1

Add the block to a popup

Open Popups & Forms, edit a popup, and add the Push subscribe block from the Input fields group. It renders as a button. The label defaults to “Get browser notifications” and you can change it in the block’s Button label field.
2

The visitor clicks it

The browser shows its own permission prompt. Senderz cannot style or move that prompt, and it cannot be shown twice in a row after a refusal, so place the block on a step where the visitor already understands what they are getting.
3

Permission is granted

The browser hands back a subscription. It is held with the popup answers and saved when the visitor submits the popup.
4

The contact is subscribed

Push consent on that contact flips to subscribed, and the subscription appears under Push devices on the contact profile.
The push subscription is saved after the email or phone opt-in, and it is best effort. If push fails for any reason, the email and SMS opt-in the visitor just gave you is still recorded.
If the visitor denies the browser prompt, the button re-enables and shows a short message. Nothing is recorded and the contact is not subscribed.

​
Registering a subscription without a popup

If you collect the browser subscription yourself, you can register it directly with POST /push/subscriptions. It authenticates with the same workspace and API key headers as the events ingest API, so a storefront script can call it. GET /push/vapid-public-key returns the public key your page needs to create the subscription in the first place.

​
The service worker requirement, and which platforms support it

A browser will only accept a push service worker served from your own storefront domain. Senderz cannot host it for you, so the push block only works where Senderz has a same-origin path on your store. On a platform where nothing can be served, the Push subscribe block renders nothing at all rather than showing a button that would fail. The rest of the popup still works.
On a custom or headless storefront you can serve your own copy of the Senderz push service worker and point the storefront snippet at it with a pushServiceWorkerUrl value. That is the escape hatch for any platform not in the table, Konimbo included. It must be a path on the same domain as the page showing the popup. See Installing a popup.

​
One subscription per browser

Push consent is not tied to an email address or a phone number. It is tied to the individual browser that granted permission. One person can be subscribed from their laptop Chrome, their phone Chrome and their work machine. Each of those is a separate subscription on the same contact.

A send reaches every browser

One Push step fans out across every live subscription that contact has. They see the notification on each device they subscribed from.

Opting out is per browser

Revoking one subscription leaves the others alone. Only when the last live one is gone does the contact’s push consent drop to unsubscribed.

​
Managing subscriptions on a contact

Open a contact and look at the Push devices card. It lists each live subscription with the browser, the platform and when it was last seen. You get a trash icon on each row to revoke that one browser, and Revoke all to revoke every browser for that contact at once. Push also has its own consent state on the contact, shown as Push in the consent list alongside email and SMS. You can switch it off in the contact editor. Switching it on by hand does not create a subscription. The recipient still has to grant permission in their browser before anything can reach them.

​
Recipients can turn push off themselves

The preference center shows a push toggle to any recipient who has ever had a push state, whether they are currently subscribed or not. Turning it off revokes every live subscription for that contact and suppresses each of those browsers, so a stale subscription cannot be resurrected by a later popup.

​
Segmenting on push

Every workspace is seeded with a Push subscribers segment covering everyone opted in to web push. Push consent and the push opt-in date are both available as segment filters, so you can build narrower audiences on top.

​
When a browser subscription dies

Browser subscriptions expire. People clear site data, uninstall a browser, or block notifications after the fact. You will not be told. The browser’s push service simply starts refusing that subscription. Senderz cleans this up on the next send. When the push service returns 404 or 410 for a subscription:
  • that one subscription is marked revoked,
  • that browser is added to your suppression list with the reason Push permission revoked,
  • if it was the contact’s last live subscription, push consent drops to unsubscribed.
The rest of the fan-out carries on. A send that reaches at least one live browser is a successful send.
Browsers also rotate a subscription silently, without telling the site. Senderz does not chase that. The next send to the old subscription comes back as gone and it is revoked, and the visitor re-subscribes the next time your popup shows. Expect a slow trickle of revocations, not a stable list.

​
Writing the notification

Create push content in Templates. Choose Push as the channel when you create the template. The editor shows a live preview for iOS and Android, and an Encrypted payload size counter.

​
The payload limit

The whole notification, encrypted, must fit in 3,500 bytes. The template editor shows how close you are and flags you when you go over. A send that is over the limit fails before any network call is made, so nothing goes out and nothing is spent. The counter is bytes, not characters. Hebrew and emoji cost more than Latin letters, and a long image URL eats into the same budget.

​
How long a notification survives

A notification is held for up to 24 hours if the browser is offline. If the person does not come back online in that window the push service drops it. There is no retry after that and nothing arrives late.

​
Compliance and the gates a push send passes

Push runs the same checks as SMS, minus the credit wallet. There is nothing to pay for a push send.
1

Workspace checks

A suspended workspace cannot send. A contact parked over your plan’s contact limit is skipped. If web push is switched off for your workspace, nothing goes out.
2

Suppression, per browser

Every one of the contact’s browsers is checked against your suppression list individually. A suppressed browser is dropped from the fan-out and the others still go.
3

Push consent

The contact’s push consent must be subscribed. Email or SMS consent has no bearing on this.
4

Frequency caps

Marketing push is capped at 3 per day and 10 per week per contact. Push has its own bucket, so it does not eat into a contact’s email or SMS allowance.
5

Quiet hours and Shabbat

Marketing push to Israeli recipients respects quiet hours and Shabbat, the same as marketing SMS.

​
Quiet hours delay a push, they do not cancel it

A marketing push that lands inside quiet hours or Shabbat is not dropped. It is put back in the queue and retried when the window opens. Retries are at least 15 minutes apart, and Senderz keeps trying for up to 4 days across up to 16 attempts. Only if the window never opens in that time is the message given up on. Your own quiet hours setting under Settings → Sending Settings narrows the window further and is applied the same way. See Israeli quiet hours for the exact windows.

​
Setting up a Push step

1

Add the step

In the automation builder, open the step menu and pick Push from the Message group. If push is not switched on for your workspace the step is locked and the builder tells you so.
2

Attach content

Click Set up push on the step. That creates a push template and opens the editor. You can also point the step at a push template you already have.
3

Set the step Live

A message step is created as a Draft. A draft step is skipped at send time, so switch it to Live before you publish, or the automation will run and quietly send nothing.

​
What to expect from push

Push is not email. Be honest with yourself about the shape of the audience:
  • Subscribers only accumulate while a popup carrying the block is live on your storefront.
  • The list decays on its own as browsers are cleared and subscriptions expire.
  • A notification is a headline. Anything long belongs in the page you link to.
  • Someone who blocks notifications at the browser level cannot be re-asked by you. Only they can undo it, in browser settings.

Popup blocks

Where the Push subscribe block lives and what else goes on the step.

Installing a popup

Getting Senderz onto your storefront so the block can run.

Automation steps

The Push step alongside every other step type.

Consent and unsubscribes

Push consent, the preference center and suppression.