Gute Ideen sollten geteilt werden

Magic links for private content are great but no system template appears to exist to customise the one-time link sent for the new passwordless login success page.    Given system templates exist for all the other related pages - login, logout etc.. nothing for the passwordless feature is a handbrake on the UX.  ... Mehr anzeigen

Currently, it's possible to add list memberships as a rule to show a module on a landing page. Could it also have the option to exclude specific lists? For example, when creating Thank You pages and displaying content (Reports, Whitepapers), it would be good to hide specific modules from competitors to get access. Thank you. ... Mehr anzeigen

Consider transferring a template containing modules of path src_modules/module_x and src_modules/module_y from one account (account_a) to another (account_b) where it already have modules with same name but different path as follows des_modules/module_x  and des_modules/module_y This activity currently pops out an error stating Error: Asset not found and in network it shows "errorCategory": "THEME_NOT_FOUND" . Workaround: change the module name and the corresponding path would now be src_modules/module_x_new  and src_modules/module_y_new . when we try to copy the template containing these modules to another account (account_b), it shows success and new modules created with the exact path. Goal: It will be a great feature if we get to transfer template across accounts even when there is a file with similar name existing in destination account but in different folder name (technically it will have a different path).  For instance,  take the above scenario where moving src_modules/module_x and src_modules/module_y from account_a to accout_b can be allowed where it would have created the files properly without any conflict (since they are in different folders and path also differs) and stayed off from des_modules/module_x  and des_modules/module_y. ... Mehr anzeigen

Take the main menu, and turn each option into a square on the homepage. Users could create a homepage with clickable squares to quickly get to what is needed more quickly.   Maybe "today's tasks", "today's activity", "today's meetings"....   AND   "My open deals", "My open tickets"   All in small sections for quick viewing on one page.   As of now the only way you can personalize the homepage is to set the primary object.   The homepage should be more comprehensive and more visually useful rather than just one object....... ... Mehr anzeigen

According to HubSpot's Support team, whether a HubDB created Page appears in the XML Sitemap or not can only be controlled at subfolder level.    We have a scenario where a parent page should be indexed by search engines, but the many pages within the subfolder should not. Unfortunately, this means the entire subfolder of content has to be included in the sitemap so that the parent page is easily indexed.    We've added a noidex code to the subpages, but at scale this is a huge number of pages we're telling search engines to crawl via the XML sitemap, only to then say "don't index".   And the result is that we have thousands of these noindex pages clogging up Google's crawls of the site, and significantly delaying the indexation of new content.    A solution like a Yes/No column in the HubDB table that says "Include XML Sitemap" would be ideal. We've tried developing one, but it is not being recognised by HubSpot and is being overridden by the Subfolder rule mentioned above. ... Mehr anzeigen

We centralise all our pixels in Google Tag Manager, all we're after is a simple callback from the CTA to the main landing page with data about the submission, so our pixels can fire correctly on successful form submission.   For regular forms this works fine, but if we have a form in a CTA this just doesn't work and it's wildly frustrating.   ... Mehr anzeigen

Would love to see the addition of an onpage editor for HubSpot assets! ... Mehr anzeigen

Protect a page where the user would have to fill out a form with whatever fields needed then submit the form for access to the page.   This would make a more streamlined gate to pages. It also allows tracking of form information for people who are viewing the content on the page. ... Mehr anzeigen

e.g. We use. support tickets for residents to report any issues in their communal areas such as a faulty light which our maintenance team can then pick up. The current customer portal only shows tickets they themselves have submitted. It would be good if they could see tickets related to a certain property that they share with other people who have submitted issues. This would be to prevent a duplication of issues being reported by customers.  ... Mehr anzeigen