> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/guides/split-test.md). # Split-test two lead journeys Use **Split Traffic** when you want a lead to enter one of several workflow variants. ## Configure the split Add two to six variants with unique identifiers and names. Set whole-number weights that total 100, such as 50/50 for two variants. Choose a **Sticky key** when the same lead should keep the same variant across runs. Email or company domain can be useful depending on what you are testing. Without a sticky key, each run gets a fresh random draw. With a shared split group and sticky key, the same subject keeps its variant across participating workflows. ## Build the variants Connect each variant port to its complete journey. For example, one branch can show a standard demo scheduler while another uses a different qualification step before showing the same event. Keep booking, CRM update and failure paths clear in both variants. A branch that ends accidentally can make the experiment look like a conversion difference. ## Verify and measure Simulate each variant, then verify controlled live cases. Record the variant output and inspect the run logs alongside actual booking outcomes. A 50/50 setting is a probabilistic allocation; a small sample need not contain exactly equal counts. Changing the split group or subject key can change assignment. Choose a stable definition before comparing results. See [Logic, timing and human steps](/workflows/logic.md) and [Routing logs](/routing/logs-and-reports.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/guides/split-test.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.