Multipage Testing in Convert Experiences

Multipage Testing is a way to run one experiment across several pages of a customer journey and keep every visitor on the same variation through the whole funnel. As of 2026, it’s available on the Convert Experiences Pro and Enterprise plans. CRO teams and agencies use it to test funnel-wide changes — a persistent cart drawer, a promotion that runs from PDP to checkout, or a redesigned multi-step signup — and measure the impact on revenue, completion, and average order value at the end of the funnel, not just per page.

Use Multipage Testing when the change spans more than one step of a funnel and the metric you care about is what happens at the end — revenue per visitor, completion rate, average order value. Use separate A/B tests when each change lives on a single page and there’s no need for the visitor to see the same variation across pages. The structural difference: three independent A/B tests can put the same shopper into Variation B on the PDP, Original on the cart, and Variation C on checkout — which makes a funnel-level conclusion impossible.

Multipage Testing is included in the Convert Experiences Pro and Enterprise plans as of 2026, and is not included in the Growth plan. It’s part of the included feature set on Pro and Enterprise — not an add-on, not a paid module. See the pricing page →

Convert remembers each visitor’s variation assignment in their browser and applies it on every page in the funnel they reach. The assignment lasts up to six months from the last visit, so a shopper who browses on Monday and checks out on Friday gets the same coordinated experience both times. Local storage backs up the cookie where browser settings allow it.

Yes. A Multipage Test works across any domains you’ve configured in the same Convert Project, including a main store on one domain and a checkout on another. Convert hands the visitor’s assignment between domains using a first-party mechanism, so the test doesn’t depend on third-party cookies that modern browsers block by default. Subdomains under the same root work automatically, while separate top-level domains use Convert’s documented cross-domain handling.

Yes. Multipage Testing works with React, Vue, Angular, and Next.js applications. SPAs need one small configuration step to let Convert know when the user navigates to a new route, since the page itself doesn’t reload, and the Visual Editor includes an SPA Mode (added in June 2025) that helps it work with dynamically rendered components. There’s also a dedicated @convertcom/tracking-react package for React, Next.js, Gatsby, and Create React App projects.

Split URL Testing tests one URL or URL pattern against a different URL or URL pattern, typically by redirecting traffic from the original to the variation URL. Multipage Testing keeps a single visitor on the same variation across multiple pages of a funnel, whether or not each step involves a redirect. Use Split URL Testing when you’re swapping one page for another; use Multipage Testing when the whole customer journey needs to feel like one coordinated experience.

Yes, for typical content, design, and copy changes. A native Multi-page Funnel Experiment is built in the Visual Editor: you add the funnel pages, make your variation changes visually on each one, and Convert links the matching variations across pages for you. Code comes into play when each funnel step needs to redirect to a separate alternate URL (Convert documents a convert.redirect() pattern for this), and when you’re working in a single-page application that needs polling configuration.

Yes. You can run full-funnel logic server-side through the Convert Experiences JavaScript / Node.js SDK as a Full-Stack experience. In that setup, your application decides the visitor’s variation in the backend and renders or redirects accordingly, rather than letting the browser snippet handle it. The persistence and reporting model is the same — the difference is where the variation decision gets made.

Most major platforms support some form of multipage or funnel testing — Optimizely Web Experimentation lists it as a distinct experiment type, and VWO supports cross-domain testing on its Data360 Pro and Enterprise tiers. The meaningful difference isn’t whether the capability exists, but how it’s delivered. Convert uses first-party cookies only (so cross-domain funnels keep working as third-party cookies get blocked), publishes its full pricing on a single page, includes Multipage Testing on every Pro and Enterprise plan without add-on charges, and supports both Visual Editor and server-side SDK workflows on the same plan.