クリエイティブな才能を開花させよう

I am reaching out because we are currently facing a significant technical limitation that is preventing us from fully migrating our processes from Typeform to HubSpot. The Feature Needed: We need the ability to use Personalization Tokens (or dynamic placeholders) within the "Redirect to another page" URL setting of a HubSpot form. The Use Case: After a lead submits a form, we want to redirect them to a booking page (e.g., a calendar or a custom application) and pass their data (email, phone, etc.) via query strings so the next step is pre-filled. Example URL: https://www.example.com/booking?email={{contact.email}}&phone={{contact.mobilephone}} The Current Problem: Character Blocking: Currently, the "Redirect URL" field in the form editor blocks the use of brackets {{ }} or []. When we try to use HubSpot syntax, the system throws an error or saves it as plain text instead of rendering the variable. Missing "Piping" Functionality: In tools like Typeform, "Piping" (passing an answer from a previous step into a URL or following question) is a native feature. In HubSpot, this currently requires complex Custom Code workarounds or hidden redirect pages, which is not scalable for a marketing team. Why this is important: Without the ability to pass contact data dynamically through the redirect URL, the user experience is fractured, as leads have to enter their data twice. This is a "hard roadblock" for us and, I believe, for many other companies looking to consolidate their tech stack within HubSpot. Proposed Solution: Allow the use of standard HubSpot Personalization Tokens within the Form Redirect URL field, similar to how they work in HubSpot Emails or Landing Pages. Is there a planned update for this, or has anyone found a reliable way to bypass the character restriction without using heavy custom-coded middleware?   Best regards, Jan ...その他を表示

Add a configurable watermark option when setting up a File Upload property in HubSpot. The watermark setting can be enabled or disabled directly at the property level. Problem it solves Files uploaded through forms may contain sensitive or confidential information. Allowing watermark configuration at the file upload property level helps reduce the risk of misuse or unintended disclosure, while giving teams control based on different data sensitivity needs.   ...その他を表示

When an IP address is excluded from analytics/activity tracking, form submissions from that IP address are automatically listed as spam submissions.   I recommend that an option be added to exempt those form submissions from the spam filter.   We use a large number of forms, and we sometimes need our own staff to fill out those forms. All of our staff are on a VPN, and that VPN is excluded from analytics tracking, so form submissions by our staff are automatically marked as spam.   We do not want to enable alaytics tracking for our staff; their activity on the website does not need to be tracked, nor do they need to be included in retargeting audiences. However, we do need to see the forms they submit.   To be honest, I don't understand why these two things are combined in this way, but I accept that someone, somewhere has a business case where it makes sense. It doesn't make sense for us. An option to always accept form submissions from a specific IP or an option to not apply the excluded IPs to the spam filter or some other way of unentangling these things would be greatly appreciated. ...その他を表示

It should be possible to convert a form made in the legacy editor to the new editor, so you avoid the hassle of creating a new one and switching out all the places it's used. ...その他を表示

Mandatory fields in multi-step forms are only checked in the last step, even if they were not filled in during the first step. This is confusing for users if they cannot see at first glance which fields have not been filled in. Mandatory fields should be checked before moving on to the next step. ...その他を表示

Currently, we make a form for every language we support. For us this means we will have 7 versions of the same form just for localization. Then we need to combine reporting and duplicate workflows and manage all these forms on localized pages. We'd like to have multi-language variants of a form with the ability to assign multiple sub-languages to a form, and the right form displays automatically based on the selected language. This could be a great enhancement to localization heavy HubSpot customers. ...その他を表示

Who is this feature for? This feature is for marketers, designers, and anyone using HubSpot's new form editor to create and manage forms on their website. It would particularly benefit those without coding knowledge who want more control over form design. What is their goal? The goal is to provide users with an easy way to align buttons (such as "Get in Touch" or "Submit") within forms without needing to switch back to the legacy editor or manually edit HTML/CSS code. What value will this add? Adding button alignment options (left, center, right) directly within the form editor’s styling options will improve the user experience by allowing for quicker design adjustments. It will reduce the reliance on legacy tools or custom code, streamlining the form creation process and keeping everything in the modern editor.  Are there examples of other places or products that have this feature? The legacy HubSpot form editor already has this feature. It would make sense to bring this functionality into the new editor to maintain and improve usability. ...その他を表示

Hi there,    As a HubSpot user, I would like to analyse forms and their submission in the custom report builder. This was already possible in beta, but was unfortunately removed again upon release. Unfortunately, @JoeMayall's  solution to this only works to a limited extent for our use case: "The best place to analyze form submissions is in the Form Analytics page (Analytics Tools > Forms)" What we need:   Filter submissions (e.g. by lifecyclestage of the contact) Further data on submissions (e.g. on which website took it place). Further options for graphical representation. Currently there are only Area, Column and Line. Drill down from the report to the individual contact. Similar to almost all existing reports, a table should open when the report is interacted with. At present, the report only links to the form. And most importantly: A report that depends on the exact time of the submission. First and recent conversion are too imprecise for this.   ...その他を表示

Often times we enter fake data into our own form to test workflows or we get spammed with fake accounts. I'd like the ability to delete form submissions so they don't impact the metrics. ...その他を表示