relaybell

relaybell turns visitors into subscribers you can bring back with one click — no

app, and no email address needed. A notification reaches them even when your site

isn’t open, and each one can carry the product or post that this subscriber is

likely to want, picked from what they viewed, read and bought on your site.

Connect in about a minute. Then new posts go out as a push when you publish,

abandoned carts get a reminder, sold-out products tell their waitlist when they’re

back, and you see which notifications brought visitors and sales back.

What you get

• More returning visitors, without paying for every click.

• Sales you’d otherwise lose: cart reminders, back-in-stock and price-drop

alerts go out on their own.

• Notifications people open: recommendations matched to each subscriber,

delivered at the hour they usually read.

• Clear numbers: delivered, clicked and revenue for every notification.

Features

Grow subscribers

• One-click Connect to relaybell — sign in or create a free account, approve

your site, done. Nothing to copy or paste.

• Opt-in prompt as a slide-in, bar, modal or the browser’s own prompt; shown after

a delay, on scroll, on exit intent or on a click; A/B-test its wording.

• Topics subscribers choose, and a “Notify me when back in stock” button.

• Chrome, Firefox, Edge, Opera, Samsung Internet and Brave on desktop and Android;

4+, from the Home Screen).

Personalized notifications

• Catalog sync: published WooCommerce products and blog posts are sent to

relaybell in the background and updated within about a minute of each change.

• Per-subscriber interests, learned from what each subscriber views, reads,

adds to the cart and buys on your site — your own first-party data only.

• Product and article recommendations: put {rec.title}, {rec.price} or

summary} in a notification and each subscriber gets their own pick.

Out-of-stock products are skipped at send time.

• GA4 events with no code: relaybell can use the Google Analytics 4

js.

• Smart timing: delivery at each subscriber’s usual hour, in their time zone,

within your quiet hours and frequency cap.

• Past orders (optional): import 90 days of orders for a head start.

Automations & journeys

• Push new posts on publish, with the featured image, for the post types you pick.

• Welcome series and custom journeys with delays and branches; subscribers leave

when they buy.

• Automations triggered by anything a subscriber does on your site.

• Recurring campaigns, RSS-to-push, scheduling and A/B-tested notifications.

WooCommerce

• Cart reminders for shoppers who added to cart or started checkout.

• Back in stock alerts to the product’s waitlist.

• Price drop alerts to shoppers who viewed, carted or wait-listed it.

• Order updates: thank-you and follow-up messages after purchases and refunds.

• Revenue attribution, with each order counted once.

• Classic checkout, the Checkout block and HPOS.

Analytics & delivery health

• Delivered, clicks, conversions and revenue per notification; CSV export.

• Delivery health: why a notification didn’t arrive, in plain words.

• Conversion goals with a funnel.

Privacy & control

• Consent: Google Consent Mode, or wait for your cookie banner’s consent.

• GDPR: export or erase everything held about a subscriber.

• Identity verification: logged-in visitors’ IDs are signed by your server, so

nobody can pose as a customer to get their notifications. On from the start.

• A switch for each WooCommerce event and for catalog sync.

• Suggested privacy policy text for your site, under Settings → Privacy.

Works with

WooCommerce, Google Tag Manager and GA4, Zapier, the relaybell REST API and

js and PHP, and common page-cache plugins.

Why relaybell

• Set up in about a minute: one click, no keys, no code, no theme changes.

• It checks itself: the status panel tests eight things — connection, HTTPS,

the script, the service worker, your browser, your public pages, page caches

and sign-in IDs — and says how to fix anything that isn’t right.

• Never slows your site: events are sent after the page is built; the catalog

and past orders go out in small background batches; saving a post never waits

for relaybell.

• Built for real hosting: the service worker is a static file in the plugin

folder (no clash with PWA plugins, any permalink setting), its address avoids

patterns hosting firewalls block, and 13 common page caches are cleared when

your set-up changes.

• Secure by default: signed visitor IDs, HTTPS-only connection settings, and

the API key is cancelled when you disconnect.

• Open: GPL plugin, documented REST API and webhooks, CSV export.

Your data

Nothing is sent until you connect. The catalog holds only what is public on your

site — never password-protected, private or hidden items, and no customer data.

Activity is recorded only for visitors who subscribed. Order events carry the

customer’s email (or your hashed ID) only to find their subscription — no names,

addresses or phone numbers. Past orders are sent only when you ask. Every request

is listed under “External services”.

External services

com), a web push

notification service operated by Nexistech. relaybell is required: browser push

notifications can’t be stored or delivered without a push service, and this

plugin is the WordPress client for it. You need a relaybell account and API key.

1. js)

Loaded on every front-end page once a Project ID is saved, so visitors can opt in.

On each page view it also fetches your project’s public settings (GET

com/api/v1/projects/{project id}/config: push key, prompt and

on-site message settings). Browsers send their normal request data (IP address,

user agent, your site’s address). If you use them, it also reports, without

personal data, which A/B prompt version was shown (POST …/prompt-event) and

on-site message views and clicks (POST …/onsite-event).

2. com/api/v1/projects/{project id}/subscriptions)

When a visitor accepts the notification prompt: the browser’s push endpoint URL

and encryption keys, the page URL, language, time zone, prompt version, and your

topics or tags (for logged-in users, their WordPress role). The service worker

re-sends a subscription the browser replaced. Topic choices made in the box

showPreferences() are saved (GET/POST …/preferences).

For a logged-in visitor (never an administrator) who opted in, their account email

is sent as externalId, with a userHash signature (see 9). Hash it with the

relaybell_external_id filter, or turn off “Link subscribers to their account

email”.

3. com/api/v1/notifications)

With “Send on publish” on: the post’s title, first 20 words, permalink, featured

image URL and (with “Category → topic”) topic. Never for password-protected posts.

4. com/api/v1/events)

With your API key, at the end of the request that caused them: purchase and

started (order id and number, total, currency, and up to 50 products:

refunded (order id and number,

updated (product name, id and URL, cart value);

signup (user id); back_in_stock and price_drop (product name, id, URL, and

old and new price). All on by default; each can be turned off under Settings →

relaybell. While “Link subscribers to their account email” is on, the

customer’s email (account email, else the billing email, or your

started,

refunded; with it off, they’re sent without

updated not at all. updated is only sent for logged-in

shoppers. back_in_stock and price_drop never include customer data.

5. com/api/v1/projects/{project id}/events)

From the browser, only for visitors subscribed to your notifications:

viewed (a product page, while

Price drop or “Send my products” is on: product id, category, price, currency,

viewed (a post, while “Send my posts” is

on: post id, title, type, category, up to 10 tags, permalink), followed once by

read when they scrolled 75% of the page or stayed 30 seconds. Each

carries your project id, the push endpoint URL and, for a logged-in visitor with

“Link subscribers…” on, their externalId and userHash.

6. com/api/v1/notifications/{id}/receipt and /click)

From the service worker: the notification id, a signed token and the

subscription’s id — no page content or personal data.

7. com/api/v1/connect/exchange)

Connect to relaybell sends the administrator’s browser to relaybell with your

site’s address and name, the wp-admin return address and a one-time security

value. Your server then trades the one-time code (with your site address) for

your Project ID and an API key, saved in your database.

8. com/api/v1/…)

From your server, with your API key: subscriber count (GET /stats), that the

Project ID matches the key (GET /me), and when relaybell last ran on your pages

(GET /setup-status); the Plugins screen re-checks an unverified account at most

hourly. The administrator’s browser fetches the script and public settings to

check they aren’t blocked, and your server occasionally fetches your own home page

to detect a stale page cache (that request stays on your site). Subscribe this

browser subscribes the admin’s browser (see 2) and marks it as a test device

(POST /test-devices: its endpoint URL); Send test push sends a test to test

devices only (POST /test-devices/send: test title, text, home page address); a

“send test to my device” link registers that browser (POST /test-devices/claim:

the code and endpoint URL). Advanced → relaybell host changes where these

requests go (https only).

9. com/api/v1/identity)

Your server fetches your project’s identity secret — when you connect, when you

open Settings → relaybell, and daily — and the first time asks relaybell to

accept only verified sign-in IDs (changeable in your relaybell dashboard). The

secret signs logged-in visitors’ IDs on your server and never appears in your

pages. No visitor data is sent.

10. com/api/v1/keys/current)

Disconnect cancels the API key one-click Connect created (only the key is

sent). A key entered by hand is left alone.

11. com/api/v1/catalog/items and /catalog/items/delete)

So notifications can recommend them, your server sends the public details of

published WooCommerce products (“Send my products”) and posts (“Send my posts”),

both on by default: id, title, permalink, image URL, price and sale price with

the currency, category path, brand, tags, a short plain-text summary, stock

status and publication date. Never password-protected, private, draft or hidden

items, and no customer data. WP-Cron sends them in the background, 100 per run:

everything when you connect, update the plugin, change these settings or click

Sync now, and weekly; and each product or post you publish, edit,

unpublish, trash or delete within about a minute (for the last three, only its

id). Turning a switch off removes those items from relaybell.

12. com/api/v1/events/import)

Only after an administrator clicks Import the last 90 days of orders: that

period’s paid orders as purchase events, 50 per background run — the details of

a live purchase (see 4), the payment date, and the customer’s email (or your

relaybell_external_id value) to find their subscription. relaybell keeps only

orders of customers who already get your notifications, never counts an order

twice, and gets no names, addresses or phone numbers.

Nothing is sent until you connect (or save a Project ID and API key manually).

in)

com/terms

com/privacy

com/dpa