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-placeholderclass). It relies entirely on the global HubSpot tracking script to read thedata-hubspot-wrapper-cta-idand 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!