The Email Love Figma Plugin automatically converts your unsubscribe links into the correct merge tags for your email service provider (ESP). This means you don't have to memorize different syntax for each platform. Just use our simple convention and we'll handle the rest.
How It Works
The plugin looks for any link in your design that points to unsubscribe.com. When you export your email, it automatically swaps that link for the correct unsubscribe merge tag for your chosen ESP.
The link is what matters, not the text around it. So this works whether the link is on the word "Unsubscribe," a button labeled something like "Manage preferences," or even an icon. As long as it points to unsubscribe.com, it gets converted on export.
Supported Platforms
This automatic conversion works with all our out-of-the-box integrations, including:
- Braze
- Iterable
- Klaviyo
- Mailchimp
- And more
Each platform has its own specific unsubscribe syntax, and the plugin handles the translation for you.
Step-by-Step Instructions
Option 1: Manual Setup
- Add your unsubscribe text in your footer (or anywhere in your email)
- Highlight the word "Unsubscribe" (or select your button or icon)
- Link it to:
unsubscribe.com
- Export your email and select your ESP integration
- The plugin automatically converts the link to your ESP's unsubscribe merge tag
Option 2: Use Our Pre-Built Footers
The fastest way to add an unsubscribe link is to use one of our standard footer components:
- Open the Email Love plugin in Figma
- Navigate to the Footer section
- Choose any footer component you like
- Insert it into your design
All our pre-built footers already include the word "unsubscribe" linked to unsubscribe.com, so you're ready to export immediately.
Example: Exporting with Braze
- Select your email frame in Figma
- Open the Email Love plugin
- Choose Braze from the ESP dropdown
- Click Export or Copy Code
- The plugin converts
unsubscribe.com→ Braze's unsubscribe merge tag
The same process works for any of our supported integrations.
Best Practices
Placement: While you can technically place the unsubscribe link anywhere in your email, it's best practice (and often legally required) to include it in the footer.
Visibility: Make sure your unsubscribe link is easy to find and read. Use a reasonable font size and sufficient color contrast.
Bring Your Own Tag: If you already know your ESP's unsubscribe merge tag, you can link directly to it in Figma and the plugin will keep it as-is on export. See Advanced below. And if you'd rather paste the merge tag in manually after export, that's totally fine too. The automatic conversion is just there to save you time.
Customization
You can customize:
- The styling of the unsubscribe text (font, color, size)
- The placement within your email
- The surrounding text (e.g., "Click here to unsubscribe")
Just make sure the link points to unsubscribe.com (or, if you're using your own tag, your ESP's unsubscribe merge tag).
Advanced: Bring Your Own Merge Tag
Most people should just link to unsubscribe.com and let the plugin handle the conversion. But if you want a specific merge tag, you can type your ESP's unsubscribe tag directly into the link field in Figma. The plugin recognizes the common unsubscribe tags for each ESP and will preserve yours exactly on export, instead of replacing it with our default.
For example:
- Iterable:
{{hostedUnsubscribeUrl}}
- Braze:
{{${email_unsubscribe_url}}}
…or the documented unsubscribe merge tag for your platform (Klaviyo, Customer.io, Mailchimp, HubSpot, Salesforce Marketing Cloud, and more).
A few things to keep in mind:
- Figma may automatically add
https://in front of your tag. That's fine. The plugin removes it for you on export.
- Make sure the tag matches the ESP you're exporting to. A Braze tag won't work on an Iterable export.
- If you leave the link as
unsubscribe.cominstead, the plugin simply inserts the standard merge tag for your ESP, so existing emails keep working exactly as before.
Need Help?
If you have questions about how unsubscribe links work with the plugin:
- Join our Discord server and ask in the support channel
- Contact us via email or Slack (for Enterprise customers)
Powered by