Your subscribe form on a Webflow site

An Embed element is where the snippet goes. Drag one into the page in the Webflow Designer, paste both lines of the script embed into it, save, and publish: the form renders on the published site in your newsletter’s colour and body font.

Copy either snippet from Settings, then the Subscribers tab, which shows both with a copy button and a preview of the form. Webflow serves an Embed element’s markup as written, so neither snippet needs adjusting first.

Where the HTML goes

An Embed element, for a form in a particular place on a particular page. Webflow’s site-wide custom code fields do the same job for every page at once, with the script tag in the footer field and a <div data-issuemint></div> wherever a form belongs.

Both routes end in the same place. One script tag mounts a form into every container on the page, so a site-wide script tag plus a container in three page templates gives you three forms and one script.

Which of the two snippets to use

The script embed, in nearly every case. It confirms the signup underneath the button instead of navigating away from your site, which on a designed page is the difference between a small message and losing the reader to our thank-you page.

The plain HTML form is the one to paste when you intend to restyle the whole thing, because it is ordinary markup that takes your own classes. It needs no JavaScript at all, and it posts a normal form, so the reader does leave the page for a moment.

Do not put it inside a Webflow form block

Webflow’s Form Block is itself a <form>, and a form inside another form is not something browsers handle predictably. The plain HTML snippet’s own <form> is discarded outright when the page is parsed, and the script embed, which builds a form of its own inside the container, ends up nested in Webflow’s.

Why the canvas shows an empty box

Custom code does not run in the Designer. The Embed element reserves its space on the canvas and stays blank, because Webflow deliberately does not execute pasted script while you are editing.

Publish the site, or open the published address, and the form appears. This is worth knowing before you spend an afternoon debugging a snippet that was working the whole time. If the form is still missing on the published site, view the page source and look for the container: a missing data-issuemint container is the one failure that produces no message anywhere, since a broken embed must never break the page hosting it.

What arrives on your list

Signups from either snippet reach your Issue Mint list within a second or two, marked as coming from the embed, which keeps them separable from an import or a signup on the hosted site every newsletter gets.

A reader whose address has no mail server behind it is refused in the field rather than accepted and quietly dropped, so the numbers on your list stay honest. Whether the address then needs confirming is up to your double opt-in setting, which applies to both snippets equally.