# Map Beside the List or in Its Own Tab? A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/map-beside-the-list-or-in-its-own-tab-ab-test

## Hypothesis

A map beside the list lets visitors compare location and listing at once but fits fewer listings on screen; a separate tab gives both views full room but adds a switch that may be harder on mobile. If visitors choose by comparing locations, the side-by-side layout could reach the higher target action completion rate; if they scan the list first, the tab layout could.

## When to run this test

Compare these two layouts when visitors to location-based results seem to struggle moving between list and map, such as frequent view switching in session recordings, visitors who stop scrolling a list squeezed by the map, or feedback from people who could not find a listing on the map. If one layout fits the need, visitors in it find the listing they want with less switching and complete the predefined target action more often. Before launch, define the target action and the usable layouts for each device, and use location only after the visitor grants permission.

## Primary metric

**Target action completion rate**: Define the target action before launch and compare completion among all eligible visitors assigned to the list or map experience.

## Other metrics

- **Listing-detail click-through rate**: Check whether visitors open a listing.
- **Map interaction rate**: Measure comparable map interactions; opening a tab is not the same as viewing an embedded map.
- **Listings seen**: Make sure the narrower list does not materially reduce the number of listings seen.
- **Page load time**: Make sure the map does not slow the page.

## What to check before and during the test

- **Placement**: Compare a map beside the list with the same map in a separate tab.
- **Keep constant**: Keep results, sorting, card design, filters and map behavior unchanged.
- **Space**: Check how the map affects the number of listings visible on screen.
- **Matching**: Make sure each map pin clearly matches its listing.
- **Device**: Predefine usable layouts by device and assess each separately.

## What to watch when reading the result

- Do not compare map interaction rate directly across versions; opening a tab and seeing an embedded map on screen are not the same behavior. Target action completion rate settles which layout leads; listing-detail click-through rate only helps explain why. If the leading layout cuts listings seen by an unacceptable amount, its lead on the target action is not enough to ship it.
- Read mobile and desktop results separately, since the layout that wins on one device can lose on the other. Do not take low map usage in this test as a reason to remove the map; a smaller group may still rely on it to decide.
- A rare target action easily leaves a small gap unresolved, so use the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) to work out how many visitors you need, and run the numbers per device if you plan to read devices separately. Should the result stay unclear, do not force one winner on both devices; choose the layout per device based on usability findings.
- If page load time is longer in the side-by-side layout, check whether the map sits on the critical loading path, because a speed gap gets mixed into the effect of placement. Load the map off that path in both versions so the comparison reflects placement alone.

## Frequently Asked Questions

### Can map-use rates be compared directly between layouts?

Only comparable interactions should be compared. Opening a map tab differs from an embedded map being visible. Use the predefined target-action completion as the primary outcome.

### How can a side-by-side map affect the list?

It can reduce visible listings. Monitor that loss against the agreed limit and verify that map markers clearly correspond to list entries.

### How should the layouts be handled on mobile?

Define usable device-specific layouts before testing. Avoid making the map a critical loading dependency, and request location access through the appropriate permission flow.