JeriCommerce can send five automatic emails from Settings > Customer Flows > Emails. If you want Klaviyo to own the design, sending, and reporting, create one metric-triggered Klaviyo Flow for each email you replace.

Keep each JeriCommerce email on until its Klaviyo flow has been tested. Turn off only the matching JeriCommerce email after the Klaviyo flow is live, otherwise customers can receive the same message twice.

Before you start

  • Connect Klaviyo in JeriCommerce.
  • Set up a sender email or sending domain in Klaviyo.
  • Confirm that your customer profiles have the consent required for the type of email you plan to send. See Klaviyo's consent guidance.
  • Keep one test customer available for each event.
  • Prepare your email design, subject line, sender details, and links.

Enable the right features in JeriCommerce

1

Open the Klaviyo integration

In the JeriCommerce admin, go to Settings > Integrations > Klaviyo. If Klaviyo is not connected yet, click Authenticate Klaviyo and complete the authorization in Klaviyo.
2

Turn on Events

Turn on Events and save. This sends JeriCommerce customer activity to Klaviyo as metrics that can trigger flows. Events are not a replacement for the email itself. They are the connection between the JeriCommerce action and your Klaviyo flow.
3

Turn on Custom Fields

Turn on Custom Fields if you want loyalty data in the email, such as the customer's balance, tier, or the profile property jericommerce_download_wallet_pass_url. This feature is recommended for personalization, but it is not required for event-triggered flows.
4

Leave Segments optional

Turn on Segments only if you also want Klaviyo audiences available for JeriCommerce campaigns and wallet push notifications. It is not required to send these emails from Klaviyo.

The Wallet pass requested event contains the one-time downloadLink only when the matching JeriCommerce email is turned off. Use the controlled test below before launch so you can verify the link without sending an incomplete email to a customer.

The wallet pass event needs a short exception to the normal testing order because JeriCommerce withholds downloadLink while its built-in email is on.

1

Keep the Klaviyo flow in Draft

Build the flow and email, but leave the flow in Draft. This prevents the test event from sending a live Klaviyo email.
2

Temporarily turn off the JeriCommerce email

In Settings > Customer Flows > Emails, turn off Download loyalty card for the test. Do not turn off the other automatic emails.
3

Request a pass for a test customer

Use a test customer to request a wallet pass. JeriCommerce sends a Wallet pass requested event with the one-time downloadLink.
4

Preview the event in Klaviyo

Open the flow email in Klaviyo, choose Preview and test, and select the new event. Confirm that event.downloadLink is present and opens the expected wallet installation page. Klaviyo's event personalization guide explains how to copy event variables from this panel.
5

Restore the toggle while you finish

Turn Download loyalty card back on while you continue editing the flow. When you are ready to launch, set the flow and email to Live, then turn the JeriCommerce email off again. Trigger a new test event after launch if you need to test the one-time link itself.

Create a Klaviyo flow

Create one flow for each email you replace. Klaviyo calls a JeriCommerce event a metric when it is used as a flow trigger.

1

Create a flow from scratch

In Klaviyo, open Flows, click Create flow, choose Build your own, name the flow, and create it.
2

Choose the JeriCommerce metric

In the flow builder, choose Metric as the trigger and select the exact JeriCommerce event from the table below. If it is not listed yet, check Analytics > Metrics and create a fresh test event after turning on Events in JeriCommerce. See Klaviyo's metric-triggered flow guide for more about metric triggers and re-entry.
3

Add the email

Add an email action immediately after the trigger. Configure the sender, subject, preview text, and message content. Use the event properties shown below for the dynamic parts of the email.
4

Insert event data

Open the email editor and choose Preview and test. Select the event that triggered the flow, then copy properties from the Event Properties menu. Event variables are case-sensitive. Klaviyo's event personalization guide explains this workflow.
5

Test and set the flow live

Send a test email, check every link and dynamic value, and confirm the event appears on the test profile. For the wallet pass email, follow the controlled test above. Set the email and the flow to Live, then turn off only the matching JeriCommerce email toggle.

Email and event mapping

JeriCommerce email Klaviyo metric Use in the email Important detail
Confirm email Customer created person.first_name, person.email This event does not list a JeriCommerce verification URL. Use it for a welcome message, but keep the built-in email on when the customer must verify their account to activate it.
Download loyalty card Wallet pass requested event.downloadLink This is a one-time installation link. The profile property jericommerce_download_wallet_pass_url is also available when Custom Fields is on.
Coupon assigned Coupon assigned event.code, event.installUrl, event.header, event.body Use the code for checkout or the install URL for a wallet coupon pass.
Reward available Reward redeemable event.rewardTitle, event.rewardValue, event.rewardCost, event.rewardLink Choose the CTA destination based on the merchant's active loyalty experience, as described below.
Reward redeemed Reward redeemed event.rewardTitle, event.code, event.rewardLink Include the discount code so the customer can use the redeemed reward.

The complete event list and payload reference is available in Register Wallet Events on Klaviyo.

Choose the reward CTA destination

Use the destination that matches the merchant's active customer experience:

  • If the Storefront Widget is active, wrap the reward route in a storefront URL: https://your-store.com?jeri={{ event.rewardLink }}. Do not link directly to event.rewardLink.
  • If the widget is inactive, link to the merchant's active Loyalty Hub URL instead. This can be the public storefront hub or the customer account hub when Shopify New Customer Accounts is enabled. Replace the example with the merchant's actual hub destination.

Gift card messages

Gift cards use a separate Gift card sent event. It includes event.code, event.installUrl, event.header, event.body, and event.mailSent. This event is not one of the five toggles on the Automatic Emails card, so check your gift card delivery setting before creating a Klaviyo replacement. Use event.mailSent to inspect whether JeriCommerce recorded an email send and avoid sending a duplicate.

Launch checklist

  • Confirm the matching JeriCommerce toggle is still on while testing.
  • Trigger a real test event and verify the metric appears on the Klaviyo profile.
  • Preview the email with event data, not only with a blank template preview.
  • Check one-time wallet links before sending a second test to the same customer.
  • Set the email and flow to Live.
  • Turn off the matching JeriCommerce email.
  • Review Klaviyo's Smart Sending settings. Smart Sending can skip a message when the profile recently received another email.

JeriCommerce's built-in emails use the customer's stored language and fall back to your program default. A Klaviyo email uses the content you build in Klaviyo, so create translated versions or conditional language blocks there if your program is multilingual. The pre-built flow templates can speed up the coupon and reward flows, but they do not replace the full five-email setup in this guide.