With the Klaviyo integration, address errors trigger your own branded Klaviyo flows instead of (or in addition to) AddressHero's built-in emails.
Create a private API key in Klaviyo. The scopes must include Lists (Read & Write) and Events (Read & Write). Keys without the Lists scope are rejected, this is the most common connection error.
Add the key in AddressHero under Address Validation settings.
Choose which address errors should trigger your flow.
Create a new flow and select the trigger metric "Incorrect Shipping Information".
Note: the metric only appears in Klaviyo AFTER the first event was sent. Place a test order with a broken address if you cannot find it.
Build your email using the event parameters:
{{first_name}} and {{last_name}}
{{event.url}}: the link to the order status page where the customer corrects the address
{{event.address1}}, {{event.address2}}, {{event.city}}, {{event.zip}}: the original address
{{event.error}}: the specific issue
Video tutorial: Klaviyo setup (Loom)
Work through this list, it resolves nearly all cases:
Recreate the connection with a NEW private API key, checking the scopes (Lists Read & Write, Events Read & Write).
Confirm the error types are activated in AddressHero's Klaviyo settings.
Check the flow uses the metric "Incorrect Shipping Information" and is live, not in draft.
Place a test order with a broken address and watch the metric in Klaviyo.
If our logs show the event was sent but Klaviyo did not process it, the issue sits between Shopify and Klaviyo; contact us via support and we will check the logs for your specific order.
Two honest recommendations from our support experience:
AddressHero's own notification emails cover the same use case with less moving parts. If you do not need Klaviyo's branding and segmentation, the native emails are the more robust choice. See Customer emails and on-hold orders.
Avoid double messaging: if automatic correction is active, the error is often already fixed by the time an email would arrive. Do not send correction emails for error types that are auto-corrected, this confuses customers.
Related articles