クリエイティブな才能を開花させよう

For certain product release betas, admins don't have immediate access to turn them on/opt in -- you must select "Request Beta." I'm not sure why some are "gated" like this vs. just being able to turn them on/off, but I digress.   As far as I can tell, there is no expectation communicated to the customer as to if/when their request will be reviewed. Furthermore, when the request to join the beta is granted, customers are not notified when it is suddenly turned on.   This presents a few problems:   Betas are notoriously buggy; not a problem in itself if you are aware of the risks and can monitor for issues, but this is hard to do if you don't know if/when the beta is turned on. Some betas don't allow the "enroll just me" option; if something suddenly changes in the UI, we are unable to notify users proactively about the upcoming change.   Just today, we requested access to the new "customize associations" beta (for which we were really excited!). At some point later in the day, we suddently began experiencing HUGE issues with rogue calls being associated to completely unrelated deals. We scrambled for 20 minutes tring to figure out which workflow was misfiring until I thought to check the product updates page and indeed confirmed that the beta had been turned on.   I love betas. I understand they're betas for a reason -- they're not always perfect. But please: if you're going to require us to request access, please communicate a timeframe in which they'll be turned on/approved AND/OR notify admins when they are. This is such a poor experience and makes all of us look bad. ...その他を表示

Journey reports are challenging when trying to dial in on the time it takes to complete the steps in a journey. Current Restrictions/Limitations Only one way to control the time range of the journey (sure we can do a static range or rolling time range), it is still only one time setting. Other analytics tools we use have additional levels of time parameters, the lack of this in Hubspot journeys limits the value we get out of the reports. Lacking stat of median time between steps; we only see the average time between steps   Inability to refine time parameters on each step of the journey.   Control that the action was done the 1st time since the previous step (and then stop recording the event on that report for that contact)   ----- Further details We want to look at anyone who would enters the journey up to 30 days ago. THEN, we want to know, of those contacts, who completed the steps in the journey within 10 days of entering the journey. If a contact 'qualified' to be in the journey but dropped off before completing within 10 days, that's an interesting stat along with the 'success' rate of those that did complete within the 10 days. IF we limit the journey report date range to only include 10 days, we are NOT capturing the entire cohort of interest (like anyone who was sent the email in the last 30 days). IF we try to use the contact filter or apply a list to capture the cohort for the 30-day range, this doesn't work either. The reason being the date range on the report is set to 10 days because we want to know who completed the journey within 10 days, we will still only 'see' the contacts that did the first step in that 10-day range (even though we want to look at a cohort of contacts that did the first step in the last 30 days). ------ Median is good to see in addition to Average. OR at least allow us to decide which we prefer to see for each step. ----- We should be able to refine the parameters between each step as well and control how those actions are counted. (refinements) IF we are using a custom event or a page view, a person may do those events multiple times while in the time range of the journey. It appears that the most recent timestamp of firing those actions/event, overrides the first time after the prior journey step the contact may have done the event. This creates a challenge of knowing the time of completion between steps as the first time after the previous step is no longer recorded if the contact comes back and does the step again and again. Ex) Instead of opening an email, clicking a link, logging into our app showing seconds (confirming our engagement email is working); we are seeing opened an email, clicked a link and then the time to log into our app being hours or days later. When we dig into the contact record, we see this is due to the contact firing the event multiple times after having done the action in the previous step of the journey. We care to only see the time to complete as a reflection of the 'the first time after the previous step'. ...その他を表示

Hi,   I'm interested in having the capability to limit users' access to viewing properties, similar to how we can restrict edit access for specific users and teams. This improves would offer greater flexibility for custom fields, enabling us to conceal team-specific information from teams where it's irrelevant.   Thanks. ...その他を表示

For calls and other activities associated with a deal include a field that is "Stage During Call". This exists when looking at a call individually but having it as a field that can be reported off of. ...その他を表示

I'm interested in having the capability to filter the dashboard using ANY field. Currently, the only available options are limited to Date, Owner, Teams, and Deal/Ticket Pipeline. We aim to expand this functionality to include filtering by custom fields such as Products or Type. ...その他を表示

In the Beta version of business units, the functionality to clone a form from one business to another should be available, but it's currently unavailable. Additionally, there's no option to edit an existing form and assign it to a different business unit. ...その他を表示

We've internally assessed properties and identified a requirement to view dropdown/checkbox values. Currently, extracting these values involves manual copying, but having the option to export them would greatly enhance efficiency. Additionally, I'm unsure about the most suitable category for this idea. ...その他を表示

I'm thrilled about having access to the beta feature for creating associations and labeling them between records. However, it feels incomplete without the capability to associate records via workflows. I've been trying to implement my use case with workarounds since my company began using HubSpot.   Use Case: As a solar panel manufacturer, we sell to distributors who, in turn, sell to solar installers, who then sell to homeowners. We generate numerous homeowner leads that we want to send to our customer installer companies.   I aim to set up a workflow that associates the lead's contact record with the installer company record using the association label I created. Then, I'd like to send a new lead notification to the designated lead acquisition employee at the company, all based on the lead's location.   I want to be able to view the lead contact record and see which installer company we sent it to. Or, view an installer company and see all the leads we've sent to them. Alternatively, create a deal between the lead and the installer company for every lead we send to them.   Manually associating these records isn't feasible as we receive thousands of leads each quarter. This seems like a significant blind spot for B2B users. ...その他を表示

I heavily rely on HubSpot's workflows, and having a dashboard to easily track their success or failures would be incredibly beneficial. I manage both MQL and SQL workflows that run consistently, along with creating them for major events we participate in. Having a clearer view of their outcomes would help me identify areas for optimization, especially in terms of workflows and emails that require the most attention. A centralized way to monitor these results would streamline my workflow and enable more effective decision-making for enhancing our marketing efforts. ...その他を表示