{"id":95062,"date":"2026-11-09T13:06:31","date_gmt":"2026-11-09T09:36:31","guid":{"rendered":"https:\/\/pixflow.net\/blog\/?p=95062"},"modified":"2026-11-09T13:06:31","modified_gmt":"2026-11-09T09:36:31","slug":"checkout-champ-klaviyo-subscription-emails","status":"publish","type":"post","link":"https:\/\/pixflow.net\/blog\/checkout-champ-klaviyo-subscription-emails\/","title":{"rendered":"Checkout Champ subscriptions and Klaviyo: how to connect them, and the 5 emails that stop cancellations"},"content":{"rendered":"<div class=\"wpb-content-wrapper\" id=\"wpb-content-root\"><p>[vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;.vc_custom_1794147560442{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">Checkout Champ connects to Klaviyo through a native plugin, but the plugin only sends checkout and order events. To run subscription emails you also need Checkout Champ&#8217;s postbacks for declined rebills, cancels, pauses and upcoming charges sent into Klaviyo as events. Once those are in, 5 emails do most of the work of keeping subscribers: a welcome for new subscribers, a reminder before each charge, a failed payment email, a resume email for paused subscribers and a winback after a cancel.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At Email Kong we work as a <\/span><a href=\"https:\/\/emailkong.com\/guides\/checkout-champ-klaviyo-agency\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Checkout Champ Klaviyo agency<\/span><\/a><span style=\"font-weight: 400;\"> for subscription brands, and this is the setup we use.<\/span>[\/vc_custom_heading][\/vc_column][\/vc_row][vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;&#8221; el_id=&#8221;what-does-the-checkout-champ-klaviyo-plugin-send&#8221;]<\/p>\n<h2>What does the Checkout Champ Klaviyo plugin send?<\/h2>\n<p>[\/vc_custom_heading][vc_custom_heading css=&#8221;.vc_custom_1794147560579{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">The plugin sends 7 events: Started Checkout, Placed Order, Ordered Product, Fulfilled Order, Cancelled Order, Refunded Order and Subscription Restarted. You connect it under Admin, then Plugins, then Email Service Providers, and route each Checkout Champ campaign to a Klaviyo list.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">2 settings matter more than the rest for subscription brands.<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The rebill toggle. Successful rebills do not reach Klaviyo by default. Placed Order fires for the first sale only until you tick &#8220;Send Placed Order Event For Successful Rebills&#8221; and add a Rebill Success route. With it off, flow revenue looks lower than it is.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OrderType. Placed Order carries an OrderType field. NEW_SALE means a first order and RECURRING means a rebill. Filter your post-purchase flows on NEW_SALE, so a renewal doesn&#8217;t start them again.<\/span><\/li>\n<\/ul>\n<p>[\/vc_custom_heading][\/vc_column][\/vc_row][vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;&#8221; el_id=&#8221;what-does-the-plugin-not-send&#8221;]<\/p>\n<h2>What does the plugin not send?<\/h2>\n<p>[\/vc_custom_heading][vc_custom_heading css=&#8221;.vc_custom_1794147560716{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">The plugin does not send any of the moments that decide whether a subscriber stays. Those live in Checkout Champ&#8217;s Postback Export Profiles instead.<\/span><\/p>\n<table>\n<thead>\n<tr>\n<th><span style=\"font-weight: 400;\">Subscription moment<\/span><\/th>\n<th><span style=\"font-weight: 400;\">In the Klaviyo plugin?<\/span><\/th>\n<th><span style=\"font-weight: 400;\">Where it lives in Checkout Champ<\/span><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><span style=\"font-weight: 400;\">Upcoming charge<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pre-Billing postback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Rebill declined<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rebill Decline postback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Final failure after retries<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Recycle Failed postback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Subscription cancelled<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cancel postback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Subscription paused<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Pause postback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Subscription reactivated<\/span><\/td>\n<td><span style=\"font-weight: 400;\">No<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Reactivate postback<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">There is one trap here. The plugin&#8217;s Cancelled Order event fires when an order is cancelled in the CRM. It does not fire when a customer cancels their subscription, so you can&#8217;t build a winback flow on it.<\/span>[\/vc_custom_heading][\/vc_column][\/vc_row][vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;&#8221; el_id=&#8221;how-do-you-get-subscription-events-into-klaviyo&#8221;]<\/p>\n<h2>How do you get subscription events into Klaviyo?<\/h2>\n<p>[\/vc_custom_heading][vc_custom_heading css=&#8221;.vc_custom_1794147560853{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">You send Checkout Champ&#8217;s postbacks into Klaviyo and turn each one into its own Klaviyo event on the right profile. Postbacks are set up in Checkout Champ under Admin, then Exports. Each profile has a destination, field mappings and routings that say which trigger and which campaign fire it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The triggers that matter for subscriptions are Subscription Started, Pre-Billing, Recurring Order, Rebill Decline, Recycle Failed, Cancel, Pause and Reactivate.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you point postbacks straight at Klaviyo, these are the problems that show up a week later:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicates. Checkout Champ resends a postback until it gets a success response. If the first one landed but the response timed out, the subscriber gets 2 failed payment emails. Every event needs a stable ID so Klaviyo keeps only the first copy.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Missing fields. The postback fields have no next bill date and no portal link. A reminder email without the date is half an email, so these have to be looked up and added.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Other brands leaking in. Many Checkout Champ accounts hold more than one brand. If the routing is set to all campaigns, another brand&#8217;s cancels land in your Klaviyo and your flows email their customers.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Revenue counted twice. Only events where money moved, like Subscription Started and Recurring Order, should carry a value.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A short delay. Checkout Champ sends postbacks in runs roughly every 15 minutes, so don&#8217;t promise an instant SMS on a decline.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Test with a real low-value order, because Test Card orders don&#8217;t export through postbacks.<\/span>[\/vc_custom_heading][\/vc_column][\/vc_row][vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;&#8221; el_id=&#8221;which-5-emails-stop-cancellations&#8221;]<\/p>\n<h2>Which 5 emails stop cancellations?<\/h2>\n<p>[\/vc_custom_heading][vc_custom_heading css=&#8221;.vc_custom_1794147560990{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">These 5 cover the points where subscribers usually leave. Each one is a Klaviyo flow running on the events above.<\/span><\/p>\n<h3>1. The new subscriber welcome<\/h3>\n<p><span style=\"font-weight: 400;\">Trigger: Subscription Started, or Ordered Product where ItemType is RECURRING. Filter on OrderType NEW_SALE so renewals don&#8217;t restart it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Tell the customer they are on a subscription, when the next order ships and how to get the most from the product. Buyers from a funnel offer may not have noticed they subscribed, so say it clearly in week 1.<\/span><\/p>\n<h3>2. The reminder before each charge<\/h3>\n<p><span style=\"font-weight: 400;\">Trigger: the Pre-Billing postback, or the next bill date stored on the Klaviyo profile. We use the date and clear it when someone cancels or pauses, so the reminder stops by itself. Note the Pre-Billing postback only fires after Checkout Champ has sent its own pre-bill notification.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Send it 3 to 5 days before a monthly rebill and 5 to 7 days before longer intervals. Always send one before the first rebill after a trial or funnel offer. Include the date, the amount and what&#8217;s in the box. Leave out a &#8220;manage subscription&#8221; button, because the portal is where people cancel. Changes go through a reply to support.<\/span><\/p>\n<h3>3. The failed payment email<\/h3>\n<p><span style=\"font-weight: 400;\">Trigger: Rebill Decline. Exit: any Recurring Order, Cancel or Reactivate. Turn Smart Sending off so a campaign the day before doesn&#8217;t block it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Send the first email a few hours after the decline with one button that opens the update-card page in the customer&#8217;s Checkout Champ portal. Time the next emails to land before Checkout Champ&#8217;s recycle billing retries, so a new card is on file when the charge runs. Write to the decline reason. A soft decline like insufficient funds needs a calm note and no discount. A hard decline like an expired card needs the button first. Recycle Failed gets the last email: the subscription is on hold until the card is updated.<\/span><\/p>\n<h3>4. The paused subscriber email<\/h3>\n<p><span style=\"font-weight: 400;\">Trigger: Pause. Exit: Reactivate.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A paused subscriber hasn&#8217;t left. We send 3 emails with a resume button that opens the right page in the Checkout Champ portal, and keep any offer for the last one. Checkout Champ has no Skip trigger, so pause also does the job a skip would do on other platforms.<\/span><\/p>\n<h3>5. The winback after a cancel<\/h3>\n<p><span style=\"font-weight: 400;\">Trigger: Cancel. Exit: Reactivate or any Placed Order. Filter to the brand&#8217;s own campaigns.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We run 3 emails over about 30 days and give each one a single job. Around day 10, a plain text note from the founder asking what went wrong. Around day 20, proof: a result or a real review. Around day 30, one clear restart offer with a reactivate button. The Cancel postback carries a cancel_reason, so once you group the reasons you can lead with pause for &#8220;too much product&#8221; and with price for &#8220;too expensive&#8221;.<\/span>[\/vc_custom_heading][\/vc_column][\/vc_row][vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;&#8221; el_id=&#8221;what-should-you-switch-off-before-going-live&#8221;]<\/p>\n<h2>What should you switch off before going live?<\/h2>\n<p>[\/vc_custom_heading][vc_custom_heading css=&#8221;.vc_custom_1794147561127{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]<span style=\"font-weight: 400;\">Turn off Checkout Champ&#8217;s own autoresponders for declined rebills, cancellations and pauses. They send through your email server, so without this step subscribers get 2 messages for every event. For pre-billing, switch off the autoresponder once your Klaviyo reminder is tested, if the reminder runs on the next bill date. If it runs on the Pre-Billing postback, the notification has to stay on, because the postback only fires after it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Then measure what the flows save: rebills recovered after a decline, cancelled subscribers who reactivate, and chargebacks before and after the reminder goes live. That is the core of <\/span><a href=\"https:\/\/emailkong.com\/guides\/subscription-retention-agency\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">subscription retention<\/span><\/a><span style=\"font-weight: 400;\"> on any platform, and on Checkout Champ it starts with getting the events into Klaviyo.<\/span>[\/vc_custom_heading][\/vc_column][\/vc_row]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>[vc_row css=&#8221;.vc_custom_1785740477941{margin-top: 125px !important;}&#8221;][vc_column][vc_custom_heading css=&#8221;.vc_custom_1794147560442{margin-top: 25px !important;margin-bottom: 25px !important;}&#8221;]Checkout Champ connects to Klaviyo through a native plugin, but the plugin only sends checkout and order events. To run subscription emails you also need Checkout Champ&#8217;s postbacks for declined rebills, cancels, pauses and upcoming charges sent into Klaviyo as events. Once those are in, 5 emails [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":95063,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2687],"tags":[],"class_list":["post-95062","post","type-post","status-publish","format-standard","hentry","category-business"],"acf":[],"_links":{"self":[{"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/posts\/95062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/comments?post=95062"}],"version-history":[{"count":1,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/posts\/95062\/revisions"}],"predecessor-version":[{"id":95064,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/posts\/95062\/revisions\/95064"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/media\/95063"}],"wp:attachment":[{"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/media?parent=95062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/categories?post=95062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pixflow.net\/blog\/wp-json\/wp\/v2\/tags?post=95062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}