Docs

Lead Router
One page that sends every visitor somewhere different.

Route yourself

Try it, right here.

The real stepper. Watch the analytics panel: those events fire on every step, not just at the end.

Lead Router › Find your next step demo

Nothing here is stored or sent. On a real install this posts to a REST route with a nonce, writes to an indexed table, then hands off to your CRM in the background.

Analytics, as it happens

Every one of these is pushed to the GTM data layer the moment it happens. Step-level data is what tells you where the funnel leaks. A router that only fires on submit cannot tell you that everyone quits on question two.

  1. Nothing yet. Answer a question.
Under the hood

What it actually does.

Rules are configuration

Each routing rule is an editable record mapping a visitor's answers to a destination: an intake form, a booking link, or a tailored landing view. Marketing repoints a destination in wp-admin. Hardcoding this is how it becomes unmaintainable by month three.

It works without JavaScript

The markup is one complete form with every step visible. Script progressively enhances it into a stepper. Nothing is rebuilt and nothing is duplicated, so the two paths cannot drift apart, because there is only one set of fields.

A slow CRM cannot drop a lead

The lead is written locally first, then handed off from a background action so the visitor never waits on a third party. Failures retry with backoff, each lead carries an idempotency key so a retry cannot duplicate it, and the response is logged so a dropped lead is visible instead of silently lost.

Accessible because the buyers require it

Real fieldset and legend grouping, aria-current on the active step, managed focus on step change, visible focus rings, and no state carried by colour alone. That is the WCAG 2.1 AA and Section 508 baseline, and government and institutional buyers ask.

Analytics that survive an ad blocker

Data layer pushes at every step feed GTM through custom event triggers, and the conversion is mirrored server side from the REST endpoint through the Measurement Protocol, so the recorded count matches the leads that really reached the CRM.

Quiet defences

An off-screen honeypot rather than display:none, which some bots detect, plus per-address rate limiting and nonce-checked submission. Enough to stop the spam without putting a CAPTCHA in front of a county administrator.

Ready when you are.

Every plan is monthly and cancels whenever. The licence covers updates and the Suite installer, so you are never chasing a zip file.