Typeform with Astro
Typeform suits conversational forms, surveys and branching qualification flows. I embed it without losing the attribution behind it or the next step after submit.
Typeform at a glance
- What I do
- Embed Typeform in Astro with hidden fields, attribution, completion handling and downstream delivery to the tools that need the answers.
- Typical setup
- Adds 1–2 days
- How it is bought
- Part of a migration scope, or a Continuous development request once the site is yours
- Category
- Forms and scheduling
Setup
How I set up Typeform
Typeform earns the embed when the experience matters: surveys, qualification flows, applications, onboarding questions or anything long enough that one static form would feel punishing.
The trade is control. You get Typeform's experience, branching and response tools, but the site no longer owns the form submission. Anything downstream should listen to Typeform's webhook or integration path.
I pass attribution through URL parameters, test the completion behavior and make sure the next step is not a dead end. The visitor should finish the form and know exactly what happens next.
How the handoff works
- 01
Start
The form opens on your page
- 02
Fields
Visible answers, hidden context
Key handoff
- 03
Submit
One payload leaves
- 04
Destination
The CRM or the sheet behind it
- 05
Verify
The record carries its context
Why this is the key handoff
Typeform knows nothing the page did not tell it. Typeform cannot know where somebody came from unless the page tells it. I check that the hidden context is still attached to the response when it lands, not just that the response landed.
Included
What gets connected
-
Inline, popup, slider or full-page Typeform embeds
-
URL parameters or hidden fields carrying UTM, referrer and user context
-
Responses sent to a CRM, spreadsheet, email tool or automation
-
Completion callbacks and post-submit page behavior
-
A fallback plan for mobile and slower loads
Before you add it
What to watch out for
- 01
Completion is measured through Typeform, not the page
The embed is an iframe, so your own analytics see it open and little of what follows. Completion is tracked through the supported embed events, while partial completion and the answers themselves come from Typeform's own reporting or a submission webhook, which are different mechanisms with different coverage.
- 02
Embed sizing needs testing on mobile
An iframe does not grow with its contents, so the height is set by hand. Too short and the form scrolls inside a box, which is worst on a phone and is where I test it.
- 03
The response lives in Typeform until something moves it
The write into the CRM, the notification and the failure path are the integration. The embed is only the part somebody can see.
More tools
Keep exploring
-
Calendly
Embed Calendly in Astro with prefilled details, campaign attribution, CRM updates and a widget that does not slow every visitor down.
Adds 1–3 days
-
Google Analytics
GA4 and Tag Manager set up on an Astro site with clean events, consent behavior and performance-conscious loading.
Adds 2–4 days
-
Salesforce
Site forms that create the right Salesforce records, preserve attribution and fail visibly when Salesforce rejects a submission.
Adds 3–5 days
Let me plan your next step.
I can scope a migration. Send a brief and I will reply by email with next steps.