URL redirect tests on a custom storefront

A URL redirect test sends some visitors to a different page. On a custom storefront your server does the redirect, with the destination the SDK gives it. Runs on: the server only, before the page renders. Use the client made from the request.

Redirect on the server

On Next.js, the middleware from the Next.js guide does this for you. On Hydrogen and other servers, add it to your root loader or your middleware:

Server (loader or middleware)

// Before the page renders
const destination = abconvert.getRedirectUrl(request.url);
if (destination) {
  // Keep the SDK's cookies and keep the redirect out of shared caches
  const headers = new Headers({ 'Cache-Control': 'private' });
  for (const cookie of abconvert.getSetCookieHeaders()) headers.append('Set-Cookie', cookie);
  return redirect(destination, { status: 307, headers });
}

Send the SDK’s cookies with the redirect. Without them, a new visitor reaches the destination with no visitor ID, gets a new one, and can land in another test group there. getRedirectUrl returns null when the visitor stays: they are in Control or outside the test, the URL is not part of a test, or the visitor is a known crawler. Redirecting on the server means the visitor never sees the original page first.

Get started

Build

Configure

Advanced

Reference

URL redirect tests on a custom storefront

Redirect on the server

​Redirect on the server

Redirect on the server