Connect without sharing a private key
Authorize Veya through Klaviyo’s OAuth flow and return to the authenticated Veya workspace to finish connecting. Then choose a saved form and an existing list. Credentials stay on the server. The integration needs a configured Veya OAuth app before live use.
Give campaigns their own destination
A welcome form and a seasonal early-access form can use different lists. A signup keeps the destination selected when it was captured, so changing the form’s list does not reroute already queued signups.
Acceptance is not confirmation
Veya records explicit email consent and queues delivery. Klaviyo processes the subscription job and applies the selected list’s opt-in settings. With double opt-in, the person still needs to confirm. A form success message and a confirmed Klaviyo subscription are different milestones.
Verify one real journey
Use a dedicated test list and an address you control. Submit the form, inspect delivery, complete the confirmation email if required, and check the resulting list membership. Email and mobile collection have separate consent. SMS requires an enabled Klaviyo account and a verified live signup journey before launch.