Skip to main content
When a store connects Klaviyo, Appstle Loyalty sends its loyalty emails to Klaviyo as events instead of sending them itself. You build the message in a Klaviyo flow that uses the event’s properties. This page lists the events, when they’re sent, and what each property holds.
This page is about the events Appstle sends to Klaviyo. To receive loyalty events on your own server, use webhooks. To react to them inside Shopify, use Shopify Flow.

Get started

1

Connect Klaviyo

In the Appstle Loyalty admin, go to More > App Integrations and open Klaviyo Email. Click Connect and approve the connection in Klaviyo. The page then shows the connected account’s organization and account ID. There’s no separate on/off switch: while Klaviyo is connected, Appstle sends these emails through Klaviyo and doesn’t send its own.When the connection is approved, Appstle also sends one sample event for each of the store’s email templates, to a sample profile with the address sample.event@appstle.com, so every metric appears in Klaviyo right away. It also starts syncing the store’s profile properties.
2

Add the sample template

Click Create Sample Template. Appstle adds a template named Appstle Loyalty Email Template to your Klaviyo account. It doesn’t create any flows.
3

Create a flow for each event

In Klaviyo, create a flow whose trigger is the event’s metric, from Events, and use the event’s properties in its message.
4

Send a test event

In More > Email Templates, open a template, click Test Email, choose an address in To Email and click Send. The list offers the addresses in Email Notifications under More > Advanced Settings. Appstle sends that template’s event for the address you chose. The event uses the store’s newest loyalty customer for the customer, tier and reward codes, and sample points: availablePoints is 100, and points is 10 on the earn and redeem events. It also sets the profile properties on that address’s Klaviyo profile. Find the event in that profile’s activity in Klaviyo and preview the flow’s message with it.
5

Set the flows live

Set each flow live in Klaviyo. Keep the matching template turned on in Email Templates, because turning a template off stops its event.
Klaviyo has deprecated connecting with a public and private API key. A store that connected that way must connect again: click Connect on the Klaviyo Integration Update banner in the Appstle Loyalty admin, or in More > App Integrations > Klaviyo Email.

How Appstle sends an event

For each email Appstle would send, it posts one event to Klaviyo’s Events API (POST https://a.klaviyo.com/api/events, revision 2025-04-15) with the connected account’s credentials:
  • Metric name. One metric per email type, listed in Events. In Klaviyo, create a flow triggered by that metric.
  • Profile. The customer’s email address, plus up to four loyalty properties. Each event updates them on the profile. See Profile properties.
  • Event properties. The same values that the Appstle email template can use, such as the customer, the points, the reward and the dates. A real event carries all of them, and most are null for any one event. See Event properties.
  • No value, no event ID. Appstle sends no value, value_currency, unique_id or time, so Klaviyo uses the time it receives the event.
Klaviyo answers 202 when it accepts an event. If Klaviyo answers 401 because the access token has expired, Appstle gets a new token and sends the event once more. Appstle doesn’t retry any other failure, and doesn’t send its own email instead. If the store also has Mailchimp or Omnisend connected, Klaviyo takes precedence: the events go to Klaviyo only. Each email appears in More > Activity Logs. When Appstle skips one, the entry gives the reason, such as the app embed being off, the template being off or a restricted tag. An entry marked successful means Appstle sent the event, not that Klaviyo accepted it, so confirm it in the profile’s activity in Klaviyo.

When an event is sent

Appstle sends an event only when all of these are true:
  1. Klaviyo is connected in More > App Integrations > Klaviyo Email.
  2. The email template is on. Each email has a template in More > Email Templates with an Enable Email Notification setting. Turning it off stops the Klaviyo event as well as the Appstle email.
  3. The app embed is on in the store’s theme. With it off, Appstle sends nothing and records the failure in the activity log.
  4. Loyalty is shown on the store. The Show loyalty on your store setting in Design is on.
  5. The customer can get email. The customer’s Enable Email setting is on, and the customer hasn’t unsubscribed and hasn’t bounced or complained. Unless the merchant changes it on the customer, Send Emails To in More > Advanced Settings sets Enable Email: Active Customers (the default) turns it on for customers who are active in the program, All Customers for everyone, and Newsletter Subscribers for customers subscribed to email marketing in Shopify.
  6. The customer’s tags allow it. If the template has Restrict Customer Tags, a customer with one of those tags gets no event. If it has Allow Customer Tags, a customer without one of those tags gets none. The VIP tier expiring and upgrade reminders don’t read the customer’s tags: Restrict Customer Tags has no effect on them, and with Allow Customer Tags set they’re never sent.
The three referral events skip points 4 to 6: they need only Klaviyo, an on template and the app embed. The Monthly reward reminder has its own rules, below.
If a template has Only Send this email as Admin Notification? checked, Appstle sends that template’s event for the template’s Admin Notification / BCC Email address instead of the customer’s, and the customer’s profile gets no event for it. The event still describes the customer and sets the customer’s profile properties on the admin address’s profile, so that profile always shows the last customer it was sent for. With the box checked and no address set, Appstle sends no event.
The Monthly reward reminder is sent only while Klaviyo or Omnisend is connected, so a store that uses Mailchimp or Appstle’s own email never gets it. It goes out on the schedule in Reminder Interval Setting in More > Advanced Settings: End of Month (the default), End of Year or Weekly. It goes to every customer with an email address, Enable Email on and a points balance above 0. Of the conditions above it needs only points 1, 2 and 4: it doesn’t check the app embed, Appstle’s unsubscribe and bounce records, or the template’s tags.

Events

The metric name is the exact text Klaviyo shows. Each event comes from an email template in More > Email Templates.
Appstle Loyalty’s product review emails use a separate metric, Review Request Email Event From Appstle Review. It’s not covered on this page.

Referral events

The three referral events are built from the referring customer’s account, whichever address they go to. In them, customer, customerRewards, availableStoreCredits, tierName, vipTierPerks and the date properties describe the customer who referred, and customer.first_name is always there. availablePoints is 0 on both acceptance events.
In a message to the friend, use only referralLink, discountCouponCode, claimNow, redirectLink, subject, heading and body_content. customerRewards holds the referring customer’s own unused reward codes.
The profile properties these events set follow the same rule. On the new-customer acceptance and the invite, the friend’s profile gets the referring customer’s vipTier, vipTierExpireDate and lastActivityDate, and on the invite their availablePoints too. Both acceptance events set availablePoints to 0 on the profile they go to. Appstle doesn’t clear these values later, so don’t segment referred friends on them.

Profile properties

Each event sets up to four properties on the Klaviyo profile it goes to, and replaces their earlier values. A property that has no value for the customer is left out, and Appstle never removes one: when a customer loses their VIP tier, vipTier keeps the old tier’s name.

Profile sync

Appstle also keeps loyalty properties on the Klaviyo profile with a separate update, not an event. It updates a profile that already exists in Klaviyo, found by email address. A customer who isn’t in Klaviyo yet isn’t added. It runs when the customer’s loyalty data is loaded on the storefront, when their VIP tier changes, and in a bulk sync. While Require Customers to Opt In to the Loyalty Program is on in More > Advanced Settings, a customer who hasn’t joined isn’t updated. The sync and the events both write availablePoints and lastActivityDate, in different formats: the sync writes the exact balance, which can have decimals, and a date and time, and an event writes the rounded balance and a plain date. The profile keeps whichever was written last. In More > Advanced Settings, Klaviyo Profile Sync chooses who is updated: All Customers or Marketing Enable Only. The second option updates only customers who agreed to email marketing.

Event properties

Every event carries the properties below. Most are null unless the event’s email uses them. Dates are plain dates such as 2026-11-28, and amounts are text, formatted the way the email shows them.

Customer and balance

A field without a value is left out of customer, for example vipTier and vipTierExpiredDate for a customer with no tier.

Earn and redeem

Reward and discount

Referral and VIP

Template text and styling

The template’s own settings travel with every event, so a flow can build the same email Appstle would have sent. Don’t build logic on them.

Properties of a single event

A property that an event doesn’t use is null, or an empty array.

Example

The Point earn event for one customer, trimmed to the properties you’d use. The values are placeholders in the formats Appstle sends. Appstle posts it to https://a.klaviyo.com/api/events with the connected account’s credentials.
A real event holds all of the properties of Event properties, most of them null.

Use the properties in Klaviyo

In a Klaviyo email or SMS template, read a property with {{ event.<property> }}, a nested one with a dot, and loop over an array with {% for %}:
Property names are case sensitive. Preview the message with a test event before you set the flow live (see Get started).

Next steps

Webhooks

Receive loyalty events on your own server, with IDs and signatures.

Shopify Flow

Use Appstle Loyalty triggers and actions inside Shopify.