[Analytics] Implement tracking for user profile changes

[jakobhero]

Description

Implements tracking for user-reported user profile changes implemented in #11023 by:

• firing a profile_changed event with the old and new profile properties whenever the users submit a change to their profile
• firing an identify call with the traits { name, company, email} whenever users submit a change to their profile

Note that this change could potentially overwrite emails in tools such as customer.io with an unverified email address reported by the user.

How to test

1. Open a preview environment, sign up, and then visit the profile section. In the account tab, make changes to the vales in the fields Name, Email, and/or Company, then click Update Profile
2. Go to the debugger of Staging Untrusted and ensure that a profile_changed event that details the changes and an identify event that contains the respective user attributes are sent
3. Repeat 1 and 2 with other arbitrary combinations of the Name, Email, and Company fields to ensure stability

Release Notes

None

Documentation

Werft options:

• /werft with-preview
• /werft analytics=segment|TEZnsG4QbLSxLfHfNieLYGF4cDwyFWoe

[jakobhero]

/werft run

👍 started the job as gitpod-build-jh-analytics-profile-changes.1
(with .werft/ from main)

[jakobhero]

@chrifro i added you as reviewer because of

Note that this change could potentially overwrite emails in tools such as customer.io with an unverified email address reported by the user.

[geropl]

Note: We already have similar functionality here. Actually, this whole section should be going into protocol.ts, so it can be used from dashboard and server alike.

@jakobhero Do you want to do that? Or should I add a commit as suggestion on top?

[geropl]

Here is a commit if you want to 🍒-pick: b230334

[jakobhero]

this whole section should be going into protocol.ts, so it can be used from dashboard and server alike.

makes sense!👍🏼

Here is a commit if you want to 🍒-pick: b230334

thanks for the 🍒!🙏🏼 i used hasChanges to check before sending events, looks much cleaner now!

[chrifro]

Note that this change could potentially overwrite emails in tools such as customer.io with an unverified email address reported by the user.

I guess we can only test this once the PR is merged?

I'm not sure what you mean by "unverified email address reported by the user."

Expected behavior: the information in customer.io is in sync with the dashboard. Once any information is changed in the dashboard, the information will be overwritten in customer.io as well.

[jakobhero]

I guess we can only test this once the PR is merged?

no, apologies for not being clearer. with this change, emails in customer.io will be overwritten by new email addresses that might not be real. when users are changing their emails in the profile, we are not taking any steps to verify that they're real nor have users confirm their new email address if they're changed in the profile section, which is a step down from using the trusted emails we get through the git authenticators (i assume they have to be verified for all of them before an account is created).

Expected behavior: the information in customer.io is in sync with the dashboard. Once any information is changed in the dashboard, the information will be overwritten in customer.io as well.

this is what's going to happen if this is merged.

[geropl]

🎉 Nice, looks good!