-
-
Couldn't load subscription status.
- Fork 4.5k
Description
Q: If we have two feedback buttons sharing the same URL - are there any best practices for differentiating feedback coming from them? (i.e. let's say we have a button for grouping, and one for issue details)
what we're finding on issues is that just using url isn't granular enough for us, and we have enough volume that it can be very manual to sort through
the challenge is volume but also targeting....i.e. the use case is not a generic feedback button, but feature-specific ones
from slack https://sentry.slack.com/archives/C05J714QPRR/p1716306417928009
context: https://sentry.slack.com/archives/C04KZQBNQ2U/p1716306433600159?thread_ts=1716303774.260649&cid=C04KZQBNQ2U
The real problem here is that there's no way to call setTag() for a feedback. https://docs.sentry.io/platforms/javascript/enriching-events/tags/
This is a gap in the feedback api, and missing feature we should fix.