Turn on Vunda push notifications

Vunda push sends notifications to your app through the Expo push service, the delivery service built into the framework your app runs on. You do not need a Klaviyo or OneSignal account for it. Your app asks each shopper whether they want notifications, and only shoppers who say yes are registered.

Step 1: switch it on

In Vunda, open Integrations, choose the Vunda push card, and turn on Use Vunda push, then save. Your app has one push provider per build, so this replaces Klaviyo or OneSignal if one of them was selected.

Step 2: add your Apple push key

Apple only delivers notifications to iPhones through a push key from your own Apple Developer account, and Apple has no way for Vunda to create one for you. You create it once:

1. Sign in to Apple Developer and open Certificates, Identifiers & Profiles, then Keys.
2. Press +, give the key a name, and tick Apple Push Notifications service (APNs).
3. Choose Continue, then Register, then Download. Apple lets you download the .p8 file only once, so keep it somewhere safe.
4. Note the Key ID shown next to the key, and your Team ID from Membership details.

One key works for every app on your Apple team, so if you already have an APNs key you can reuse it.

Back on the Vunda push card, choose the .p8 file (or paste its contents into Key file contents (.p8)), enter the Key ID and Team ID, and choose Save Apple push key. Vunda stores the key encrypted and never shows it again; you only see its Key ID and Team ID afterwards. On the Publish page, until the key is saved, this step appears as Upload your Apple push key (.p8), Key ID and Team ID on Integrations > Vunda push.

Step 3: let Vunda finish the setup

Everything else is automatic. Vunda puts your Apple push key on your app, and creates the Android push setup (a Firebase app and its Firebase Cloud Messaging credential) for you. On the Publish page these appear as Vunda sets up your Apple push key for Vunda push and Vunda sets up your Firebase (FCM) credential for Vunda push while they are in progress, and disappear once they are done. The Vunda push card shows the status for iPhone and Android; choose Check again to re-run the setup straight away.

If your app already uses your own Firebase project for Google Analytics, Vunda keeps your existing Firebase configuration file and does not replace it. Android push then needs a Firebase Cloud Messaging key from your own project, and Vunda will contact you for it.

Step 4: publish a new build

Vunda push is part of your app itself, so it takes effect on your next published build, not instantly.

Step 5: send yourself a test

Open your published app on your own phone and allow notifications when it asks. Then, back on the Vunda push card, choose Send test notification. It sends one fixed test message to the device that registered most recently, so do it straight after allowing notifications on your phone.

What is stored

When a shopper allows notifications, the app registers a device push token with Vunda. If they are signed in, the token is linked to them through a pseudonymous reference, never their raw customer id. Turning notifications off in the app's own settings removes the token straight away. A token that Apple or Google report as no longer valid is never sent to again, and any token unused for about 270 days is deleted automatically. See the privacy policy for details.