Your subscribe form on a Squarespace site

A code block is where the snippet goes on Squarespace. Add one to the page, paste both lines of the script embed into it, save, and the form appears on the live page in your newsletter’s colour and body font.

Copy either snippet from Settings, then the Subscribers tab, where each has a copy button and a preview of the form beside it. Squarespace publishes a code block’s markup as written, so nothing needs escaping first. Pointing a domain you bought at Squarespace at your newsletter is a separate job with its own records.

Where the HTML goes

A code block, for a form in one place on one page. Squarespace’s code injection fields, under its advanced settings, do the same job site-wide: the script tag in the footer field, and a <div data-issuemint></div> in a code block wherever a form belongs.

The container decides where the form appears and the script tag only has to exist once. Two copies of the script tag on the same page can both reach for the same container before either finishes, which is how one paste becomes two forms.

Which of the two snippets to use

The script embed, if the page is one you want readers to stay on. The confirmation appears under the button, so nobody is sent off your site mid-visit.

The plain HTML form is the choice when you would rather nothing of ours ran on the page. It posts like any form and sends the reader to Issue Mint’s thank-you page afterwards, and the redirect setting cannot point them back to your Squarespace site, because it only accepts your newsletter’s own addresses.

If your plan has no code block

Code blocks and code injection are a paid feature on Squarespace, and which tier includes them has moved around over the years, so it is worth checking yours before planning around either snippet.

Why the block looks empty while you are editing

Squarespace does not run a code block’s script while you are in the editor, so the space stays blank or shows a note in its place. Save, then view the live page, and the form is there.

Some older 7.0 templates add a second version of the same confusion. They load pages without a full refresh, and Issue Mint’s script mounts when a page loads rather than watching for a form that turns up later. If the form appears on a hard reload but not when you click through the site’s own navigation, that is what you are looking at, and turning off the template’s Ajax loading option settles it.

What arrives on your list

Signups from either snippet reach your list within a second or two, marked as coming from the embed, so a Squarespace page’s signups stay distinguishable from an import or from your own site’s form.

An address whose domain has no mail server is refused in the field rather than accepted and dropped later. Whether the rest need to confirm before they count is set by your double opt-in preference, which the form on a Squarespace page follows exactly as your own site does.