upcoming: [UIE-9670] - Add Pendo IDs for Marketplace Filter Options and Product Cards

[pmakode-akamai]

Description 📝

Add Pendo IDs for Marketplace Filter Options and Product Cards

Changes 🔄

• Added Pendo IDs for Marketplace Filter Options and Product Cards
• Added a new optional data-pendo-id prop to the SelectionCard component to support analytics tracking

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

Target release date 🗓️

Feb release

How to test 🧪

Verification steps

• Inspect the elements and ensure data-pendo-id is added appropriately to the Autocomplete options and Product Cards
  • To inspect the Autocomplete options, remove the focusout event listener in Browser DevTools -> Elements
    

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

[dwiley-akamai]

Verification steps ✅
Code review ✅

[tvijay-akamai]

Currently, when a category or type is selected, the Pendo ID remains static (for example, data-pendo-id="Cloud Marketplace Catalog-Category" or data-pendo-id="Cloud Marketplace Catalog-Type").
Could you check with Susana and Davyd whether this should be made dynamic based on the user’s selected category or type?
Also, let's confirm whether assigning Pendo IDs to individual dropdown options is required, or if it is sufficient to reflect the selected category or type in the Pendo ID of the select field itself.
@davyd-akamai

[pmakode-akamai]

Currently, when a category or type is selected, the Pendo ID remains static (for example, data-pendo-id="Cloud Marketplace Catalog-Category" or data-pendo-id="Cloud Marketplace Catalog-Type"). Could you check with Susana and Davyd whether this should be made dynamic based on the user’s selected category or type? Also, let's confirm whether assigning Pendo IDs to individual dropdown options is required, or if it is sufficient to reflect the selected category or type in the Pendo ID of the select field itself. @davyd-akamai

If we made the input's data-pendo-id dynamic based on the selected option, Pendo would treat the input as a new element every time the selection changes. This could break historical tracking and make input-level analytics confusing.

I think It's better to keep the input ID Cloud Marketplace Catalog-Category static, and track the selected option separately using the dynamic Pendo IDs on each option, like the same pattern we follow in CM, for example in MaintenancePolicySelect at L63 & L79

[tvijay-akamai]

Currently, when a category or type is selected, the Pendo ID remains static (for example, data-pendo-id="Cloud Marketplace Catalog-Category" or data-pendo-id="Cloud Marketplace Catalog-Type"). Could you check with Susana and Davyd whether this should be made dynamic based on the user’s selected category or type? Also, let's confirm whether assigning Pendo IDs to individual dropdown options is required, or if it is sufficient to reflect the selected category or type in the Pendo ID of the select field itself. @davyd-akamai

If we made the input's data-pendo-id dynamic based on the selected option, Pendo would treat the input as a new element every time the selection changes. This could break historical tracking and make input-level analytics confusing.

I think It's better to keep the input ID Cloud Marketplace Catalog-Category static, and track the selected option separately using the dynamic Pendo IDs on each option, like the same pattern we follow in CM, for example in MaintenancePolicySelect at L63 & L79

Makes sense. Thanks.

[linode-gh-bot]

Cloud Manager UI test results

🎉 866 passing tests on test run #6 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
0 Failing	866 Passing	11 Skipped	38m 1s