PlainFunnels Categories

Home / Categories / Blog

Can I put an opt-in form inside a blog post?

Short answer

Yes, through a Raw HTML block. The form itself is built as an Inline Form or Popup Form step inside a sales funnel, and its script is pasted onto the blog page.

Why it takes two steps

The form is not built on the blog. It is built as a step inside a sales funnel, and only the finished form is carried across to the blog page as a script.

That is systeme.io's documented route and there is no shorter one in its blog articles.

Step one, build the form

  1. Open a sales funnel and click Create step.
  2. Choose Inline Form for a form that sits in the page, or Popup Form for one that opens over it.
  3. Pick a template, then open the page editor.
  4. Drag a Form input element in and set its Input type. Add as many fields as the form needs.
  5. Set what the button does when it is submitted, then save changes.

A form has to hold at least one Form input. For it to capture anybody at all, one of those inputs has to be an Email field and the button's action has to be Submit form.

Step two, put it on the blog

  1. Go back to the step configuration of the form and click Script.
  2. Click Copy link to clipboard.
  3. Open the blog page in the editor and drag a Raw HTML element to the spot the form should occupy.
  4. Open its settings, click Edit code, paste, and click Save.
  5. Save changes in the editor before leaving the page.

The popup version

A popup form reaches the blog the same way, and can be shown two ways.

  • Automatically, after a delay set in the editor in seconds. The blog side of it is identical to an inline form: copy the script, paste it into a Raw HTML element.
  • On a click. The step configuration offers Create a Link instead. Type the words that should be clickable, copy the link to the clipboard, and paste that into a Raw HTML element on the blog page.

Putting one under every post at once

Adding the Raw HTML block to a single post puts the form on that post alone. The post layout is the master template for posts, and anything added there appears on every one of them, so the block belongs there if the form is meant to be permanent.

The blog layout does the same job for every blog page as well as every post. The trade is that an element added to a layout can only be edited back inside that layout's own editor.

The rule that catches people out

Raw HTML does not render in Preview mode. It appears on the live page only, so a blank gap where the form should be is not evidence that anything failed.

Did this answer your question?