[EDIT] In order to ensure no one gets caught out by this retirement, we've added a small but important change: we will create a whitelist for apps that contained a funnel or segment that uses unity.sceneLoad. If you want to keep unity.sceneLoad as-is for now, simply create such a funnel or segment before May 28. ALL processing on unity.sceneLoad will be retired at the end of 2017. This should give everyone sufficient time to migrate to one of our proposed solutions. [/EDIT] tl;dr We plan to remove the unity.sceneLoad custom event unless we are strongly persuaded otherwise. The event will cease to be processed starting May 29. You may have noticed a custom event on your dashboard that you didn't put there. We created unity.sceneLoad to provide developers something they could use right away to build, say, a level progression funnel. As the product improved and more developers became accustomed to defining their own custom events, it became less necessary to have this default event. We've decided its day is over. So why are we removing this event now? You didn't add it to your project. You have no control over this event or its data. E.g., you can't add custom parameters. The majority of custom events in our system are unity.sceneLoad. If we could free up those resources, we could move faster on some cool features. unity.sceneLoad events clog raw data, obscuring the custom events you are actually looking for. How will this affect developers? If you have funnels or custom segments with this event, they will no longer function correctly. You will need to remake them using another custom event. This event will also be removed from Raw Data Export files. How can you replace this event? We now recommend the adoption of Standard Events for this purpose. In particular, level_start and level_complete for tracking level progression, and tutorial_start, tutorial_step and tutorial_complete for onboarding. What if you need this event the way it is? Our current plan is to stop processing these events on May 29. If you or someone you know is actively making extensive use of this event, please respond to this post and let us know what use case you're trying to solve.