Klaviyo Vol 5: Solving Localised Double Opt-In at Scale

Shopify Markets centralises all international traffic into one Shopify store. From a commerce perspective, that's powerful. From a consent and lifecycle perspective, it creates friction you can't ignore.

Shopify can only sync subscribers into one primary Klaviyo list.

When Shopify syncs subscribers to Klaviyo, everyone, regardless of country or language, goes into one default list. That list can only have one subscription source, one consent experience, and one language for the double opt-in page and email.

This immediately becomes a problem when customers are signing up from different markets expecting communications in their own language.

Market-specific consent requires localised double opt-in.

Markets across Europe don't just prefer localised consent, they often require it. Different languages, sometimes different legal wording, and often different expectations around confirmation. 

Klaviyo won't re-trigger double opt-in for "already subscribed" profiles.

Here’s the real blocker. When a subscriber enters Klaviyo via a single opt-in source, or has already confirmed their subscription, they’re immediately marked as subscribed. If that profile is later moved to another list, Klaviyo won’t re-trigger the list-specific double opt-in email.

The result? Customers were entering a global list with a single-language consent experience, never receiving the correct market-specific double opt-in, and creating compliance risk alongside a broken onboarding experience.

To fix this, we had to stop relying on default platform behaviour and engineer our own consent routing logic.

Enrich customer profiles with market and language data

First, we needed reliable detection. We added custom Shopify properties that get passed to Klaviyo: Market (e.g. BE, DE, FR), and Locale/browsing language (e.g. fr-BE, nl-BE, de-DE). These properties became the foundation for precise segmentation and routing.

Set the global Shopify-synced list to single opt-in.

Because the sync settings only allow one list with a single language to be connected to Shopify consent pages, we intentionally converted the global synced list to single opt-in. This allowed subscribers to enter Klaviyo immediately, avoided sending the wrong-language double opt-in, and gave us control to trigger the correct consent later. This wasn't about bypassing compliance, it was about sequencing it correctly.

Build a list update flow with conditional logic.

Once a subscriber entered the global list, a dedicated List Update Flow took over. The flow reads the Market and Locale properties, routes the subscriber through a detailed conditional split tree, and identifies the exact combination (e.g. BE-FR, BE-NL, DE, FR). When a match is found, the flow sends a webhook.

Use webhooks to override status and trigger the right double opt-in.

The webhook performs the critical step Klaviyo doesn't support natively. It overrides the subscription status and moves the profile into the correct market-specific list. Because that list is configured with its own language, legal copy, and double opt-in settings, the subscriber receives the correct confirmation email, in the correct language, for the correct market.