Repository navigation
Add NPS score and date and NewDot migrated date as FullStory custom user properties #103321
Description
Problem
In FullStory, we can't filter or segment sessions by a user's NPS score or by when they moved to NewDot. This makes it hard to compare the behavior of promoters and detractors, or of recently migrated and long-time NewDot users.
Proposal
Add three custom user properties to FullStory:
- NPS score: the user's most recent NPS score.
- NPS response date the date of the response of the user's most recent NPS score
- NewDot migrated date: the date the user was migrated to NewDot.
Context
FullStory identifies the user in src/libs/Fullstory/index.ts. It passes the USER_METADATA Onyx object as user properties. UserMetadata doesn't include either value today. The backend probably needs to add these fields to userMetadata. The App type should then be updated, and native should be checked to confirm the date is normalized correctly.
Expected result
Both properties appear on FullStory user profiles and can be used in segments.
Reported by @flaviadefaria via DM with MelvinBot.
Activity
[-]Add NPS score and NewDot migrated date as FullStory custom user properties[/-][+]Add NPS score and date and NewDot migrated date as FullStory custom user properties[/+]melvin-bot commentedon Oct 30, 2026
This issue has not been updated in over 15 days. @flaviadefaria, @c3024 eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!
melvin-bot commentedon Nov 3, 2026
@c3024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.30-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
flaviadefaria commentedon Nov 3, 2026
Thanks for picking this up @c3024 ❤️
c3024 commentedon Nov 4, 2026
NPS score and NPS response date are now FullStory user properties.
The NewDot migrated date is not included. The only stored date we have is the tryNewDot redirect timestamp. It updates every time an account switches between Classic and NewDot in either direction, so it shows the last switch, not when the account migrated to ND.
A reliable migrated date needs a new field that records when an account moves to NewDot. I will look into it.