"Currently, we have a default date set that is at least 25 years before today's date. There are policy concerns that this pushes people under 13 to enter an incorrect birthday."

████: "Wanted to give an update on our recent age fallback tests and provide Acquisition's recommendation on path forward. TL;DR: Acquisition wants to launch our existing Age Management solution: defaulting to today's date on the registration birthday step & age fallback together for a net impact of -12.5M MAPMAPMonthly Active PeopleCore Meta engagement metric counting distinct people active on a platform in a month. Paired with DAP in internal goal-setting; the MAP/DAP ratio is used as a measure of how frequently a monthly user returns.Full entry ↗/year across all interfaces on January 15th. We have now tested falling back to age buckets and a binary over/under 13 option. Neither experience was better than the age fallback experience already built in terms of retention. Context: As previously discussed, Acquisition needs to change the way we currently ask for age in registration. Currently, we have a default date set that is at least 25 years before today's date. There are policy concerns that this pushes people under 13 to enter an incorrect birthday. For the last few months we've been testing solutions, and landed on one which includes two major changes: 1. Defaulting to today's date on the registration birthday step. This will be an estimated -174k WAP@14 hit (18.4M MAP/year). 2. The age fallback product across all interfaces. This will be an estimated +54k WAP@14 win (5.9M MAP/year) on top of the change to default to today's date. We net out at a -12.5M MAP/year hit with these two changes. This is -4.5M India MAP/year, -1.5M Indonesia MAP year and -210k US MAP/year. 65% of the impact comes from FB4A, 12% from Lite, 11% from mTouch and 10% from Kite. New test results: Per feedback from Brian and Alex, over the last month we've tested a new solution - falling back to age buckets or over/under 13 instead of falling back to an age entry screen. These tests were not better than our existing age fallback experience in terms of retention. Both the age buckets & o/u 13 get significantly more people through the registration than age fallback, however the same or more people select an under 13 age and are therefore not able to successfully register. So we net out neutral to negative on/conf. The main test groups are below and you can find a more detailed description of the tests and results can here." "Recommendation: The Acquisition team proposes to launch the two above changes to the birthday step in registration across all platforms on 1/15. We plan to continue to do some iterations on the birthday step in Q1, like error messaging & UI changes, but do not have any other wins that can be achieved quickly that will recover a significant amount of the impact and thus believe we should ship and iterate." ████: "I'm a bit confused as to why they want the over/under 13 buttons when they say it didn't work better than the existing age fallback experience (which is what again?) -- maybe I'm reading this wrong but in the very next sentence they say 'both the age buckets and o/u 13 get significantly more people through the registration then age fallback.' Is the distinction here that the tests didn't impact RETENTION but it got more NEW users? Which is also confusing b/c why would they be going through an age flow if they're old users we're retaining? Or perhaps retention means whether or not they complete the flow? Full paragraph I'm referencing is here and highlighted in blue below: Per feedback from Brian and Alex, over the last month we've tested a new solution - falling back to age buckets or over/under 13 instead of falling back to an age entry screen. These tests were not better than our existing age fallback experience in terms of retention. Both the age buckets & o/u 13 get significantly more people through the registration than age fallback, however the same or more people select an under 13 age and are therefore not able to successfully register. So we net out neutral to negative on/conf. The main test groups are below and you can find a more detailed description of the tests and results can here."