Klaviyo + Popup Sync: Turning Spin-to-Win Leads Into Email Revenue

Coming soon. Klaviyo, Mailchimp and Omnisend sync is built and in final testing, but it isn’t switchable inside Profiter yet. Everything below describes how it works when it ships. Real-time Google Sheets sync is live on Growth+ today, and CSV export is on every plan.

A shopper spins the wheel, wins a prize, and hands over their email. From that second, a clock is running. The offer is fresh in their mind for maybe a day, maybe an hour. If that lead sits in a spreadsheet until your next weekly export, you’ve already lost the moment that made them want to buy.

That’s the real cost of a CSV-based workflow. The data is fine. The timing is what kills it.

What a CSV export can’t do

A downloaded list is a snapshot. It tells you who spun the wheel last Tuesday, not who’s spinning it right now. By the time you’ve exported it, cleaned it, and uploaded it to your email tool, the shopper has either bought, forgotten, or gone somewhere else. A welcome flow that fires three days after the event it’s welcoming feels like an ad instead.

Klaviyo, Mailchimp, and Omnisend lead sync on Profiter’s Growth+ plan ($29/month) closes that gap. Each lead reaches Klaviyo the moment it’s captured, on whatever schedule the shopper sets rather than the one you remember to keep.

The sync is deliberately fire-and-forget: the spin never waits on a third-party API. If Klaviyo is slow or returns an error, the shopper still gets their prize, and the failure is recorded against the integration for you to see in Settings rather than thrown at the person spinning the wheel.

Exactly which fields arrive in Klaviyo

Worth being precise, because “syncs your leads” hides a lot of variation between apps. A Profiter lead lands as a Klaviyo profile carrying:

Field	What it holds
email	The address the shopper entered, when you ask for one
phone_number	Only when it’s valid E.164 — Klaviyo rejects anything else, so we filter rather than let the profile fail
first_name	When your form collects it
profiter_consent	Whether the shopper actually ticked the consent box, which is never pre-ticked
profiter_source	First-touch acquisition source, as utm:…, referral:…, or direct

Source: the Klaviyo provider in Profiter’s esp/index.ts, verified 28 July 2026.

That profiter_source field is the one merchants tend to underuse. Because it’s captured at first touch rather than at the moment of the spin, it survives a shopper wandering your site before they play. Segment on it and you can see whether the wheel is earning its keep on paid traffic specifically, or only converting people who were already coming to you direct.

Why consent and double opt-in travel with the contact

Syncing consent status alongside the address matters for two separate reasons, and both cost you if you skip them.

The compliance reason is straightforward. Klaviyo and most email providers expect proof that a contact agreed to be emailed. A list built from a manual export, with consent recorded somewhere else or nowhere at all, is a gap that a spam complaint will eventually find.

The deliverability reason hits revenue harder. Inbox providers watch how a sending domain behaves — bounce rates, complaints, engagement on unconfirmed addresses — and that reputation is shared across everything you send. Push a batch of unconfirmed spin-to-win emails into a live flow and you’re gambling with the domain your best customers’ emails depend on. When double opt-in status arrives with the contact, Klaviyo’s segmentation can hold sends back until someone has confirmed.

How do I add a Klaviyo popup to Shopify?

A common point of confusion, and worth separating. Klaviyo ships its own popup forms. Merchants who want spin-to-win specifically tend to run a dedicated popup app alongside it, which gives the two tools distinct jobs:

1. Profiter lives on your storefront, captures the lead, picks the prize server-side, and mints the discount code.
2. Klaviyo receives the lead and runs the email or SMS flows that convert it.

The “integration” is the real-time sync connecting them. You install Profiter on Shopify for the popup, then connect Klaviyo so the leads go to work immediately.

The code is ready before the email is

One source of delay sits outside the sync entirely: how the discount code gets made. Generating a fresh code at the moment someone wins puts a third-party API call between the shopper and their prize.

Profiter mints single-use codes ahead of demand instead. A win claims a code that already exists, and it’s applied through the cart via Shopify Functions, so the discount is waiting at checkout without anyone copying and pasting anything. The shopper has their reward before your welcome email has finished sending.

Measuring whether the flow actually earned anything

A synced flow can look healthy — good open rates, plenty of clicks — while the wheel behind it quietly loses money on discounts. Those are two separate questions, and Profiter answers the second one on every plan, including Free:

Component	Implementation	What it’s for
Holdout bucketing	FNV-1a 32-bit hash of visitor + experiment ID	Keeps a visitor in the same arm across sessions, with no server-side state
Significance	Two-proportion z-test, 95% Wald confidence interval	Says whether the gap between wheel and holdout is real
Split integrity	Chi-square goodness-of-fit at alpha = 0.001	Flags a corrupted test before you draw conclusions from it
Profit	Profit per exposed visitor, from your margin and shipping inputs	Measures the bottom line after the discount was paid for

Source: Profiter’s stats.ts and experiments.ts, verified 28 July 2026.

If the flow converts well but profit per visitor barely beats the holdout, the fix is usually the prize odds rather than the email. The holdout test covers how to read that comparison.

If you’re running a spin-to-win popup and still exporting a spreadsheet into Klaviyo once a week, turning the sync on and retiring the spreadsheet is the whole fix — see the Klaviyo integration for how it works.