Skip to main content
Smile sends customers four cashback emails: a welcome when their first cashback lands in their store credit, Cashback issued when each later one lands, and a first and a final reminder before it expires. You can send these from Klaviyo instead. Smile sends Klaviyo an event at each of these moments and builds a draft of each email there for you.

Connect Klaviyo

  1. In Smile, go to Settings > Customer emails.
  2. On Klaviyo emails, click Connect Klaviyo.
  3. Pick your Klaviyo account and click Allow.
Smile then sends a sample of each cashback event your Klaviyo account doesn’t have yet to a test profile (klaviyo-test-events@smile.io), so both events are ready to use in Klaviyo.

Start with Smile’s emails

This is the quickest way to start. On Klaviyo emails, click Create drafts. Smile creates a draft flow in Klaviyo for each cashback email, named after it, like Smile: Cashback issued, with the email’s current text, your logo and your button colors. Each flow triggers on its event, with a filter that keeps it to its email (count for the welcome and Cashback issued, reminder_position for the reminders) and held_out equals false, and has Smart Sending off. Drafts send nothing. If Klaviyo is still registering an event, Smile waits for it, usually a minute or two. Create drafts shows until a flow in Klaviyo uses one of Smile’s events. After that, each email has its own Create in Klaviyo button while no flow sends it.

Send an email from Klaviyo

  1. On Settings > Customer emails, click Open in Klaviyo next to the email.
  2. Review the email, send yourself a test, and set the flow to Live.
  3. Back in Smile, click Edit on the matching Smile email and turn it off, so customers get one email, not two. A Smile email that a live Klaviyo flow also sends says Also sent from Klaviyo. To turn off all of Smile’s cashback emails at once, use the switch on Smile emails.
Smile shows every Klaviyo flow that uses its cashback events, including flows your team builds, with the status Klaviyo reports: Live, Draft or Manual. It reads Klaviyo each time you open the page. If you delete Smile’s draft, click Create in Klaviyo to make a new one.
Note: Once an email is in Klaviyo, Klaviyo owns it. Smile never turns a Klaviyo flow on or off, and changes you make to the Smile email afterwards don’t update the Klaviyo version.

What Smile sends to Klaviyo

Smile sends each event once, to the customer’s Klaviyo profile by email address. Customers with no email address in Smile get no events.
  • Cashback Issued goes out once for each cashback. An order can earn more than one: a boost given at your point of sale is its own cashback, with its own event. Cashback that was taken back, for example after a refund, before Smile sends the event gets none.
  • Cashback Expiring goes out only while expiry reminders are on in your cashback program, and only on its reminder days. Smile checks once a day. A customer gets one event per reminder day for all their cashback in one currency that expires on the same day. If they’ve spent it all, or it’s already expired, they get none. Turning off Smile’s own reminder email doesn’t stop this event; turning off expiry reminders in your program does.
Each event includes the properties below. Use the formatted properties in email text, and the raw ones for flow filters and your own formatting. When cashback never expires, Cashback Issued has expires set to false and leaves out expires_at and expires_at_formatted. When your cashback uses Keep it while you shop (How cashback expires), Cashback Issued has expires set to true and no expires_at, because the date moves with every order and with new cashback added to the balance. Cashback Expiring names the day the whole balance expires unless the customer orders before then. A customer whose balance and a dated cashback expire on the same day gets an event for each. To say so in one email for both styles, use {% if event.expiry_style == "whole_balance" %}. Smile’s drafts already do. In Cashback Expiring, amount is the total the customer still has to spend from all their cashback that expires on that day, checked with Shopify just before Smile sends the event. With each_credit, it isn’t their whole balance, and it isn’t what was first issued, and expires_at is the earliest of those expiry times. With whole_balance, it’s all the cashback that expires with the balance, and expires_at is the day the balance expires. Here’s what each event looks like in Klaviyo:
Cashback Issued
Cashback Expiring
reason says why the cashback was issued: order for cashback earned on an order, manual for cashback your store added, shopify_flow_cashback for cashback from a Shopify Flow workflow, activity for cashback from an activity like a review, and more values as Smile adds new ways to earn. reason_label says the same thing as a short label in the customer’s language, such as Order #1042 or Added by Bill's Store. Use it as a line of its own, not inside a sentence. An email that shows reason_label reads right for every reason, including ones Smile adds later, with no change to your flow. Two of Smile’s emails share each event. count tells the welcome (1) from Cashback issued (more than 1), and reminder_position tells the first reminder from the final one, whatever your reminder days are. held_out is true for a customer your email holdout keeps from cashback emails. Smile still sends their events, so your segments see every customer, and Smile’s drafts filter on held_out equals false so those customers get no email. If your email only makes sense for orders, add a trigger filter in Klaviyo for reason equals order. Klaviyo doesn’t let you add trigger filters to flows Smile creates: clone the flow in Klaviyo and add the filter to the copy. If you only use cashback, Smile sends Klaviyo cashback data only: no points events or points profile properties.

Build your own flow instead

  1. In Klaviyo, create a flow with a Metric trigger and pick one of the events. Add a trigger filter for held_out equals false, and one for count or reminder_position if the flow replaces only one of Smile’s emails.
  2. Add an email and turn off Smart Sending, so a customer who gets cashback on two orders in a day gets both emails.
  3. Add the event properties to the email, for example:
    • {{ event.amount_formatted }}
    • {{ event.reason_label }}
    • {{ event.expires_at_formatted }}
    • {{ event.days_until_expiry }}
  4. Set the flow to Live.
  5. In Smile, go to Settings > Customer emails, click Edit on the matching Smile email and turn it off. Your flow shows up under Klaviyo emails.

Languages and currencies

amount_formatted, expires_at_formatted, expires_in and reason_label are in the customer’s language and the cashback’s currency, the same way Smile’s emails show them. When the cashback’s currency isn’t your store’s, the amount has a symbol that can’t be mistaken for yours, like C$10.00 on a US store. Smile uses the language the customer last used with Smile on your store, or your store’s language in Smile when it doesn’t know. Klaviyo formats money in your account’s one currency and dates in English only, so these properties save you from building that yourself. If you use Klaviyo’s Smart Translations, Klaviyo translates the text you write into each customer’s language, and shows Smile’s properties exactly as Smile sends them. Smile’s drafts greet a customer as “Hi Sam,” or just “Hi,” so the greeting translates cleanly. If you write a greeting with a fallback word, like {{ first_name|default:'there' }}, Klaviyo translates that word on its own, which can read oddly. If your Klaviyo emails are in one language only, a customer who shops in another language can see an amount, date or label in their own language in an otherwise English email. To avoid that, format the raw amount and expires_at properties in Klaviyo instead.

Customers who unsubscribed

Klaviyo sends flow emails as marketing email, so customers who unsubscribed from your marketing don’t get them. To send cashback emails to every customer, apply for transactional status on each email in Klaviyo. Klaviyo reviews the request within one business day, and editing the email removes the status until you apply again. Learn more in Klaviyo’s guide to transactional flow emails.

Send from your own domain

Send these emails from an address on your own domain, with Klaviyo’s branded sending domain set up for it. Email sent from a domain that hasn’t authorized Klaviyo can land in spam or be held by the customer’s email provider.