Skip to content

track sensitiveProperties in a duplicate event.#9807

Merged
brad-decker merged 1 commit intodevelopfrom
support-sensitive-properties
Nov 10, 2020
Merged

track sensitiveProperties in a duplicate event.#9807
brad-decker merged 1 commit intodevelopfrom
support-sensitive-properties

Conversation

@brad-decker
Copy link
Copy Markdown
Contributor

@brad-decker brad-decker commented Nov 5, 2020

Explanation:

  • A common pattern we're seeing in the new MetaMetrics schema is duplicated events, one with the anonymousId one with the user's real MetaMetricsID.

Details:
by providing an object with sensitiveProperties, those properties will be sent in a separate event with anonymousId set instead of the user's MetaMetricsID. If both sensitiveProperties and properties are provided then the anonymous event will include both, and the identifiable event will include only properties.

@brad-decker brad-decker requested review from Gudahtt and danjm November 5, 2020 20:02
@brad-decker
Copy link
Copy Markdown
Contributor Author

@Gudahtt and @danjm curious about your thoughts on this. I imagine that there will be more places with two events than there will be one event in the future...

@Gudahtt
Copy link
Copy Markdown
Member

Gudahtt commented Nov 6, 2020

This seems like a good idea!

I hope we're not to cavalier about what we're collecting with these "sensitive properties", as we still can't include anything that is identifiable on its own. But having this pattern built-in seems convenient to me - and helps explain to the reader what's happening, whereas the old pattern of two events always looks strange at first glance.

@brad-decker brad-decker force-pushed the support-sensitive-properties branch from 4330f90 to a7feec6 Compare November 9, 2020 19:20
@brad-decker brad-decker changed the title RFC: allow for tracking sensitive properties in duplicate event track sensitiveProperties in a duplicate event. Nov 9, 2020
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [a7feec6]
Page Load Metrics (466 ± 51 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint34108502110
domContentLoaded32765646410651
load32965946610651
domInteractive32765646410651

@brad-decker brad-decker marked this pull request as ready for review November 9, 2020 20:15
@brad-decker brad-decker requested a review from a team as a code owner November 9, 2020 20:15
@brad-decker brad-decker force-pushed the support-sensitive-properties branch from a7feec6 to b492ea2 Compare November 9, 2020 22:59
@metamaskbot
Copy link
Copy Markdown
Collaborator

Builds ready [b492ea2]
Page Load Metrics (510 ± 62 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint328845168
domContentLoaded31674650912962
load31774851012962
domInteractive31674650812962

Copy link
Copy Markdown
Member

@Gudahtt Gudahtt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@brad-decker brad-decker merged commit 980b140 into develop Nov 10, 2020
@brad-decker brad-decker deleted the support-sensitive-properties branch November 10, 2020 15:49
@github-actions github-actions bot locked and limited conversation to collaborators Nov 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants