Active subscribers (silently)
Every browser that already granted push permission to your origin re-subscribes silently on its next visit. No prompt, no decision, no churn. The user never knows the cutover happened.
Migration
Migrate from Webpushr to ReachBell in 5 minutes.
Webpushr keeps VAPID keys locked vendor-side — and that’s usually where switches stall. ReachBell’s silent re-subscribe rolls over your active list without prompting a single user, then adds email and automations on top.
Zero subscriber loss. No re-prompt required.
Webpushr won’t hand over your VAPID keys. ReachBell’s SDK doesn’t need them. Silent re-subscribe leverages the existing push permission on your origin to bind every active browser to your new ReachBell project — quietly, on the next page view, with no UI surface. Your users notice nothing. You keep the list.
Three steps
Silent. Background. Done.
No user-facing change, no permission UI, no lost list. The cutover happens in JavaScript.
1. Configure silent re-subscribe
Webpushr manages VAPID keys server-side and rarely exposes them to customers. Instead of trying to extract them, set up ReachBell's silent re-subscribe mode — our SDK detects the existing push permission on your origin and re-binds the browser to your new project on its next visit. No prompt. No banner.
2. Replace the SDK script
Remove the cdn.webpushr.com script and the webpushr-sw.js service worker from your site root. Install the ReachBell three-line snippet and /reachbell-sw.js in their place. The push permission stays valid; only the destination changes.
3. Verify re-subscribe rollover
Open ReachBell → Project → Verification. As real visitors hit your site, you'll watch subscribers come online live. Most sites recover 70-80% of active subscribers within a week, 90%+ within two — without a single visible prompt.
The SDK swap
One script out, one script in.
The only code change on your site. Silent re-subscribe handles the rest.
index.html · <head>
- <script>
- (function(w,d,s,id){
- w.webpushr=w.webpushr||function(){(w.webpushr.q=w.webpushr.q||[]).push(arguments)};
- var js,fjs=d.getElementsByTagName(s)[0];
- js=d.createElement(s); js.id=id; js.async=1;
- js.src="https://cdn.webpushr.com/app.min.js";
- fjs.parentNode.insertBefore(js,fjs);
- }(window,document,"script","webpushr-jssdk"));
- webpushr("setup",{ key: "BO..." });
- </script>
+ <script src="https://cdn.reachbell.com/sdk/v1/reachbell.js" defer></script>
+ <script>
+ window.ReachBell = window.ReachBell || [];
+ ReachBell.push(rb => rb.init({
+ projectId: "prj_...",
+ silentResubscribe: true // takes over the existing permission
+ }));
+ </script>Drop webpushr-sw.js from your site root and replace with reachbell-sw.js — browsers re-register on next visit.
What you keep
All of it. Quietly.
Active subscribers, segments, deliverability, history — nothing breaks, nothing prompts.
CSV-exported audience data
Webpushr's Subscriber Insights → Export ships tags, segment names, browser, geo, and last-seen — import directly into ReachBell's subscriber tables.
Welcome and trigger flows
Welcome notifications, abandoned-cart triggers, and time-zone scheduled campaigns translate node-for-node into ReachBell's automation builder.
Deliverability and CTR
Browser-side reputation is tied to the origin, not the SDK vendor. Click-through rate carries straight over the moment the new SDK loads.
What you gain
Three things Webpushr won’t ship.
Stop bolting on tools around your push provider. ReachBell consolidates the stack.
One tool, three channels
Webpushr is push-only. ReachBell adds email campaigns and transactional sends on AWS SES — same dashboard, same segments, one bill.
Real automations on Growth
Visual journey builder with branches, waits, and exits — included on the ₹2,999/month plan. Webpushr's flows top out at sequence-style nudges.
INR pricing with GST invoice
Webpushr bills in USD. ReachBell bills in rupees via Cashfree (UPI, cards, net banking) and issues a compliant GST invoice your accountant will accept.
Total engineering time for the average Webpushr cutover: under 3 hours. Reach sales@reachbell.com
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Webpushr won't give me VAPID keys. Will I lose my list?
No. Webpushr's architecture treats VAPID keys as vendor-managed, so they're rarely retrievable — that's actually the design pattern most modern push platforms use. ReachBell handles this with silent re-subscribe: our SDK detects an existing push permission on your origin and creates a fresh subscription against our VAPID pair, in the background, with no permission dialog. The user sees nothing; your active list rolls into ReachBell as visitors come back to the site.
How fast does silent re-subscribe recover my list?
Recovery depends on visit frequency. For an e-commerce site with daily visitors, we typically see 70-80% of the active list re-subscribed within one week and 90%+ within two. Subscribers who haven't visited in 60+ days were likely dormant anyway — Webpushr would have shown them as "active" but they weren't opening pushes.
How do I export my Webpushr data?
In Webpushr, go to Audience → Subscriber Insights → Export. You get a CSV with subscriber IDs, segment memberships, tags, browser/OS, geolocation, and last-active timestamp. Upload it via the ReachBell dashboard's subscriber importer or POST it to /v1/subscribers/import. We rebuild your saved segments from the tag columns automatically.
Can I run Webpushr and ReachBell in parallel during the rollover?
Yes — keep both scripts on the page for a week and you'll see ReachBell's subscriber count climb as Webpushr's holds steady. Once ReachBell's count plateaus, remove the cdn.webpushr.com script and delete webpushr-sw.js from your site root. Browsers will unregister the stale service worker on the next visit.
Do I get migration help?
Every paid plan includes free migration assistance. Email sales@reachbell.com with your Webpushr workspace and a sample CSV — we'll handle the import, rebuild your automation flows in the journey designer, and ship a verification call. Most Webpushr cutovers complete in under three hours of total engineering time.