Funnel Analysis
Funnel drop-off analysis in GA4: we find the step, device and channel where visitors leave and set priorities with data.
ExploreThe hard part of A/B testing is not setting up the tool; it is making sure the result is not down to chance. Tests stopped early, run on too little traffic or overlapping with a sale week declare a 'winner', and the change that ships then delivers nothing. Our A/B testing service starts with a traffic calculation, and we write down the duration and success criteria before the test goes live.
We run A/B tests to prove that a change to the site actually increases sales before rolling it out to everyone. Decisions on design and price display rest on measured results, and changes that would lose sales are caught on a small share of visitors first. Every result feeds the hypothesis for the next test.
Funnel stages it serves
Three values determine how much traffic a test needs: the current conversion rate, the smallest difference we want to detect, and the margin of error we accept. For example, on a page with a 2 percent conversion rate, detecting a 10 percent relative lift (from 2 to 2.2 percent) at 95 percent significance and 80 percent power requires roughly 80,000 visitors per variant.
This calculation often changes what gets tested. If traffic is not enough, instead of small changes such as button color, we test changes likely to make a big difference: price display, the number of checkout steps, offer structure. If needed, we also move the primary metric to a higher step in the funnel, for example from purchase to checkout start.
We calculate the duration from the required sample and always round it up to full weeks, because weekday and weekend visitors behave differently. We do not check results every day and stop the test when significance appears; that approach markedly increases the chance of declaring a false winner. We also account for periods specific to the shopping calendar in Türkiye:
Google Optimize shut down on 30 September 2023, and GA4 has no built-in A/B testing tool. Today we work with standalone tools such as VWO, AB Tasty, Optimizely or Convert and send variant information to GA4 as an event parameter. That way we can read results in GA4 and order data as well as in the tool's own report.
Because client-side tests change content while the page loads, they can cause a brief flicker, and the anti-flicker snippet can hurt page speed, especially LCP. For critical tests such as checkout flow and pricing, we recommend a server-side setup where the variant is chosen while the page is rendered on the server. We decide which setup to use based on the share of revenue that passes through the page under test.
Test ideas come from funnel analysis and session recordings. We rank them using the ICE score described in growth experiments; for site tests, we score Impact based on the volume of drop-off at the step the change affects. We run site tests separately from ad tests: for creative and messaging tests, we use the platforms' own experiment tools and ad creative analysis. A winning ad message, in turn, often provides the next hypothesis to test on the landing page.
We recommend it
We don't recommend it
Metrics we track
What you need to get started
Official sources
To learn more about A/B Testing or other conversion optimization services, contact The Brand Move Conversion Optimization team today.
Funnel drop-off analysis in GA4: we find the step, device and channel where visitors leave and set priorities with data.
ExploreHeatmaps, scroll maps and filtered session recordings in Clarity or Hotjar that show where and why visitors get stuck.
ExplorePage speed optimization: LCP, INP and CLS measured with real-user data and a prioritized fix list for your developers.
ExploreNot if the planned sample and duration have not been reached. Interim results fluctuate, and the difference seen in tests stopped early usually shrinks later. Once the planned duration is complete, we decide based on the threshold and primary metric set in advance.
We test bigger changes that are likely to move the needle, such as price display, the number of checkout steps or offer structure, instead of small tweaks like button color. If needed, we move the primary metric to a higher step in the funnel, for example from purchase to checkout start.
Yes, on different pages and in areas that do not affect each other. If we test within the same user flow, for example on both the cart and checkout pages, we either separate users or run the tests in sequence to control for interaction.
We record the test as inconclusive; we do not extend it in search of significance. An inconclusive test tells us the two versions cannot be told apart at this traffic level. We then write a new hypothesis with a bigger change or move the primary metric higher in the funnel.
Client-side tools change content while the page loads, which can cause flicker, and the anti-flicker snippet can hurt page speed, especially LCP. For critical tests such as checkout and pricing, we recommend server-side testing, where the variant is chosen before the page reaches the browser.
In a free call we review the drop-off points in your funnel and your landing pages, then send you the first three ideas to test in writing.