Conversion rate optimisation · UAE

Get more enquiries from the visitors you have.

Conversion rate optimisation here starts with a diagnosis, because most sites cannot split their traffic and tell the two halves apart. Webzenia fixes what the recordings show, then tests where the volume carries one.

Get a read on where the visits are lost

What conversion rate optimisation is

What your numbers can prove.

Conversion rate optimisation turns more of the visits you already have into business. At the volumes this market runs on, the method is settled by arithmetic rather than by preference.

Experiment planner · CheckoutUnderpoweredTest inputsWeekly sessions1,200Baseline rate2.1%Detectable effect+20%Confidence95%Weeks to a readable result31weeks95% confidence · 80% powerDecision window4 weeksDiagnose insteadwhat we run at this volumeSession replayForm field drop-off5 moderated testsdiagnose first · test only what the traffic can prove

The number that matters.

A raw conversion rate counts everyone who reached the end of the form. The rate we work to counts only the enquiries you could invoice, and the two move in opposite directions more often than anyone expects.

What your volume carries.

The same page is a testing problem at one traffic level and a diagnosis problem at another. Which one you have is a calculation, not a judgement, and it is settled in the first fortnight rather than argued about for a quarter.

What consent leaves visible.

Consent is the primary lawful basis under the UAE PDPL, so a share of your conversions is never observed at all. Every rate quoted here is a rate about consented sessions, and we report it as one.

Two methods, one threshold

Test it or diagnose it.

Both are real methods and both are sold here as the same service. Which one your site can actually use is a question about volume, and it has a number in it.

A testing programmeSplit the traffic, wait for the answerDiagnose and sequenceFind the failure, then fix it in order
What it needsTens of thousands of sessions on the one page being changed.One page, and enough recorded sessions to watch people fail on it.
Time to an answerMonths, and the answer describes the page you had when it started.Days for the finding, then the fix ships as soon as it is built.
What it tells youWhich of two versions won, and nothing about why.Where people stopped, and what they were trying to do at the time.
What a wrong call costsA result read early is noise, and shipping it makes the site worse with a number attached.A fix that returns nothing shows up in the next month of enquiries.
When it fitsOnce a single page carries enough traffic to fund the wait.First, on every site, and for a long time after that on most sites here.
The method your volume affords.

Most sites here need the better part of a year of traffic before a split test can tell a genuinely better page from the one they have, and by then the page and the offer have both moved. That is arithmetic, not an opinion about testing, and it is why diagnosis runs first. We say when a page has grown enough to carry a test, with the calculation attached. Where the real problem is the destination your ads point at, that is landing page design; where it is the build underneath, website design and development.

From the field · UAE conversion work

What your numbers can settle.

Webzenia has worked with Gulf clients since 2018. These three come back on almost every conversion brief here, and none of them is a design finding.

  1. 01of 03
    Significance costs trafficThe arithmetic

    A split test costs you sessions.

    The sample a readable result needs is fixed by your starting rate and the size of the change you want to detect. Neither is negotiable, so the only variable is how long you wait. A Dubai Marina clinic on a DET mainland licence waits past the point where the offer has moved.

    Our methodThe sample your page would need is calculated in week one, from your own numbers, before any method is proposed.
  2. 02of 03
    The rate rises, revenue fallsThe licence, in the numbers

    Your licence decides a real enquiry.

    Selling direct to a mainland customer generally needs a distributor, a mainland branch or a permit, so an enquiry from the wrong side of that line is a queue to apologise to rather than an order. Every analytics tool you own still counts it as a conversion.

    Our methodA qualified enquiry is defined against your licence on the first call, then counted separately from the raw rate.
  3. 03of 03
    Consent decides what you seePDPL, Federal Decree-Law 45 of 2021

    Consent hides some of your conversions.

    The advertising platform still reports a number, because it models what it could not see. A conversion rate built on that is a modelled figure, not a measured one, and it comes apart the first time the finance team at a Business Bay brokerage on a DET mainland licence asks where it came from.

    Our methodConsented sessions and platform-modelled conversions are reported as two lines, never blended into one rate.

The scope

The work, in order.

Six pieces of work, in the order a diagnosis actually runs. One of them is conditional, and the first two decide whether it happens at all.

Attention heatmap3 leaksRanked leaks1Primary CTA below the fold2Sign-up form: 9 fields3Slow hero imageheatmaps, recordings and funnels find where visitors drop

Recordings of where people stop.

Session replay, click and scroll behaviour and the form field people abandon, read on your own traffic rather than against a published benchmark

Output

a ranked list of failures, each with the sessions behind it

Session replayField drop-off
Funnel analysisbiggest leak: −58%Visit · 10,000Product · 5,800−42%Cart · 4,000−31%Checkout · 1,680−58%the biggest, most fixable drop-offs tackled first

A funnel counted step by step.

Every step from arrival to enquiry measured as a session count, with the qualified enquiries split out from the rest

Output

the step that costs the most, named and numbered

Step countsQualified split
Test roadmapprioritiseddo firstImpactEffort →each fix a testable hypothesis, ranked by impact and effort

A fix order, with reasons.

Each fix priced by what it takes to build against what the recorded evidence says it returns, then put in order

Output

a sequence you can argue with, not a wishlist

EffortExpected return
A/B teststill runningVariant A · control3.1%Variant B · challenger3.7%+0.6 pts · inside the noise62% confidence · not readable yeta test is only called when the traffic can carry it

Tests where traffic allows them.

A split test run only on a page whose volume reaches a readable result inside a window you would actually wait, with the stopping point set before it starts

Output

a called result, or a written reason there is no test

Sample calculated firstConditional
UX & speed fixesfriction removedFixbeforeafterCheckout fields94Hero LCP4.1s1.9sCTA clarityvagueclearError messagesgenericinlinefriction, confusion and slowness found and fixed

Fixes shipped one at a time.

The changes the diagnosis called for, built and released singly so the next month of enquiries can be read against each one

Output

a dated log of what changed and when

One at a timeDated
Reporting9 shipped9 changesshipped this quarter2 tested · 7 decided on evidenceCheckout: 9 fields → 4session replayCash on delivery made visiblesupport ticketsArabic number formatting fixedform drop-offat this volume most calls are evidence, not tests

Reporting on qualified enquiries.

Qualified enquiries and consented sessions reported beside the spend that produced them, with the modelled half of the platform number kept on its own line

Output

a figure that survives being questioned

QualifiedConsented

Our stack

The tools we read visits with.

Six tools, and the fifth is one most sites here should not be paying for yet. Select one to see why it earns its place, and what we do with it.

GA4
Why GA4

GA4 is the only place the funnel and the traffic source sit in the same table, and it is already installed on nearly every site we are asked to look at. Its weakness is that it reports what consent allowed it to see and does not label which half that is.

How we excel

We rebuild the funnel as explicit events on the steps your business actually cares about, then read consented sessions apart from the modelled total, so a rate is never quoted without saying what it is a rate of.

Funnel stepsSource detailConsent state
GA4Reported
MatomoSelf-hosted
MixpanelProduct only
Platform dashboardsModelled

How the work runs

Diagnose first, then test or fix.

Three phases, and the second is a fork rather than a step. Which way it goes is settled by the arithmetic in phase one, never by which is easier to sell.

01Weeks 1 to 2Measured

Establish the baseline.

We define a qualified enquiry against your licence, rebuild the funnel as counted events, and watch the recorded sessions on the step that loses the most. Then we calculate the sample a test on that page would need and how long your traffic takes to produce it. That number decides phase two, and you get it in writing before anything is proposed.

  • BaselineQualified enquiries, defined against the licence
  • Read onYour own recorded sessions
  • OutputThe sample the page would need
02Weeks 3 onwardBranching

Diagnose, or test where you can.

Below the threshold we ship the diagnosed fixes one at a time and read the next month of qualified enquiries against them, which attributes more slowly and acts far faster. Above it we run a split test, set the stopping point before it starts, and leave the result alone until it arrives. Neither branch is chosen because it is the larger engagement.

  • BelowFixes shipped one at a time
  • AboveA test, with the stopping rule set first
  • NeverA result read early
03Each monthReported

Report enquiries, then reorder.

Each month you get the qualified enquiries, the consented sessions behind them and the spend that produced them, with what changed and on what date. The remaining sequence is then reordered against what the last month actually returned, because a plan written in week two is a hypothesis about the rest of the year.

  • ReportedQualified enquiries and consented sessions
  • BesideThe spend that produced them
  • ReorderedAgainst what the last month returned

Reported on qualified enquiries, beside the spend that produced them.

Qualified enquiries only
QualifiedConsented sessionsSequenced

Our commitment

Our promises on the method.

Conversion work is sold here on an uplift number nobody can check. These four are what Webzenia asks to be held to instead.

  • Nothing changes before diagnosis.

    The first thing you receive is a ranked list of failures with the recorded sessions behind each one. No page is redrawn on an opinion, including ours, and the list arrives before any build work is quoted.

  • We say when a test cannot work.

    The sample your page needs is calculated from your own numbers and shown to you with the working. Where no test is readable inside a window you would wait, we say so, even though a testing retainer is the easier thing to sell.

  • Qualified enquiries, beside the spend.

    A raw rate is easy to move, and easy to move the wrong way. You get the enquiries you could actually invoice, the consented sessions behind them, and whatever the platform modelled kept on its own line.

  • One named lead on the numbers.

    One person owns the measurement, the sequence and the monthly report, and is the same person on the call in a month that returned nothing. Nobody new is introduced for that conversation.

Common questions

Conversion rate optimisation in the UAE, answered

Next step

See what your numbers can settle.

Send us the pages that get the most traffic. We will come back with what is worth changing, in what order, and what your volume will let you prove.

Tell us what you need.

+971
Chat on WhatsApp