Typeform is a form builder known for its conversational, one-question-at-a-time interface. Where standard HTML forms present all fields at once, Typeform presents questions sequentially — which typically produces higher completion rates for longer forms, surveys, and quiz-style lead qualification flows.
If you run a WordPress site and want to embed Typeform forms, connect submissions to your CRM or email platform, and track which marketing channel brought in each respondent, this guide covers all three.
Embedding Typeform in WordPress
Typeform provides a few embed methods, all of which work in WordPress:
Standard Embed (Inline or Popup)
From your Typeform dashboard, go to Share > Embed > Get the code. Typeform generates an embed code snippet. In WordPress, you paste this snippet into a Custom HTML block (in Gutenberg) or into a “Text” widget/HTML module in whatever page builder you use (Elementor, Divi, Beaver Builder).
Options: Standard (inline, takes up space on the page), Popup (opens in a centered modal on button click), Slider (slides in from the side), Popover (small button in corner). Each has its own embed code from the Typeform share panel.
Typeform Block for Gutenberg
Typeform maintains an official WordPress plugin that adds a Gutenberg block. Install “Typeform Block” from the WordPress plugin directory, and you’ll have a block that lets you paste your Typeform URL and choose embed style (standard, popup, slider) without touching HTML. This is the cleanest option if you’re using the Gutenberg editor.
URL Redirect
For some use cases (like linking to a form from a button without embedding it on the page), simply linking to the Typeform URL directly works. Typeform’s hosted forms are mobile-responsive and load on their own domain. You lose the branded URL and site experience, but it’s the fastest implementation.
Connecting Typeform Submissions to Your CRM and Email Platform
Typeform’s integrations ecosystem is extensive. From your Typeform dashboard under Connect > Integrations, you can find native connections to:
- HubSpot — creates or updates contacts from each Typeform submission
- Mailchimp — adds subscribers with tags based on Typeform answers
- ActiveCampaign — creates contacts and can trigger automations
- Salesforce — creates leads
- Google Sheets — appends each submission as a new row
- Slack — posts submission notifications to a channel
- Notion — creates database entries from submissions
For platforms not natively supported, Typeform connects to Zapier, Make (formerly Integromat), and n8n — all of which can route submissions to thousands of additional tools.
Setup for a native integration:
- In your Typeform form, go to Connect > Add an integration.
- Authenticate with the destination platform (HubSpot, Mailchimp, etc.).
- Map each Typeform question to the corresponding field in the destination (email -> email, first name -> first name, etc.).
- Test with a submission to verify the mapping works.
The mapping step is where attention matters: Typeform’s field names are your question text, while your CRM expects specific property names. Take care to map the email field correctly — a mismatch means contacts are created without email addresses, which makes them functionally useless.
Using Typeform as a Lead Qualification Tool
Typeform’s conversational interface makes it particularly effective for lead qualification flows where you want to ask multiple questions and route leads based on their answers. A simple contact form asks name and email; a Typeform flow can also ask budget, timeline, company size, specific needs, and their biggest challenge — all in a way that feels less like a form and more like a conversation.
Typeform’s Logic Jumps feature routes respondents to different questions based on previous answers. A service business might use this to qualify leads: if budget is under a threshold, the form routes to a different CTA than if budget is above it. This pre-qualification means sales conversations start with better context about the lead.
With native CRM integration, you can map qualification answer fields to CRM lead properties, so your sales team sees budget, timeline, and use case data before making contact — without any manual data entry.
Tracking Lead Source for Typeform Submissions
Here’s the attribution gap that most Typeform + WordPress setups don’t close: when a submission arrives in your CRM, you know who submitted, what they said, and what email to contact — but not what marketing channel brought them to your WordPress site in the first place.
Someone who clicked a Facebook ad, landed on your WordPress page, and filled out your Typeform leaves no automatic trace of that path. The CRM contact looks the same as a contact who found you through organic search or an email campaign.
The solution is to capture UTM parameters on your WordPress site and pass them into the Typeform submission as hidden fields.
Hidden Fields in Typeform
Typeform supports hidden fields — values that are passed to the form via URL parameters but not shown to the respondent. You set them up in Typeform under your form settings > Variables > Hidden fields. For UTM tracking, you’d add hidden fields: utm_source, utm_medium, utm_campaign, utm_content, utm_term.
Once the hidden fields exist in Typeform, you populate them by appending parameters to the Typeform embed URL when the form is loaded. The embed URL accepts these as query parameters, and Typeform passes them as hidden field values on submit.
The full implementation requires JavaScript on your WordPress page that:
- Reads UTM parameters from the current URL (or from session/cookie storage, to capture the first-touch source even if the visitor is on a different page from when they arrived).
- Modifies the embedded Typeform URL (or calls Typeform’s
tf.load()function with the params) to include those UTM values as hidden field parameters.
Once implemented, every Typeform submission includes the UTM parameters from the WordPress session. These flow through your native integration (or Zapier) to your CRM as contact properties. Your CRM now shows lead source alongside every Typeform-generated contact.
Using a First-Party Attribution Tool
If maintaining custom JavaScript for UTM capture and Typeform hidden field population sounds like ongoing maintenance overhead, dedicated attribution tools like Sales Provenance handle this automatically for WordPress. The tool captures UTM parameters on the visitor’s first session, persists them across pages and sessions, and populates the hidden fields in embedded forms (including Typeform) when a conversion happens.
The advantage of first-party attribution over session-scoped UTM capture: it handles cases where the visitor’s original source was from a previous session. A lead who clicked a Google ad last week, came back directly today, and submitted your Typeform carries their original Google ad source through to the CRM — not “direct” (which is what session-level capture would record).
Typeform vs. Native WordPress Forms for Lead Capture
Should you use Typeform or a WordPress-native form plugin? Both have legitimate use cases:
Use Typeform when: The form is long or involves qualification logic (multiple questions, conditional routing). The conversational format will improve completion rates. You want the visual polish of Typeform’s design system without styling a native form to match. You’re building a quiz or survey, not just a contact form.
Use a native WordPress form plugin (Gravity Forms, WPForms) when: The form is short (3-5 fields) and inline. You need the form to match your site’s design exactly. You want all submissions stored in your WordPress database as a backup. You need complex server-side logic (conditional fields based on other WordPress data, file uploads, payment integration via WooCommerce).
Many sites use both: native forms for quick contact forms and newsletter sign-ups, Typeform for longer qualification or survey flows. Attribution tracking should be implemented on both for consistent lead source data.
If you want help connecting Typeform to your WordPress site with full lead source attribution included, Sales Provenance is built for this integration.