What is this about?
In segment, in order to improve user props update, identification is expected as soon as possible. We currently only do it when optin and not at app start when user is already optin.
We may miss some properties updated.
Scenario
No response
Design
No response
Technical Details
add identify in the Metametrics.configure after metametricsId is ready
Threat Modeling Framework
No response
Acceptance Criteria
- check identify is sent at app startup only when user has metrics enabled.
- when metrics disabled, no identify and no track should be sent.
- unit test updated if needed.
Stakeholder review needed before the work gets merged
References
https://github.com/MetaMask/metamask-mobile/blob/main/app/core/Analytics/MetaMetrics.ts#L512-L529
What is this about?
In segment, in order to improve user props update, identification is expected as soon as possible. We currently only do it when optin and not at app start when user is already optin.
We may miss some properties updated.
Scenario
No response
Design
No response
Technical Details
add identify in the Metametrics.configure after metametricsId is ready
Threat Modeling Framework
No response
Acceptance Criteria
Stakeholder review needed before the work gets merged
References
https://github.com/MetaMask/metamask-mobile/blob/main/app/core/Analytics/MetaMetrics.ts#L512-L529