Abuja Digital Studio · Est. 2018
Start a Project
DocsOConvertTroubleshooting
Troubleshooting

Troubleshooting

OConvertorravo.com/docs/oconvert/troubleshooting

Troubleshooting

No events being recorded

Check three things in order:

  1. The runtime script is loading. View the page source and search for oconvert-runtime. If missing, another plugin or a cache is stripping it. Make sure wp_enqueue_scripts runs unimpeded.
  2. The visitor cookie is set. Open the browser devtools, Application, Cookies and look for ocv_vid. Without it, OConvert_Events::record() rejects the write.
  3. You are not hitting the rate limit. The ingest endpoint caps 600 events per IP per minute. The response will be a 429 if you trip it.

A/B test always shows the same variant

That is by design - assignment is sticky per visitor. Clear the ocv_vid cookie (or use a private window) to get a fresh assignment. To verify, query wp_oconvert_assignments for your vid and you will see exactly one row per test_key.

Visual capture mode does not load

Three requirements:

  • You must be logged in as a user with manage_options.
  • The URL must include both ?ocv_capture=1 and a test_key parameter.
  • The page must not be in the admin (is_admin() skips the script).

If all three hold and the overlay still does not appear, check the browser console for a CSP violation - the capture overlay uses inline styles.

Exit-intent fires too often

Increase cooldown_days and lower max_per_session in the oconvert_exit_intent option (or via the Exit Intent admin page). The defaults are 7 days and 1 per session. Also bump min_dwell_ms to require a longer dwell before any trigger is eligible.

Troubleshooting · OConvert Docs | Orravo