Privy lists integrations across stores, email, SMS, automation, analytics, help desk, reviews, loyalty, list growth and subscriptions. Use the directory to choose a route, then verify identifiers, consent, fields, duplicates, follow-up and failures in the actual accounts.
Vendor documentation · checked 2026-09-06
Choose the connection for your workflow, then verify what reaches the destination. These are source-based findings; the checks below are our evaluation guidance, not hands-on test results.
The directory lists Shopify, BigCommerce and Wix for store data plus Squarespace, Weebly and WordPress.org for displays and forms.
Privy lists email and phone sync to both; it specifically names custom properties for Klaviyo.
The directory lists phone-number and SMS-consent sync to external SMS providers.
Privy describes Alia contacts, discounts and mini-quiz responses syncing into Privy.
Privy describes routing SMS conversations into the Gorgias helpdesk inbox.
The directory lists subscription events and loyalty or referral data for segmentation, personalization and Flows.
Privy lists post-review messaging and reviewer engagement workflows.
The directory lists signup and display tracking in Google Analytics plus contact creation and update automation through Zapier.
Suggested setup checks
A provider name is only the starting point. Prove the required record, fields and follow-up in the actual accounts.
Record which platform captures consent, stores the primary contact and sends each welcome or support message.
List email, phone, consent, list, quiz, discount, loyalty and subscription fields with their destination names.
Check create, update, duplicate and suppression behavior with controlled contacts.
Confirm the intended Flow, campaign, review message or support conversation starts once.
Create a safe validation failure and identify where it appears, who owns it and how it is retried.
6 of 6 guides available
Install Privy on Wix, distinguish app installation from form placement, and verify visitor consent, mobile layout and signup delivery.
Connect Privy to Postscript, choose each display’s keyword, and verify subscriber arrival and the intended follow-up with a controlled test.
Connect Smile.io to Privy, inspect imported loyalty fields, configure signup rewards, and test member targeting and personalized content.
Connect Privy to Attentive with a Source ID, configure the required phone field, and verify subscription channels and custom-field transfer.
Connect Privy to a Klaviyo list, review the API-key documentation discrepancy, and verify contact fields, phone formatting and follow-up behavior.
Connect Privy to Mailchimp, configure each display’s sync rule, and verify audience, required fields and opt-in status with a test signup.
Questions before you decide
The current directory covers analytics, automation, ecommerce, email, help desk, list growth, reviews, loyalty, SMS and subscriptions. Named providers include Google Analytics, Zapier, Shopify, BigCommerce, Wix, Klaviyo, Mailchimp, Gorgias, Alia, Judge.me, Junip, Smile, Rivo, Yotpo, Attentive, Emotive, Postscript and Recharge.
Privy describes Alia contacts, discounts and mini-quiz responses syncing into Privy. Inspect those properties and the discount on a test contact before using them in a segment or Flow.
Privy's directory specifically names email addresses, phone numbers and custom properties for Klaviyo. Verify exact field names, consent, list membership and update behavior with fresh and existing test profiles.
It routes Privy SMS conversations into the Gorgias helpdesk so a support team can reply there. Test an incoming conversation and ownership of the reply; this is different from syncing a marketing contact.
Optimizely's guide says to copy the ODP Tracker ID, link the Zaius account in Privy, then create a campaign automation rule. It names email, first name and last name and says additional form fields can match ODP fields.
Treat overlapping capture and follow-up as a conflict risk. Postscript's current setup guide should control the connection steps; document which platform collects consent and sends each message, then test a fresh phone number before launch.
Test a fresh record, an existing record and a safe validation failure. Inspect identifiers, consent, list or audience membership, custom fields, automation entry, duplicates, timestamps and failure visibility in every destination.
