No-code experiment builder for marketers on Adobe Target

A marketing team that wants to test a headline change on a landing page should not need to understand the difference between an mbox and an at.js call. But today, running even a simple A/B test in Adobe Target without a developer means using the Visual Experience Composer — which breaks on sites with dynamic rendering, requires specific browser extensions, and produces results that are 'a bit of an eyesore' to manage at scale. The phrase 'setting up the targets can be very manual' is a precise complaint: there is no abstraction layer between the marketer's intent and the raw configuration interface.

This gap persists for a structural reason: Adobe Target is priced and sold to enterprises that can afford dedicated optimization teams. The product roadmap is influenced by those power users, who want more configurability, not less. The marketer at a mid-market company who inherited a Target license from an agency engagement gets a tool built for someone else.

What's actually missing is not a simpler version of Target — it's a layer that sits in front of Target's API and translates marketer-friendly inputs (a page URL, a change description, an audience condition expressed in plain language) into valid Target activities. The 'too many options, making it difficult to navigate' complaint points directly at this: the interface exposes infrastructure choices that most users never need to make.

Without something like this, a marketer either pays an agency to run every test (expensive, slow), skips testing and ships changes based on gut feel (costly in conversion terms), or spends weeks building internal documentation to compensate for the tool's opacity. The need recurs every time a new test needs to run — which, for any active optimization program, is weekly.

What to build

Build a web-based front-end that connects to Adobe Target via its admin API and lets marketers create, launch, and read results of A/B and experience tests through a form-based interface — no VEC, no mbox knowledge required — with the underlying Target activity created and managed automatically.

Where to start

Start with e-commerce marketing teams running Magento or Shopify Plus, where the site architecture is predictable enough that you can pre-build reliable Target activity templates for the five most common test types (hero banner, CTA text, product page layout, checkout step, email capture modal).

The hard part

Adobe's API surface changes without notice and their partner program gates API access in ways that can delay early customer acquisition — you may need to operate as an unofficial integration for the first cohort of customers, which creates a fragile dependency before you have enough revenue to pursue formal partnership.

How it makes money

Monthly subscription per workspace ($299–$799/month depending on number of active experiments), with usage measured by active Target activities managed through the interface rather than by seat count.