Troubleshooting
Fix common Pushrr setup issues with Shopify installation, browser permissions, subscribers, campaigns, and abandoned cart recovery.
Troubleshooting
Use this guide when Pushrr setup or sending does not behave as expected.
Shopify install button shows a store-domain error
Pushrr could not determine the Shopify store domain from the saved site URL.
Fix:
- Open site settings.
- Enter the real Shopify storefront URL.
- Save settings.
- Try Install Shopify app again.
Browser permission prompt does not appear
Possible causes:
- Notifications are blocked for the site in browser settings.
- The browser does not support Web Push.
- The user is on iOS Safari without adding the site to the home screen.
- The prompt was dismissed and is waiting for the next eligible prompt window.
Fix:
- Test in Chrome or Edge first.
- Reset notification permission for the storefront.
- Reload the storefront.
- Try from a new browser profile if needed.
Subscriber does not appear
Check:
- The visitor clicked Allow, not Not now.
- The storefront URL matches the saved Pushrr site URL.
- The Shopify connection is active.
- The browser request was not blocked by extensions or privacy tools.
Campaign does not send
Check:
- The site has active subscribers.
- The selected audience matches at least one active subscriber.
- The workspace is approved and within plan limits.
- The notification destination URL is valid.
- The subscriber endpoints are still reachable.
Abandoned cart notification does not send
Check:
- Shopify is connected.
- The automation workflow is enabled.
- The automation step is enabled.
- The shopper is an active push subscriber.
- The cart or checkout was not recovered before the send time.
- The send delay has elapsed.
Existing subscribers stopped receiving pushes
Do not rotate web push keys for a live site. Contact support before changing low-level push configuration. Pushrr is designed to keep VAPID keys stable per website to avoid orphaning existing browser subscriptions.
Contact support
Include the store domain, workspace email, affected campaign or automation name, browser, device, and approximate time of the issue.