DRIP / Apex
ExperimentationSix to ten tests at once, safelyLikelihood to WinThe odds of every idea before you testThe genome4.3 million tests behind every scoreFeature managementFlags, rollouts and kill switchesPersonalizationRule-based experiences with a holdbackAPI & developersREST API, webhooks, CLI, MCP and SDK
IntegrationsSecurityCustomersDocsLog inSee if your shop is a fit
Log in
See if your shop is a fitSee if you're a fit

Feature management

Feature flags that live next to your tests

Roll out what won, switch off what misbehaves and hand engineering typed configuration, with the same targeting as your experiments.

See if your shop is a fit

Flags

From winning test to rollout in one click

A flag has a key, a status and typed values: on or off, a string, a number or a JSON object. Create one from scratch or straight from a winning experiment, and the lineage stays attached.

Visual flags run in the same storefront runtime as your tests, and the edge evaluates them too. For flags your own code reads, the SDK and the API return the value.

  • Flags for your backend are served as state: your code fetches them over the API and decides
Feature flag · example
bundle-moduleActive
Environment
ProductionStaging
Rollout
25%
Targeting
Device is mobile · Page matches /products/*
Schedule
Monday to Friday · Europe/Berlin
Values
on: true off: false
Source
Winner of “Bundle module on PDP”

Everything a rollout needs

Percentage rollouts

Release to 5%, 25% or everyone, and change it any time. The same targeting rules as experiments decide who is eligible.

Environments

Production and Staging out of the box, up to twelve environments per shop, each with its own flag state.

Weekday schedules

Deliver a flag only on chosen weekdays, in an explicit timezone. Ramps are set by percentage, not on a timer.

Kill switches

Pause a single flag, or switch off the whole runtime for a shop, and the change republishes to the edge.

Decision debugger

See exactly why a visitor would or would not get a variant before you activate anything.

Audit log

Every create, change, pause, activation and archive is recorded with who did it.

Read a flag in React

The npm package ships React bindings. Apex owns assignment and persistence; your component reads the value.

ProductDetails.tsx
import { DripProvider, useFeatureFlag } from "@drip-apex/sdk/react";

function ProductDetails() {
  const showBundle = useFeatureFlag("bundle-module");
  return showBundle ? <BundleUpsell /> : <DefaultProductDetails />;
}

In the docs

Feature flags ↗SDK feature flags ↗React bindings ↗
DRIP and Apex

Want Apex on your shop?

Apex can come with the research on your shop and the team that reads the results, or run on its own, and a free plan for one store needs no card. The main way in is a call: if your shop does six figures a month, book one and we'll find the setup that fits.

See if your shop is a fit

30 minutes, and you'll know exactly where your shop stands.

DRIP / Apex
ExperimentationLikelihood to WinThe genomeFeature managementPersonalizationIntegrationsAPI & developersFor AI agentsSecurityCustomersDocs
ImprintTermsPrivacy

Apex by DRIP. A product of Drip Trading GmbH. dripagency.de

Cookies

We use optional analytics and marketing cookies to improve performance and measure campaigns. Privacy Policy