Grandes mentes pensam igual

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! ... Exibir mais

The new CTA tool is amazing! Great work team!    However, it looks like pop-ups load within iframes, which makes sense to ensure styling and scripts are isolated from the embedded website.  However, at the moment this means those submissions and clicks can't be tracked from these on third party analytics services (such as google analytics).    It would be great to be able to load these outside an iframe if required, or some way to embed custom tracking codes into the head HTML of the iframe.  ... Exibir mais

Perhaps I'm just missing the functionality, but with the new CTA tool (I love the freedom of design and some of the new power), I can no longer create smart versions, nor A/B test things like color or copy. Can those be brought back?    ... Exibir mais

I was in the process of working on the CTA (beta) located at https://app.hubspot.com/calls-to-action/5417432/edit/119840060830/content and noticed that the font family (poppins) we use on our website linezero.com is not showing in the 'rich text' section of the CTA beta widget.By further investigating on this issue I came to know it is not supported in the Rick text. (Taking a look at the documentation, it seems the option to use custom fonts in text-rich modules is not yet supported within the new CTA's feature, it is only available in the legacy ones. That being said, as this feature is still in BETA this means the team keeps improving the options and settings.) In order to maintain consistency with our website's appearance, I would appreciate it if hubspot could integrate the custom fonts within the CTA beta. ... Exibir mais

Could you please add the option to enable the use of Smart Content within new Pop-up CTAs, specifically called CTAs (Beta)?   We currently have a wide range of options to create different types of pop-ups.  It would be nice to have smart rules option as well. This would allow us to add smart button or add smart rule to the text or image.    ... Exibir mais

It looks like adding a personalization token to a CTA URL is not currently possible in HubSpot, as the token will become URL-encoded when the CTA is created in the CTA tool, instead of populating with a contact's information (unlike a regular link that's created directly in the email editor). ... Exibir mais

We need to be able to move the send/submit button in the new forms editor, at the very least pick left/center/right. It is currently fixed to the right side and cannot be moved.  ... Exibir mais

Hi I recently tried your new CTA Builder since the legacy will be sunset. It appears for emails that you can ONLY use a BUTTON or IMAGE. The new HTML CTA cannot be added to an email. The new CTA BUTTON options have eliminated the HTML Code area to add styles (ie css for a gradient or dropshadow). This limits us to flat, one color buttons that are not eye-catching, or having to create images in Photoshop/Adobe for each effort. Disappointed in this change. Please add the HTML option to your new CTA Button builder.  ... Exibir mais

The new CTA feature in HubSpot allows for popup boxes with buttons and/or forms. The current reporting options available are "how many views / clicks / submissions" which can be filtered by date range. That is about it. This help article covers most of the limited options.   We need to be able to see on which pages a CTA popup was viewed, and on which pages it was clicked through on. This would allow us to better analyze how the CTA is performing, and on what type of content/topic it resonates the best with.    HubSpot already has similar reporting options for Forms. A way to see on which page a Form is loaded, how many times it was seen, and how many times it was clicked on. We need this same functionality on CTAs.  ... Exibir mais