Surface analytics

[argyleink]

not sure how to do this, but it'd be super rad if designers could inspect and contribute to what and when analytics are being tracked on the page/components

[lcds90]

Hi @argyleink, super excited to contribute to this topic! I would like to bring some ideas based on my day to day and have a bridge as UX metrics

The initial idea is

• Offer an input as a pre-definition of selectors, being able to separate with , to have the option of one more selector, previously located selectors will be saved in the localStorage after saving
• When selecting certain elements, can generate a list to export and pass on to the development team to map
• User can upload and download with the following pre-definitions
• The copy button would copy all mapped selectors in the actual page

Selector	Normalized name	Extra description	Is mapped
[data-track="test"]	Button with action	This button does x action	true
[data-track="test-not-mapped"]	Back button	This button returns to the previous screen	false

I'm still adapting some of the presentation points, but I'd like some feedback on this issue

• The name displayed would be the normalized name, otherwise the fallback will be the selector
• The intention is to save an object with these four keys so that the description is integrated into the details only when there is registration
• I would still like to validate how the user registers this information, so I'm open to feedback!

All my changes are here, let me know what you think about!

https://github.com/user-attachments/assets/6abfb62c-76a5-42d8-8f3b-bfe5cd77fd13

For some inspiration, I'm seeing about heurio too! https://www.heurio.co/product-management

[argyleink]

nice proto! starting a data-track namespace should work great. the download/upload would need a normalized scheme for working with an analytics service, which is doable but probably tough to get others to do, but maybe there's an existing scheme that services offer? starting to make this feature sound more like an integration than a generic feature, but i suppose it kind of needs to be.

i wonder too, if the Inspect overlay tooltip could show some of the information too? hover over an element and see what's being tracked on it. then maybe take a screenshot and note what else, or what changes, should be made about that tracking?

glad you're finding the tool hackable!