Back to Documentation

Klaviyo Best Practices

How our tool's analysis aligns with the Klaviyo email platform to ensure your code and content are fully compliant and optimized.

Personalization Merge Tags
Klaviyo uses specific Django-style merge tags for personalization, like `{{ first_name|default:'Friend' }}`. Our tool checks for these to ensure your personalization will work correctly.
Klaviyo Unsubscribe Tag
The most reliable way to create a compliant unsubscribe link in Klaviyo is by using the `{% unsubscribe %}` tag. This tag generates a unique link for each recipient.
View in Browser Link
To allow users to view the email in a web browser, Klaviyo uses the `{% web_view_url %}` tag. This is the recommended method over a static link.
CSS Inlining
Klaviyo automatically inlines CSS from `<style>` blocks in your email's `<head>`. Our tool recommends consolidating CSS into a style block, which is a best practice that works perfectly with this feature.
Section-Based Editing
For users of Klaviyo's visual editor, our AI can rewrite content section-by-section. This allows you to improve the copy for one block at a time without altering the entire template.
No Scripts or Forms
Like all major email clients, Klaviyo strips out any `<script>`, `<iframe>`, or `<form>` tags for security reasons. Our analysis flags these as critical errors.