What are event and profile properties?
Skio automatically sends subscription events and customer data to Klaviyo via event metrics, giving you the properties you need to build targeted flows and segments. This guide shows you which properties are available and how to use them in common subscription flows.
How Skio sends data to Klaviyo
.png?sv=2022-11-02&spr=https&st=2025-12-23T15%3A03%3A01Z&se=2025-12-23T15%3A17%3A01Z&sr=c&sp=r&sig=dy6VitStpvGjWj%2FMy2zEcQAJhShQ6OvK2%2BWWcc8FUTc%3D)
Example: When a new subscription is created, Skio sends a subscriptionCreated event metric that includes three types of properties: event properties (like nextBillingDate), profile properties (customer information), and custom properties.
Skio sends three types of data to Klaviyo with each event:
Event properties: Sent each time a subscription event occurs (like a renewal, cancellation, or product swap). These are tied to specific moments in the subscription lifecycle.
Profile properties: Updated on the customer's Klaviyo profile and persist across all events. These reflect the customer's current subscription state.
Custom properties: These properties may change depending on what type of event is being sent.
Learn more about how to add personalization to your flows in Klaviyo here.
Common Klaviyo flows and the properties you need
Renewal reminder flows
Send reminders before a subscription renews to reduce surprises and payment failures.
Property | Type | Description | Example use |
|---|---|---|---|
| Event | When the subscription will renew | Trigger flow 3 days before this date |
| Event | Days until next renewal | "Your order ships in |
| Event | Total order value before shipping | "Your upcoming charge: $ |
| Event | Shipping cost | Show total including shipping |
| Event | Product in the order | Remind them what's coming |
| Event | Direct link to Customer Portal. Alternatively, use a Quick Action link. | "Update your order: |
Flow structure example:
Trigger: Skio renewal event
Time delay: Wait until 3 days before
nextBillingDateEmail: "Your [product] ships in 3 days"
Winback flows (post-cancellation)
Re-engage customers who cancelled their subscription.
Property | Type | Description | Example use |
|---|---|---|---|
| Event | Timestamp of cancellation | Trigger flow immediately or with delay |
| Event | Number of orders before cancelling | Segment by loyalty: "Thanks for 6 orders with us" |
| Event | What they were subscribed to | Personalize: "Missing your [product]?" |
| Profile | Whether customer has any cancelled subs | Use in segments to exclude active subscribers |
| Profile | Total cancelled subscriptions | Identify high-risk customers |
Flow structure example:
Trigger: Skio cancellation event
Time delay: Wait 7 days
Conditional split: If
skio_hasActiveSubscription= false (they have no other active subs)Email: Winback offer with incentive
Payment failure recovery flows
Recover revenue when a subscription payment fails.
Property | Type | Description | Example use |
|---|---|---|---|
| Event | Subscription Status | Trigger when status = "FAILED" or "PAST_DUE" |
| Profile | Whether customer has failed subs | Segment for follow-up campaigns |
| Profile | Number of failed subscriptions | Prioritize high-value recovery |
| Event | Direct link to update payment | "Update your payment method: [link]" |
| Profile | Whether backup payment exists | Split messaging based on payment status |
| Event/Profile | Customer email | Coordinate with email dunning |
Flow structure example:
Trigger: Skio payment failed event
Email 1: Friendly reminder to update payment
Wait 3 days
Email 2: IMPORTANT - update your payment method
All event properties sent to Klaviyo
Event properties
These variables can be used as Trigger filters and splits in addition to being used to display dynamic information about the event in a message.
Learn more about trigger filters here.
Learn more about using variables to personalize your messages here.
Property | Brief description |
|---|---|
| Unique identifier for the subscription associated with the event |
| Platform-level ID of the subscription line related to the event |
| Subscription status at the time the event occurred |
| Additional context explaining the subscription status |
| Next scheduled billing date at the time of the event |
| Timezone-adjusted renewal timestamp |
| Number of days until the next renewal when the event fired |
| Billing interval unit (e.g., week, month) |
| Number of intervals between billings |
| Number of billing cycles completed at event time |
| Price of the product involved in the event |
| Quantity of the product involved in the event |
| Total amount associated with the event |
| Net subscription total after discounts |
| Net subscription total in the site’s currency |
| Shipping price applied at the time of the event |
| Total discount amount applied at event time |
| Standard discounts applied during the event |
| Surprise discounts applied during the event |
| Indicates whether a surprise discount was applied |
| Currency code used for pricing (e.g., USD, CAD) |
| Currency symbol used for display |
| Store’s base currency code |
| Name of the product involved in the event |
| Name of the product variant involved |
| SKU of the product variant |
| Platform-level product ID |
| Platform-level product variant ID |
| Product image URL |
| Product variant image URL |
| Indicates whether the product was a one-time upsell |
| Indicates whether the subscription is prepaid |
| Indicates whether the prepaid subscription is a gift |
| Indicates whether the subscription was temporarily paused |
| Indicates whether the item was skipped |
| Indicates whether the item was out of stock |
| Original order ID associated with the subscription |
| URL used by customers to manage their subscription |
| Secure token used for authenticated actions related to the event |
| Storefront user ID associated with the event |
| Platform-level customer ID associated with the event |
| Customer email address associated with the event |
Profile properties
Property | Brief description |
|---|---|
| Customer’s first name |
| Customer’s last name |
| Customer email address |
| Customer phone number |
| Primary street address |
| Secondary street address |
| City |
| State or region |
| Postal or ZIP code |
| Country |
| Customer locale or language setting |
| Customer’s time zone |
| Geographic latitude, if available |
| Geographic longitude, if available |
| Unique identifier for the customer profile |
Custom properties
These variables can be used as Conditional filters and splits in addition to being used to display dynamic information about the event in a message.
Learn more about conditional filters here.
Learn more about using variables to personalize your messages here.
Property | Brief description |
|---|---|
| Storefront user ID tracked by Skio |
| Indicates whether the customer has an active subscription |
| Total number of active subscriptions |
| Indicates whether the customer has prepaid subscriptions |
| Total number of prepaid subscriptions |
| Indicates whether the customer has paused subscriptions |
| Total number of paused subscriptions |
| List of paused subscriptions |
| Indicates whether the customer has failed subscriptions |
| Total number of failed subscriptions |
| List of failed subscriptions |
| Indicates whether the customer has cancelled subscriptions |
| Total number of cancelled subscriptions |
| List of cancelled subscriptions |
| Total quantity of items across all subscriptions |
| Next billing date across subscriptions |
| Total number of completed billing cycles |
| ID of the active subscription that will bill next |
| Indicates whether a backup payment method exists |
| Secure token for authenticated subscription actions |
| Available Skio credits balance |
| Monetary value of Skio credits |
| Currency code used for Skio credits |
Conditional filters & splits
Property | Brief description |
|---|---|
| Active subscriptions used for conditional logic and splits |
| Paused subscriptions used for conditional logic and splits |
| Failed subscriptions used for conditional logic and splits |
| Cancelled subscriptions used for conditional logic and splits |
| Subscribed product titles used for segmentation |
| Subscribed variant titles used for segmentation |
| Subscribed SKUs used for segmentation |