# One Guarantee Block or Spread Across the Page A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/one-guarantee-block-or-spread-across-the-page-ab-test

## Hypothesis

Grouping the assurances in one block gives a tidy answer, but visitors who never reach that block may not see them at all. Placing each assurance next to the decision it informs means it can be read when needed; as long as the page does not feel crowded, that layout could post a better primary action completion rate than the single block.

## When to run this test

Look for three signs that assurances are out of reach when visitors need them: visitors who leave before scrolling to the reassurance block, abandonment that clusters at points of concern like the price or the form, and support contacts about data security while filling in the form. In the distributed layout, each assurance should be seen next to its step, and abandonment at those steps should fall. Before moving anything, set aside information that must appear in a specific place for legal reasons and leave it where it is; if abandonment has another cause, such as a form error, fix that first.

## Primary metric

**Primary action completion rate**: Compare completion to see whether distributing reassurance statements changes the target action.

## Other metrics

- **Step-level abandonment rate**: Check whether abandonment falls at points of concern.
- **Reassurance visibility**: Make sure visitors continue to see the reassurance statements.
- **Related support contacts**: Track questions about the same topics.
- **Time to action**: Check whether the distributed layout materially delays the target action.

## What to check before and during the test

- **Placement**: Move each existing reassurance from one shared block to a predefined relevant location.
- **Keep constant**: Keep wording, terms and number of statements unchanged.
- **Relevance**: Place each statement where it answers the relevant question.
- **Visibility**: Measure whether each statement enters the viewport.
- **Separate tests**: Repeating a reassurance or changing its wording is outside this comparison.

## What to watch when reading the result

- A drop in step-level abandonment or related support contacts does not make either layout the winner unless the primary action completion rate moves too. Make sure, too, that reassurance visibility does not fall in the distributed layout and that time to action does not grow materially.
- Treat the result as specific to this page and these pairings of assurance and location. In the distributed layout, confirm that each assurance uses the same wording everywhere it appears; different wording can undermine trust and means you can no longer credit the difference to placement alone.
- Do not rush to declare either layout the winner while the gap is unclear. Enter each layout's visitors and primary action completions into the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test); if the gap is not significant, accept that this test could not separate the two layouts and consider a longer run.

## Frequently Asked Questions

### Where should individual assurances move?

Place each near the decision it informs while preserving wording and conditions. Keep every assurance accessible and do not move information contrary to applicable placement requirements.

### Could distributing assurances reduce their exposure?

Yes. Measure each assurance’s actual visibility. A single block can also be missed, so compare exposure without assuming either format guarantees reading.

### Which diagnostics help explain the main-action outcome?

Inspect abandonment near relevant decision points, related support contacts and time to action. Use completed main actions as the primary outcome rather than treating diagnostics as alternative winners.