> ## Documentation Index
> Fetch the complete documentation index at: https://developers.appstle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Klaviyo events reference

> The events Appstle Loyalty sends to Klaviyo: each event's metric name, when it is sent, the properties it carries, and how to use them in a Klaviyo flow.

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.

> [!NOTE]
>
> This page is about the events Appstle sends **to Klaviyo**. To receive loyalty events on your own server, use [webhooks](https://developers.appstle.com/loyalty/webhooks.md). To react to them inside Shopify, use [Shopify Flow](https://developers.appstle.com/loyalty/shopify-flow.md).

## 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](#profile-sync).

**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](#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](#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.

> [!WARNING]
>
> 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](#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](#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](#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.

> [!WARNING]
>
> 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](#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**.

| Metric name | Template and when it's sent |
| - | - |
| `Welcome event from Appstle Loyalty` | **Welcome Email**. A customer joins the loyalty program. |
| `Point earn event from Appstle Loyalty` | **Point Earn**. A customer earns points from an earn rule, or a merchant adds points to their account. |
| `Store Credit earn event from Appstle Loyalty` | **Credits Earn**. A customer earns store credit from an earn rule, or a merchant adds store credit to their account. |
| `Point redeem event from Appstle Loyalty` | **Point Redeem**. A customer redeems points for a reward: in the customer portal, at checkout, through the Admin API (`POST /api/external/redeem-points`), or when the merchant redeems for them in the admin. The same redemption also sends the Reward available event. |
| `Reward available reminder event from Appstle Loyalty` | **Reward Available Reminder**. A customer redeems points for a reward (see Point redeem), receives a referral reward, or gets a reward the merchant sends to customers in bulk from the admin. |
| `Monthly reward reminder event from Appstle Loyalty` | **Monthly Reward Reminder**. On the schedule in **Reminder Interval Setting** (the end of each month by default), for customers with **Enable Email** on and a points balance above 0. Sent only while Klaviyo or Omnisend is connected. |
| `Reward expiring reminder event from Appstle Loyalty` | **Points Expiring Reminder**. A customer's points are about to expire. Sent the number of days before expiry set in **Points Expiring Reminder (days before)** in the template's settings, 3 by default, to customers with points to lose. |
| `Discount expiring reminder event from Appstle Loyalty` | **Discount Expiring Reminder**. A reward discount code the customer hasn't used expires in 3 days. |
| `Birthday Reward event from Appstle Loyalty` | **Birthday**. On a customer's birthday, after the birthday earn rule credits them. |
| `Vip tier achieved event from Appstle Loyalty` | **VIP Tier Achieved**. A customer moves into a VIP tier. |
| `Vip tier expiring reminder event from Appstle Loyalty` | **VIP Tier Expiring Reminder**. 7 days before a customer's VIP tier expires. |
| `Vip tier upgrade reminder event from Appstle Loyalty` | **VIP Tier Upgrade Reminder**. Sent together with the VIP tier expiring reminder, to a customer who has a higher tier to reach. |
| `Referral Acceptance Confirmation for new customer event from Appstle Loyalty` | **Referral Acceptance Confirmation for new customer**. A referred friend accepts the offer. The event goes to the friend's email address. |
| `Referral Acceptance Confirmation for existing customer event from Appstle Loyalty` | **Referral Acceptance Confirmation for existing customer**. A referred friend accepts the offer. The event goes to the customer who referred them, and `referredEmail` holds the friend's address. |
| `Send referral invite to new customer event from Appstle Loyalty` | **Send referral invite to new customer**. A signed-in customer invites a friend by email in the customer portal. The event goes to the friend's email address, and `referralLink` is the inviting customer's link. |

> [!NOTE]
>
> 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.

> [!WARNING]
>
> 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.

| Property | Type | Description |
| - | - | - |
| `availablePoints` | Number | The customer's available points, rounded like the `availablePoints` event property. Left out when the value isn't a number |
| `vipTier` | String | The customer's VIP tier name |
| `vipTierExpireDate` | String | When the customer's VIP tier expires, as a date such as `2027-01-15` |
| `lastActivityDate` | String | The customer's last loyalty activity, as a date such as `2026-11-10` |

### 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.

| Property | Type | Description |
| - | - | - |
| `availablePoints` | Number | The customer's exact available points |
| `availableStoreCredits` | Number | The customer's store credit balance |
| `availableStoreCreditsCurrency` | String | The store credit currency. Not written by the bulk sync |
| `customerFrom` | String | `Appstle Loyalty` |
| `loyaltyReferralLink` | String | The customer's referral link |
| `dob` | String | The customer's birthday, as a date such as `1990-04-21`, when they've given one |
| `vipTier` | String | The VIP tier name, when the customer has one |
| `loyaltyStatus` | String | The customer's status in the program: `ACTIVE`, `INACTIVE`, `EXCLUDED` or `EXCLUDED_BY_CUSTOMER` |
| `lastActivityDate` | String | The customer's last loyalty activity, as an ISO 8601 date and time |
| `pointsExpireDate` | String | When the customer's points expire, as an ISO 8601 date and time. Set when points expiry is on and the customer has had activity. In stores that expire points **After a time without activity**, it counts from the later of the customer's newest points transaction and their stored last activity, so it can be later than `lastActivityDate` plus the window. In stores that expire points **A set time after they're earned**, it isn't the expiry date of any batch of points |
| `nextVipTier` | String | The next VIP tier the customer can reach. The four next-tier properties are set only when VIP tiers are on and the customer's tier wasn't assigned manually. In the top tier, `nextVipTier` is an empty string, the two amounts are `0` and the percentage is `100` |
| `nextVipTierMilestone` | Number | The next tier's milestone, in the program's unit: points earned, orders placed or amount spent |
| `remainingToNextVipTier` | Number | What is left to reach it |
| `nextVipTierProgressPercent` | Number | How far the customer is toward it, as a percentage |

## 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

| Property | Type | Description |
| - | - | - |
| `customer` | Object | The customer. See the fields below |
| `availablePoints` | String | The customer's available points, rounded the way the store's rounding setting says: down to a whole number by default, up, or to two decimals when rounding is off. It doesn't count points still pending approval, and it's `0` on the two referral acceptance events. As a number, it's also a [profile property](#profile-properties) |
| `availableStoreCredits` | String | The customer's store credit balance, in the store's money format, such as `$12.50` |
| `tierName` | String | The customer's VIP tier name. An empty string when the customer has no tier |
| `nextTierName` | String | The next tier's name. Set on the VIP tier upgrade reminder |
| `customerStatus` | String | The same as `customer.status`: `Active`, or `Guest` for a customer who isn't active in the program |
| `lastActivityDate` | String | The date of the customer's last loyalty activity |
| `vipTierExpireDate` | String | The date the customer's VIP tier expires |
| `pointExpireDate` | String | The date the customer's points expire, when points expiry is on and the customer has had activity. On the Points expiring reminder, the date the points will be removed |
| `shop` | Object | The store, as `{"name": "..."}` |

| `customer` field | Type | Description |
| - | - | - |
| `id` | Number | The customer's Shopify ID |
| `display_name`, `first_name`, `last_name` | String | The customer's names. `display_name` is the first and last name joined with a space. On the referral events, `first_name` is always `there` |
| `token` | String | The customer's referral token, the end of their `referralLink` |
| `vipTier` | String | The customer's VIP tier name |
| `status` | String | `Active`, or `Guest` for a customer who isn't active in the program |
| `availableCredits` | Number | The store credit balance saved for the customer |
| `lastActivity`, `vipTierExpiredDate` | Number | Unix timestamps in seconds, with a decimal part, such as `1794303000.000000000`. Unlike the date properties above, these aren't dates in text. Use `lastActivityDate` and `vipTierExpireDate` in a flow |

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

### Earn and redeem

| Property | Type | Description |
| - | - | - |
| `points` | String | The points earned or redeemed, on the Point earn, Store Credit earn and Point redeem events, rounded like `availablePoints`. On the Store Credit earn event it's the credit amount rounded the same way, so with the default setting a \$12.50 credit is `12` |
| `store_credit` | String | The same amount as `points`, in the store's money format, such as `$12.00` for that \$12.50 credit |
| `ruleName` | String | On the earn events, the earn rule's name when all the points came from one rule. On the Point redeem event, the redeem rule's name |
| `earnActivity` | Array of strings | On the earn events, when the points came from more than one rule: the note saved with each points transaction, one entry per transaction. `null` otherwise |
| `redeemRuleName` | String | The name of the redeem rule that issued the reward. Set on the Reward available event after a redemption |
| `suffixLabel` | String | The label that follows an amount of points, `Points` unless the template changes it |
| `available_points_label` | String | The template's label for the balance |
| `earnRuleSummaries` | Array of objects | The active earn rules this customer can use, except the referral rules, each with `ruleName`, `ruleDescription`, `iconUrl` and `iconSvg` (always `null`). Filled only when `showEarnRules` is `true`, an empty array otherwise |
| `rewardsSummaries` | Array of objects | The active redeem rules this customer can use, each with `note` (the rule's name), `discount` (its description), `discountType` (`%`, or the currency symbol), `points` (the points it costs), `iconUrl` and `minSpendAmount`. Filled when `showRedeemRules` is `true`, and always on the Monthly reward reminder. An empty array otherwise |

### Reward and discount

| Property | Type | Description |
| - | - | - |
| `rewardName` | String | Depends on the event: the discount code on the Reward available, Birthday and Discount expiring events that carry one, the redeem rule's name on Point redeem, the tier's name on VIP tier achieved and the next tier's name on VIP tier upgrade reminder. An empty string when there's nothing to name |
| `rewardDescription` | String | A description of the reward |
| `rewardMinimumSpendAmount` | String | The minimum spend the reward's discount needs, in the store's money format |
| `rewardDiscountCode` | String | The discount code the customer redeemed. Set on the Point redeem event |
| `discountCouponCode` | String | The referral reward's discount code: the friend's code on the new-customer acceptance, the referring customer's code on the existing-customer acceptance |
| `rewardExpireDate`, `expireDate` | String | When the reward or the points expire. The two hold the same date |
| `customerRewards` | Array of objects | The customer's unused reward discount codes, each with `code` and `description` |
| `claimNow` | String | The text of the email's button, such as `Claim Now: AL_XYZ123` |
| `redirectLink` | String | Where the email's button goes: the store, `/discount/<code>` for an event with a discount code, the template's redirect URL on the Point earn event, or the referral link on the referral invite |

### Referral and VIP

| Property | Type | Description |
| - | - | - |
| `referralLink` | String | The referring customer's referral link. Set on the three referral events |
| `referredEmail` | String | The email of the friend who accepted. Set on the existing-customer acceptance |
| `referralRewardSide` | String | Which side of a referral a reward is for: `REFERRAL` for the customer who referred, `REFERRED` for the friend. Set on the Reward available event for a referral reward |
| `vipTierPerks`, `vipPerks` | Array of strings | The labels of the perks of the customer's VIP tier. Empty when the customer has no tier. The two properties hold the same list |

### 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.

| Property | Type | Description |
| - | - | - |
| `emailSettingType` | String | The email type, as a code: `WELCOME_EMAIL`, `POINT_EARN`, `STORE_CREDIT`, `POINT_REDEEM`, `REWARD_AVAILABLE_REMINDER`, `MONTHLY_REWARD_REMINDER`, `REWARD_EXPIRING_REMINDER`, `DISCOUNT_EXPIRING_REMINDER`, `BIRTHDAY`, `VIP_TIER_ACHIEVED`, `VIP_TIER_EXPIRING_REMINDER`, `VIP_TIER_UPGRADE_REMINDER`, `REFERRAL`, `REFERRAL_CUSTOMER` or `REFERRAL_LINK` |
| `subject`, `heading`, `body_content`, `footer` | String | The template's texts, with the customer's values already filled in |
| `claimNowButtonText`, `rewardAvailableHeading`, `rewardsAvailable`, `earnRulesAvailableText`, `showMoreEarnRuleText`, `showMoreRedeemRuleText`, `unsubscribeText` | String | More texts from the template |
| `showEarnRules`, `showRedeemRules`, `showAvailablePoints`, `rtlEnabled`, `usingCustomDomain` | Boolean | The template's display settings |
| `logo_url`, `logo_height`, `bannerImageUrl` | String | The template's images |
| `header_text_color`, `header_background_color`, `text_color`, `footer_text_color`, `footer_link_color`, `footer_background_color`, `claimNowButtonTextColor`, `claimNowButtonBackgroundColor`, `claimNowButtonBorderColor`, `rewardsAvailableHeadingColor`, `templateBackgroundColor` | String | The template's colors |
| `ending_in_text`, `bodyLines`, `button_border_radius`, `referralAcceptRequest` | | Not used. `ending_in_text` and `button_border_radius` are `null`, `bodyLines` is an empty array, and `referralAcceptRequest` is `{"discount": null, "discountType": null, "discountCouponCode": null, "minimumPurchaseAmount": null}` on every event |

### Properties of a single event

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

| Event | Properties |
| - | - |
| Point earn, Store Credit earn | `points` and `store_credit` (the amount earned), and `ruleName` or `earnActivity`. When some of the points are still pending approval, `showAvailablePoints` is `false`, because `availablePoints` counts only approved points. On Point earn, `redirectLink` is the template's redirect URL when it has one |
| Point redeem | `points` and `store_credit` (the points spent), `ruleName` and `rewardName` (the redeem rule's name), and `rewardDiscountCode` (the code the customer got) |
| Reward available | `rewardName` (the discount code), `rewardDescription`, `rewardMinimumSpendAmount`, `claimNow` and `redirectLink` (`/discount/<code>`). After a redemption, also `redeemRuleName`. For a referral reward, also `referralRewardSide` |
| Birthday | `rewardName` (the discount code, when the birthday reward is one), `rewardDescription`, `rewardMinimumSpendAmount`, `claimNow` and `redirectLink` |
| Points expiring | `pointExpireDate`, `rewardExpireDate` and `expireDate`, all the date the points will be removed |
| Discount expiring | `rewardName` (the discount code), `rewardDescription`, `rewardMinimumSpendAmount`, `claimNow`, `redirectLink`, and `rewardExpireDate` and `expireDate` (3 days after the event) |
| VIP tier achieved | `rewardName`, the new tier's name |
| VIP tier expiring reminder | `vipTierExpireDate` |
| VIP tier upgrade reminder | `nextTierName` and `rewardName`, the next tier's name |
| Referral acceptance, new customer | `discountCouponCode` (the friend's code), `claimNow` and `referralLink`. See [Referral events](#referral-events) for the other properties |
| Referral acceptance, existing customer | `discountCouponCode` (the referring customer's code), `claimNow`, `referralLink` and `referredEmail` |
| Referral invite | `referralLink`, the inviting customer's link, which is also `redirectLink` |

## 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.

```json theme={null}
{
  "data": {
    "type": "event",
    "attributes": {
      "metric": {
        "data": {
          "type": "metric",
          "attributes": {
            "name": "Point earn event from Appstle Loyalty"
          }
        }
      },
      "profile": {
        "data": {
          "type": "profile",
          "attributes": {
            "email": "jordan.lee@example.com",
            "properties": {
              "availablePoints": 1250.0,
              "vipTier": "Gold",
              "vipTierExpireDate": "2027-01-15",
              "lastActivityDate": "2026-11-10"
            }
          }
        }
      },
      "properties": {
        "emailSettingType": "POINT_EARN",
        "subject": "You earned 50 points",
        "heading": "You earned 50 points",
        "customer": {
          "id": 6789012345,
          "display_name": "Jordan Lee",
          "first_name": "Jordan",
          "last_name": "Lee",
          "token": "TOKEN",
          "vipTier": "Gold",
          "status": "Active",
          "availableCredits": 12.5,
          "lastActivity": 1794303000.000000000,
          "vipTierExpiredDate": 1799971200.000000000
        },
        "shop": { "name": "Example Store" },
        "availablePoints": "1250",
        "availableStoreCredits": "$12.50",
        "points": "50",
        "store_credit": "$50.00",
        "ruleName": "Product purchase",
        "tierName": "Gold",
        "suffixLabel": "Points",
        "redirectLink": "https://your-store.myshopify.com",
        "pointExpireDate": "2027-05-10",
        "vipTierExpireDate": "2027-01-15",
        "lastActivityDate": "2026-11-10",
        "vipTierPerks": ["Free shipping", "2x points"],
        "earnRuleSummaries": [
          {
            "ruleName": "Product purchase",
            "ruleDescription": "Earn 1 point for every $1 you spend",
            "iconUrl": "https://example.com/icon.png"
          }
        ],
        "rewardsSummaries": [
          {
            "note": "$5 off your order",
            "discount": "Get $5 off orders over $35",
            "discountType": "$",
            "points": "500",
            "iconUrl": "https://example.com/icon.png",
            "minSpendAmount": "$35.00"
          }
        ],
        "customerRewards": [
          { "code": "AL_XYZ123", "description": "$5 off your order" }
        ]
      }
    }
  }
}
```

A real event holds all of the properties of [Event properties](#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 %}`:

```liquid theme={null}
Hi {{ event.customer.first_name }},

You earned {{ event.points }} points for {{ event.ruleName }}.
You now have {{ event.availablePoints }} points.

{% for reward in event.customerRewards %}
  {{ reward.description }}: {{ reward.code }}
{% endfor %}

<a href="{{ event.redirectLink }}">Visit the store</a>
```

Property names are case sensitive. Preview the message with a test event before you set the flow live (see [Get started](#get-started)).

## Next steps

> [card] [Webhooks](https://developers.appstle.com/loyalty/webhooks.md)
>
> Receive loyalty events on your own server, with IDs and signatures.

> [card] [Shopify Flow](https://developers.appstle.com/loyalty/shopify-flow.md)
>
> Use Appstle Loyalty triggers and actions inside Shopify.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.