How Formulayt Submissions Work

When a visitor submits a Formulayt gate, Formulayt sends the submitted data to the configured destination.

Formulayt supports different submission methods depending on the destination. The standard submission method for Formulayt is Fetch.

Fetch allows Formulayt to determine whether a submission has reached the receiving endpoint. If a submission is blocked, Formulayt can detect the failure and provide feedback to the user rather than allowing the submission to fail silently.

Fetch is used for:

Webhooks submit through Formulayt’s API for server-side delivery, with separate error handling. Marketo and HubSpot use their own APIs.

Older Formulayt accounts, built before August 2024, may still use the legacy iframe submission method.

Modern browsers, privacy tools, ad blockers, corporate security software, and network policies can prevent submissions from reaching external systems such as marketing automation platforms.

With the Fetch submission method, Formulayt can detect that the submission failed and immediately notify the user. Without Fetch, the submission would typically fail silently. The user would believe their submission was successful, even though it never reached your receiving platform.

This provides:

For destinations that use Fetch, Formulayt sends the submission using a browser Fetch request.

The process is:

Fetch only provides visibility into the request and response. It does not detect validation failures that occur before the request is sent, or problems that occur after the receiving platform has accepted the submission. For example, if the destination receives the submission but subsequently fails to process, store or sync the data, Formulayt cannot detect this as a Fetch submission failure.

By default, Formulayt uses Fetch to submit form data to Pardot. Because Fetch submissions occur outside the page context, Pardot Form Handler re-posts configured through the success location will not work.

Instead, we recommend using secondary submissions in Formulayt to send submissions to multiple Pardot Form Handlers. Typically, the primary submission sends data to a master Form Handler, while secondary submissions send data to additional Form Handlers that perform specific completion actions, such as sending an autoresponder email.

Secondary Form Handlers only need the email field if all other required fields are handled by the master Form Handler in the primary submission.

For more information, see configuring secondary submissions.

Note: Formulayt can also submit to Pardot using the iFrame POST method instead of Fetch. Contact Formulayt support to request this configuration.

A submission may fail because:

For example, some privacy tools classify marketing automation platforms as tracking technologies and prevent submissions from being sent.

This behavior can affect all major marketing automation platforms, not just a specific provider.

If the browser reports that a Fetch submission request has failed, Formulayt displays a submission failure message.

This lets users know that their submission was not completed and encourages them to try again or contact you using another method.

Without this message, users would have no indication that anything had gone wrong.

The submission failure message is as below but can be customized.

The form could not be submitted. This can sometimes be caused by ad blockers or browser privacy settings. Please update your browser settings and try again.

To customize your message, go to:

Setup > Settings > Forms

You can update the message shown to users under Submissions and validation and translate it using the Translation Manager.

Note: The message must first be triggered and indexed by the platform before it appears in the translations area.

If users report submission failures despite disabling browser privacy settings, there may still be another underlying cause, such as:

Unfortunately, browsers do not expose the exact reason a request was blocked, so Formulayt cannot determine the precise cause.

Where possible, and if required, we recommend reproducing the issue with the affected user while reviewing the browser's Network tab in Developer Tools.

When a Fetch submission fails, Formulayt raises a submission failure event.

This event can be used to:

For example, you could send a form_fail event into your analytics platform to help measure how often submission failures occur.

Note: If analytics scripts are also blocked by browser privacy tools or ad blockers, those tracking events may not be recorded either.

Redirects and downloads generally behave the same regardless of the submission method used. However, some browsers can restrict actions that open a new tab or trigger a download after submission.

Some browsers require these actions to happen directly from the user's click on Submit. Because Fetch waits for the submission first, browsers may treat delayed actions as pop-ups and block them. Safari is generally the strictest browser in this area.

Formulayt dynamically adapts the behavior where required and provides a fallback button for redirects and downloads, so visitors can still access the destination or content.

Older Formulayt accounts may still use the legacy iframe submission method.

The key difference with an iframe submission is that Formulayt has less visibility into whether the external destination successfully received the submission.

If the browser, privacy software or network security prevents the iframe submission from reaching its destination, Formulayt may not be able to detect the failure. The submission can therefore appear successful to the user even though the destination did not receive the data.

This is why Fetch is the recommended, standard submission method and all new Formulayt accounts created from August 2024 use Fetch.

If your account still uses the legacy iframe submission method, your Account Manager can help you assess whether moving to Fetch is appropriate.

Migration may require consideration of your current submission destinations, integrations and post-submission behavior.