Las grandes mentes piensan igual

Hello,   My team and I have been working on implementing some regularly scheduled emails for our clients using HubSpot's Transactional Email API + the beta custom coded template/module features.    These emails are really more like marketing emails, but to leverage hubspot's single send API features we've been implementing them as transactional emails (it best suits our use-case for a range of reasons; for example, because there's a lot of bespoke data that needs to be pulled into the emails per-client in our backend, and which we don't want to store on HubSpot). Overall our desired implementation has gone well and the emails are almost ready to ship.   We've included unsubscribe links in the email footer which leverage our own unsubscribe solution, since these are going to act more like marketing emails and need to comply with relevant regulations. The unsubscribe url – which we're sending as a customProperty with the api request, and then implementing in the template – points to an endpoint of ours which implements in-house unsubscribe logic. This is important to us because we want our clients to be able to manage their subscription status both in-platform (ours) and through clicking the unsubscribe link.    The above setup for a footer unsubscribe link is working well. But to get to the point here, as a final step we want to implement those same unsubscribe links with List-Unsubscribe and List-Unsubscribe-Post headers for these emails, to comply with recently announced requirements from Google and Yahoo for marketing emails. I recently made a post on Hubspot Community inquiring whether it is possible to somehow specify values for these headers somewhere in the Transactional Email/Single-Send API flow, and per your Community Manager (and my scouring of HubSpot documentation) it looks like this is not currently supported.   This seems like a relatively simple ask and one that we'd like to formally request. From skimming around the web it looks like many email services are adding manual support here, including for teams like us with their own unsubscribe solutions: here's an example from Postmark showing what looks like a relatively straightforward manual implementation (the two headers and their values getting sent inside a "Headers" list with the API request). Is this something Hubspot can implement for its Transactional Email/Single Send API?   TL;DR: Enable specification of values for List-Unsubscribe and List-Unsubscribe-Post headers within API requests to HubSpot's Transactional Email / Single-Send API (example implementation from PostMark here), in support of compliance with Google/Yahoo requirements, for teams that need to implement an in-house unsubscribe solution with that API. ... Mostrar más

We need the ability to specify specific styles for an email that is rendered on a mobile device.  Since the drag and drop editor does not give us access to the email head and we can't include any media queries, the drag and drop GUI needs to provide an intuitive way for the email builder to control how the email looks on mobile.   we may want to change font sizes, swap imagery, cut down content, etc when the email is viewed on mobile.   please upvote ... Mostrar más

Currently the email builder only provides two kinds of smart rules: for list subscription and for lifecycle stage. I find these two options too limiting, as I would like to be able to create rules based on geographical region or language.   Therefore I would like to expand the smart rules to more properties if not all properties for multiple objects (account, contact, etc.) ... Mostrar más

When sending Marketing emails from Hubspot, when looking at the email detail, Mailed-by section always has a random hubspot email such as bf03x.hubspotemail.net instead of the company/sender email domain. Can we have the Mailed-by section to also list out the sender company domain or email instead of a hubspot one? This will avoid a lot of suspicion that can arise from end user prospect/customers that get emails and looks spammy.  ... Mostrar más

Currently, while we can implement straightforward personalization tokens for greetings, the lack of a user-friendly if/then/else condition directly in templates poses challenges, especially for those not familiar with HubL.   Our customers would like to have a more intuitive, visual interface for implementing if/then/else conditions directly within email and template editors, allowing users to easily create personalized greetings based on contact properties like gender. Use Case to make this more vivid: We have a client who needs to implement the following salutations in German: For female contacts: "Sehr geehrte Frau {{contact.lastname}}" For male contacts: "Sehr geehrter Herr {{contact.lastname}}" For neutral or unknown gender: "Hallo {{contact.firstname}} {{contact.lastname}}"   The first two are easy to do, the last one, however, is problematic if you don't want to build a workaround or if you're not familiar with if statements within templates and therefore can't tell HubSpot the following: "if gender is male or female, then use the values for greeting, salutation and last name. Else use the default value for salutation and individual values for first and last names."  Benefits of a more user-friendly conditional logic within templates Non-technical users could create personalized content without needing to learn HubL syntax. More tailored greetings could enhance user engagement and improve response rates in email campaigns, especially for gender-sensitive languages like German. Users could implement complex logic without cumbersome workarounds, making the platform more versatile for various marketing strategies. This feature would streamline the process of creating personalized content and make HubSpot an even more powerful tool for marketers. I believe many users would appreciate this enhancement, and I encourage others to support this idea. ... Mostrar más

I'd like to propose an improvement to the way personalization tokens handle empty fields, particularly for salutations in marketing emails and 1on1 templates. Current Situation: We're using a personalization token for the first name field in our email salutations. When a contact doesn't have a first name, we want the salutation to default to just "Good Morning" without any extra spaces. However, the current behavior adds an unwanted space, resulting in "Good Morning ," (note the space before the comma). Proposed Improvement: It would be incredibly helpful if HubSpot could implement smarter handling of empty personalization tokens. Specifically: When a personalization token is empty and no default value is set, HubSpot should automatically remove any trailing spaces and punctuation associated with that token. Alternatively, provide an option to specify how empty tokens should be handled (e.g., remove associated punctuation, keep as is, etc.). This improvement would enhance the professionalism of our communications and save time that's currently spent on tedious workarounds. ... Mostrar más

I'd like to propose an enhancement to the editor interfaces in HubSpot that could significantly improve user workflow and productivity. Currently, e.g. in the Marketing Email Editor, there's an "Exit" button in the top left corner that takes users back to the Marketing Email overview:   The "Exit" button in the top left corner of the Marketing Email Editor   While this is useful in some scenarios, our team has observed that it doesn't always align with our workflow needs. We suggest adding an "Open in New Tab"-option or something similar next to or instead of the current "Exit"-button. This would allow users to open the Marketing Email overview in a new tab while keeping the current email draft open for editing.   Benefits: 1. Users can reference other emails without losing their place in the current draft. 2. Ability to work on multiple emails simultaneously. 3. Easy access to the full email list for inspiration or consistency checks. 4. Minimizes the risk of unintentionally leaving the email draft.   Use Case: When crafting or editing an email, we often need to reference other emails for consistency in style, content, or design. The current "Exit"-button forces us to manually open the other emails in additional tabs; involving several tiring clicks until we get to the emails we want to open, and potentially losing our train of thought.   An "Open in New Tab"-option – also in other HubSpot editor interfaces (e.g. for CTAs, Blog, Website and Landing Page) – would seamlessly solve this issue. We believe this small change could lead to a significant improvement in user experience and productivity for many HubSpot users. ... Mostrar más

We would like the ability to add a question after someone unsubscribes so we can understand why they unsubscribe. From my understanding, there is not a way to do this without code.  ... Mostrar más

Property to know the source of the unsubscription, if it's not workflow, by contact... So we can integrate it into our reports and lists. ... Mostrar más