In some funnels, certain questions are more critical than others and you don’t want to lose that data if users don’t complete the entire funnel.
With Partial Submits, you can place partial submit points at strategic moments in your funnel to save important data early (for example, contact details), while still allowing users to continue and submit additional information later. All submissions made within the same session are automatically merged into one enriched response.
This means you can:
Secure high-value data early
Add additional submit buttons later in the funnel
Avoid creating multiple responses for the same user
Partial Submits are especially useful for longer or more complex funnels where users may submit more than once before finishing.
💡 This feature is opt-in per funnel and gives you more control over how submissions are counted and enriched.
🔎 Privacy Notice: If you use Partial Submits, you are responsible for ensuring that users consent to having their data saved (e.g., via a checkbox). Heyflow is not responsible for storing data without proper consent.
❗ When using the partial submit feature, billing is based on each response, not each submit. A single response can include multiple partial submits without extra charges. Learn more about response limits.
How Partial Submit Enrichment works
Opt-in per funnel
Partial Submit Enrichment is disabled by default
You can enable it individually for each funnel
Enrichment behavior
Within a single user session:
Each submit enriches only one response
Multiple submits are merged into that response
Previously submitted data can be overwritten by new inputs.
If a field is left blank during a later submission, the earlier value will be reused.
There is no visual indicator in the Responses tab showing whether a response was enriched via partial submit
❗ Important: Response Handler integrations (e.g. webhooks, CRM sends) are still triggered on every submit button click, unless you explicitly disable them in the button’s settings.
User sessions explained
Sessions are stored using
sessionStorageSessions are:
Unique per funnel
Limited to one browser tab
Persistent as long as the tab stays open (including page reloads)
A new session starts when:
The tab is closed and reopened
A new browser window or tab is opened
❗This means submissions from different tabs or windows are not merged.
How to set up Partial Submit Enrichment
Step 1: Set up multiple submit buttons in your funnel
Go to the funnel where you want to enable Partial Submits
Add submit buttons at any point where you want to save the data from your visitor
Step 2: Enable Partial Submit Enrichment
Open the funnel settings
Find the Partial Submit Enrichment option
Toggle it on. There's no need to publish your funnel, this change is live immediately.
Step 3 (Optional): Adjust submit button integrations
If you don’t want integrations to trigger on every submit:
Select the submit button
Open the button settings
Enable "Skip integrations" to disable response handler and auto reply integrations for that button
Publish your funnel.
This gives you full control over when external systems are notified.
Tracking with Multiple Submits
By default, tracking integrations and conversion events are triggered on every submit button click. This means all partial or multi-submit clicks will be counted as conversions in your connected tools.
If you want to track individual buttons separately, you can set up button-level tracking:
Activate Tracking for the submit button blcok.
Assign a custom event name to the button. This event name will be sent to your connected tracking tools.
This setup allows you to differentiate which submit buttons triggered specific events, giving you more granular insights into user behavior.
❗️Meta allows a maximum of 50 characters for an event name.
❗Custom Tracking of Submit Buttons:
When tracking a submit button click as an event, the event is triggered immediately upon clicking the button - not necessarily upon successful submission. If there are errors on the page (e.g., missing required inputs), the event is still sent, which can lead to discrepancies in conversion tracking.