Your subscribe form on a Framer site

Framer’s embed component, set to take HTML rather than a URL, is where the snippet goes. Paste both lines of the script embed into it, publish, and the form renders in your newsletter’s colour and body font.

Copy either snippet from Settings, then the Subscribers tab, where both sit with a copy button and a preview of the form. Framer serves what you paste, so no part of either snippet needs changing for it.

Where the HTML goes

An embed component, for a form in one place on one page. Framer’s site-wide custom code fields do the same for every page, with the script tag at the end of the body and a <div data-issuemint></div> in whichever components should show a form.

The container is the part that decides where the form appears. One script tag mounts a form into every container on the page, so there is no reason to paste the script more than once, and two copies loading together can put two forms in the same place.

Which of the two snippets to use

The script embed. It keeps everything in one place: the confirmation appears under the button, and nobody is sent to a thank-you page on our domain halfway through looking at your site.

The plain HTML form still works if you want no script of ours involved, and it needs no JavaScript from anybody. The trade is the navigation: the reader leaves your page for Issue Mint’s thank-you page and has to come back.

Leave room under the button

The form grows by a line when somebody uses it. A short message appears underneath, saying either that the reader is on the list or that a confirmation email is on its way, and an embed sized exactly to the unused form clips that message out of sight.

If the form is missing after moving between pages

Issue Mint’s script mounts when the page loads and does not watch for containers added afterwards. It marks each container it has filled, then stops, which keeps it cheap and stops it fighting with the rest of your page.

So if the form is there after a reload but absent when you arrive from another page, that page was reached without a full load and the script never ran for it. Reload once to confirm that is what you are looking at. Putting the form somewhere readers land on directly, or in a site-wide footer container, avoids the question entirely.

What readers get on your list

Signups from either snippet arrive within a second or two, marked as coming from the embed, and go onto the same list your issues go to, since sending is included from the day you sign up with nothing to configure first.

An address whose domain cannot receive email is refused in the field, so a typo is fixed while the reader is still looking at it rather than turning into a confirmation email that bounces. Whether an address needs confirming at all is set by your double opt-in preference, which applies to both snippets.