Personalized recommendations: your public products and posts are sent to relaybell in the background (two switches under Settings \u2192 relaybell \u2192 Personalization), and order events now include the products bought.<\/p>","1.2.6":"
The relaybell notices now show only on the Plugins screen and can be dismissed. No settings change.<\/p>","1.2.5":"
Maintenance release: the settings page loads its script and styles as files, and the readme lists every request the plugin makes. No settings change.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3764998,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3764998,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3764998,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3764998,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.2.6","1.3.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3764998,"resolution":"1","location":"assets","locale":"","width":1534,"height":988},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3764998,"resolution":"2","location":"assets","locale":"","width":1534,"height":988},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3764998,"resolution":"3","location":"assets","locale":"","width":1255,"height":562},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3764998,"resolution":"4","location":"assets","locale":"","width":1255,"height":668},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3764998,"resolution":"5","location":"assets","locale":"","width":1534,"height":988},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3764998,"resolution":"6","location":"assets","locale":"","width":1534,"height":988},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3765724,"resolution":"7","location":"assets","locale":"","width":1534,"height":988},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3765724,"resolution":"8","location":"assets","locale":"","width":1534,"height":988},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3765724,"resolution":"9","location":"assets","locale":"","width":1534,"height":988}},"screenshots":{"1":"Settings \u2192 relaybell before connecting: one click on Connect to relaybell links your site \u2014 nothing to copy or paste.","2":"The status panel checks the connection, HTTPS, your public pages, the relaybell script, the service worker, this browser and visitor sign-in IDs, and says how to fix anything that isn't right.","3":"Publishing: push new posts automatically for the post types you choose, send each post to the topic of its category, and link logged-in subscribers to their account.","4":"WooCommerce events \u2014 purchase, cart, back in stock, price drop, sign-up, checkout and refund \u2014 each with its own switch, plus the waitlist button.","5":"The opt-in prompt your visitors see. Its style, text and timing are set in your relaybell dashboard.","6":"The \"Notify me when back in stock\" button on a sold-out product.","7":"Your relaybell dashboard, Settings \u2192 Catalog: the products and articles synced from WordPress, kept up to date automatically.","8":"The Send composer with \"Recommend a product\", and a preview of what one subscriber will get.","9":"A subscriber's interests, learned from what they viewed, read and bought on your site."}},"plugin_section":[],"plugin_tags":[15962,155593,1155,37677,286],"plugin_category":[45,55],"plugin_contributors":[288502],"plugin_business_model":[],"class_list":["post-390617","plugin","type-plugin","status-publish","hentry","plugin_tags-abandoned-cart","plugin_tags-back-in-stock","plugin_tags-push-notifications","plugin_tags-web-push","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_category-seo-and-marketing","plugin_contributors-relaybell","plugin_committers-relaybell"],"banners":{"banner":"https:\/\/ps.w.org\/relaybell\/assets\/banner-772x250.png?rev=3764998","banner_2x":"https:\/\/ps.w.org\/relaybell\/assets\/banner-1544x500.png?rev=3764998","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/relaybell\/assets\/icon-128x128.png?rev=3764998","icon_2x":"https:\/\/ps.w.org\/relaybell\/assets\/icon-256x256.png?rev=3764998","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-1.png?rev=3764998","caption":"Settings \u2192 relaybell before connecting: one click on Connect to relaybell links your site \u2014 nothing to copy or paste."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-2.png?rev=3764998","caption":"The status panel checks the connection, HTTPS, your public pages, the relaybell script, the service worker, this browser and visitor sign-in IDs, and says how to fix anything that isn't right."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-3.png?rev=3764998","caption":"Publishing: push new posts automatically for the post types you choose, send each post to the topic of its category, and link logged-in subscribers to their account."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-4.png?rev=3764998","caption":"WooCommerce events \u2014 purchase, cart, back in stock, price drop, sign-up, checkout and refund \u2014 each with its own switch, plus the waitlist button."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-5.png?rev=3764998","caption":"The opt-in prompt your visitors see. Its style, text and timing are set in your relaybell dashboard."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-6.png?rev=3764998","caption":"The \"Notify me when back in stock\" button on a sold-out product."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-7.png?rev=3765724","caption":"Your relaybell dashboard, Settings \u2192 Catalog: the products and articles synced from WordPress, kept up to date automatically."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-8.png?rev=3765724","caption":"The Send composer with \"Recommend a product\", and a preview of what one subscriber will get."},{"src":"https:\/\/ps.w.org\/relaybell\/assets\/screenshot-9.png?rev=3765724","caption":"A subscriber's interests, learned from what they viewed, read and bought on your site."}],"raw_content":"\n
relaybell turns visitors into subscribers you can bring back with one click \u2014 no\napp, and no email address needed. A notification reaches them even when your site\nisn't open, and each one can carry the product or post that this subscriber is\nlikely to want, picked from what they viewed, read and bought on your site.<\/p>\n\n
Connect in about a minute. Then new posts go out as a push when you publish,\nabandoned carts get a reminder, sold-out products tell their waitlist when they're\nback, and you see which notifications brought visitors and sales back.<\/p>\n\n
Grow subscribers<\/strong><\/p>\n\n Personalized notifications<\/strong><\/p>\n\n Automations & journeys<\/strong><\/p>\n\n WooCommerce<\/strong><\/p>\n\n Analytics & delivery health<\/strong><\/p>\n\n Privacy & control<\/strong><\/p>\n\n Works with<\/strong><\/p>\n\n WooCommerce, Google Tag Manager and GA4, Zapier, the relaybell REST API and\nwebhooks, server SDKs for Node.js and PHP, and common page-cache plugins.<\/p>\n\n Nothing is sent until you connect. The catalog holds only what is public on your\nsite \u2014 never password-protected, private or hidden items, and no customer data.\nActivity is recorded only for visitors who subscribed. Order events carry the\ncustomer's email (or your hashed ID) only to find their subscription \u2014 no names,\naddresses or phone numbers. Past orders are sent only when you ask. Every request\nis listed under \"External services\".<\/p>\n\n This plugin connects to relaybell<\/strong> (https:\/\/relaybell.com), a web push\nnotification service operated by Nexistech. relaybell is required: browser push\nnotifications can't be stored or delivered without a push service, and this\nplugin is the WordPress client for it. You need a relaybell account and API key.<\/p>\n\n 1. Browser SDK (https:\/\/relaybell.com\/relaybell-sdk.js)<\/strong><\/p>\n\n Loaded on every front-end page once a Project ID is saved, so visitors can opt in.\nOn each page view it also fetches your project's public settings (GET\nhttps:\/\/relaybell.com\/api\/v1\/projects\/{project id}\/config: push key, prompt and\non-site message settings). Browsers send their normal request data (IP address,\nuser agent, your site's address). If you use them, it also reports, without\npersonal data, which A\/B prompt version was shown (POST ...\/prompt-event) and\non-site message views and clicks (POST ...\/onsite-event).<\/p>\n\n 2. Subscribing (POST https:\/\/relaybell.com\/api\/v1\/projects\/{project id}\/subscriptions)<\/strong><\/p>\n\n When a visitor accepts the notification prompt: the browser's push endpoint URL\nand encryption keys, the page URL, language, time zone, prompt version, and your\ntopics or tags (for logged-in users, their WordPress role). The service worker\nre-sends a subscription the browser replaced. Topic choices made in the box\nopened by 3. Publish pushes (POST https:\/\/relaybell.com\/api\/v1\/notifications)<\/strong><\/p>\n\n With \"Send on publish\" on: the post's title, first 20 words, permalink, featured\nimage URL and (with \"Category \u2192 topic\") topic. Never for password-protected posts.<\/p>\n\n 4. WooCommerce events from your server (POST https:\/\/relaybell.com\/api\/v1\/events)<\/strong><\/p>\n\n With your API key, at the end of the request that caused them: 5. Visitor activity (POST https:\/\/relaybell.com\/api\/v1\/projects\/{project id}\/events)<\/strong><\/p>\n\n From the browser, only for visitors subscribed to your notifications:\n waitlist.join (the \"Notify me\" button), 6. Delivery and click reports (POST https:\/\/relaybell.com\/api\/v1\/notifications\/{id}\/receipt and \/click)<\/strong><\/p>\n\n From the service worker: the notification id, a signed token and the\nsubscription's id \u2014 no page content or personal data.<\/p>\n\n 7. Connecting (https:\/\/relaybell.com\/connect\/wordpress, POST https:\/\/relaybell.com\/api\/v1\/connect\/exchange)<\/strong><\/p>\n\n Connect to relaybell<\/strong> sends the administrator's browser to relaybell with your\nsite's address and name, the wp-admin return address and a one-time security\nvalue. Your server then trades the one-time code (with your site address) for\nyour Project ID and an API key, saved in your database.<\/p>\n\n 8. Admin status and test push (https:\/\/relaybell.com\/api\/v1\/...)<\/strong><\/p>\n\n From your server, with your API key: subscriber count (GET \/stats), that the\nProject ID matches the key (GET \/me), and when relaybell last ran on your pages\n(GET \/setup-status); the Plugins screen re-checks an unverified account at most\nhourly. The administrator's browser fetches the script and public settings to\ncheck they aren't blocked, and your server occasionally fetches your own home page\nto detect a stale page cache (that request stays on your site). Subscribe this\nbrowser<\/strong> subscribes the admin's browser (see 2) and marks it as a test device\n(POST \/test-devices: its endpoint URL); Send test push<\/strong> sends a test to test\ndevices only (POST \/test-devices\/send: test title, text, home page address); a\n\"send test to my device\" link registers that browser (POST \/test-devices\/claim:\nthe code and endpoint URL). Advanced \u2192 relaybell host<\/strong> changes where these\nrequests go (https only).<\/p>\n\n 9. Identity verification (GET and PUT https:\/\/relaybell.com\/api\/v1\/identity)<\/strong><\/p>\n\n Your server fetches your project's identity secret \u2014 when you connect, when you\nopen Settings \u2192 relaybell<\/strong>, and daily \u2014 and the first time asks relaybell to\naccept only verified sign-in IDs (changeable in your relaybell dashboard). The\nsecret signs logged-in visitors' IDs on your server and never appears in your\npages. No visitor data is sent.<\/p>\n\n 10. Disconnecting (DELETE https:\/\/relaybell.com\/api\/v1\/keys\/current)<\/strong><\/p>\n\n Disconnect<\/strong> cancels the API key one-click Connect created (only the key is\nsent). A key entered by hand is left alone.<\/p>\n\n 11. Catalog (POST https:\/\/relaybell.com\/api\/v1\/catalog\/items and \/catalog\/items\/delete)<\/strong><\/p>\n\n So notifications can recommend them, your server sends the public details of\npublished WooCommerce products (\"Send my products\") and posts (\"Send my posts\"),\nboth on by default: id, title, permalink, image URL, price and sale price with\nthe currency, category path, brand, tags, a short plain-text summary, stock\nstatus and publication date. Never password-protected, private, draft or hidden\nitems, and no customer data. WP-Cron sends them in the background, 100 per run:\neverything when you connect, update the plugin, change these settings or click\nSync now<\/strong>, and weekly; and each product or post you publish, edit,\nunpublish, trash or delete within about a minute (for the last three, only its\nid). Turning a switch off removes those items from relaybell.<\/p>\n\n 12. Past orders (POST https:\/\/relaybell.com\/api\/v1\/events\/import)<\/strong><\/p>\n\n Only after an administrator clicks Import the last 90 days of orders<\/strong>: that\nperiod's paid orders as Nothing is sent until you connect (or save a Project ID and API key manually).<\/p>\n\n Service provider: Nexistech (https:\/\/nexistech.in)\nTerms of service: https:\/\/relaybell.com\/terms\nPrivacy policy: https:\/\/relaybell.com\/privacy\nData processing agreement: https:\/\/relaybell.com\/dpa<\/p>\n\n\n Your site must use HTTPS \u2014 browsers only allow push notifications on secure\nsites (and on localhost for testing). The status panel tells you if anything\nneeds attention.<\/p>\n\n The WooCommerce integration loads by itself when WooCommerce is active \u2014 there is\nnothing extra to set up.<\/p>\n\n\n No. Without WooCommerce you get the opt-in prompt, publish-time pushes and post\nrecommendations. The commerce features switch on by themselves when WooCommerce\nis active.<\/p><\/dd>\n No. Web push works from the browser subscription alone. If a user is logged in,\nrelaybell also binds their account email as an The plugin keeps relaybell's copy of your catalog up to date (products and posts),\nand records what each subscribed visitor opens. relaybell turns that, plus their\ncart adds, purchases and notification clicks, into an interest profile per\nsubscriber. Put The public details of published products and posts: title, link, image, price,\ncategory, brand, tags, a short summary and stock status \u2014 see \"External\nservices\" (11). Untick Send my products<\/strong> or Send my posts<\/strong> under\nSettings \u2192 relaybell \u2192 Personalization<\/strong> to stop sending them (they are then\nremoved from relaybell). Developers can leave out single items or change what is\nsent with the No. Saving a post or a product only notes its id; WP-Cron sends the changes in\nthe background within about a minute, and the full catalog goes out 100 items per\nrun, picking up where it stopped if a run is interrupted. On a site with little\ntraffic, WP-Cron runs less often, so a large first sync can take a while \u2014 the\nstatus on Settings \u2192 relaybell<\/strong> shows how far it got.<\/p><\/dd>\n Yes. Add your post type with the The paid orders of the last 90 days, with the same details as a new order's\n purchase event. relaybell keeps only orders from customers who already get your\nnotifications, and never counts an order twice \u2014 not even one it already got\nwhen it was placed \u2014 so you can run it again at any time.<\/p><\/dd>\n On Settings \u2192 relaybell<\/strong>, click Subscribe this browser<\/strong> (allow notifications\nwhen your browser asks), then Send test push<\/strong>. The test goes only to your own\nbrowser \u2014 never to your subscribers \u2014 and appears within a few seconds. The\nsettings page then tells you whether it reached this browser, and what to check\nif you don't see it.<\/p>\n\n If no permission pop-up appears, look for a bell icon in the address bar and\nchoose Allow. If notifications are blocked, the status panel explains how to\nunblock them.<\/p><\/dd>\n Most often your relaybell account email isn't verified yet. Until it is,\nrelaybell doesn't send anything to your visitors \u2014 new-post pushes, campaigns\nand automations are all held back \u2014 while test pushes to your own browser still\nwork. Click the link in the email relaybell sent when you signed up (check your\nspam folder), or send it again from your relaybell dashboard. The status panel\nand the Plugins screen show a red warning while this is the case.<\/p>\n\n Also check that Send on publish<\/strong> is turned on (it is off by default) and,\nif you use Category \u2192 topic<\/strong>, that relaybell has a topic for the post's\ncategory. Password-protected posts are never pushed.<\/p><\/dd>\n relaybell's set-up is part of every page, so a cached page keeps the set-up it\nwas saved with. When you connect, disconnect, change the connection or update\nthe plugin, relaybell clears the cache of WP Rocket, LiteSpeed Cache, W3 Total\nCache, WP Super Cache, SiteGround Speed Optimizer, Breeze, Nginx Helper, Cache\nEnabler, WP Fastest Cache, WP-Optimize, Hummingbird, WP Engine and Kinsta. If\nyour host or a CDN such as Cloudflare caches your pages too, clear that cache\nyourself. The status panel warns when visitors still get an older copy, and\nshows when relaybell last ran on your public pages. (Developers: other caches\ncan hook into With it on, each new post is sent only to subscribers who follow the relaybell\ntopic named like the post's primary category \u2014 for example a topic \"Tech News\"\nfor the category Browsers only allow push notifications on HTTPS sites, plus Your server must be able to make outgoing HTTPS requests to relaybell.com. If\nyour host blocks that, open Advanced<\/strong> on the settings page and enter your\nProject ID and an API key from the relaybell dashboard manually.<\/p><\/dd>\n Yes. The plugin declares \n
\n
{rec.title}<\/code>, {rec.price}<\/code> or\n {rec.summary} in a notification and each subscriber gets their own pick.\nOut-of-stock products are skipped at send time.<\/li>\n\n
\n
\n
\n
Why relaybell<\/h4>\n\n
\n
Your data<\/h4>\n\n
External services<\/h3>\n\n
RelayBell.showPreferences()<\/code> are saved (GET\/POST ...\/preferences).\nFor a logged-in visitor (never an administrator) who opted in, their account email\nis sent as externalId<\/code>, with a userHash<\/code> signature (see 9). Hash it with the\n relaybell_external_id filter, or turn off \"Link subscribers to their account\nemail\".<\/p>\n\npurchase<\/code> and\n checkout.started (order id and number, total, currency, and up to 50 products:\nid, name, category, unit price, quantity); order.refunded<\/code> (order id and number,\namount, currency); cart.updated<\/code> (product name, id and URL, cart value);\n signup (user id); back_in_stock<\/code> and price_drop<\/code> (product name, id, URL, and\nold and new price). All on by default; each can be turned off under Settings \u2192\nrelaybell<\/strong>. While \"Link subscribers to their account email\" is on, the\ncustomer's email (account email, else the billing email, or your\n relaybell_external_id value) is sent with purchase<\/code>, checkout.started<\/code>,\n cart.updated, signup<\/code> and order.refunded<\/code>; with it off, they're sent without\nit and cart.updated<\/code> not at all. cart.updated<\/code> is only sent for logged-in\nshoppers. back_in_stock<\/code> and price_drop<\/code> never include customer data.<\/p>\n\nproduct.viewed<\/code> (a product page, while\nPrice drop or \"Send my products\" is on: product id, category, price, currency,\nbrand, page URL, image) and content.viewed<\/code> (a post, while \"Send my posts\" is\non: post id, title, type, category, up to 10 tags, permalink), followed once by\n content.read when they scrolled 75% of the page or stayed 30 seconds. Each\ncarries your project id, the push endpoint URL and, for a logged-in visitor with\n\"Link subscribers\u2026\" on, their externalId<\/code> and userHash<\/code>.<\/p>\n\npurchase<\/code> events, 50 per background run \u2014 the details of\na live purchase<\/code> (see 4), the payment date, and the customer's email (or your\n relaybell_external_id value) to find their subscription. relaybell keeps only\norders of customers who already get your notifications, never counts an order\ntwice, and gets no names, addresses or phone numbers.<\/p>\n\n\n
\n
Do I need WooCommerce?<\/h3><\/dt>\n
Do subscribers need to give an email address?<\/h3><\/dt>\n
externalId<\/code> for richer targeting;\nyou can substitute a hashed value with the relaybell_external_id<\/code> filter.<\/p><\/dd>\nHow do recommendations work?<\/h3><\/dt>\n
{rec.title}<\/code>, {rec.url}<\/code>, {rec.price}<\/code> or {rec.summary}<\/code> in a\nnotification \u2014 or choose \"Recommend a product\" in the relaybell composer \u2014 and\neach subscriber gets their own pick. Someone relaybell doesn't know yet gets your\npopular items.<\/p><\/dd>\nWhat exactly is sent for the catalog? Can I leave something out?<\/h3><\/dt>\n
relaybell_catalog_item<\/code> filter.<\/p><\/dd>\nWill syncing slow down my site or my edits?<\/h3><\/dt>\n
Can I recommend courses, listings or other custom post types?<\/h3><\/dt>\n
relaybell_catalog_post_types<\/code> filter, and use\n relaybell_catalog_item_type to send it as a course<\/code> or listing<\/code> (it is an\n article otherwise).<\/p><\/dd>\nWhat does \"Import the last 90 days of orders\" send? Is it safe to run twice?<\/h3><\/dt>\n
How do I send a test notification?<\/h3><\/dt>\n
The test push works, but my visitors never get my posts<\/h3><\/dt>\n
I use a page cache or a CDN \u2014 do I need to do anything?<\/h3><\/dt>\n
relaybell_purge_page_caches<\/code>.)<\/p><\/dd>\nHow does \"Category \u2192 topic\" work?<\/h3><\/dt>\n
tech-news<\/code>. Create those topics in your relaybell dashboard\n(Audience \u2192 Topics) first: a post whose category has no matching topic isn't\npushed. Visitors choose their topics in the box your site opens with\n RelayBell.showPreferences() (for example from a \"Notification settings\" link).<\/p><\/dd>\nThe status panel says my site isn't on HTTPS<\/h3><\/dt>\n
localhost<\/code> for\ndevelopment. Enable HTTPS (most hosts offer a free certificate), and make sure\nboth addresses under Settings \u2192 General<\/strong> start with https:\/\/<\/code>.<\/p><\/dd>\nConnect doesn't work on my server<\/h3><\/dt>\n
Does it support HPOS (custom order tables)?<\/h3><\/dt>\n
custom_order_tables<\/code> compatibility and uses the\nWooCommerce CRUD APIs throughout.<\/p><\/dd>\nWhich hooks\/filters can I use?<\/h3><\/dt>\n
\n
relaybell_external_id<\/code> \u2014 swap the account email for a hashed id. Also applied\nto the customer email sent with WooCommerce events and the past-orders import\n($user<\/code> is null for a guest order).<\/li>\nrelaybell_sdk_init<\/code> \u2014 modify the full SDK init options. For a logged-in\nvisitor the plugin identified, the userHash<\/code> for the externalId<\/code> you return is\nadded afterwards.<\/li>\nrelaybell_user_hash( $external_id )<\/code> (function) \u2014 the userHash<\/code> for an id your\nown code passes to relaybell (e.g. to RelayBell.identify( id, hash )<\/code>), so\nrelaybell accepts it while User ID verification is on.<\/li>\nrelaybell_publish_payload<\/code> \u2014 modify the publish push body.<\/li>\nrelaybell_category_topic<\/code> \u2014 map a post's primary category to a relaybell\ntopic (its slug, or its id).<\/li>\nrelaybell_woo_event_payload<\/code> \u2014 modify any commerce event body before sending.<\/li>\n