GET ONLY the 'Usage' field of TitlePublicConfigurationModel. Retention policy for the player's activity history (Usage). The engine keeps a rolling window of per-day records and folds everything older into monthly totals, then months of finished years into yearly totals — otherwise the per-day map grows forever inside the hottest document on the platform. WARNING: the fold is IRREVERSIBLE, per-day detail outside the window is gone for good. Do not lower DailyWindowDays below 400 without also lowering the analytics range cap: publisher analytics (DAU/WAU/MAU, retention cohorts, funnels) is computed lazily from those very per-day records, accepts ranges of up to 366 days, and needs 30 extra preceding days per requested day for MAU. Also holds SessionIdleTimeoutMinutes: how many minutes of silence end a session (default 30, the same rule Firebase/GA4 use, so the two reports stay comparable). The session boundary is decided by the SERVER from the player's last activity — the client's IsNewSession flag is not trusted for counting. Leave every field null unless you have a specific reason — the defaults (enabled, 400-day window, 30-minute session gap) are what the analytics horizon was sized against.