It would be great, but not P0 for LA or EA, to have button-click style analytics within the toolbar codebase.

The problem is that we don't and can't have the amplitude sdk installed and sending messages directly to aplitude.com. The reason is that the messages would probably be coming from the 3rd party site that is hosting the toolbar, and we can't add that to the amplitude domain allow list.

Also, this kind of non-essential data would probably need to be opt-in or opt-out, we need to decide on the config.

Approaches:

1. We could put the amplitude sdk inside the iframe, and use that to proxy messages directly to amplidute.com to be saved. Ideally we have a separate Project in Amplitude to keep data separate from sentry.io data. OR we'd need to make sure that we annotate messages to know that they come from the toolbar and don't mess up any existing pipelines that are sentry.io specific
2. Similarly we could setup an endpoint within getsentry that accepts messages from the toolbar (with or without auth? without is nice for seeing impressions but no clicks). This endpoint could forward messages into any of our storage destinations: amplitude, reload, gcs, etc.
3. We go without!
4. We leverage sentry traces and annotate things! see also [DevToolbar] Figure out whether and how to instrument the toolbar sdk with the JS Browser SDK #62