top of page
7 days ago
9 min read

Updated: 7 days ago

Klaviyo Setup for Shopify: List Growth and Your First Ecommerce Flows


By Trayan Hristov · Thrivelia · Updated 15 November 2026


Klaviyo Shopify setup: connect the store, grow the list and test the first ecommerce flows.

A Klaviyo account is not ready because a pop-up appears and three flows say Live. It is ready when a shopper can subscribe, receive the promised message, buy, and stop receiving reminders that no longer make sense.


Here is the setup order I would use for a Shopify ecommerce brand. It starts with email and the customer data needed for the first journeys. Add SMS and more complex segmentation once that path works. If you are replacing an existing email platform, use a controlled migration checklist as well.


These are practical setup steps with recommended test cases. Exact menu labels and available features may differ by account. The linked platform instructions were checked on 15 November 2026. Use the full Klaviyo account for this walkthrough; Shopify's embedded Klaviyo experience may present a shorter setup.


Step 1: Confirm the account and existing sends


Check whether the store already has a Klaviyo account before creating another one. Confirm the store domain, business details, timezone, default currency and the people who need access. Keep ownership with the business rather than one contractor's personal login.


Make a short register of current sends: Shopify order confirmations, shipping updates, abandoned checkout, newsletter forms and any existing email app. Record which system sends each message. Do not turn off order confirmations as a side effect of changing promotional flows.


Decide who owns the storefront, DNS, subscriber policy, creative and final approval. A founder may own several of those roles, but each decision still needs an owner. If an outside implementer is involved, give them an agreed scope and a rollback contact.


Step 2: Connect Shopify and verify real data


Use Klaviyo's Shopify integration and complete the store authorisation. In its subscriber sync settings, select the intended email subscriber list. Enable the Klaviyo app embed in the published Shopify theme and save the theme. These are core steps in Klaviyo's Shopify integration instructions.


Then inspect a controlled test profile and order. Check that the email, products, variant, currency and order value correspond to the store. Open a product as an identifiable test shopper and examine the resulting activity. If you rely on an Added to Cart event, verify that exact event too.


Tracking can depend on the store's privacy settings and the shopper's consent. Do not assume every anonymous visit can trigger a personalised email. After changing themes, retest the app embed rather than assuming the previous theme's configuration carried over.


Step 3: Set up the sending identity before increasing volume


Choose a recognisable sender name, a reply address someone monitors and the brand's sending domain. In Klaviyo's domain settings, start the branded sending-domain setup, choose the appropriate send type and give the generated DNS records to the domain owner. Verify and activate the configuration after the records resolve. Follow the current sending-domain instructions, including the DMARC guidance.


Use the records generated for your account. Do not paste example DNS values from a blog into a live domain. If a record conflicts with an existing service, investigate with the domain owner before replacing it.


Successful authentication does not establish that a whole historical database is suitable for a launch campaign. Start with a controlled sending plan and monitor delivery and subscriber responses. If you are diagnosing an existing problem, use our deliverability guide.


Step 4: Choose the main email list and opt-in method


Give your main email subscriber list a clear internal name. Review the opt-in setting and confirmation pages. Route the intended website, footer and checkout subscriptions into the welcome path; do not assume those sources all use the same destination.


Klaviyo's Shopify subscriber-sync guide explains the list handoff and confirmation step. With double opt-in, a person needs to complete confirmation before they join the list and enter its welcome flow. Test this with a fresh address and an accessible inbox.


Keep email, SMS and account registration distinct. A purchase or store account does not automatically mean the customer subscribed to marketing. Preserve existing consent and suppression information when moving data between tools.


Step 5: Publish one useful signup form


In Klaviyo, open Website, then Sign-up forms and Create form. Select a web template, name it and choose the intended subscriber list. Edit the content, targeting and success state, then preview on the storefront and a phone before publishing. Klaviyo's form setup guide documents the current builder.


Start with a clear reason to subscribe. For example, early access to a specific collection is more concrete than “join our community.” If you offer a discount, state the eligibility and make sure the promise matches the checkout rules. Use our welcome-offer testing guide when deciding between a discount, gift or shipping incentive.


Use a mobile layout that fits the screen with the keyboard open. Test the close control on every variation and step. Check that the form does not block a customer from browsing or paying. Choose targeting and redisplay settings deliberately; do not make “show immediately on every visit” the default answer.


Make the success message accurate. With double opt-in, explain the confirmation step. With a displayed coupon, check its expiry, product exclusions and application in checkout. A successful form submission is only the start of the test.


Step 6: Build the welcome flow around the signup promise


In Flows, create or select a welcome series and choose the same list used for subscriber entry. Review the trigger, sender details and every message before making it live. A list-triggered welcome flow normally admits a person once. See Klaviyo's welcome-series instructions for the builder steps.


For a simple first release, I would write three different jobs. The first email delivers the promised offer or resource. The next answers a buying question. A later message helps the subscriber choose a product, using proof that is relevant to that decision. Timing is a test decision based on your buying cycle, not a universal template.


Decide what changes after a purchase. A first-order coupon reminder should stop being the main message once the person buys. Existing customers joining through another source may need a different introduction. Our welcome-flow guide develops those content and routing decisions.


Step 7: Add checkout recovery with a purchase exclusion


Create a checkout recovery flow using the actual checkout event supplied by your Shopify integration. Klaviyo commonly labels this Started Checkout; select the event from the correct integration and verify it on a test profile. Add the profile filter for Placed Order zero times since starting the flow. Klaviyo's abandoned-cart guide explains why this continuing check matters.


Set a delay that gives the shopper time to finish without a reminder. Preview with a real test event and inspect the item, variant, price and return-to-checkout link. Then place the order before the next message and check that the promotion is skipped.


Review Shopify's existing recovery emails before launch. Choose which system owns that recovery moment and prevent duplicate reminders. Use our Shopify and Klaviyo recovery guide for the coordination. Cart activity and checkout activity are separate events; expand into another recovery flow only after defining how they exclude one another.


Step 8: Add a post-purchase journey that helps product use


Use the order or fulfilment milestone that matches the message's purpose. Klaviyo's post-purchase guide shows an order-triggered starting point. For instructions that assume the parcel has arrived, connect the timing to a reliable delivery signal or a deliberately chosen delay rather than pretending order placement equals product use.


Begin with the customer's next practical question. Footwear buyers may need fit and exchange help. A skincare customer may need a usage routine. A gift buyer may need help passing instructions to the recipient. Keep service updates and marketing eligibility appropriate to the actual message.


Before a cross-sell, check whether the suggested item was already purchased and whether there is an unresolved issue. Measure the first-to-second purchase rate over a suitable period. An order confirmation being delivered does not establish that retention improved.


Step 9: Add browse recovery and social capture after the basics work


Browse recovery needs identifiable product activity and rules that defer to cart, checkout and purchase states. Keep it behind the core journeys until those events are trustworthy. Our browse-abandonment guide covers that hierarchy.


For Instagram traffic, choose either native Klaviyo subscriber capture or a defined ManyChat journey. The ManyChat list-growth guide covers the conversation, and the integration guide covers the subscription handoff. Do not add another acquisition route until it can reach the correct welcome path.


Step 10: Run the launch test and monitor it afterwards


Complete the full journey on mobile and desktop. Subscribe with a new test identity, finish confirmation if required, inspect list entry and receive the welcome. Start checkout, then complete a purchase and verify that recovery stops. Test an existing subscriber and an unsubscribed profile as separate cases.


Keep screenshots of each form state, the expected flow decisions and the test results. Agree who can stop a send if an event fails. After launch, inspect real entrant counts, skips, delivered messages, broken links and customer replies. Repeat the important checks after a theme change, integration reconnect or major flow edit.


For reporting, separate form views, valid submissions, confirmed new subscribers, delivered welcome emails and buyers. State the period and attribution setting for any revenue number. Compare store outcomes as well as the email platform's claims. Our flow-monitoring guide is the next operating step.


Advanced Shopify setup: prove the account under changing customer states


The basic setup establishes the core journey. The next level is deciding what happens when a customer qualifies for several messages or the data changes after entry.


Situation

Decision to specify

Test before release

Browse becomes checkout

Checkout recovery takes precedence

Product reminder does not compete with checkout help

Checkout becomes purchase

Acquisition recovery stops

Placed Order excludes the next recovery send

Customer buys another item

Recommendation is reconsidered

Already-owned items are excluded where data supports it

Subscription becomes active

One-time replenishment is reassessed

Customer is not asked to duplicate a scheduled shipment

Support issue stays open

Promotions follow the agreed service policy

Escalated customer does not receive an insensitive upsell

Required property is missing

Use a safe general route

No guessed claim or broken personalisation


These are recommended decisions, not a list of controls automatically enabled by Shopify. Each rule depends on a reliable event or property and an implementation that can use it. If the signal does not exist, name the gap and adjust the message rather than pretending the exclusion works.


Use event examples as an implementation contract


Keep samples for a single-item order, multi-item order, changed variant, discounted basket and the relevant cancellation or refund states. Record which source supplies each field and which flow uses it. Test product links, images, quantities and currency against those examples.


Keep current customer state separate from the event snapshot. The checkout event describes the basket then; a profile property may describe the customer now. Use each deliberately. A later field update can change a recommendation without changing the original event.


Coordinate frequency across the whole programme


Count what one shopper can receive from flows, campaigns and SMS in the same period. Set message priorities and review the platform's send controls for each journey. A time-sensitive promised resource, a service message and an optional promotion have different jobs.


Do not apply one skip rule to everything and assume it solves the experience. Test the person who subscribes, browses, starts checkout and purchases on a campaign day. Record which messages should send, which should wait and which should stop.


Run an experiment that can change the next build


After the account is reliable, choose one decision: offer, product advice, timing or recommendation. Define the assigned audience, primary outcome, observation window and costs. Where practical, keep assignment stable and avoid changing surrounding campaigns differently between groups.


For a post-purchase test, compare retained contribution and equal-age second-purchase outcomes, not only clicks. Keep the no-purchase and no-open customers in their assigned groups when analysing the treatment. With small samples, report uncertainty and continue collecting evidence rather than declaring a confident winner.


Use the Alia setup guide when acquisition has multiple destinations, and the Hiro measurement guide when reporting views disagree. The monthly operating standard explains how to maintain the account after setup.


Get help with the complete path


Thrivelia connects the customer analysis, signup offer, creative, implementation and QA within an agreed scope. If the account is already live, start with the Klaviyo audit checklist so the team fixes the largest gaps first. To discuss the build, apply to work with us with your store and current setup.


Setup questions


Which Klaviyo flows should an ecommerce store build first?


Start with a working welcome, checkout recovery and a useful post-purchase journey, after confirming the data and subscriber route. Add browse, replenishment and other journeys when you can define their eligibility, timing and relationship to existing messages.


Why does the pop-up work but the welcome email never arrive?


Check confirmation, destination list, trigger, previous flow entry and message status. A visible form does not prove that the person became an eligible subscriber or entered the intended flow.


Do I need ManyChat to grow a Klaviyo list?


No. Website forms, checkout subscriptions and Klaviyo's native Instagram capture can provide routes into the list. Consider ManyChat when a defined conversation need justifies another tool and you can verify its subscription handoff.


 
 
 

Recent Posts

See All

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page