Log in to Split using your corporate credentials with Split’s support for SAML(Security Assertion Markup Language). Configuring SAML lets all of your teammates access Split using the credentials stored in your organization’s Active Directory, Okta, or another identity store that has been configured with a SAML Identity Provider. Documentation
Security Certifications Available Performed and past pen-test and OWASP10 analysis. Report available on request.
Clickable segment names in targeting definition, making it easier to navigate between your Splits and Segments.
Usage tab shows the number of calls across your organization’s Splits.
The Split Synchronizer coordinates the sending and receiving of data to a remote data store that all of your processes can share when updating definitions and rules for the evaluation of treatments. Documentation
Custom impressions listener available for .NET, Java and Ruby—see each language’s SDK documentation for more. Documentation
Increase the exposure of customers exposed to the Split by specifying the percentage of traffic that the ‘targeting rules’ should be evaluated on. Documentation
Additional Matchers The editor continues to get more powerful, now supporting not, additional string, and new set matchers. Target by users whose “email ends with @acme.com” or who’s “plan type is part of premium, growth, basic”. Documentation
SAML (Coming Soon)
Soon you will be able to login to Split with your corporate credentials with Split’s support for SAML(Security Assertion Markup Language). Configuring SAML for your Split account will let you and all your teammates log in to Split using the credentials stored in your organization’s Active Directory, LDAP, or another identity store that has been configured with a SAML Identity Provider.
We’ve upgraded our status page to provide enhanced reporting for our customers. Subscribe at status.split.io to receive updates in service changes.
New and augmented logging framework for JS to allow better traceability of what’s going on during evaluations of treatments and network activity for debugging purposes. Documentation
Tagging Use tags to organize and manage splits and segments across the Split web console. You can use tags to isolate splits and segments for a particular team or feature release. Create tags like “reporting team”, “front end”, or “geo search release”. Documentation
Split groups are a convenient way to manage a collection of users in your organization. You can use groups to grant administrative controls and grant environment, split or segment level controls. Documentation
Building on groups, Split’s permissioning can be enabled by environment, by split, or by segment, limiting the actions non-editors can take. Documentation
Target 100% of a segment with ease, making many clicks, just a few. Add a segment to the includes section of the editor to serve a particular treatment to all of the IDs in that segment.
.NET Core Support The .NET SDK is now compatible with .NET Core. Documentation
Node.JS & Redis Node.JS now integrates with Redis and exposes the Manager API to inspect Splits and treatments. Documentation
Impression tables now render additional information about the impression and the particular reason a treatment was shown. Documentation
Drag-and-drop Conditions Drag and drop makes it easy to adjust your rollout plan. Want to move a condition earlier in the evaluation order? Not a problem, via drag and drop you can change the condition order with ease.
Same power with better organization. We heard your feedback! No longer do you need to create 3 segments with the same name for 3 different environments. Create one segment and simply “add to environment” to begin utilizing in your rollout plans in that environment. Documentation
Blocking Access on Failed Login
We’re continuing to add security, first with two-factor authentication and now by blocking application access after five failed login attempts.
.NET Redis Support
Enable Redis in .NET to add an extra level of caching. Documentation
Run Split SDK with in-memory cache on popular frameworks like Django in multiprocess mode on uWSGI servers. Documentation