
Strategy
Donation page optimization: A/B testing ideas that don't need a developer
Six donation page A/B tests a non-developer can ship, plus the conversion rate and average gift size numbers that decide which variant stays live.
What to take away
Donation page optimization does not require a code release.
- Six tests you can ship without a developergift array default, monthly toggle placement, amount labels, form length, and button wording.
- The sixth is a matching-gift line.
- Define conversion rate as completed gifts divided by form sessions, and write the definition down before the test opens.
- A variant earns a production slot at a 10 percent relative lift with 100 or more completed gifts per arm.
- Conversion rate hides gift size, so check revenue per form session before you call a winner.
- Set the stopping date and sample size in advance, then hold to both.
- The controls live in admin form builders such as Donorbox, Givebutter, Donately, GiveWP, and Neon CRM.
Six A/B testing ideas for donation pages without a developer
These six tests change copy, order, or a default inside a form builder. None needs a code release. Run one at a time. Donorbox, Givebutter, Donately, GiveWP, and Neon CRM all put the amount array, recurring toggle, field order, and button text in an admin panel.
Donorbox publishes a 1.75 percent platform fee on donations, plus card processing. Givebutter charges no platform fee and asks donors for an optional tip. Donately lists plans from about $59 a month. GiveWP offers a free WordPress plugin with paid add-ons. Neon CRM pricing is quote-based.
Gift array default. Preselect the middle amount instead of the lowest. Track conversion rate and average gift together. In Donorbox, this is a default amount setting.
Monthly toggle placement. Move the recurring option above the one-time option. Monthly donors retain far better than single-gift donors, so a small conversion cost can still pay. Givebutter and Donately let you reorder the recurring toggle without code.
Amount labels. Replace bare figures with what they buy. '50 dollars covers a week of meals' against a plain '50'. Keep the figures identical in both arms. GiveWP supports custom amount labels in its form builder.
Form length. Cut every field you do not use for receipting or stewardship. Test the short form against the current one, not against a hypothetical. GiveWP's form builder lets you remove or reorder fields without a developer.
Button wording. 'Give now' against 'Support the food bank'. Specific beats generic in most tests, but run it. Donorbox and Givebutter let you edit button text in the form settings.
Matching-gift line. Add one line naming a current match. Only run this when a match is real and documented. Put it above the amount array in Donately or GiveWP.
What to measure
Conversion rate is completed donations divided by sessions that load the form, not by all site sessions. Visitors who never reach the form cannot convert, and counting them flattens every effect you are trying to see.
Three metrics to record
Conversion rate
- Definition
- Gifts divided by form sessions
- Leaves out
- Gift size, refunds, intent
- Minimum sample
- 100 gifts per arm
Average gift
- Definition
- Revenue divided by gifts
- Leaves out
- Number of gifts
- Minimum sample
- 100 gifts per arm
Revenue per form session
- Definition
- Revenue divided by form sessions
- Leaves out
- Long-term donor value
- Minimum sample
- 100 gifts per arm
Record two companions. Average gift shows whether a cleaner form is pulling smaller gifts. Revenue per form session combines both and is the number your finance lead will recognize.
| Metric | Definition | What it leaves out |
|---|---|---|
| Conversion rate | Completed gifts divided by form sessions | Gift size, refunds, donor intent |
| Average gift | Total revenue divided by completed gifts | Number of gifts |
| Revenue per form session | Total revenue divided by form sessions | Long-term donor value |
Traffic splitting works the same way it does anywhere else, as the A/B testing article on Wikipedia sets out. An illustrative minimum is 100 completed gifts per arm. Below that, a handful of gifts moves the rate by whole points.
Reading the result
Read relative lift, not absolute points. A move from 2 percent to 2.2 percent is a 10 percent relative gain. On 40 gifts, the same movement is noise.
A 0.2 point gain on a 2 percent base is a 10 percent relative lift. On 40 gifts it is a coin toss.
Weekends and month-end behave differently, so compare like days to like days. Keep counts where you can still read them next quarter, which is the practice behind nonprofit marketing analytics.
Worked example: the default gift
Two arms. One preselects the lowest amount in the array. The other preselects the middle amount.
Default gift worked example
Control
- Preselected amount
- Lowest
- Conversion rate
- 2 percent
- Average gift
- 45 dollars
- Revenue per session
- Lower
Variant
- Preselected amount
- Middle
- Conversion rate
- 2 percent
- Average gift
- 52 dollars
- Revenue per session
- Higher, ship it
Suppose control converts at 2 percent with a 45 dollar average gift, and the variant holds 2 percent with a 52 dollar average gift. Revenue per form session rises, so ship it. If conversion drops to 1.7 percent and average gift rises to 52 dollars, revenue per form session falls and control stays.
Do not read the result on day one. Early gifts cluster around your most engaged donors.
What the numbers cannot tell you
Conversion rate treats a returning major donor and a first-time visitor as equal. It ignores refunds and chargebacks, which land weeks later. It says nothing about whether donors give again next year.
The acknowledgment you send after a gift falls under IRS rules on substantiation and disclosure, so a form change that alters the data you capture can affect compliance. Canadian receipting follows CRA rules instead, and either way the specifics belong with a qualified charity lawyer.
Whether the new donor returns is a donor retention question, and it needs its own test.
Attribution and its limits
Attribution tools split credit between email, paid search, social and direct. A donor who opens an email on Monday and gives on Friday is usually credited to the last click. Platform dashboards count the same gift twice, and none of them agree on the total.
Every tracking script you add to the form widens the data you hold. The FTC guidance on data security is a reasonable baseline. In Canada, PIPEDA, BC PIPA and Quebec Law 25 each add their own consent and retention duties, so check with counsel before you add a pixel.
When to stop and decide
Stop at 14 days or 200 completed gifts per arm, whichever comes first. Ship at a 10 percent relative lift or better with revenue per form session holding. Kill the variant under 5 percent. Between 5 and 10 percent, keep control and run it again with more traffic.
Stop and decide rule
Stop at 14 days or 200 gifts per arm?
Ship at 10 percent relative lift or better
Kill under 5 percent, keep control between 5 and 10
Checking the dashboard daily and stopping on a good day inflates false positives. Pre-register the decision rule and the date. A donation page test also runs inside a campaign calendar, where heavy email and paid support make the result hard to read, as the nonprofit fundraising campaigns notes describe.
Common questions
How long should a donation page test run?
Two weeks minimum, and long enough for 100 completed gifts per arm. A shorter window favors whichever weekday lands inside it.
Can I test two changes at once?
You can, and you will lose the ability to credit the lift to either one. Run separate rounds unless traffic is heavy enough to split four ways.
What if my traffic is too low to test?
Then stop testing and start reading. Form abandonment surveys and a handful of donor calls beat a test that can never reach a decision. If most of your traffic arrives through email, the nonprofit email marketing notes explain why the send itself moves the number.
Does a higher conversion rate always mean more money?
No. If average gift falls by more than the conversion rate rises, revenue drops. Check revenue per form session before you celebrate.







