Troubleshooting email template error messages

You will learn

If you encounter errors or warnings in an email template, you may need to resolve them before sending your message. Search this resource for the error message or warning you’re encountering to find tips for resolving the issue.

Campaign sending warnings

• We found # blocks in your email that either still have the default text unmodified or are blank. Please review your email before continuing.
  If you encounter this warning, look for empty blocks or placeholder content (e.g., “This is a text block. Click here to edit it.”) in your template. Check the desktop and mobile versions of the template. If you can’t find an empty block or placeholder content, send a preview message to yourself and review it on both desktop and mobile. If the preview looks good, it’s safe to send the message and ignore this warning.
• Possible email content issues. It doesn’t look like there are any links in your email. Did you forget to add them to your email?
  This warning appears if your plain-text or custom HTML email doesn’t include any links. Review the message to make sure all content has been added, including links for any calls-to-action. If you do not want to include any links in your email (other than your unsubscribe link), you can ignore this warning.
• Unsubscribe link. No unsubscribe link found in this template. Klaviyo will automatically add an unsubscribe link when sending the email.
  This warning appears if you haven’t added an unsubscribe tag to your message (e.g., {% unsubscribe %} or {% unsubscribe_link %}). Add an unsubscribe link to avoid Klaviyo’s default footer being appended to your message.

Preview errors

When previewing a message, you may encounter this error message:

Message displayed without tags or variables
Fix invalid template tags or variables to preview the message with actual profiles and events.

This message means Klaviyo couldn’t render a template tag or variable. To locate the source of the error, check your message’s subject line and body content for variables, tags, or conditional statements (i.e., anything in your template surrounded by {{ }} or {% %}) that don’t follow the format outlined in the message personalization reference. Below are some tips for locating the error:

• Check both the desktop and mobile versions of your message.
• If your message contains a dynamic coupon, make sure the coupon name is correct, and that your coupon has been configured in the Coupons tab.

After correcting the issue, preview the message again with a profile or event that contains the data your template uses. Confirm that the variables populate before sending a test email.

Custom HTML template errors

• We couldn't find the following images: ... Make sure they are included in the zip file you uploaded.
  Check that you’ve spelled all image source paths correctly, and that they match the file names of the images you uploaded. If no image paths are provided in the error message, review your HTML file for empty background attributes (e.g., background=""). Remove empty background attributes, then upload the corrected HTML file again.
• An {% unsubscribe %} tag is required.
  Add a Klaviyo unsubscribe tag to your message footer to resolve this error.
• Could not parse the remainder: 'Z' from 'XYZ'.
  This error means Klaviyo couldn’t read part of a template expression. Check the expression quoted in the error for misplaced or repeated quotation marks, spaces in property names, or incorrect filter syntax. The problem can be inside {{ }} variables or {% %} tags. Refer to the message personalization reference for supported syntax and examples.

Catalog errors

If your template uses a catalog lookup tag, you may encounter the error Unable to find item with code: __. It may have been deleted.

If you see this error, it means we don't recognize the item ID included in the tag. Make sure that:

• You're previewing with an event that contains item IDs (if the item ID dynamically references event data).
• If the item ID comes from event data or a profile property, the reference is correctly formatted.
• The item ID in your tag, event data, or profile property matches an item in your Klaviyo catalog.

Shopify template errors

• Body html Liquid syntax error: Unknown tag 'unsubscribe'
  Body html Liquid syntax error: Unknown tag 'web_view'
  These errors, and other errors like them, mean that a Klaviyo-specific tag was added to your template before exporting it to Shopify. Shopify doesn’t support Klaviyo’s unsubscribe, manage preferences, or web view links. Remove those Klaviyo-specific links from the Shopify notification template before exporting it again.
• Body Html Liquid Syntax Error : Unknown tag "Load"
  This error indicates that the exported HTML contains a Klaviyo-specific tag that Shopify doesn’t support. If your Shopify notification template contains a Klaviyo product block, remove it, export your template’s HTML, and import it into Shopify.
• Body html Liquid syntax error: Unknown tag 'elsif'
  Body html Liquid syntax error: 'if' tag was never closed
  Body html Liquid syntax error: 'X' Tag Was Never Closed
  Many of Klaviyo’s Shopify notification templates include conditional statements, which make your message dynamic based on the customer’s order status, and loops, which repeat content for items in an order. If part of a statement or loop is deleted, you can see an error like the ones above.
  
  To resolve this, open the template in Klaviyo and restore the missing tags. Each {% if ... %} needs a matching {% endif %}, and each {% for ... %} needs a matching {% endfor %}. Keep {% elsif ... %} and {% else %} within their matching statement. If you intentionally remove a statement or loop, remove its entire block, including its contents, so no unmatched tags or item variables remain. Look for these opening, branching, and closing tags:
  • {% for item in...
  • {% endfor %}
  • {% if...
  • {% elsif...
  • {% else %}
  • {% endif %}

After making changes, export the updated template and import it into Shopify. Preview and test the notification in Shopify before saving it. Shopify notification variables populate in Shopify; a Klaviyo preview only lets you check the styling.