What is Omniconvert Explore?

What Explore does

Omniconvert Explore is a conversion rate optimization (CRO) platform. It lets you test changes to your website, personalize what different visitors see, and collect feedback - all without writing code or involving a developer for every change.

The platform is built around four core features:

• A/B Testing - show two (or more) versions of a page to different visitors and see which one converts better. The original is called the Control, and each changed version is a Variation.

• Personalization - technically an A/B test, but instead of comparing fixed variations against each other, you use On-Page Variables and Customer Attributes to tailor the experience to each individual visitor. Rather than "Version A vs. Version B," the content itself adapts per visitor.

• Overlays - pop-ups, banners, or interstitials that appear based on a trigger (time on page, scroll, exit intent, and more).

• Surveys - collect direct feedback from visitors, from simple pop-up questions to full NPS surveys.

Every one of these is called an experiment in Explore, regardless of which type it is.

Core concepts you'll see everywhere

Experiment, Control, Variation

An experiment is any A/B test, personalization, overlay, or survey you set up in Explore. Inside an A/B test or personalization experiment, the Control is the original, unmodified version of your page, and a Variation is a version with your changes applied. You can have multiple variations in a single experiment.

Goals

A goal is what you're measuring - a sale, a click, a pageview, a scroll depth, or something custom you define. Every experiment needs at least one goal so you can tell whether it worked.

Segments and Audience

A segment defines who sees your experiment - for example, only mobile visitors, only visitors from a specific country, or only people who've visited more than once. The Audience section of an experiment is where you combine a segment with the pages you want the experiment to run on.

Tested Visitor vs. Tested View

These two terms sound similar but mean different things, and they matter because your plan is usually built around one of them.

• A Tested View is counted every time a visitor sees a modified page - a variation, an overlay, or a survey. If the same visitor sees a change on three different pages, that's three tested views.

• A Tested Visitor is counted once per unique visitor, no matter how many times or how many different experiments they see.