Currently CTA (Beta) logic does not work on Single Page Applications.
For SPAs with page tracking enabled in the HubSpot JS, please add support for the CTA logic listeners to trigger when the target pageview means there should be a CTA visible.
This is so needed!
Links to similar/identical issues, with slightly different descriptions or angles of approach:
- https://community.hubspot.com/t5/APIs-Integrations/Force-CTA-Scripts-to-Run-on-History-Change-for-si…
- https://community.hubspot.com/t5/APIs-Integrations/When-we-change-the-route-in-our-React-single-page…
- https://community.hubspot.com/t5/APIs-Integrations/Tracking-code-problem-in-Angular-Site/m-p/360261
- https://community.hubspot.com/t5/APIs-Integrations/pop-up-form-not-triggering-in-single-page-application/m-p/756377#M61471
Hi, I am looking into the same. Any update or workaround for this one?
I’ve outlined a slightly-hacky solution for this problem using Google Tag Manager and Javascript, at https://community.hubspot.com/t5/APIs-Integrations/Force-CTA-Scripts-to-Run-on-History-Change-for-single-page/m-p/977800/highlight/true#M73696
Hi everyone! Thanks for submitting feedback around this idea.
We recently launched a CTA API, through which CTAs are supported in Single Page Applications (SPAs). This API only works with CTAs created with the new editor, and does not support Legacy CTAs.
You can read more about this API here: Accounts Dashboard | HubSpot
@radapop I’m extremely glad there’s now proper API support for this. We are wanting to use CTA’s to provide in app help for new users. Not an ideal solution for in app help, but it’s a good start for us at the moment.