When you activate an Antla flow, the corresponding flow is available in Klaviyo. Antla provides the starting event and event data; Klaviyo lets you build the rest of the customer journey.
Understand the Antla trigger
At the top of the Klaviyo flow, the trigger appears as an Antla campaign event followed by an identifier. Keep an Antla event as the trigger when the flow or template relies on Antla variables.
From that starting point, you can add Klaviyo actions such as:
email, SMS, or WhatsApp messages;
time delays;
conditional or trigger splits;
profile and list updates;
internal alerts;
webhooks; and
filters based on the customer’s Klaviyo profile or other events available in your account.
The screenshot shows an example split that checks recent checkout activity and routes everyone else down a second path. This is sample logic, not a required Antla configuration.
Edit the follow-up email
Open the Antla-created flow in Klaviyo.
Select the Virtual try-on follow-up email card.
Review the email name and status.
Under Subject and sender, select Edit to update the subject line, preview text, sender name, or sender address.
Under Template, select Edit to open the Klaviyo template editor.
The email-details panel also lets you:
create an A/B test;
switch between desktop and mobile previews;
enable Smart Sending;
enable UTM tracking; and
add message-level filters.
Customize the template
In the template editor, you can change the layout, copy, colors, buttons, images, and conditional blocks just as you would in another Klaviyo email. Antla’s event variables keep the content personalized for the shopper who triggered the flow.
Common customizations include:
displaying the shopper’s original try-on;
displaying one or more recommended try-on images;
linking images and buttons to tracked product URLs;
showing product titles and prices;
adding a discount only when one is present in the event; and
linking to the store, all-products collection, About page, News blog, or Contact page.
Build additional paths
After the Antla trigger, you can use Klaviyo data to create journeys such as:
remind shoppers who did not begin checkout;
change the message for shoppers who began checkout but did not order;
stop or redirect follow-up after a purchase;
send a different recommendation to a particular segment;
wait and send a second message if the first did not lead to the desired action; or
notify an internal team or another system through an alert or webhook.
Only use conditions backed by data that is actually present in your Klaviyo account. Events from other connected systems can participate in the logic when those integrations make the data available to Klaviyo.
Preview and test safely
Before making the flow live:
Preview the email on desktop and mobile.
Send an Antla test event so the template receives real event properties.
Verify that every dynamic image resolves.
Verify that each button and image uses the intended tracked URL.
Test paths for both matching and non-matching split conditions.
Confirm the flow and each message have the intended status.
If a field is blank, confirm that the flow is triggered by an Antla event and that the selected Antla email type supplies the referenced data.



