Skip to main content
Marketo and HubSpot both bind a form instance to the page (or landing page template) it’s embedded on. allGood treats a form as its own capture target with a stable Form ID, and lets any number of pages point at it. Same goal, which is collecting submissions safely, but a different seam.

​
At a glance

What that changes in practice:
  • Reusing a form across campaigns doesn’t mean cloning it. Point another page at the same Form ID, the way you might already reuse a Marketo smart form or HubSpot module across templates that share one.
  • Editing fields updates every page using the form at once, rather than only the instance you opened. See Find where a form is used before making a change.
  • Markup and styling stay with your page, the same as a self-hosted Marketo or HubSpot form. allGood never renders or restyles it for you.
  • There’s no progressive profiling. The form itself always asks for the same fields; allGood doesn’t shorten or pre-fill it for a visitor it recognizes. The common case this covers in Marketo or HubSpot, which is not showing the form again to someone who already submitted, is still doable: a developer can have the page remember an accepted submission (for example, a flag in localStorage set when allGood reports the submission accepted) and swap in different content on a repeat visit. That’s custom script on your page, not a platform setting. See Adding a form to a page for how the page hears about an accepted submission.
  • Consent is a separate, reusable asset, not a setting on the form itself. See What a form is for how a form references a consent text, and Connect your consent platform to set one up.
Exact field names and settings in Marketo and HubSpot vary by subscription tier and account configuration, so use this table as a map between the two worlds, not a feature-for-feature spec.