The embeddable subscribe form
Two snippets, both public, both safe to paste anywhere. Signups from either arrive on your list tagged as coming from the embed.
-
The script embed
The two lines of HTML that put a subscribe form on any website, what the script renders, where the colour comes from, and what a reader sees after signing up.
-
The plain HTML form
The subscribe form that needs no JavaScript, quoted in full, what its hidden honeypot field is for, and how to send a reader to your own page afterwards.
-
What you can change, and what you cannot
The honest scope of the embedded form's customisation: two attributes, colour and font from your branding, and the route to take if you want your own design.
-
Your subscribe form on a WordPress site
Where the Custom HTML block sits in WordPress, which of the two Issue Mint snippets belongs in it, and what WordPress.com filters out on plans without custom code.
-
Your subscribe form on a Ghost site
Where Ghost's HTML card and code injection fields take the Issue Mint snippet, why code injection on its own shows nothing, and what the emailed version of a post does.
-
Your subscribe form on a Webflow site
Where an Embed element takes the Issue Mint snippet in the Webflow Designer, why the canvas shows an empty box, and the nested form mistake to avoid.
-
Your subscribe form on a Framer site
Where Framer's embed component takes the Issue Mint snippet, how much height to leave under the button, and what to do when the form is missing after moving pages.
-
Collecting signups from a Notion page
Notion runs neither Issue Mint snippet, so this page covers what does work: a link to your newsletter's own site, an embed block, or a builder with a code field.
-
Your subscribe form on a Squarespace site
Where a code block takes the Issue Mint snippet on Squarespace, what to do on a plan without code blocks, and why the block looks empty while you are editing.
Try it on your own list.
14 days, every feature, no card. Sending works from the moment you sign up.
Start your trial