3. Postflows Event Properties Reference
Every event Postflows sends to Klaviyo or Omnisend includes a set of properties you can use to personalize email content. This article lists all available properties and how to reference them in your email templates.
Before using any property below, always confirm it against the live event data in your email platform's preview tool first. In Klaviyo, that's Preview Email β the "All properties" panel on the right. In Omnisend, it's the event data shown in Preview & test. The tables below are a reference guide, but the live payload in your own account is the source of truth.
How to use properties
In Klaviyo, reference properties directly under event:
{{ event.customer.first_name }}
{{ event.tracking.tracking_number }}
{{ event.order.name }}In Omnisend, reference properties using double square brackets. Profile data, like the customer's name, is accessed under contact instead of being nested under event:
[[contact.first_name]]
[[event.order.name]]
[[event.tracking.tracking_number]]Order details
Customer details
Shipping address
Billing address
Same structure as shipping address, under billing_address.*.
Line items
Line items is an array. In Klaviyo, iterate using {% for item in event.line_items %}.
Tracking details
Event metadata
Tips
Linking to your tracking pagetracking.url is the Postflows tracking page URL. Use it to send customers to their branded tracking experience:
<a href="{{ event.tracking.url }}">Track your package</a>Linking directly to the carrier Use tracking.carrier_link for a direct link to the carrier's tracking page (UPS, FedEx, etc.):
<a href="{{ event.tracking.carrier_link }}">Track on carrier site</a>Note: carrier_link is null for order_created events β wrap it in a conditional.
Estimated delivery date tracking.estimated_delivery_date is not always available - depends on carrier. Wrap in a conditional in Klaviyo:
{% if event.tracking.estimated_delivery_date %}
Estimated delivery: {{ event.tracking.estimated_delivery_date }}
{% endif %}