Split is a feature experimentation and continuous delivery tool. It enables you to maximize the impact of your product features by combining feature flags and data. With Split, you can test new features through rigorous A/B testing and deploy them seamlessly while ensuring data privacy and maximum performance.

RudderStack supports Split as a destination to which you can seamlessly send your customer data.

Find the open source transformer code for this destination in the GitHub repository.

Getting started

Before configuring Split as a destination in RudderStack, verify if the source platform is supported by Split by referring to the table below:

Connection ModeWebMobileServer
Device mode---
Cloud modeSupportedSupportedSupported
To learn more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.

Once you have confirmed that the source platform supports sending events to Split, follow these steps:

  1. From your RudderStack dashboard, add a source. Then, from the list of destinations, select Split.
  2. Assign a name to the destination and click Next.

Connection settings

To successfully configure Split as a destination, you will need to configure the following settings:

splitio connection settings
  • API Key: Enter the API Key for your Split workspace.
  • Environment: Enter the corresponding environment available in the dashboard.
  • Traffic Type: Enter the correct traffic type listed in your account.
RudderStack sends each call as an event to Split.


The identify call lets you uniquely identify a user and record any associated traits about them like their name, email, etc.

A sample identify call is shown below:

rudderanalytics.identify("1hKOmRA4el9Zt1WSfVJIVo4GRlm", {
name: "Alex Keener",
email: "alex@example.com",
plan: "GOLD",
age: 40,


A track call lets you capture user events along with the properties associated with them.

A sample track call is shown below:

rudderanalytics.track("Clicked button", {
color: "red",
buttonText: "Get started",

RudderStack sends the above track call as a Clicked_button event to Split along with the additional properties.

The eventTypeId argument (Clicked button in the above example) in track call should meet the following requirements:

  • It should start with a letter or number.
  • It should contain 80 characters or less.
  • It should contain only letters, numbers, hyphen, underscore, or period.


A page call lets you record your website's page views with any additional relevant information about the viewed page.

A sample page call is shown below:

rudderanalytics.page("homepage", "home", {
url: "https://abc.com",
title: "Test",
referrer: "https://google.com",

RudderStack sends the above page call as a Viewed_home_page event to Split, along with the associated properties.


The screen call lets you record whenever the user views their mobile screen, with any additional relevant information about the screen.

A sample screen call is shown below:

[[RSClient sharedInstance] screen:@"Main" properties:@{@"prop_key" : @"prop_value"}];

The above snippet captures information related to the viewed screen such as its name and category. RudderStack sends this call as a Viewed_Main_screen event, along with the associated properties.


The group call lets you link an identified user with a group such as a company, organization, or an account, and record any traits associated with that group, for example, company name, number of employees, etc.

A sample group call is shown below:

rudderanalytics.group("groupId", traits, options, callback)


Where can I find my Split API key and environment?

To obtain your Split API key, log into your Split dashboard and go to Admin Settings > API Keys, as shown:

Split API key

You can also find your Split environment by going Admin Settings > All environments, as shown:

Split environments

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page