feat: [UIE-9805] - Extract EUUID from /profile header and send to Adobe analytics

[tanushree-akamai]

Description 📝

Make the EUUID (Enterprise UUID) from the X-Customer-Uuid API response header available to Adobe Analytics via _satellite.track(), including for users with restricted billing access.

Changes 🔄

List any change(s) relevant to the reviewer.

• EUUID is captured once per session (flag prevents duplicate tracking)
• EUUID is included in every page view event after capture
• Works for all authenticated users including restricted billing access

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Preview 📷

How to test 🧪

Verification steps

• Add this to your .env file: REACT_APP_ADOBE_ANALYTICS_URL='https://assets.adobedtm.com/fcfd3580c848/15e23aa7fce2/launch-92311d9d9637-development.min.js'
• Use the browser tools Network tab, filter requests by "adobe", and check that successful network requests have been made to load the launch script and its extensions.
• Add a breakpoint in line 28 of useAdobeAnalytics.ts file
• Reload the page, when the breakpoint is encountered, in the browser console, type _satellite.setDebug(true)
• You should see Adobe debug log output in the console. Each page view change or custom event that fires should be visible in the logs.

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #2 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	866 Passing	11 Skipped	42m 13s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

[jdamore-linode]

Hey @tanushree-akamai, having trouble finding a way to test this, but will continue looking into it tomorrow. Feel free to reach out if you have any questions/suggestions! Thanks!

[tanushree-akamai]

Hey @tanushree-akamai, having trouble finding a way to test this, but will continue looking into it tomorrow. Feel free to reach out if you have any questions/suggestions! Thanks!

@jdamore-linode : I have elaborated on the testing steps, hope it helps!