LoopAware

Embeds

Inline subscribe forms for landing pages

LoopAware's subscribe script can render an inline form with copy and display options, so a launch page can collect interest without building a custom backend endpoint.

Why inline matters

Some pages need a subscriber form in the body, not a floating widget. Inline mode keeps the form where the offer appears while still using LoopAware's public subscription endpoint and subscriber dashboard.

<script defer src="https://loopaware.mprlab.com/subscribe.js?site_id=YOUR_SITE_ID&amp;mode=inline"></script>

Configurable form details

Mode and accent

Render inline and set an accent color that matches the surrounding section.

CTA and messages

Customize button text plus success and error copy for the page context.

Name field choice

Collect only email when speed matters, or include name when follow-up needs it.

Limitations

  • The form captures subscriber interest; it does not send newsletter campaigns.
  • Allowed-origin validation still controls where public subscription requests can come from.
  • Embedded copy should match the page's privacy and communication expectations.

Best fit

Use this on launch pages, product waitlists, and documentation sign-up blocks where the form should live in the page flow.

Implementation checklist

  • Confirm the LoopAware site and public origin that will host the subscriber form or confirmation links.
  • Decide how pending, confirmed, unsubscribed, exported, and deleted subscriber records should be handled by the operator team.
  • Test one subscription path end to end before adding the form to every page that needs list growth.

Common questions

When should teams use this inline subscribe forms guide?

Embed LoopAware inline subscribe forms with mode, accent, CTA, success, error, and name-field options for public landing pages. It is a fit when subscriber capture needs to live beside feedback, traffic, and team access instead of in a disconnected list tool.

What should teams verify after setup?

Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.

Logging out...

Logging out...