Convert.com Developer (Convert Experiences)
Convert is branded both as Convert.com and as Convert Experiences. It is the same platform under either name, and this page covers both. It gives developers more direct control than most testing tools: variation and experience-level JavaScript and CSS editors, a synchronous snippet that avoids flicker by default, and a documented client-side and server-side API. We build, debug and QA experiments in Convert for agencies and in-house teams working in their own Convert account.
CRO strategy, design and development across Shopify, WordPress, Convert, Optimizely, VWO and Adobe Target.
Does this sound familiar?
These are the situations teams actually describe when they get in touch about this, not a generic list of pain points.
The snippet was moved to async without the anti-flicker piece
Convert’s tracking code loads synchronously by default, which is why teams rarely see flicker on it. Switching to asynchronous loading for a Core Web Vitals score, without configuring the accompanying body-hiding behaviour and timeout, reintroduces exactly the flash that synchronous loading was avoiding.
A performance layer is stripping the snippet
Optimisation proxies and script deferral features can move or rewrite the tracking code. Convert documents the Cloudflare Rocket Loader case specifically: the snippet needs data-cfasync="false" so it is not deferred. The same class of problem appears with other optimisation plugins and CDNs.
Variation JavaScript is doing what Global Experience JavaScript should do
Convert separates code that applies to a single variation from code that applies across the whole experience. Setup and instrumentation duplicated into every variation drifts out of sync, and then the arms differ by more than the thing under test.
The variation is applied once and lost on re-render
On a client-rendered site, or a Shopify product page that re-renders on variant selection, a change applied at execution time disappears. It needs to reapply on the state changes that matter, and the reapplication needs to be idempotent so it does not stack.
Goals do not correspond to the hypothesis
A click goal bound to a selector that also matches an unrelated element, or a revenue goal firing on a page that is reachable without a purchase. The experiment then reports movement in something nobody hypothesised about.
What is included
Scope stated as specific outputs rather than as adjectives.
- Experiment implementation in your Convert account: variations, experience-level code and shared setup
- Variation JS and Variation CSS, plus Global Experience JS and CSS for logic common to every arm
- Site-wide code for instrumentation that must exist before an experience executes
- Audience and URL targeting configured and then verified from a real session
- Goal configuration, including click, form, page-visit and revenue goals, validated on every arm
- Flicker handling appropriate to your snippet mode, synchronous or asynchronous
- Single-page-application and dynamic-content handling that reapplies safely rather than repeatedly
- Mutually exclusive experiment setup where concurrent tests would otherwise interact
- Debugging of experiments that are not activating, not bucketing, or not recording
- Full pre-launch QA pass and post-launch validation on live traffic
How the work runs
- 1
Confirm how the snippet actually loads on your site
Before building anything we check the load mode, whether any optimisation layer is interfering with it, and what that implies for flicker. This single check explains a large share of the “Convert is broken” reports we are sent.
- 2
Build the experience
Shared logic goes in Global Experience JS; per-arm changes go in Variation JS. Selectors are chosen against your real DOM for stability, not from the visual editor’s first guess.
- 3
Target and instrument
Audience and URL rules configured, then verified from both a qualifying and a non-qualifying session. Goals checked to fire once, on the intended action, on control as well as variation.
- 4
QA, launch, watch
Full pre-launch matrix, then validation on live traffic once the experience is active, including a check that the split matches configuration.
Who this is for
Agencies standardised on Convert
You run client programmes in Convert and need development capacity that already knows the editors and the API, often delivered white-label.
In-house teams who chose Convert for privacy or control
Convert is frequently selected for its data-handling posture and its developer access. Both are only worth what your implementation makes of them.
Ecommerce teams on Shopify and WooCommerce
Convert is common on ecommerce storefronts, where the hard part is the re-rendering cart and product state rather than the platform itself.
Convert surface we work in
Named specifically, because “modern tooling” tells a buyer nothing.
- Variation JS / Variation CSS
- Global Experience JS / Global Experience CSS
- Site-wide and project-level code
- Audiences, segments and URL targeting rules
- Goals: click, form submit, page visit, custom and revenue
- Client-side and server-side experimentation
- Feature flags
- Mutually exclusive experiment groups
- Preview and debug modes for QA
- Synchronous, asynchronous and SPA loading modes
How this gets checked
Every engagement carries a QA pass. It is written down so that “QA done” means something specific.
- Snippet load mode confirmed and flicker measured on a throttled mobile connection
- Variation verified after client-side navigation, variant change and cart update
- Qualifying and non-qualifying sessions both checked against the audience rules
- Every goal fired manually and confirmed recorded on each arm
- Console free of errors attributable to the experience
- Traffic split checked against configuration once live
- Experience confirmed to deactivate cleanly, with no residual DOM change
Ways to work together
The commercial shape is chosen after we know the scope, not before.
Dedicated partnership
Reserved capacity for a steady pipeline of work.
Flexible hours
Draw down specialist time as the work arrives.
Project engagement
A defined scope, owned end to end.
All three are described in full under engagement models.
Questions people ask before buying this
Convert Experiences documentation
Platform behaviour described on this page was checked against the vendor’s own current documentation. Verify against these before relying on any of it, because vendors change APIs.
Services on this platform
Other experimentation platforms
Further reading
Hire a Convert Experiences Developer
Tell us what you are trying to run in Convert, or what has stopped working. We will look at the account and come back with what it needs.