How to Integrate Privy with Klaviyo

Privy documents a one-way sync from displays to Klaviyo lists, with a separate sync rule for each display. Connecting the accounts does not automatically configure every form, and a Klaviyo segment is not a direct sync destination.

The workflow below follows Privy’s Klaviyo integration guide, checked September 6, 2026. Credential wording in that guide needs clarification before you follow it literally.

Connect the accounts and check the credential type

1. Open Settings → Linked Accounts in Privy.
2. Select Klaviyo from the available integrations.
3. Review the credential fields presented in your account and provide the required credentials before selecting Link Account.
4. Confirm Klaviyo appears among authorized accounts.

Privy’s guide recommends full access across API scopes but calls the credential a public key. Klaviyo’s API-key documentation distinguishes public identifiers from private keys used to access account data. Do not treat those as interchangeable. Confirm Privy’s current required key type and permissions if the prompt is unclear; the reviewed guide does not establish a minimum scope set.

Enter a private credential only into the intended integration configuration, never into a public page snippet or screenshot. Keep the key itself out of your setup notes.

Configure each display’s destination

Open the display’s Settings → Advanced Settings → Sync Integrations, select Klaviyo, configure the list destination and save. Repeat for every display that needs to send signups.

Write down the campaign and selected list name. If you later use a Klaviyo segment, verify its membership rules separately; arrival in a list does not prove a contact satisfies that segment’s conditions.

Check phone numbers before testing SMS-related data

Privy requires E.164 phone formatting for this sync. It documents adding the missing +1 prefix for US and Canadian numbers. Other countries need their country code supplied; Privy says it adds an omitted plus sign.

A formatted phone number and permission to send SMS are different checks. Inspect the destination’s actual subscription state rather than assuming that successful phone-field transfer makes the contact eligible for a message.

Run one traceable signup test

Use a new test address and record the display, source page, selected list and submission time. These are editorial verification steps, not evidence that we executed the integration in a customer account.

A profile arriving does not prove that an automation sent successfully. Keep each checkpoint distinct so a failure in sending does not lead you to unnecessarily reconnect the accounts.

Treat browser identification as a separate setting

Privy also documents Settings → Scripts & Tracking → Other Customizations → Enable Klaviyo Javascript integration. This can identify a captured visitor with a Klaviyo session cookie for abandonment use cases.

Enabling that setting is not an end-to-end test of an abandonment flow. Verify the intended browser interaction and downstream flow behavior in your setup. Avoid counting a saved checkbox as proof of message delivery.

Plan changes to an existing connection

Privy documents disconnecting through the Klaviyo delete control in Linked Accounts. Identify affected displays first and retest their routing after any connection change. Do not assume removal cleans up destination contacts, flows or separately configured browser tracking.

For the fields captured at signup, see Privy Profile Attributes. Compare other supported destinations in Privy integrations.