Great minds think alike

Currently it's not possible to query or "find out" which pages a Form is being used in if the form is being used within a "Custom Form Module" on a HubSpot hosted Website page or Landing Page. This is a roadblock for Enterprise websites (with Localized or Multi-language variants) hosted on HubSpot, that have created/use Custom Modules.  Example: The website for Enterprise Company XYZ is built and hosted on HubSpot. This website has been localized to 24 different language variants, resulting in over 1000 website pages (Landing Pages included). These pages use Custom Modules, created per their design requirements and to provide additional functionalities. Within HubSpots Forms UI, when, displaying the "Appears On" column, it displays as "No HubSpot places". (Attached Screenshot). Here is HubSpot Supports response on the matter: "In custom modules, a content editor usually selects a form inside the module fields (with a “form” type field). The association between a page and the form is stored at the page-level module instance, not easily queryable from the UI. So we dont really have a way to check via the UI" ...read more

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. ...read more

Currently, staging does not allow us to make multi-language variants causing us to move to production first then make all our variants on a default system domain, and then switch it to the live domain. If we could just get our full language page groups ready in staging we could publish to live and improve the development workflow. ...read more

We have a website where we group 22 language variants under the en-US primary page. But there are technically multiple primary languages. So having the ability to make subgroups of languages would help tap into the fallback language options. The primary language for a group becomes the fallback for all languages. If you land on a page missing that language then it will go to the primary. But we may have several languages that are associated and we'd like to select a primary for that group. For example: fr-FR (primary for this set of language regions) fr-BE fr-CH So if fr-CH is missing, Id like it to fallback to fr-FR but still have it in the larger associated group of language page variants. ...read more

Hello product team,   For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly.   Why is this currently a bad user experience for users?   Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name.   Why is this currently a bad user experience for admins?   Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names.   If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users.   Here's what a solution could look like   To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking.   Here's a quick mockup of what this could look like when creating a new page.     The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited.   Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title).   (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.)   I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc.   Thanks in advance for reviewing! ...read more

Currently, only legacy forms are available to be used in custom modules. In order to add a form created with the new form editor to a page, the only option is to use HubSpot's default 'form' module that's provided in the drag-and-drop editor. It is fundamental that the ability to utilize new forms in a custom module is added ASAP.  ...read more

The Saved Section is really helpful, but it's missing the essential editing part. On my website I have re-used a section several times and I had to edit them one by one since there is no "Global Update". That can be an easy feature to add with a huge impact 🙂 ...read more

Developers are limited to using version 5.14.0 and can't update themes to version 6.   Who: developers creating themes and marketers using themes What/goal: ability to use the latest icon sets Value: adds backwards compatibility   If the theme was created with 5.0.10 it is not possible to update to 5.14.0 because 5.14.0 is not downward compatible with 5.0.10. Updating the icon_set would break the icons on existing website pages where 5.0.10 was used.   Fontawesome introduced downward compatibility with version 6, but since HubSpot doesn't allow version 6, it's not possible to update existing themes.   Editing to include that without this update, users can't select TikTok or the new Twitter X icons.   Editing to include the icon field now supports v6.4.2 which works for all new themes or custom themes (doesn't resolve backwards compatibility issue). ...read more

Hey,  I would really like to have the option to update my subscribtion page by drag and drop. In fact, I dont see why all system pages, e.g. 404, are not featured in the drag and drop builder.  Even when changing the page via coding a lot of problems and frustrations arise. We dont seem to have any problems with the normal landing pages and websites.  Please implement this feature.  Greetings.  ...read more