Checkout Champ and Klaviyo: Setup, Events and the Flows to Build

Checkout Champ sits between your store and your customer at the most valuable moment in the funnel. If your email platform can’t see what happens there, your abandoned checkout, post-purchase and subscription flows are running blind. This guide covers how the Klaviyo integration works, the settings that matter, and the flows to build on top of it.

We’re an official partner of both Checkout Champ and Klaviyo, and this is the setup we run for clients. Every event name and setting below is from Checkout Champ’s help centre, checked in September 2026. If you’re still deciding whether Checkout Champ is right for you, start with our Checkout Champ review.

---

How the integration works

Checkout Champ’s Klaviyo plugin sends data to Klaviyo server-side, from Checkout Champ’s CRM rather than from the shopper’s browser. That matters because server-side events aren’t blocked by ad blockers or lost when a buyer closes the tab mid-upsell.

It does three things:

1. Adds customers to Klaviyo lists, using campaign routes you set up (each Checkout Champ campaign maps to a Klaviyo list).
2. Updates the Klaviyo profile with name, email, phone, billing and shipping address, consent status, and order details.
3. Sends events (Klaviyo calls them metrics) that trigger and filter your flows.

The seven events Checkout Champ sends

Event	When it fires	Use it for
Started Checkout	A checkout page loads with products in the cart	Abandoned checkout flow
Placed Order	An order is placed (initial sales by default)	Post-purchase flows, flow exits, segments
Ordered Product	Alongside Placed Order, one per item	Product-specific cross-sell and replenishment
Fulfilled Order	The shipment record is marked shipped	Shipping and delivery emails, review timing
Cancelled Order	An order is cancelled in the CRM	Suppress from post-purchase and review requests
Refunded Order	A refund is processed	Suppress, and exclude from win-back offers
Subscription Restarted	A subscription is restarted	Re-onboarding for returning subscribers

Source: Checkout Champ Help Center, Klaviyo plugin, September 2026.

---

Setting it up

In the Checkout Champ CRM:

1. Go to Admin → Plugins → Email Service Providers and activate Klaviyo.
2. Enter your Klaviyo private API key (it starts with pk_) and the phoneCode value the plugin asks for.
3. Click the blue Edit icon to open the advanced settings.
4. Use the green + Route button to map each Checkout Champ campaign to a Klaviyo list.

The form code you download from each campaign’s Landing Page section contains Klaviyo’s StartedCheckout script, which is what sends partial orders to Klaviyo. If you add Klaviyo after the form code is already on your site, download the form code package again and deploy the new config file, or partials won’t reach Klaviyo.

Create a dedicated private API key in Klaviyo for Checkout Champ rather than reusing one from another app, so you can revoke it on its own if you ever need to.

---

The settings that matter

The plugin has a long list of toggles. These are the ones that change how your flows behave:

• includeSalesUrl. Turn this on. It sends the cart URL with Started Checkout, which is what lets an abandoned checkout email link the buyer straight back to their cart.
• Send Placed Order Event For Successful Rebills. Off by default, which means Placed Order only fires for initial sales. Turn it on if you want subscription rebills in Klaviyo revenue reporting and segments. If you do, add a filter to post-purchase flows so a monthly rebill doesn’t restart the new-customer welcome sequence.
• Use Subscribe Profiles API. Subscribes customers through Klaviyo’s subscription API, which respects double opt-in on lists that require it. Single opt-in lists subscribe directly.
• Only Send Events For Route Campaigns. Limits events to campaigns you’ve routed. Useful when one CRM runs several brands, and a common reason a new funnel sends nothing.
• Use Email Address as the Customer Profile ID. Turn this on. Unchecked, Checkout Champ uses the order session ID as the Klaviyo profile ID instead of the email, which makes it harder to keep one profile per customer when the same buyer also arrives from Shopify, forms or other apps.
• sendCustomFields, sendCoupon, sendPaymentGatewayInfo. Extra profile and order data. Coupon data is worth sending: it lets you exclude discount-code buyers from full-price VIP segments.
• Do Not Send [event]. Per-event off switches. Use them to avoid duplicates (next section).

---

Watch for double-counted orders

If Checkout Champ sits on top of a Shopify store and Klaviyo is also connected to Shopify, check whether the same order reaches Klaviyo twice: once from Checkout Champ and once from Shopify. Two Placed Order events for one purchase inflate attributed revenue, can send two order confirmations, and can trigger post-purchase flows twice.

How to check: open a recent test order’s Klaviyo profile and look at the activity feed. If you see two Placed Order events a few seconds apart, decide which source owns orders. Then either switch off the duplicate in Checkout Champ with the Do Not Send settings, or build your flows on one source’s metric only. Our guide to email revenue attribution in Klaviyo covers why double-counting quietly breaks reporting.

---

Partials, leads and abandoned checkout

Checkout Champ’s CRM records two kinds of incomplete checkout:

• Partials: abandoned checkouts that contain products
• Leads: abandoned checkouts with no products (someone entered details but the cart was empty)

On its reports, leads show as partials. For email, the difference matters: a partial has a product to remind them about, a lead doesn’t. Started Checkout only fires when a checkout page loads with products in the cart, so leads won’t enter a cart flow. If they reach Klaviyo through a list, send them your welcome series, not a cart reminder.

Partials reach Klaviyo through the StartedCheckout script in the funnel’s form code. Campaign routes can also route customers by type, but Checkout Champ’s docs say to omit the “Partial” customer type routings when the form-code script is running, so the same partial isn’t sent twice.

Klaviyo can only email a profile it can identify. So an abandoned checkout flow reaches people who typed an email or phone before leaving, or who were already known to Klaviyo in that browser. Put the email field first in the checkout, and the phone field with SMS consent right after it. That one layout change decides how big your partials list is.

As Pete put it on the Checkout Champ podcast, partials aren’t lost buyers. They’re people whose reason to buy hasn’t arrived yet. The flow’s job is to give them one.

---

The flows to build on Checkout Champ data

1. Abandoned checkout (trigger: Started Checkout)

Three emails and, with consent, one SMS:

• Email 1 at 1 hour. A plain reminder with the cart link (from includeSalesUrl) and the product image. No discount.
• SMS at 4 hours, only to profiles with SMS consent.
• Email 2 at 24 hours. Handle the likely objection for your category: shipping time, guarantee, ingredients, sizing.
• Email 3 at 48 to 72 hours. Your offer, if you use one, with a real deadline.

Flow filter: Placed Order zero times since starting this flow. Timing detail is in our abandoned cart timing guide, and the full structure is on our abandoned cart flow page.

2. Post-purchase (trigger: Placed Order, initial sales only)

Order confirmation stays transactional. The flow starts after it: how to use the product, what to expect and when, then a cross-sell built on Ordered Product data. If buyers took a one-click upsell, don’t pitch it again. See our post-purchase flow guide and cross-sell and upsell emails.

3. Shipping and delivery (trigger: Fulfilled Order)

Use Fulfilled Order to time “it’s on its way” and “how’s it going?” emails. Time review requests from fulfilment rather than from purchase, so nobody gets asked to review something they haven’t received.

4. Subscriptions (triggers: rebill Placed Order, Subscription Restarted)

If you’ve turned on rebill events, send a light pre-rebill reminder and a usage tip rather than a sales pitch. Use Subscription Restarted to welcome returning subscribers back without putting them through the new-customer sequence. More in subscription retention.

5. Suppression (Cancelled Order, Refunded Order)

Add both as flow filters on post-purchase, review request and VIP flows. Someone who just asked for a refund shouldn’t get “loving your new order?” the next day, or a win-back discount a month later.

---

SMS and WhatsApp consent

The Klaviyo plugin can pass SMS consent. When the order or lead carries contactOptIn, the customer can be subscribed to SMS in Klaviyo, as long as phone export is enabled. Phone numbers are formatted with a country code from the billing address, so check international orders format correctly. There’s also a WhatsApp consent collection option.

Consent wording on the checkout has to meet SMS rules in each country you ship to. Our SMS compliance guide covers TCPA and 10DLC in the US and the rules elsewhere.

---

Setup checklist

• Klaviyo plugin active with a dedicated pk_ private key
• Every live campaign routed to the right Klaviyo list
• includeSalesUrl on
• Decision made on rebill events, with post-purchase filters to match
• Test order checked in Klaviyo for duplicate Placed Order events
• Form code redeployed if Klaviyo was added after funnels went live
• Use Email Address as the Customer Profile ID on
• No “Partial” customer type routes while the StartedCheckout script is running
• Email field first in the checkout, SMS consent after the phone field
• Abandoned checkout, post-purchase, shipping and suppression flows live

If you want this built for you, or checked against what you already have running, book a free audit. We’ll go through the integration settings, the flows and the reporting, and send you the fixes in writing.

---

Sources

• Checkout Champ Help Center, Klaviyo plugin (setup, events, settings, consent; September 2026)
• Checkout Champ Help Center, Postback Export Profiles (partials and leads)
• Checkout Champ Help Center, Analytics Definitions