Split action explained: what it changes for small business

Split action explained: what launched and what changes

GoHighLevel's Split action now offers Even split and Weighted split beside the Random split it already had, so a workflow can send each new contact to the next path in turn instead of by chance. If your team already routes leads or enrolls contacts in GoHighLevel workflows, this is worth reviewing this month; if you do not run split logic in a workflow, the launch does not change your buying decision.

GoHighLevel's launch record dates the changelog entry November 13, 2026. The entry says the Split action "now supports Even split and Weighted split, giving you more control over how contacts move through your workflow paths." It treats the two new types as additions rather than replacements: Random split "remains available," and existing Random split actions "retain their current configuration." The comparison that matters is therefore turn-based splitting against the chance-based split buyers already used.

The buyer question is narrower than the launch itself. Even split answers "keep the groups balanced," and Weighted split answers "send one path a larger share." Neither picks a winning path, and the vendor has not announced one.

Key Takeaways

• Even split sends each contact to the next path in turn, which keeps the paths balanced as contacts arrive.

• Weighted split also runs in turn, using whole-number percentages that total 100%, so one team or journey can take a larger share.

• Random split stays available, and the vendor says equal percentages on it do not guarantee equal groups, especially with few contacts.

• Settings lock once contacts enter an Even or Weighted split; Reset test lets you edit them again but clears the split's statistics.

• The winner-picking split test on GoHighLevel's ideas board is listed as in progress, so it is not part of this launch.

• Enterprise pricing is quote-based for both GoHighLevel and Zapier, and a stitched build in another tool carries setup and upkeep costs that no pricing page lists.

What a split action does

A split action is a workflow step that sends each contact who reaches it down one of several paths, so different follow-up journeys or sales teams receive different shares of contacts.

TL;DR: The launch adds two turn-based ways to split contacts. Use Even split for equal rotation, Weighted split when one path should get more, and Random split only when chance assignment is acceptable.

What the changelog confirms, and what the vendor has not published

The changelog describes Even split as a way to "send contacts to each path in turn, keeping the distribution even," with two uses: sharing incoming leads evenly across teams, or creating balanced groups for different follow-up journeys. Weighted split sends contacts "to each path in turn, based on the percentages you set," which suits a case where one team or journey should receive a larger share. The vendor's own example is a 60/40 split: Weighted split example: 60/40 according to GoHighLevel (2026). Under that setting, three out of every five newly distributed contacts go to one path and two to the other.

Setup happens inside the workflow. Open or add a Split action, choose Even split or Weighted split from Distribution Type, name the paths, enter whole-number percentages totaling 100% for Weighted split, then save and publish the workflow, as the same changelog entry describes.

Two behaviors matter for planning. With Returning contacts set to Keep the same path, contacts who re-enter follow the path they were assigned before. Once contacts enter an Even or Weighted split, its distribution settings lock. Reset test lets you edit them again, but saving a reset clears the split's statistics and restarts the rotation.

The vendor has not published several things a buyer would want. It has not published the maximum number of paths for either new split type. It has not published which GoHighLevel plans include Even split or Weighted split. The pricing page places Workflow Builder on the Starter plan, but the changelog does not tie the new types to any plan. It has not published a winner-selection option, and the ideas board lists a split test as in progress with no date shown. For Random split, the changelog says contacts are assigned "randomly" and says nothing more about the method.

How we evaluated these tools

This is an informed buyer's guide built from public pages. Nothing below describes a hands-on test. We weighted six criteria that a small or mid-size operator decides on. Launch facts come only from GoHighLevel's own pages, and rival facts come from ActiveCampaign's and Zapier's own pages. Market context comes from two surveys published on third-party sites, and we name each survey's sponsor. Where a page did not answer a question, the tables say so rather than fill the gap.

The weights add to 100%. Plan access carries the second-largest weight because budget is the first constraint for most owners. Evidence and audit trail carries the least weight here, though it matters more for any build you own yourself.

Feature matrix: the six decisions side by side

Read "Not read" as "the page that would answer this returned an error or no detail in this review," not as "the feature is missing." ActiveCampaign's help pages returned errors, which is why its split setup is absent from this article. The Zapier pages read describe rule-based branches. They do not describe percentage-based or turn-based distribution, so do not assume Zapier has it.

What it costs: pricing and total cost checks

Pricing checked November 13, 2026. Starter plan monthly price: $97 according to GoHighLevel (2026). The same page lists GoHighLevel's Starter plan at $970 per year, its Unlimited plan at $297 per month or $2970 per year, and its Founder plan at $497 per month or $4970 per year. The Enterprise plan is marked "Speak with Our Enterprise Team," so it is quote-based.

Zapier's Professional plan costs $29.99 per month billed monthly, or $19.99 per month billed annually, according to Zapier (2026). The same page lists the Team plan at $103.50 per month billed monthly or $69.00 per month billed annually, and says the Free plan includes 100 tasks per month with two-step Zaps only.

ActiveCampaign's pricing page returned placeholder text in this review, so no ActiveCampaign amount appears here. Its Starter tier does cap multi-step automations at 5 actions each, according to ActiveCampaign (2026), and its plan listings reference a 1,000-contact basis billed yearly.

Total cost of ownership is more than the plan line. A native split costs the plan plus the review time you spend on it. A stitched build adds setup, testing, and maintenance that no pricing page lists, so count that labor before you compare plan prices.

Vendor profiles: fit, limits, and evidence

GoHighLevel: fit, limits, and evidence

Best fit: teams already running GoHighLevel workflows that need either an equal rotation or a stated share. The turn-based options answer the vendor's own point that equal Random percentages may not produce equal groups.

Limits: settings lock after contacts enter, Reset test clears statistics, winner selection is not in this launch, and the vendor has not published a path maximum. The pricing page's FAQ calls the Founder plan "Pro," which conflicts with the pricing table, so confirm the plan name before you buy. The page also says usage-based charges for telecom and AI services apply on top of plan prices.

Implementation: follow the setup steps in the changelog, test on a small set of contacts, and record the counts before any Reset test, because the reset clears them. For a real estate comparison, see GoHighLevel vs Follow Up Boss for real estate teams.

ActiveCampaign: fit, limits, and evidence

Best fit: teams already on ActiveCampaign that want to test automations or email variants. The pricing page ties automation A/B testing to the Pro and Enterprise tiers and lists email-only A/B testing on Plus and Starter.

Limits: the Starter tier caps multi-step automations at 5 actions each. This review could not open ActiveCampaign's split help article, so this article does not describe its percentage setup. The help center lists an update titled "Update: Percentage & Multi-Splits Enhancements" in its help article, and a buyer should read that page before deciding.

Evidence: the ActiveCampaign pricing page and the help article above.

Zapier: fit, limits, and evidence

Best fit: teams that connect several apps and want rule-based branches. Zapier's Paths run a branch only when its rules are met, and a fallback branch runs when no other branch matches.

Limits: the Free plan covers two-step Zaps only and excludes Paths and Filters. Paths are available on Professional and higher. Each path group allows one fallback branch, and the pages read do not describe turn-based or percentage-based distribution.

Evidence: Zapier's Paths rules article and its conditional logic article.

Build it yourself: Zapier, Make, or n8n

For many small teams, the real alternative to a native split is a stitched workflow in Zapier, Make, or n8n, or an in-house build. This review did not open Make or n8n pricing or feature pages, so it gives no figures for them. Configured well, tools like Zapier can keep run histories, retries, error branches, and audit evidence. The buyer still designs and owns the parts that decide whether routing is right: idempotency so a lead is not routed twice, escalation when a route fails, access controls over credentials, and maintenance when a connected app changes.

Worked example, illustrative and not a customer case: a team receives 90 new contacts in a month and wants a 60/40 share between Rep A and Rep B. A Weighted split at 60/40 sends 54 contacts to Rep A (90 × 0.60) and 36 to Rep B (90 × 0.40), in turn, so Rep A gets three of every five. Built by hand in Zapier, Paths route by rules and there is no built-in turn-based 60/40 rotation, so the buyer builds and maintains a counter or lookup step that tracks each lead, for example by an ID such as contact.id, the merge field in GoHighLevel's custom webhook example. The buyer must also validate that logic and maintain it.

Where a split goes wrong, and a proposed design

Three things break a split in practice: contacts re-enter, the target share changes, and settings lock after the first contact arrives. The vendor's own text covers each of them, so a design should plan for them before go-live. The design below is a proposal, not a description of a live deployment, and US Tech Automations would configure it only after the prerequisites are confirmed.

A proposed US Tech Automations workflow for a two-rep lead team starts when a new lead arrives through an inbound feed from the web form, which requires API or webhook credentials and a test account. A rule step checks territory and lead source, then passes only qualified contacts into a GoHighLevel workflow whose Weighted split is set to 60/40. The output is that each qualified contact lands on Rep A or Rep B in turn, with the path name written to a log kept outside GoHighLevel. Human review points: an owner approves the 60/40 setting before publishing, and a named person reviews every lead the rule step rejects.

In the same design, US Tech Automations would run a second check each week. The trigger is a scheduled time, such as Monday morning. The action pulls each path's contact count from an export and compares it with the 60/40 target, flagging drift beyond a threshold the owner sets. The output is a short report of path counts and any contacts who re-entered. The prerequisite is a path-level export from GoHighLevel, which this review did not confirm is available on your plan. The owner decides whether a reset is worth losing the statistics, because Reset test clears them and restarts the rotation.

Our read is that re-entry rules need a deliberate choice. With Keep the same path, a returning contact stays with its earlier assignment, which protects continuity but can pull the shares away from target over time. Decide that trade-off before you publish.

Signal vs speculation: where our read goes beyond the page

Signal, confirmed on vendor pages: the three split types, the 60/40 example, the setup steps, the locked-settings and Reset test behavior, the Keep the same path setting, and the Workflow Builder listing on the Starter plan.

Speculation, our read: Even and Weighted split matter most where lead volume is small or team capacity is uneven, because the vendor itself says equal Random percentages do not guarantee equal groups with few contacts. We expect the owner's main ongoing work to be reviewing counts rather than building the split.

Open question: whether a winner-picking split test ships. The ideas board lists it as in progress with no date shown, so do not buy for it.

Who this is for

Owners and operations leads who already route leads or enroll contacts in GoHighLevel should treat this launch as a configuration decision. Teams weighing GoHighLevel against other platforms should compare the setup and upkeep of a native split with a stitched build.

Market context points the same way, though it is not a verdict. SMB owners using some automation: 76% according to KEYT (2026). That figure comes from a survey of 508 U.S. owners and operators conducted by Centiment for Zapier, which sells one of the tools compared here, so treat the 76% as sponsor-supplied. The same survey puts AI that decides across multiple systems with limited human input at 30%. A separate business.com survey of 1,009 U.S. workers at companies with fewer than 250 employees, sponsored by business.com and conducted with Dialog, reports that 57% of U.S. small businesses are investing in AI, according to Business.com (2025). That measures AI investment, not workflow automation, so read it as context only.

If you run a marketing agency on GoHighLevel, see the marketing agency alternatives guide. If you run a gym or studio, see the gyms and studios guide.

Red flags: you need a winner picked by a test today, nobody is assigned to review split counts, or your routing must span several apps outside GoHighLevel.

Decision checklist

• Confirm that a GoHighLevel workflow already receives the contacts you want to split.

• Choose Even split for equal rotation, and Weighted split for a stated share such as 60/40.

• Accept that settings lock after the first contact and that Reset test clears statistics.

• Confirm in writing whether your plan includes the new split types, because the vendor has not published which plans do.

• Name the person who reviews path counts and approves any reset.

• If routing spans several apps, price a stitched build, including setup and upkeep, before comparing plan prices.

When not to use US Tech Automations

A proposed custom design is the wrong choice if a native split already covers your routing, such as one equal rotation between two reps inside GoHighLevel, where the built-in Even split is simpler than any outside build. It is also the wrong choice without API or export access to your lead source and CRM, because the design cannot run without them. Skip it if you only need a periodic count of contacts per path, which the split's own statistics may already show.

Frequently asked questions

Is the GoHighLevel Split action new?

No. The Split action already existed with Random split; this launch adds Even split and Weighted split beside it, and Random split remains available.

Does Even split pick a winner?

No. Even split sends contacts to each path in turn, and the vendor has not published a winner-selection option. A winner-picking test is an in-progress request on the ideas board.

Which plan do I need?

The vendor has not published which plans include Even split or Weighted split. The pricing page places Workflow Builder on the Starter plan, so confirm the split types on your own plan before you buy.

Can I change a split after contacts enter it?

Not directly. Settings lock once contacts enter, and Reset test lets you edit them again, but saving a reset clears the split's statistics and restarts the rotation.

Should I choose GoHighLevel or Zapier for routing?

Choose GoHighLevel if your leads already live in its workflows and you want a native split. Choose a stitched Zapier build if routing must span several apps, and accept that you own the error handling and upkeep.

Does the 60/40 example give an exact split?

It gives a turn-based pattern: three of every five newly distributed contacts go to one path and two to the other, as the vendor's example describes.

Decision for this month

If your team already runs GoHighLevel workflows and splits contacts by chance, this month is a reasonable time to review it. Confirm your plan, choose Even or Weighted split, and publish on a small set of contacts first. Record the counts before any Reset test, because the reset clears them. If your routing spans several apps, price a Zapier build against the native option, and see how US Tech Automations configures this once you have confirmed the prerequisites in this article.