Events

Go to Apps → Klaviyo → Events in the Subtotal Dashboard. Create an event by choosing its trigger, name, and delivery status.

Renaming an event creates a new Klaviyo metric. Update flows and segments that use the old name first.

Trigger	Suggested name	Sent when
Purchase created	Shared a Purchase	Subtotal collects a matching purchase
Account connected	Connected an Account	A customer successfully connects a retailer account. Klaviyo records this event once per connection. Events recorded before late September 2026 may include repeats from customers who signed in again on the same connection. It is also sent for each new connection.
Account reauthenticated	Reauthenticated Connection	A customer signs in on a connection that previously lost authentication or was disconnected. It is sent on every later sign in.
Account disconnected	Disconnected an Account	The connection is disconnected by the customer or by your application through the API.
Connection needs reauthentication	Unauthenticated Connection	A retailer connection loses authentication
Profile created	Shared a Profile	Subtotal first collects the profile for a retailer account. If the profile was collected before this connection existed, no Shared a Profile event is sent for the connection.
Profile updated	Profile Updated	A previously collected retailer account profile changes

Event names are configurable. Your Events page shows the exact names sent to Klaviyo.

You can limit any event to selected retailers. Purchase events can also be filtered by UPC, brand, or purchase date, and multiple conditions can match either all or any conditions. For purchase events, choose which purchase dates to send relative to when the account was linked:

Include all history
New purchases only
Include purchases up to a number of days before linking

Changes affect future deliveries and do not resend past events. Deleting an event does not remove events already in Klaviyo.

Purchase event properties

Key	Type	Description
`purchase_id`	string	Identifier for the purchase
`retailer`	string or null	Identifier for the retailer where the purchase was made
`date`	string or null	Purchase date and time in ISO 8601 format
`item_count`	integer	Number of items in the purchase
`subtotal`	number or null	Purchase subtotal
`tax`	number or null	Sales tax paid
`total`	number or null	Grand total paid by the customer
`brands`	array of strings	Unique brands among the purchase items available to your account, with lowercase letters and hyphens in place of spaces
`upcs`	array of strings	UPCs of the purchase items available to your account

When priced items are available, purchase events set Klaviyo’s monetary value field to the value of the purchase items available to your account. This may differ from the receipt total.

Example: Shared a Purchase

{
  "purchase_id": "01KJ8N2D4F6G8H0J1K3M5P7QRS",
  "date": "2026-09-24T18:42:11",
  "total": 40.78,
  "tax": 2.31,
  "subtotal": 38.47,
  "item_count": 2,
  "upcs": [
    "012345678905",
    "098765432105"
  ],
  "brands": [
    "example-foods",
    "sample-snacks"
  ],
  "retailer": "walmart"
}

Account connection event properties

The account connected, reauthenticated, disconnected, and needs reauthentication triggers use the following properties:

Key	Type	Description
`connection_id`	string	Identifier for the connection
`retailer`	string	Identifier for the retailer
`link_url`	string, optional	Link the customer can use to reconnect; included on disconnected and needs reauthentication events when a Link URL is configured

Example: Connected an Account

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "retailer": "walmart"
}

Example: Reauthenticated Connection

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "retailer": "walmart"
}

Example: Disconnected an Account

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "retailer": "walmart",
  "link_url": "https://link.subtotal.com/example?connection_id=01KJ8M4R7G2H9N5Q3T6V8W0XYZ"
}

Example: Unauthenticated Connection

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "retailer": "walmart",
  "link_url": "https://link.subtotal.com/example?connection_id=01KJ8M4R7G2H9N5Q3T6V8W0XYZ"
}

Profile event properties

The profile created and profile updated triggers carry the same properties. A profile update is sent when the stored identity collected from the retailer changes, such as the customer’s name, email address, mobile number, postal code, or retailer account creation date. New purchases alone do not trigger a profile update, although the latest purchase metrics are included whenever a profile event is sent.

Key	Type	Description
`connection_id`	string	Identifier for the connection
`first_name`	string or null	Customer’s first name
`last_name`	string or null	Customer’s last name
`email`	string or null	Email address collected from the retailer account. It can differ from the email that identifies the Klaviyo profile.
`mobile`	string or null	Mobile number collected from the retailer account. It is not used to identify the Klaviyo profile.
`postal_code`	string or null	Customer’s postal code
`account_created_date`	string or null	Retailer account creation date in ISO 8601 format
`total_purchases`	integer	All time number of purchases on the connected account
`last_purchase_date`	string or null	Most recent purchase date in ISO 8601 format
`brand_purchases`	integer	Number of those purchases shared with your account. For accounts with brand scoped access, these purchases include your brands.
`last_brand_purchase_date`	string or null	Most recent shared purchase date in ISO 8601 format
`brand_purchase_rate`	number	`brand_purchases` divided by `total_purchases`, from `0.0` to `1.0`

Example: Shared a Profile

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "first_name": "Jordan",
  "last_name": "Lee",
  "email": "jordan.lee@example.com",
  "mobile": "+12025550142",
  "postal_code": "84101",
  "account_created_date": "2024-03-12T09:30:00+00:00",
  "total_purchases": 24,
  "last_purchase_date": "2026-09-24T18:42:11Z",
  "brand_purchases": 6,
  "last_brand_purchase_date": "2026-09-24T18:42:11Z",
  "brand_purchase_rate": 0.25
}

Example: Profile Updated

{
  "connection_id": "01KJ8M4R7G2H9N5Q3T6V8W0XYZ",
  "first_name": "Jordan",
  "last_name": "Lee",
  "email": "jordan.lee@example.com",
  "mobile": "+12025550142",
  "postal_code": "84101",
  "account_created_date": "2024-03-12T09:30:00+00:00",
  "total_purchases": 24,
  "last_purchase_date": "2026-09-24T18:42:11Z",
  "brand_purchases": 6,
  "last_brand_purchase_date": "2026-09-24T18:42:11Z",
  "brand_purchase_rate": 0.25
}

Older event names

If your integration was connected before these names changed, it may still send Purchased at Retailer and Profile Created. Your Events page shows the names in use.

Documentation

Platform

Developers

Integrations

Guides

Purchase event properties

Account connection event properties

Profile event properties

​Purchase event properties

​Account connection event properties

​Profile event properties

Purchase event properties

Account connection event properties

Profile event properties