Skip to main content

Personalize Klaviyo emails with Tie event properties

T
Written by Tim Hughes

Tie passes product, cart and checkout details into Klaviyo as event properties, so a flow email can show exactly what a shopper viewed or left in the cart without you maintaining a product catalog by hand.

Events that carry product and cart data

Event

What you can show

Tie View Item

The product they viewed

Tie Add to Cart

The product they added

Tie Started Checkout

The items in their cart and a link back to checkout

Flows for new shoppers use the Tie Prospect version of each event, which carries the same properties.

Properties you can use

Property

What it holds

ProductName

Product name

ImageURL

Product image

Price

Price

Quantity

Quantity

Brand

Brand

ProductID

Product ID

Categories

Product categories

Items

Every item in the cart

ItemNames

The names of every item in the cart

CheckoutURL

A link back to the shopper's checkout

Each event carries the properties that apply to it, and availability can vary with your storefront setup. Event properties are available only inside flows triggered by that same event.

How to personalize an email in Klaviyo

  1. Go to Flows and open a flow triggered by a Tie event, for example Tie Add to Cart.

  2. Click an email in the flow and select Edit Email.

  3. Add a text, image or button block.

  4. Click Personalization, choose Event Properties, and pick the property. Klaviyo inserts the right tag for you.

  5. Save the email.

Showing every item in the cart

For a cart or checkout with several products, use a table block with dynamic rows pointed at event.Items, so each product gets its own row. Preview the email to confirm each row shows the product name and image.

Example tags

Product name, with a fallback:

Still thinking about {{ event.ProductName|default:"it" }}?

Product image:

<img src="{{ event.ImageURL }}" alt="{{ event.ProductName }}">

Link back to checkout:

{{ event.CheckoutURL }}

Property names are case sensitive, so ProductName works and Product Name does not. Always include fallback content so a field is never empty.

Validate before sending

  1. Trigger the flow with a test profile.

  2. Open the flow email and click Preview, then Preview as Contact.

  3. Select a profile with recent Tie events.

  4. Confirm the product and cart data renders correctly.

If something is blank, check that the email sits in a flow triggered by the same event, that the event happened recently for the test profile, that the property names in your tags match exactly, and that every dynamic field has a fallback.

Related

Did this answer your question?