If your marketing team still relies on legacy CTAs in HubSpot, you’re not alone.
These older call-to-action tools are deeply embedded in many portals, often tied to established tracking methods, globally used modules, or long-running templates.
While HubSpot has introduced newer CTA tools with expanded design and analytics features, the original version continues to play a practical role for teams that rely on consistent reporting and stable historical data.
You may be updating an older page and find a CTA that still drives conversions or feeds lifecycle workflows. Preserving that data stream matters. Replacing or removing it can break dashboards or erase valuable comparison points.
This guide explains what a legacy CTA is, where to find it, and how to use it correctly, including setup considerations and reporting behavior.
Understanding Legacy CTAs in HubSpot
A legacy CTA in HubSpot is a clickable button or image used to prompt a visitor action, such as downloading a resource, submitting a form, or navigating to another page.
These CTAs focus on core functionality:
- Basic styling
- Standard performance tracking
- Flexible placement across pages and templates
To access legacy CTAs, navigate to Marketing > Lead Capture > CTAs in your HubSpot portal.
From there, you can:
- Build CTAs that link to external URLs, HubSpot pages, or files
- Track views, clicks, and conversions
- Embed CTAs using code or insert them through HubSpot modules
Even with newer CTA tools available, legacy CTAs remain active and supported. They are especially useful when working with older templates or global modules built around legacy embed formats.
In HubSpot CMS, the legacy CTA module is available in the Design Manager, allowing it to be placed directly in templates or individual pages.
How It Works Under the Hood
When a legacy CTA is added to a HubSpot page, HubSpot inserts a tracking script tied to a unique CTA ID.
Each page load and click sends data back to HubSpot analytics. If a visitor later converts, HubSpot connects that interaction to the contact record using cookies.
Required Inputs:
- Internal Name: Used for filtering and reporting
- Button Type: Text, image-based, or custom HTML
- Destination Link: External URL, file, or HubSpot page
- Placement: Embedded via module or inserted with code
Captured Metrics:
- Total views
- Clicks and click-through rate
- Contacts influenced by the CTA
With the HubSpot tracking code installed, these interactions are logged for both anonymous visitors and known contacts. This continuity is one reason legacy CTAs remain relevant across long-running campaigns.
Design flexibility is limited. Styling is inherited from surrounding CSS, so previews across screen sizes are important before publishing.
Main Uses Inside HubSpot
Tracking Conversions on Landing Pages
Legacy CTAs are often used on landing pages tied to forms or gated content.
Example:
After updating an ebook landing page, a team places the same legacy CTA above the signup form. Using the existing CTA ID allows quarter-over-quarter performance comparison without disrupting reports.
Embedding Calls-to-Action in Blog Posts
Legacy CTAs can be placed directly into blog content using embed code.
Example:
A CTA linking to a related webinar is added at the end of each blog post. Over time, reporting shows which topics generate the most clicks.
Linking Emails to HubSpot Pages
Using the same CTA ID across emails and landing pages consolidates reporting.
Example:
An event follow-up email and recap page both use the same legacy CTA. Reports show whether engagement occurred on the page or through email clicks.
Using in Global Modules or Footers
Legacy CTAs work well in global modules where consistent tracking matters more than design flexibility.
Example:
A footer CTA links to a contact form. Because the CTA is embedded in a global module, sitewide exposure can be measured across all pages.
Common Setup Errors and Wrong Assumptions
CTA Not Visible Due to Missing Script
Explanation:
If the CTA is embedded on a page without the HubSpot tracking code, metrics will not be recorded.
Fix:
Install the HubSpot tracking snippet and confirm views and clicks appear in CTA reports.
Wrong Placement in Modular Templates
Explanation:
Some layout containers cause styling or alignment issues.
Fix:
Place CTAs in stable containers or adjust styling in Design Manager.
Duplicate CTA IDs Across Templates
Explanation:
Reusing the same CTA ID across unrelated pages merges metrics and skews reporting.
Fix:
Create new CTAs for unique page usage.
Misaligned Reporting Periods
Explanation:
Comparing legacy and newer CTAs without adjusting methodology leads to misleading results.
Fix:
Segment reports by CTA type and timeframe.
Step-by-Step Setup or Use Guide
Before starting, confirm you have permission to edit CTAs, pages, and templates.
- Go to Marketing > Lead Capture > CTAs
This is where legacy CTAs are created and managed. - Create a New CTA
Click Create CTA and select the legacy option if prompted. Use a clear internal name. - Choose a Button Style
Select text, image, or custom HTML, then set link destination and styling. - Save and Copy the Embed Code or Assign to a Module
Choose based on how your page is built. - Open the Page Editor or Template
Navigate to the page or template where the CTA should appear. - Insert the Legacy CTA Module
Select the CTA from the dropdown inside the module. - Publish and Test
Publish the page and confirm views and clicks appear in the CTA dashboard. - Review Performance After 24 Hours
Validate data accuracy before promoting the page.
Measuring Results in HubSpot
Legacy CTAs provide detailed performance data inside Marketing > Lead Capture > CTAs.
Available metrics include:
- Views
- Clicks
- Click-through rate
- Contacts influenced
For campaign-level analysis, create custom reports using CTAs as the data source.
Review Checklist:
- Confirm views appear shortly after launch
- Match clicks with landing page sessions
- Watch for abnormal click-through rates
- Connect CTA activity with forms and workflows
CTA clicks are most useful when tied to downstream conversions and contact activity.
Short Example That Ties It Together
A Q3 campaign builds on a lead magnet launched the previous year. The landing page already includes a legacy CTA.
The team updates the asset link and republishes the page. Email traffic is routed to the updated page, and because the CTA ID remains unchanged, the performance history stays intact.
Reporting shows current engagement alongside prior results, without rebuilding dashboards or losing attribution.
How INSIDEA Helps
Managing legacy and newer CTAs across HubSpot pages requires discipline, especially when templates, reports, and workflows overlap.
INSIDEA supports teams that want stable tracking without disrupting existing data structures.
Support areas include:
- HubSpot Onboarding: Portal setup, permissions, and baseline configuration
- Ongoing HubSpot Management: Template governance, CTA usage consistency, and data hygiene
- Automation Services: Workflow logic aligned with actual user behavior
- CRM and Reporting Sync: Clean attribution across marketing and sales
For teams deciding whether to retain or replace legacy CTAs, INSIDEA provides practical audits and implementation guidance. You can hire HubSpot experts who understand how CTA decisions affect reporting continuity.
INSIDEA also delivers HubSpot consulting services for organizations that need long-term structure, reliable tracking, and controlled evolution of their CMS and CTA framework.
Don’t let outdated CTA handling disrupt clean measurement. With the right structure in place, every click remains trackable and meaningful.
