# Preset Amount Buttons vs Free Entry A/B Test Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/preset-amount-buttons-vs-free-entry-ab-test ## Hypothesis If preset amount buttons cut typing and show a starting range, users may find it easier to settle on an amount and complete the transaction more often. The preset version could then reach a higher total amount per assigned user than free entry, but if the buttons pull choices toward the suggested values, free entry could come out ahead. ## When to run this test Users may be struggling to pick an amount when field analytics shows long pauses at the amount step, amounts are later corrected or cancelled, or drop-off clusters at that step. If the buttons make the choice easier, that arm sees faster choices and less drop-off; if free entry works better, users type their own amount without being pulled toward the suggestions. When drop-off comes from fees, currency or payment errors, fix those first. Before launch, confirm that the button version keeps a visible "Other amount" path and that the amount labels are easy to read on mobile. ## Primary metric **Total amount per assigned user**: Divide the total amount of completed transactions by all eligible assigned users, including those who did not complete a transaction. ## Other metrics - **Transaction completion rate**: Compare completed transactions among eligible assigned users who start one. - **Amount per completed transaction**: Compare transaction amounts among completed transactions only; do not confuse this with total amount per user. - **Custom amount entry rate**: Compare visitors who enter their own amount. - **Amount correction and cancellation rate**: Track transactions corrected or cancelled because the amount was wrong. ## What to check before and during the test - **Interface**: Compare free entry with predefined amount buttons and an “Other amount” option. - **Keep constant**: Keep currency, fees, amount limits and transaction flow unchanged. - **Recommendations**: Predefine suggested amounts; results apply to this set of suggestions. - **Selection**: Do not preselect a suggested amount. - **Audience**: Review first-time and repeat users separately. ## What to watch when reading the result - A higher transaction completion rate can come with a lower amount per completed transaction, so do not pick a winner from completion alone. Total amount per assigned user is the deciding measure; read the custom amount entry rate and the amount correction and cancellation rate to see whether the buttons push people toward amounts that do not fit them. - Whichever side wins has only been tried with this suggestion set. Try other amounts in a separate test where the buttons are already in place, so their presence and their values never change together. Count corrections and cancellations over the same follow-up window in both arms, and review first-time and repeat users separately. - Total amount per user can swing with a few large transactions, so before you decide on a narrow or unclear gap, make sure no single outlier is driving it and that the arms split as planned. Run the transaction completion rates through the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test) to see whether that gap stands out from chance. The calculator does not test averages, so treat the gap in amount per user with the same caution. ## Frequently Asked Questions ### How is amount per user calculated in the preset-amount test? Presets can change the amount selected, so completion alone is insufficient. Divide the total transaction amount by all assigned eligible users, including non-completers. Apply identical cancellation and correction rules. ### Can one suggested amount be preselected? Not in this comparison. Preselection introduces another nudge. Keep a custom-amount option and avoid steering users into an unnoticed higher payment. ### Does the result apply to every preset set? No. It concerns the selected amounts. Fix those values, currency, fees and limits before launch. Another preset set requires a separate comparison. ### How should incorrect amount choices be monitored? Compare corrections and cancellations attributed to unsuitable amounts. Custom entry is diagnostic. Examine first-time and repeat users where those groups are defined before exposure.