We have updated our Privacy Policy as of September 22, 2023, for more information click here
The orginalTimestamp precision has been updated to go from seconds to milliseconds when sending impressions to Segment. This update makes our timestamp field more consistent with the precision Segment uses.
The feature flag definitions tab has added two minor UX updates to the editor flow. The treatment section will now automatically collapse once a flag definition has been created/updated. Also, users will be able to view treatment information via the environment cards on the left. These enhancements help the user understand which treatments are available in their environment and guide them to the targeting section.
When filtering your organizational metrics on the Metrics impact page, MCC will only be applied once for all organizational metrics. This will prevent users from seeing different p-values when metric results are filtered.
To help prevent unintentional resets of your data, the recalculate metric button has been disabled for feature flags that don’t have any data available for calculations or haven’t received traffic within Split’s data retention period.
The feature flag configuration flow on the definition tab has been reimagined with updated terminology and new visual cues. This will enable users to configure flags with a higher degree of confidence for any use case (percentage-based rollout, on/off, etc.).
The entire Split application has gone through a visual refresh. Users will see a modern, forward-looking aesthetic with refined colors tuned for accessibility, visual cues, and more.
To reduce the confusion between “Split”, our product, and “split”, the feature flag, we are changing the term “split” to “feature flag” across our application and documentation.
Customers can now map Split traffic types to mParticle MPID when sending events to Split.
Users can now clone API Keys with the same access levels and scope as the key that is cloned. This will enable users to securely change/rotate keys on a regular basis while eliminating manual work.
Split now supports TLS encryption for Split Synchronizer and Split Proxy endpoints. This will enable developers to further secure their SDK traffic.
Developers can now encrypt the persistent cache of rollout plans on their iOS and Android SDKs. This will help enhance the security of this data.
Developers can now configure specific proxies using higher precedence than environment variables to perform the server requests for the .NET SDK. This will give developers the flexibility to proxy Split traffic separated from app traffic.
Essential scheduling provides the capability to launch a feature on a certain date and time, up to 90 days in advance. This enables users to get all the necessary rollout work done, like getting approvals, long before the release.
There are new UI and UX updates to the feature flag editing experience that make the selection of environments and the editing of flag details more intuitive and easier. The updates include an environment pick list showcasing feature flag traffic per environment, production environment indicators, and upgraded headers to easily edit flag details.
With SCIM Support, IT Admins can now manage Split users and groups using their preferred Identity Provider (IdP) including Azure Active Directory and Okta. This will help streamline the onboarding/offboarding processes as well as reduce the risk when governing users outside one’s security platform.
We’re excited to accompany you on your journey as you build faster, release safer, and launch impactful products.
