Please add Tessen instrumentation for stitched path buttons about docs-website HOT 11 CLOSED

We currently aren't integrated with Tessen with our open source docs sites, but it's on the Docs Site Roadmap so we'll address it as a series of MFFs in the future. So we'll backlog this, and I'll take it with a label "instrumentation"

from docs-website.

@roadlittledawn if this is quick implementation on the drupal site, I think we can add it.

from docs-website.

@roadlittledawn was going to estimate this so we can prioritize it.

from docs-website.

FWIW. when i quickly dug into this, we need some reliable way of identifying the stitched path links in order to attach a click listener to just those links to report them via tessen.track() method. we can add a class or data attribute to each <a> element and that should do that trick. this would require editing some content.

from docs-website.

I have this working locally and we're able to send the URL path that user is on when clicking on it. We aren't able to send user identifying data though. anything else that should be sent along with this event?

from docs-website.

@rhetoric101 ...

from docs-website.

Okay, I've updated the script so it sends data to Tessen if the link has this data attribute set: data-tessen="stitchedPathLinkClick"

Additionally, since stitched path links are different depending on the integration, I added the link href that was clicked because that seems useful.

from docs-website.

This change is in dev and ready for review. @rhetoric101 , let me know when you have some time and we can go over it.

from docs-website.

Just deployed. Updated intro to kubernetes doc link just now and looks like it's reporting correctly.

from docs-website.

Clinton,

Sorry for the late follow-up on this! As I mentioned in Slack, those data points aren't showing up in Amplitude, even though they are showing up in DIRAC. At this point, I'm thinking you can close this since your work seems to be successful. From my discussions with the Product Analytics team, it looks like the issue where the segment isn't getting populated stems from something beyond the basic instrumentation.

Thanks,

Rob

from docs-website.

This issue has been automatically marked as stale because it has not had recent activity. It will be automatically closed if no further activity occurs. Thank you for your contributions.

from docs-website.