Skip to main content

Use Antla event variables in Klaviyo templates

A practical variable reference for generated images, products, tracked links, discounts, and event metadata.

Written by Aaron From Antla

Antla event variables let a Klaviyo email display the shopper’s generated try-on, recommended looks, product data, tracked store links, and optional discount information.

These variables work only in Klaviyo flows triggered by Antla events. In an unrelated flow or template, the values will be empty because the required event data is not available.

Open the variable reference

In Antla’s flow builder:

  1. Open the Send email card.

  2. Select View template variables.

  3. Copy the variable you need.

  4. Paste it into the appropriate field in the Klaviyo template editor.

Original try-on variables in Antla

Configure a dynamic recommended image

For a recommended look, configure the Klaviyo image block with matching variables:

  • Image source: {{ event.antla_looks.0.tryon_image_url }}

  • Alt text: {{ event.antla_looks.0.product_title }}

  • Link address: {{ event.antla_looks.0.product_url }}

A Klaviyo image block using Antla variables

Use the same look index for the image, title, product URL, and price so all fields describe the same recommendation.

Original try-on variables

Use these fields to show the look the shopper originally generated.

Variable

Value

{{ event.antla_original_tryon_image_url }}

Customer’s original generated try-on image URL

{{ event.antla_original_product.product_id }}

Shopify product ID

{{ event.antla_original_product.product_title }}

Product title

{{ event.antla_original_product.product_url }}

Tracked storefront URL for buttons and clickable images

{{ event.antla_original_product.product_image_url }}

Original Shopify product image URL

{{ event.antla_original_product.product_type }}

Shopify product type; may be empty

{{ event.antla_original_product.vendor }}

Product vendor; may be empty

{{ event.antla_original_product.price }}

Formatted price, including the currency symbol

{{ event.antla_original_product.price_min }}

Minimum product price as a number

{{ event.antla_original_product.price_max }}

Maximum product price as a number

{{ event.antla_original_product.currency_code }}

Store currency code, such as USD

{{ event.antla_original_product.currency_symbol }}

Store currency symbol, such as $

product_image_url is the normal Shopify catalog image. antla_original_tryon_image_url is the personalized image generated for the shopper.

First recommended look

Use index 0 for the first recommendation.

Variable

Value

{{ event.antla_looks.0.tryon_image_url }}

Generated try-on image for the first recommended product

{{ event.antla_looks.0.product_id }}

Shopify product ID

{{ event.antla_looks.0.product_title }}

Product title

{{ event.antla_looks.0.product_url }}

Tracked storefront product URL

{{ event.antla_looks.0.product_image_url }}

Original Shopify product image URL

{{ event.antla_looks.0.product_type }}

Shopify product type; may be empty

{{ event.antla_looks.0.vendor }}

Product vendor; may be empty

{{ event.antla_looks.0.price }}

Formatted price, including the currency symbol

{{ event.antla_looks.0.price_min }}

Minimum product price as a number

{{ event.antla_looks.0.price_max }}

Maximum product price as a number

{{ event.antla_looks.0.currency_code }}

Store currency code

{{ event.antla_looks.0.currency_symbol }}

Store currency symbol

Recommended-look variables in Antla

Additional recommended looks

Antla supports recommendation indexes from 0 to 5. Replace [index] with the number you need, and use the same number for every field belonging to that look.

{{ event.antla_looks.[index].tryon_image_url }}
{{ event.antla_looks.[index].product_id }}
{{ event.antla_looks.[index].product_title }}
{{ event.antla_looks.[index].product_url }}
{{ event.antla_looks.[index].product_image_url }}
{{ event.antla_looks.[index].product_type }}
{{ event.antla_looks.[index].vendor }}
{{ event.antla_looks.[index].price }}
{{ event.antla_looks.[index].price_min }}
{{ event.antla_looks.[index].price_max }}
{{ event.antla_looks.[index].currency_code }}
{{ event.antla_looks.[index].currency_symbol }}

For example, the third recommended look uses index 2:

{{ event.antla_looks.2.tryon_image_url }}
{{ event.antla_looks.2.product_title }}
{{ event.antla_looks.2.product_url }}

Tracked store links

Variable

Destination

{{ event.antla_store_url }}

Storefront home page

{{ event.antla_shop_url }}

Store’s all-products collection

{{ event.antla_about_url }}

About page

{{ event.antla_news_url }}

News blog

{{ event.antla_contact_url }}

Contact page

Use these event URLs for buttons and linked images when you want Antla’s tracked destination rather than a hard-coded URL.

Discount and event metadata

Variable

Value

{{ event.antla_flow_id }}

ID of the Antla flow that sent the event

{{ event.antla_discount.code }}

Discount code; may be empty

{{ event.antla_discount.percentage }}

Discount percentage; may be empty

{{ event.antla_test_event }}

Whether the event is a test event; also used internally by Antla-created Klaviyo flows

Store-link, discount, and event metadata variables in Antla

Show a discount only when it exists

Because discount fields can be empty, wrap discount copy in a Klaviyo conditional block:

{% if event.antla_discount.code %}
Use code {{ event.antla_discount.code }} for {{ event.antla_discount.percentage }}% off.
{% endif %}

Apply the same pattern to optional product values such as product_type or vendor if the design should hide the entire line when no value is present.

Variable checklist

Before activating the flow, confirm that:

  • the flow is triggered by the matching Antla campaign event;

  • every dynamic field keeps its opening and closing braces;

  • image, alt-text, link, title, and price fields use the same look index;

  • generated try-on images use tryon_image_url, not product_image_url;

  • clickable products use product_url;

  • optional fields are hidden conditionally when empty; and

  • the template has been tested with an Antla test event.

Did this answer your question?