CRO OmniConvert: Distinguishing Button Versions for Improved Result

Posted by: Veronica Pamintuan Date Posted: May 23, 2024
Back to Case Studies

Issue

Most of the time, a CRO request will have only one goal in OmniConvert: to track two versions of button clicks (desktop and mobile).

Solution

Simply explain that we must create a secondary goal in OmniConvert to distinguish which button version triggered the goal. Without the mobile and desktop versions of the buttons, you wouldn’t be able to tell which was initiated or triggered.

To identify if it was triggered using the mobile version, we must create a custom Javascript variable that would return true if the user used a mobile device.

Here’s a custom JS:

function() {
return /Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent) ? ‘Mobile’ : ‘Not Mobile’;
}

Achievement

The CRO Specialist is happy about our recommendation. This shows that we, too, are very concerned about the outcome the team wanted to achieve from the A/B testing they had set up for the client.

Snippet/Screenshot/Link

https://app.webfx.com/todos/262212095