Klaviyo
Give your email and SMS traffic its own optimization stream and reuse Luria's winning copy in your flows, with nothing to install.
Email and SMS visitors already know you. They opened your message, they clicked on purpose, and they often arrive with a specific offer in mind. A page tuned for cold Meta traffic is the wrong page for them. Luria gives Klaviyo traffic its own stream, and all it needs is the UTM tags Klaviyo can already add for you.
What you get
- A separate optimization stream for Klaviyo traffic. Luria recognizes
utm_source=klaviyoand learns what your subscribers respond to, independent of paid and organic. See Traffic sources. - Winning copy you can reuse. Every headline and angle Luria proves on your site is stored in your Brand Brain. Lift the winners into your flows and campaigns.
- No conflict. Klaviyo's onsite tracking, forms, and pop-ups keep working untouched. Luria reads its own events and never fires or blocks Klaviyo's.
There is no connector to set up and nothing to install in Klaviyo.
Setup: make sure Klaviyo tags its links
Klaviyo can append UTM parameters to every link in your emails and SMS automatically. Turn it on once and every send is covered.
Step 1: Turn on UTM tracking in Klaviyo
In Klaviyo, go to Settings > Other > UTM tracking (older accounts: Account > Settings > UTM Tracking) and switch it on. Keep the default values: Klaviyo sets utm_source=klaviyo, utm_medium=email (or sms), and fills utm_campaign with the campaign or flow name.
If you prefer to set UTMs per campaign or per flow message, that works too, as long as utm_source stays klaviyo.
Step 2: Check Luria sees it
Send yourself a test email, click a product link, then open the Luria dashboard. Klaviyo should appear under Traffic within a few minutes. If it doesn't, open the link you clicked and confirm utm_source=klaviyo is in the address bar.
Flows vs campaigns
Klaviyo's default UTM values put the flow or campaign name in utm_campaign. Luria uses that to tell a welcome flow from an abandoned cart flow from a Black Friday blast, so high-volume flows can earn their own page versions over time, the same way an ad set can. See Ad-level pages.
Reusing winners in your flows
Luria tests headlines, subheads, CTAs, and proof on your site. Once something wins at high confidence, it shows up in your Brand Brain as proven language. That's a gift for email:
- In the Luria dashboard, open Brand Brain > Proven copy.
- Filter to the page or source you care about (for example, "Klaviyo traffic, product page").
- Copy the winning headline or angle into your flow or campaign.
Why it works: the language already beat its alternatives with your real visitors, on your real pages, in your voice. It's the opposite of guessing a subject line. This is a manual copy-and-paste today; there is no automatic sync into Klaviyo.
What Luria does not touch
| Klaviyo feature | Effect of Luria |
|---|---|
| Onsite tracking (Active on Site, Viewed Product) | None. Klaviyo's script runs as usual. |
| Sign-up forms and pop-ups | None. Luria doesn't move, hide, or restyle them. |
| Klaviyo's attribution and revenue reporting | None. Klaviyo still counts what it counts. |
| Shopify integration, order sync | None. |
Because Luria never changes Klaviyo's conversion tracking, the revenue Klaviyo attributes to a flow and the lift Luria reports for Klaviyo traffic are two different measurements and will not match. That's normal; see Google Analytics for why tools count differently.
Good to know
- SMS links often go through a short-link domain. Klaviyo's UTM setting still applies to them; the final landing URL carries the parameters.
- If a flow sends visitors straight to checkout or to a cart link, Luria sees little of that session and optimizes less for it. Sending to a product or landing page gives Luria more to work with.
- Subscriber traffic converts at a higher rate than cold traffic, so the "lift" Luria reports for Klaviyo is measured against your already-good email baseline. Expect it to be smaller in percentage terms than your paid lift, and still worth having.