How does the point and click UI generate event targets? At my work we use Pendo which sounds very similar to Freshpaint. Pendo’s UI generates CSS selectors. Problem is that we use CSS modules and our class names include a hash, so they change frequently. Also our classes aren’t designed to communicate the semantics the Product team is trying to capture, and there’s also no way for Pendo to know that the selector it generated uniquely captures whatever event the user wants - it’s entirely possible that the same selector could occur on a different screen.

We’ve been asked to “stabilize” our class names for the product team, so that Pendo doesn’t “break”, but we have resisted as fundamentally this is not what CSS is meant for. Nonetheless we now have an invisible, undocumented coupling between our application internals and Pendo.

IMO the only way this kind of event tracking can be done right is if developers and Product communicate and the devs, who understand the code, put the tracking in the right place.

I’d encourage you to bless a “data-freshpaint” attribute as the preferred way to link events to your system, if the way it currently works is CSS selectors.