Add attribution to redirections to mfT

metalbear-co / mirrord

Connect your local process and your cloud environment, and run local code in cloud conditions.

https://mirrord.dev

MIT License

3.8k stars 103 forks source link

Add attribution to redirections to mfT #2703

Open eyalb181 opened 2 months ago

eyalb181 commented 2 months ago

We redirect users to mfT from within the product (e.g. "You're trying to target a deployment, this is supported in mfT"). We need to be able to attribute website visits to these links in order to analyze them, do A/B tests, etc.

gememma commented 2 months ago

More details:

use query parameters "utm_source" and "utm_medium" (most others get removed by plausible)
differentiate between features that cause the redirect eg. multipod separate from copy_target
track both the source message (above) and the source platform i.e. VSCode/IntelliJ/CLI
most links are to documentation on MfT, there is one to app.metalbear.co which can be handled separately

Razz4780 commented 1 month ago

This will require some extra care in the IntelliJ plugin, since links in notifications there are not processed/rendered - just embedded raw. We don't want to show ugly links to the users. Possible solutions:

Make the links clickable and shorter in the notification body (not sure if doable)
Display a different version of the notification in the IDE with extra actions (Progress:ide)