Spike (website): test out Carbon Autotrack

[shleewhite]

📌 Summary

This PR is testing out Carbon Autotrack on the HDS website.

Dev mode is currently enabled, so all elements that are 'tracked' by Autotrack are highlighted. The tracking isn't hooked up to anything currently, it just console logs the information it would track about the element. Like this:

Override event (UI Interaction) - 
Data: {"CTA":"Code","text":"Code","elementId":"tab-code","location":"top: 261.97442626953125px, left: 526.40625px","uiElement":"button","type":"button","objectType":"[role=\"tab\"]",
"data":"{\"autotrackDevindex\":\"[role=\\\"tab\\\"]: button: 1\"}","variation":"cds-autotrack-dev-highlight","action":"Autotrack","actionType":"click","color":""}

To get it to actually be tracked, we need to do some setup to get access to IBMs system.

📸 Screenshots

🔗 External links

Jira ticket: HDS-5661

---

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
hds-showcase	Ready	Preview	Nov 24, 2025 3:41pm
hds-website	Ready	Preview	Nov 24, 2025 3:41pm

[shleewhite]

Presumably, we'd need to add all the classnames used on links and buttons in the design system to this list just to be safe. But Autotrack also tracks all buttons/links by default.

[shleewhite]

Closing this because we got the information we needed about Autotrack.