Docs / Data sources / Split

Split

Business software

Built when you ask for it

Sync Split feature flag, environment, treatment, and event data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Split connector syncs your feature flagging and experimentation data into analytics-ready tables in your data warehouse. Pull splits, environments, treatments, and events from the Split API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Splits
  • Environments
  • Treatments
  • Events

How it gets built

  1. Choose Split when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Split's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Split itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

Bearer token (Admin or SDK API Key). Generate an Admin or SDK API Key in Split. Split was acquired by Harness; account/help pages now redirect to developer.harness.io.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Split connector?
Not as a finished connector yet. Ingest builds it from Split's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Split data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Split API documentation: https://docs.split.io/reference/authentication

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for SaaS teams: Asana, Jira, Airtable, Clockify, Facebook Ads, Frankfurter.

Request Split