-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: remove duplicate dapp transaction analytics #11628
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Quality Gate passedIssues Measures |
i was asked to comment on this ticket, but it's not clear what the result of this PR would correct from the description alone. In the case of an event, like If this is not the case, it would be helpful to understand both the before and after effects of this PR. |
Sorry, I still don't understand what this ticket is trying to address. Happy to jump on a call if helpful. Generally,
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is global change breaking all the anonymous system for all the app. I don't think this is what you want to do...
This PR has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions. |
This PR was closed because there has been no follow up activity in 7 days. Thank you for your contributions. |
Description
The
Dapp Transaction Completed
analytics was being tracked & sent to Segment twice because inMetaMetrics
we:anonymous: false
sensitiveProperties
: it is sent to Segment with the flaganonymous: true
This was the case with the
Dapp Transaction Completed
as it contains sensitive propertiesactive_currency
andasset_type
Consequences:
The non-anonymous event in Segment contains:
while the anonymous event does not contain this information and user ID
which means we would lose location information of transaction events and also lose userId information.
NOTE
If we toggle the behaviour and only send the non-anonymous payload (like is the case with the rest of the events) then we would lose the sensitive information properties only namely
active_currency
andasset_type
.Full payload:
With anonymous info (the only data that would otherwise be logged with this PR change):
Without anonymous info (the additional "duplicate" info that is currently logged in addition to the above):
Pre-merge author checklist
Pre-merge reviewer checklist