Push notifications
Campaigns, audiences, scheduling and the writing assistant; order-status updates, abandoned-cart recovery and the three automations; and connecting your own Firebase project.
Updated September 25, 2026
Open Push. Notifications reach every shopper who installed the app and allowed them. Android delivery goes through Firebase and iPhone delivery goes directly to Apple using the push key you added on the Publish page; the page shows how many devices of each kind it can reach.
The Push notifications add-on is the master switch. Turning it off stops every campaign, order update, automation and stock alert, and any pushes sent through your API keys. Abandoned-cart recovery has its own switch and keeps running.
Send a campaign
- Title, up to 80 characters, and Message, up to 240.
- Opens: the app home, a category, or a product (search your synced catalogue). Scheduled campaigns keep it, and the scheduled list shows where each one opens.
- Audience: Everyone, iPhone and iPad, Android, Has something in their cart, Has ordered before, Has never ordered, or Installed in the last 30 days. Each shows a live count; a zero audience warns before you send.
- Send at: leave empty to send now, or pick a time. Scheduled campaigns appear in a list with a Cancel button.
- Write it for me (Pro): choose what the campaign is about (a promotion, new arrivals, something back in stock, a nudge to come back, or something else), add notes, and get three drafts. Only what you write is used; offers, prices and dates are never invented.
Sending to everyone right now is on every plan. Narrowing the audience and scheduling are Pro.
Best send time appears once your shoppers have opened at least 50 notifications in the last 90 days: a three-hour local window and the share of opens it holds.
Automations
Order-status updates. Always on while Push is on. When an order’s status changes in WooCommerce, the shopper who placed it in the app receives Order #123 — Your order is now processing (or whatever the new status is), once per change.
Abandoned cart recovery (Pro, its own switch). A shopper who leaves items in the cart for 30 minutes gets one nudge: Still thinking it over? Your cart is waiting. Once per cart, never repeated. The card shows how many carts are sitting abandoned right now.
Three recipes (Pro, off by default), each with an editable title and message that is exactly what the shopper receives:
- Thank a first-time buyer. Once, after a shopper’s first order through the app.
- Win back a quiet shopper. After 60 days without an order (7 to 365), and not again for 90 days.
- Recognise a regular. When a shopper reaches three orders (2 to 50).
History
Recent sends lists every send with its type (Campaign, Order update, Cart recovery, Thank-you, Win-back, Regular), the message, how many devices it reached, and the time. Opens are tracked per campaign and feed the open rate on the Analytics page.
Shoppers can turn notifications off on the Account screen. They are then left out of every send, and the reach counts on this page already exclude them.
Your own Firebase project (Pro and Agency, optional)
Push works with no setup on StoreToNative’s shared Firebase project. Connecting your own project means the push credentials and Firebase’s delivery analytics belong to you.
- Create a free Firebase project, or reuse one.
- In Google Cloud IAM for that project, grant the service-account address shown on the card the Firebase Admin role.
- Paste the project id and press Connect. The grant is checked before saving.
The card reads Connected, Access lost if the grant disappears, or Optional. Disconnecting returns the app to the shared project.
Still stuck? Open a ticket from Support in the console, or contact us.