How to Redirect a HubSpot Form to Different URLs Based on the Answer

This is one of the most common HubSpot CMS questions: "I have a form with a country dropdown — how do I send UK submitters to one page and everyone else to another?" It sounds like it should be a setting. It isn't, quite, but it's a few lines of JavaScript once you know the one gotcha that wastes everyone's first afternoon.

What HubSpot gives you for free

Every HubSpot form already supports a post-submit action: show an inline thank-you message, or redirect to a page or external URL. If you want allsubmitters to land on the same place, you don't need any code — set it in the form's Options tab and you're done. Custom logic is only required when the destination depends on the visitor's answer.

The onFormSubmit method

HubSpot's JavaScript embed accepts callbacks. The one you want is onFormSubmit (fires as the form submits, giving you the form object) or onFormSubmitted(fires after, giving you the submission values). Here's the pattern most teams land on:

The gotcha: the form is in an iframe

Here's what costs people hours. Classic HubSpot forms are rendered inside an iframe. That means the form's input fields are notpart of your page's document — so the instinctive document.querySelector("[name=country]") returns null, every time. You have to read the value through the form reference HubSpot passes into the callback (the formargument above), which has access to the iframe's internals. If you're using onFormSubmitted, read from its submissionValues instead. Either way: never query the document directly for form fields.

onFormSubmit vs onFormSubmitted — which callback?

HubSpot fires two different callbacks around a submission, and picking the wrong one is the second most common mistake after the iframe issue. onFormSubmit runs asthe form is submitting and receives the form element, so it's the right place to read a field and decide a destination before the visitor leaves. onFormSubmitted runs after the submission completes and receives a submissionValuesobject — useful if you'd rather read the clean submitted data than reach into the form, or if you want to wait until HubSpot has confirmed the submission before redirecting. For a simple "branch on a dropdown" case either works; if you need the submission to be definitely recorded before you navigate away, prefer onFormSubmitted.

One forward-looking note: HubSpot has been rolling out newer form types that don't use an iframe. If you're on those, the field-access gotcha may not apply — but the callback pattern is the same, and building against the callbacks (rather than scraping the DOM) keeps your code working across both form generations.

Where this approach stops working

Form-based redirects are perfect for routing on something the visitor tellsyou — a country dropdown, a "what describes you" picker, a plan choice. But they have hard limits worth knowing before you build:

• They only fire on submit.Someone browsing your pricing page who never fills in a form is never routed. If the goal is "show visitors the right regional page," the form is the wrong tool — most visitors never submit one.
• They depend on self-selection. The visitor has to pick the right country. People in a hurry pick wrong, or skip optional fields entirely.
• They're per-form. Every form that needs the behavior needs the script, and the field names have to stay in sync.

The complement: geo-redirects before the form

The other half of the problem — routing people by where they actually are, before they interact with anything — is solved by IP-based geo-redirects that run on page load. The two techniques pair naturally: a geo-redirect puts a German visitor on your German site to begin with, and form logic handles the finer branching once they engage (say, routing enterprise enquiries to a different booking page). One reads location automatically; the other reads intent that only the visitor can supply.

If your real goal was "send visitors to the right regional page," reach for geo-redirects rather than bending forms into a routing tool they were never meant to be. If you genuinely need to branch on a form answer, the onFormSubmit pattern above is the supported way to do it.