How can we modify our HubSpot form implementation to work with Firefox’s strict protection mode? Currently, the form fails to load due to Cross-Origin Request Blocking when Firefox’s Enhanced Tracking Protection is set to strict.
Hi, @Rahul_Sharma 
Thanks for your post. This one has come up a few times. The short answer is this an external feature of Firefox that is designed to disable exactly this kind of content (external tracking and forms), and is not something HubSpot can affect.
In the Mozilla’s docs, they explicitly call out forms as one of the types of content this is designed to block:
"Many websites load external ads, videos and other content with tracking code from other companies. For example, a website may embed a video from a video platform. The code that loads the video contains trackers. Blocking tracking content can make sites load much faster, but parts of pages might not work correctly or appear at all.
Tracking content can include:
Ads
Login fields
Forms
Payments
Comments
Videos and photos
Buttons"
This feature is only enabled by default in private windows. Any users encountering this in normal Firefox windows have opted into using that service for added privacy.
Best,
Jaycee
Hi Jaycee,
Thanks for the explanation. We are experiencing the same issue with our customer, who is unable to use their own forms. Since this is a large customer, their employees are limited to using either Firefox (with privacy set to high) or Edge (with privacy set to high).
We initially thought that if we couldn’t load the form, we could catch the error and provide a link back to the previewlink of the form. However, this approach isn’t working because the preview URL(hsforms.com) differs from the script URL(hs-scripts.com), making the script appear as a third-party script, which causes the same issue. It would help if at least the preview URL worked.
A better solution would be if we could relay the scripts through our domain, for example, via hbsp.domain.com, or for landing pages or pages hosted on HubSpot, directly on the domain. This is already possible for content stored in the file-manager.
What do you think? I don’t think it’s fair to blame the user for this.
We’re having the same issue. A visitor reached out through email because they’re using Edge with strict privacy settings and can’t access our forms to register for a webinar or download PDFs. I agree with DMarketing328, it’s not fair to blame the user for this; and on the business side, we’re missing signals from potential customers and providing a poor user experience.
Also, it’s not just a Firefox issue; it’s now Edge too, and they see a message that says they need to use a different browser or change their privacy settings, but they still find it frustrating.
Hi @Yndira_Escobar and welcome, it’s a pleasure to have you here!
To work with Firefox’s strict protection mode, set your form as raw HTML in the form editor.
This prevents the form from loading in an iframe, which Firefox’s Enhanced Tracking Protection blocks as a cross-origin request.
In your form settings, enable the “Set as raw HTML form” option. This renders the form directly as HTML on your page instead of in an iframe, bypassing Firefox’s strict tracking protection.
This feature requires a Marketing Hub or Content Hub Professional or Enterprise subscription.
Please note: Forms created with the new beta editor don’t yet support this option or custom embed code modifications.
Here are some resources for reference:
- Legacy forms
- HubSpot forms
Also, let’s consult our Top Experts: Hi @karstenkoehler, @GRajput and @sylvain_tirreau do you have any tips to share to help @Yndira_Escobar, please?
Have a great day and thanks so much!
Bérangère
This post was created with the assistance of AI tools.