CTA not working without HubSpot Tracking Code

Hi,

Due to how the embed code for the new interactive CTAs is set up for external (non-HubSpot) CMS pages, the CTAs aren’t fully functional if the HubSpot tracking code is missing from the website—or if it’s blocked because the user hasn’t granted cookie consent.

Looking at the code, the technical difference is quite clear:

  • The legacy CTA embed was self-contained. It loaded its own dedicated script (js.hscta.net/cta/current.js) and provided a fully functional HTML fallback.

  • The new CTA embed acts purely as a temporary shell (using the hs-cta-simple-placeholder class). It relies entirely on the global HubSpot tracking script to read the data-hubspot-wrapper-cta-id and dynamically render the CTA.

Because of this shift, anytime a user declines cookies and blocks the global tracking script, the dynamic rendering fails, leaving behind a broken placeholder or mere fallback image.

Is there any workaround for this? The legacy approach, which didn’t rely on the global tracking script to render basic CTA functionality, was in my opinion a much more reliable and robust approach. Any insights would be appreciated!

Hi @highfidelitymkt, I hope that you are well!

Thank you for your detailed explanation and thoughtful feedback, we really appreciate you taking the time to outline the differences between the legacy and new CTAs.

This is currently a limitation of the new interactive CTAs when the HubSpot tracking code is missing or cookie consent hasn’t been granted. I invite you to upvote this similar Idea " Allow loading new CTAs (Beta) outside of iframe " for more visibility.

The good news is that there is a workaround! You’ll find more information thanks to the solution of @TomM2 on this thread “Pop-up form on click using CTA is blocked when cookies are rejected – is there a way to avoid this?”. I encourage you to check it out, and hopefully it will help bridge the gap.

Let us know how it goes!

Have a wonderful weekend!
Bérangère