Connect Klaviyo push notifications

Connecting Klaviyo has two halves: a public key you paste into Vunda (so your app can talk to Klaviyo), and sending credentials you upload to Klaviyo (so Klaviyo can deliver push to Apple and Google). Vunda never touches your push credentials.

What you will need

• A Klaviyo account.
• An Apple Developer account (for the iOS APNs key).
• A Firebase project (for the Android FCM credential).

Step 1: paste your public key into Vunda

In Vunda, open Integrations, turn on Enable Klaviyo, and paste your key into the Public API key (Site ID) field. It is a short 6-character, case-sensitive code (for example AbC123). Use the public key only, never your private API key.

Step 2: give Klaviyo your sending credentials

This step happens inside Klaviyo and Apple/Google, not in Vunda, so the exact screens are owned by those providers. Verify each step against their current guides (linked below) before you rely on it.

• iOS. In your Apple Developer account, create an APNs authentication key and download the .p8 file. In Klaviyo, go to Settings then Push Notifications, enable the iOS section, and upload the .p8 along with your Key ID, Team ID, and app Bundle ID. (Source: Klaviyo iOS push setup.)
• Android. In Klaviyo's Android push setup, provide your Firebase service-account credential so Klaviyo can send through FCM. Your app build also needs the matching google-services.json from the same Firebase project. (Source: Klaviyo Android push setup.)

Step 3: report each upload in Vunda

Vunda cannot see inside your Klaviyo account (Apple has no API for creating push keys, and Klaviyo has none for reading them), so once each credential is uploaded, tell Vunda. Back in Integrations, open the Klaviyo card and find Push credentials. Click I uploaded the APNs key (.p8) to Klaviyo after the iOS step and I uploaded the FCM credential to Klaviyo after the Android step.

These buttons record your own report; they are not a verification. Before your next build is published, Vunda staff check in Klaviyo that both credentials are in place for your app, and the Publish page lists that check as a Vunda step until it is done. Your keys stay in Klaviyo: nothing is uploaded to Vunda. If you later switch provider or change your public key, the reports reset and you will be asked again.

Choosing when shopper events reach Klaviyo

The Klaviyo card has one more setting, When to send shopper events to Klaviyo, with two options. It decides whether shoppers who decline (or are never asked about) push notifications still show up in Klaviyo. It applies on your next app build, like the rest of the card.

• Only after the shopper accepts push notifications (default). Klaviyo is not started in the app until the shopper says yes to notifications. A shopper who declines, or has not decided yet, produces no Klaviyo profile and no events. This is the privacy-safe setting and needs nothing extra from you.
• Always: Klaviyo receives browsing and cart events for every shopper. Klaviyo starts when the app opens, and product views, add-to-cart, checkout starts, app opens and the signed-in shopper's identity reach Klaviyo for everyone, whatever they said about notifications. Push notifications themselves still need the shopper's permission: nobody is prompted, registered or messaged without it. Choose this only if your privacy notice covers app tracking and you have a lawful basis for it. Vunda does not decide that for you.

Switching from Always back to the default takes effect on the next build too: shoppers who never accepted push stop producing events from that version on. Under the hood the choice ships in the build as EXPO_PUBLIC_KLAVIYO_EVENT_CONSENT_MODE.

After you connect

Publish a new version of your app from the Publish page. Once that build is live, Klaviyo push and your on-device events (product views, add to cart, checkout started) are wired in.