Upcoming Sunset: Legacy CTAs

[hseligson]

We are sunsetting the Legacy CTAs (Call-To-Action) app and migrating it into a new CTA 2.0 editor tool beginning June 15, 2023. This sunset will consist of two parts:

1. Sunsetting the Legacy CTAs editor.
2. Sunsetting the Legacy CTA assets.

Please see below for more details about each part of the sunset. 

Editor Sunset

This sunset will restrict access to the CTAs editor. However, users will still be able to create, close, or edit existing CTAs.

Timeline:

• LCTAs Migrate Tool becomes available in GA Q1 2024
• New customers + customers with no Legacy CTAs lose access to CTAs Legacy homepage and editor - Q1 2024
• LCTA editor and clone options become unavailable to all remaining customers Q2 through to Q4 2024

Assets Sunset

This sunset will result in the following changes:

• Tracking will be turned off for any existing Legacy CTA.
• The assets will continue working as simple buttons, so at no point will pages be broken or missing a button during this sunset.
• HubSpot will be removing the tracking on customers’ existing CTAs, and they will turn into simple buttons. However, customers will still be able to access the historical tracking data of their existing CTAs.
• HubSpot will provide an easy way for customers to copy their legacy CTAs into new CTAs and replace them in all the pages they are used in.

Timeline:

• Sunsetting LCTA assets that haven’t received views in past 90+ days - they become simple buttons Q2 2024
• Sunsetting all remaining LCTA assets - they become simple buttons Q3 2024 through to Q1 2025

Note: Please be advised that the sunset may extend beyond September 2024. We at HubSpot will strive to follow the given timelines, but kindly note that they are subject to change.

Why is this happening?

We are launching a new CTA 2.0 in 2023, allowing customs to create engaging, reusable, trackable assets and embeddable CTAs.The current Legacy CTA tool offers fewer customer customization options and does not provide a dashboard to track, report, and compare assets for a better user experience. 

When is this happening?

HubSpot will begin the Legacy CTAs sunset on June 15th, 2023, after which new portals and existing portals with no Legacy CTAs will no longer have access to the Legacy CTAs editor. 

The Legacy CTA will continue to work as they are until Q2 2024 of next year, after which date HubSpot will start sunsetting the ability to use Legacy CTAs for tracking purposes. With that change, any existing assets on customer websites will continue to work as buttons but will stop collecting views and click data. However, HubSpot will make it easy for customers to clone and replace Legacy CTAs with new CTAs with a migration tool that will be available in Q1 2024.

Please let us know if you have any questions.

[radapop · Accepted solution]

Hi everyone! My name is Rada and I'm a product manager at HubSpot working on CTAs.

Please see this important updated announcement with regards to the CTA sunset: https://community.hubspot.com/t5/Developer-Announcements/Update-Legacy-CTA-Sunset/m-p/981759#M723

[penguinMarket]

Hello, have there been any updates on the new features that the new team is working on? 

Is there a plan in production for a bulk migration for all types of CTAs? Right now we do not have a way to bulk migrate or filter the CTAs for a way locate the most used CTAs to attack first.. This will take at least 60 days for a single manager to identify, find, update, and test all of our image-based and simple CTAs. Please give some guidance on how to bulk migrate CTAs before we run out of time. 

There has not been an update on the dev log for 2 weeks. 

Thank you!

[penguinMarket]

Any updates on this or any timeline updates? We can't start planning a project timeline if HubSpot has not released any updates or confirmed that the bugs everyone is listing below will be fixed. I never received a reply and support tickets aren't providing solutions to plan for this huge lift of a project. Please let me know.

[hseligson]

Hello, HubSpot Community!

Thank you for your engagement and feedback on our initial announcement regarding the sunset of HubSpot's Legacy CTAs. Your input is invaluable as we strive to make this transition as smooth and beneficial as possible for everyone involved.

We’ve taken your feedback and concerns to heart and are updating the scope and timeline of this sunset to accommodate our customers' needs better. We are excited to share these updates to provide additional support and preparation time for this sunset.

What’s New:

• Updated Timeline: The sunset period has been extended to Q4 2024. This extra time will allow you to plan and execute the necessary migrations without haste.
• Scope Adjustments: We’re refining the scope of the sunset by adjusting our priorities to enhance Smart CTAs and introduce A/B testing capabilities, along with addressing other identified needs, before moving forward with the legacy CTA sunset. More information on this scope will be available in the upcoming weeks.
• Resources and Support: We will provide increased flexibility and support in the coming weeks to assist you in this transition. 

For more information about this update, please refer to our latest Developer Changelog post and subscribe for any new posts on the Developer Changelog. Please note that all future updates from HubSpot regarding this sunset will be posted on the Developer Changelog and not this thread.

We understand that sunsets can be challenging and stressful, but we are committed to helping you through it all. We appreciate your patience and understanding as we work together to create a more efficient approach to this process.

Thank you!
HubSpot Community & HubSpot Developer Advocacy

[Caroline_Pretty]

We went through an extensive legacy CTA documentation, audit, and migration process and we are experiencing several issues with custom CSS styling being stripped from HubSpot CTAs when moving from the legacy to the new tool. This is happening even though the client's website is built on HubSpot and we are selecting the correct CTA type in the migration process. The cleanup for this is going to be a massive undertaking for our development team as there isn't a way to identify in either the new or legacy CTA tool which CTAs have custom CSS styling applied pre or post-migration. This is creating a lot of friction with our client as hundreds of CTAs are not rendering correctly on their website. Given this, we are pausing all HubSpot CTA migration implementations for our clients. I hope there will be increased functionality in the migration tool because with the volume of CTAs our clients have (800+) the current migration tool has made this a very painful process.

[MusicMarketer78]

@hseligson - question on reporting for the new pop-up CTAs - will there be source/medium reporting available for the view data? It would be incredibly helpful if we could see the data from sources so we can understand what is driving the traffic/engagement on the pop-up. 

Thanks!

[lexnicole]

Does this mean that when I use the migration tool to transfer over my CTAs, I will have to go find where I had it embedded on my WordPress website and re-embed all of them?

Thank you!

[hseligson]

@lexnicole and @MusicMarketer78 - Thank you both for your questions! Currently, our team is adjusting the sunset scope and timeline to provide improved support and guidance to our customers. We will soon have more information available, and I will update this post directing everyone to that update, so it won't get lost within this thread.

I apologize for any inconvenience caused and appreciate your patience while we work towards providing better support to all of you during this sunset.

[MNault]

@hseligson  Today we realized that there does not seem to be a way to migrate the form popups built in the Forms tool. Is the option to build form CTAs in the form tool going away now that form popups can be built in the new CTA tool?

[hseligson]

Hi @MNault - Thank you for the question! I believe there are no current plans to support form popups. However, I am contacting our product lead to confirm and will follow up with you when I have more feedback. Thank you!

[evaldas]

@hseligson  are there any plans for CTA 2.0 to be available as a field in Design Manger? 

The "CTA" field is still available in the Design Manager for creating modules but it looks like it's still tied to Legacy CTAs. Currently there is an issue in certain portals when a custom module contains a Legacy CTA field - it ends up causing errors.

[hseligson]

Hi @evaldas - Thank you for this feedback! We don't plan to add 2.0 as a field in the Design Manager, but we'll review this internally over the coming weeks. 

In the meantime, please submit a support ticket regarding the error and let me know if you have a ticket number.

I'll also follow up in a private message to request your HubId so our product lead can take a look and there you can let me know the support ticket number. Thank you!

[KWinberg]

When will CTA 2.0 A/B Testing be available?

[orkun]

Yes, please! Do we have an ETA on when the A/B testing feature for CTA 2.0 will roll out?

[hseligson]

@KWinberg and @orkun - Thank you for your question regarding the ETA for A/B testing for the new CTA 2.0. We're prioritizing the development of Smart CTAs and A/B testing for the new CTAs and addressing other identified gaps before proceeding with the sunset.
The sunset timeline and scope are being revised, and a new announcement will soon be published on the Developer Changelog (https://developers.hubspot.com/changelog).

Please subscribe to make sure you're up to date. I'm very sorry for any inconvenience this caused.  

[hseligson]

Hi @KWinberg - thank you for your question! I am contacting the product lead to determine when A/B testing will be available for the new CTA and will let you know once I receive confirmation. 
In the meantime, I did find a similar question, and the response provided a workaround till this feature is available: 

If you're linking to a page with a CTA you could manually create an a/b test though. You could use the targeting and target based on a query string. You can then use queries in the url to define which CTA is shown. 

For example let's say you were linking to mysite.com/contact, You could have mysite.com/contact?cta=1 and mysite.com/contact?cta=2 with those queries (the parts after the ?) being the targets for the CTA. It's not perfect as it would mean choosing a link each time but is the closest workaround I could think of at the moment. 

[BHolman9]

Hey @hseligson,

I've got a couple of questions:

1. When I migrate a legacy CTA using the migrate tool will I need to manually update any reports or dashboard that had the legacy CTA. Or ,will it automatically add in the new CTA to relevent reports and dashbaords where the legacy one was?

2. If we do not migrate CTA’s that open pdf's in time will HubSpot automatically change the CTA to a normal link that opens a pdf? 

3. If we prematurily delete legacy CTA's we reliase should just be normal links, will HubSpot delete the button off the page it is on. Or, will it keep the button displayed on the page but just downgraded from CTA button to a normal button?

[hseligson]

Hi @BHolman9  - thank you so much for your questions! Below, I've included feedback for each question:

1. When I migrate a legacy CTA using the migrate tool will I need to manually update any reports or dashboard that had the legacy CTA. Or will it automatically add in the new CTA to relevent reports and dashbaords where the legacy one was? No, when migrating a legacy CTA to a new CTA, you can refer to the new CTA dashboard. Please see the screenshot exemplifying how to easily access the new CTA dashboard.
I believe you might have meant custom dashboards from reporting, and yes, you are correct that you will need to replace these manually.

2. If we do not migrate CTA’s that open pdf’s in time will HubSpot automatically change the CTA to a normal link that opens a pdf?

Yes, this is correct.

3. If we prematurily delete legacy CTA’s we reliase should just be normal links, will HubSpot delete the button off the page it is on. Or, will it keep the button displayed on the page but just downgraded from CTA button to a normal button?
It will stay as a button, but it will just lose the tracking attached to it.

Please let me know if you have any further questions!

[MNault]

Good morning! I  found out through a team member on our marketing team that HubSpot has a Beta CTA migration tool. For all those following this Announcment can you elaborate on this? Any additional information you can give us would be helpful. Thank you!

[hseligson]

Hello! We announced the CTA migration tool beta in our January 2024 rollup in the HubSpot Developer Changelog. Anyone can find more details by referencing these links:

• January 2024 Rollup, Community Forum: https://community.hubspot.com/t5/Developer-Announcements/January-2024-Rollup/m-p/914183#M597
• January 2024 Rollup, Developer Changelog: https://developers.hubspot.com/changelog/january-2024-rollup 

Thank you!