HubSpot with Astro

HubSpot is easy to connect badly, and the first decision is which form owns the submission.

An iframe embed hands the whole form to HubSpot: the form retains HubSpot's supported behavior, a change made in HubSpot reaches the site without a deploy, and styling control goes with it. A developer embed keeps that logic while letting the markup be styled in your own components, at the cost of resyncing when the form's structure changes on the HubSpot side. A form of your own connected to HubSpot keeps the design and the interaction native, and is bounded by the field types the chosen route supports.

None of those is the wrong answer, and I pick per form rather than per site, on what the fields, the validation, the tracking and the styling actually need.

The tracking code is just as important as the form. Without it, HubSpot may still receive a submission, but page views, visitor activity and attribution can be incomplete. I verify the whole path: visit, consent, submit, contact creation, attribution and conversion event.

On one build the form submitted and HubSpot created the contact, and the source and campaign never arrived with it. The hidden fields looked populated in the browser, and the form's own code was sending different values, so what HubSpot received was not what had been written into the page.

I now check the saved contact and its attribution as part of every form test: a contact with the expected fields, the attribution that produced it, and the workflow enrollment that was meant to follow.