Gute Ideen sollten geteilt werden

One of the best features is being removed. The Chrome plugin saves my team so much time. Of course, you'd get rid of it. Seriously the most disappointing Hubspot news I've heard. Waiting for my sales team to freak out.  Here's the explanation my sales rep got when it wasn't working. "Although this is a feature that the team is working to remove from all profiles, and it's possible that they are making those changes soon. I'm not sure when this option will no longer be available." ... Mehr anzeigen

Today when we put one of our clients' HubSpot blog through the website grader, we saw that the blog had a page size of 13mb. The problem was that the images they we're uploading as the featured image were large images (3000x3000px+). We quickly figured out that we could resize the original image by adding and specifying a width attribute to the <img> tag. This process changed the page size from 13mb to 1.8mb.   I have two examples here: http://cdn2.hubspot.net/hub/53/file-733888619-jpg/assets/hubspot.com/about/management/brian-home.jpg?width=300 http://cdn2.hubspot.net/hub/53/file-733888619-jpg/assets/hubspot.com/about/management/brian-home.jpg?width=500 The first one resizes (crops) the image to a 300px width, and the second image it's resized (cropped) to a 500px width.   I got this back from support:  "looked into this and it does have to do with the url structure and our ability to intercept the request before our content delivery network receives it. With how these tokens grab the url of an image, we can not manually resize them.   Using the default CDN host, http://cdn2.hubspot.net/hubfs/53/00-Blog_Thinkstock_Images/hubspot-15k.png?width=761 needs to be changed to http://cdn2.hubspot.net/hub/53/hubfs/00-Blog_Thinkstock_Images/hubspot-15k.png?width=761"   Because we are using the featured image tag, {{ content.post_list_summary_featured_image }}, we can't edit the URL to include the "/hub/"-part. Is it possible to implement that on the featured image url as a standard so we can specify the width in the url on future blogs? ... Mehr anzeigen

Our team uses TeamWork PM for all of our project management and task tracking.  The hubspot task option doesn't notify me and the emails get caught in my 'promotions' tab of the email and go unnoticed.  It would be great if hubspot integrated with TeamWork so that when i create a task in hubspot CRM it created one in TW for me under a sales project. ... Mehr anzeigen

Migrated from legacy feedback forum with 68 votes.   I have had several instances where the ability to set the default values for form fields would have saved me hours of integration time.   For example: My client has 10 webinar pages each with its own unique thank you page. Our current form configuration (not-HubSpot integrated) redirects the user to the appropriate thank you page which contains the webinar requested for view.   I can already dynamically change the thank you page destination from the form embed code - but what I am looking for is to also set a hidden fields value inside the embed code as well.   For example the embed code would look something like this: <script> hbspt.forms.create({ portalId: 'XXXXXX', formId: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', formFields: { fieldID1 : { value : "my value" }, fieldID2 : { value : "my value" } } }); </script>   Where the field ID parameters and their values would correspond to certain fields (hidden or visible) in the form. This would allow me to use a single form across multiple pages on my site and also be able to send through the correct values for certain form fields based on the action / content they requested on the site.   If you guys can do this - or if it is already possible and I didn't know about it - I would love you forever. ... Mehr anzeigen

One of the biggest oversights in the COS is that it's very difficult to create looped content. As far as I'm aware, the only thing that lets you do a loop is a slider (if you use export_to_template_context), which has a limited number of fields per iteration. Consider this simple case: I want to create a custom widget where the user can create an arbitrary number of buttons. Each button has a link, text, and a few style options. Currently , they way I would have to do that is to decide what the most buttons I would ever need is, then add that number of each field (for example, five links, five button texts, five style drop-downs, and then distinct markup for all five). Obviously, a very tedious process. And if I want six for some reason, I have to go back and edit the module. So, here's how I envision this working. First, add a new option to the custom widget editor to create "field groups". Field groups could contain any number of other fields (perhaps even their own child field groups, because why not?), and would have their own labels, names, and description fields. Then, the person using the page editor would be presented with those fields grouped together visually, with add and remove buttons. Clicking add would create a fresh copy of all the fields in the group, clicking remove would remove that item in the group. Then, in the template, you would have the ability to iterate through items in the group with a for loop. Something like this: {% for button in widget.field_group_name %} <a href="{{ button.link }}" class="{{ button.style }}">{{ button.text }}</a> {% endfor %} The user can have as many buttons as they please, the page editor doesn't get clogged with useless fields, and the code remains simple and easy to maintain. This would give developers a lot of control over presentation without sacrificing ease of use for the page editor. I really can't emphasize enough how much this would simplify certain aspects of template building. ... Mehr anzeigen

Hi guys, we recently hosted our first event with Eventbrite and Hubspot and while there is a basic article explaining the technical details of the Eventbrite integration and how it works, a detailled article à la "How-to properly host an event using Eventbrite and Hubpost" tutorial is missing. I imagine a step-by-step article, pretty much as this one, of what to look out for on the Hubspot and on the Eventbrite side. Which workflows are useful, what lifecycle stage do new Eventbrite leads have etc. etc..    what do you say?    Amon  ... Mehr anzeigen

In the Hubspot CRM, there are so many filter options to choose from, it would be great if we could have the ability to customize those filter options so that they are specific to our company.  ... Mehr anzeigen

Why not give me an option to use existing keywords in my Hubspot portal when building landing pages? Why do i have to enter them again?  Ideally, you should present me with a list of current keywords so i can pick/choose which ones to add to LPs.  ... Mehr anzeigen

Can HubSpot please revert back to the original import logic for Contact Imports? The recent changes have made the process far more restrictive, reducing flexibility and customization—which feels like a step backward. Background: Previously, HubSpot’s contact import logic allowed users to match and update records using unique custom properties (skys the limit!) without requiring additional fields. This was highly customizable and efficient.   Since then, HubSpot’s contact import validation logic has changed, and the documentation was updated afterward to reflect this. This happened January 2026. Current Behavior: For Contact imports, HubSpot now requires that at least one of the following fields be included before allowing any custom property to be used as the matching identifier: Email First Name Last Name Even if you prior had used a field as a unique property, it cannot be used on its own to match existing Contact records during an import after the change in import logic. Impact: At this time, there is no supported way to update Contacts via import using a unique property without also including Email, First Name, or Last Name. This behavior is enforced by the import system and cannot be overridden. Request: Please revert the import logic to allow the use of unique identifiers (as chosen by clients) as the sole matching property again. This sudden change has made imports far more constrained and inconvenient compared to the flexibility HubSpot users have come to expect.   This change impacts workflows for teams that rely on custom identifiers—restoring the previous logic would greatly improve efficiency and user experience. ... Mehr anzeigen