Skip to main content
Go to Apps → Klaviyo → Events in the Subtotal Dashboard. Create an event by choosing its trigger and Event name. Turn on Event delivery to send it when its conditions match.
Renaming an event creates a new Klaviyo metric. Update flows and segments that use the old name first.
Event names are configurable. Your Events page shows the exact names sent to Klaviyo.
Klaviyo data from before late September 2026 can hold repeat Connected an Account events for one connection. If the profile was collected before this connection existed, no Shared a Profile event is sent for the connection. The purchase trigger marks when your brand receives access to the purchase, which may differ from when Subtotal first collected it. 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.

Wait for the purchase to complete

Open the event settings for Purchase shared. Turn on Wait for the purchase to complete, then save the event. Wait for the purchase to complete is off by default. It applies separately to each purchase event or earning action. The event's other conditions, such as retailers and purchase dates, also apply. With the option on: If status is null, purchases from Amazon, Walmart, and Target wait because these retailers report status. Purchases from every other retailer send at share time. If a waiting purchase remains open or has no status, Subtotal sends it about 31 days after the purchase date. A purchase already past that deadline sends at share time. A delivery after the wait counts once, the same as a normal Purchase shared delivery. Waiting does not create an extra billable event. Simulated purchases from the Event Simulator always send at share time. With the option on, the event sends each purchase at most once, even when the purchase is shared again after a reconnect. With the option off, the event sends each qualifying purchase when it is shared.

Purchase event properties

status is the purchase status when the event is sent. A later status change sends no event; read it from GET /purchases/.
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

Account connection event properties

The Account connected, Account reconnected, Account disconnected, and Account needs reconnecting triggers use the following properties: Example: Connected an Account
Example: Reauthenticated Connection
Example: Disconnected an Account
Example: Unauthenticated Connection

Profile event properties

The Profile shared 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. Example: Shared a Profile
Example: Profile Updated
Some integrations send Purchased at Retailer for Purchase shared and Profile Created for Profile shared. Your Events page shows the names your integration sends.