Currently the new CTA beta feature has been great for a new info popup my client needs on their third party website. The ability to configure it to show after time delays on certain pages has gotten us 90% of the way to our goal, but the ability to better control via code when the button trigger (using classes on HTML elements) would mean we could go even further.
Who -
This idea is primarily for software engineers/developers who will integrate third party apps/websites with hubspot, but depending on the execution could also be used by less-technical staff who are configuring the way CTA’s work.
What -
The goal is to gain more control over how and when CTA’s are triggered, either programatically or by having additional options on the hubspot side.
Value -
The new CTA’s are already a great value to the way our external website interacts with hubspot, this idea would further that by giving us more fine-grained control, allowing our current CTA’s to be more accessible and meaning we can use CTA’s for more things in the future
Examples -
We currently would like to pop up an info modal for customers when a form element is clicked on. Currently, we can set this trigger up which does work and show the desired CTA when clicked. However, there’s no simple way to remove the trigger, so that it only happens once during the form interaction.
The basic flow is -
- User clicks on a form field
- CTA pops up
- User edits form field
- We remove the CTA classes (e.g.hs-cta-trigger-button hs-cta-trigger-button-1111111111111)
- User returns to form field to edit/update
- CTA still shows, as there was a trigger we now don’t control on the HTML element.
We’re building the website in React and while there are definitely hacks/workarounds that we could perform to get through it, I think in general having more control in the future to add/remove/manipulate triggers would make CTA’s even more powerful.
EDIT -
As someone pointed out below, it is technically possible to control the HTML button component via elements and scripting, however what this Idea is specifically about is controlling the effects of the CTA button, for example being able to add/remove triggers to elements, not just manipulating existing elements that use the CTA trigger.