Orravo, Abuja Digital Studio

Getting started

Admin layout

With Orravo Core installed, OConvert nests as a submenu under Orravo Core; otherwise it gets its own top-level menu at position 62.

Six sections sit under the parent slug:

Overview (page=oconvert) - event counts by type, active test count
A/B Tests (page=oconvert-tests) - create, run, conclude tests
Heatmap (page=oconvert-heatmap) - binned click heatmap per page
Exit Intent (page=oconvert-exit) - rule config and payload editor
Integrations (page=oconvert-int)
Settings (page=oconvert-settings)

All six are registered with Core's command palette so Cmd+K finds them from anywhere in wp-admin.

Front-end runtime

OConvert injects a small config block into wp_head at priority 5. It looks like this:

html<script id="oconvert-cfg">window.OCV={...};</script>

The config carries: REST base URL (/wp-json/oconvert/v1), the visitor cookie name, the list of active tests with their assigned variants, feature flags for heatmap and exit-intent, the heatmap sample rate (default 0.25), and the exit-intent ruleset.

The oconvert-runtime script then reads window.OCV and starts capturing.

First test

Create a test in OConvert, A/B Tests. Pick a test_key (lowercase, hyphens) and one or more variant IDs. Then drop the shortcode pair anywhere a variant matters:

[oconvert_test key="hero-headline"]
  [oconvert_variant id="a"]Original copy[/oconvert_variant]
  [oconvert_variant id="b"]New copy[/oconvert_variant]
[/oconvert_test]

Assignment is sticky per visitor via the ocv_vid cookie. Variant selection uses crc32(vid + ':' + key) % count on the first visit, then writes a row to wp_oconvert_assignments so subsequent renders return the same variant.