Before GivingTuesday, Try Your Donation Journey on a Phone

Your GivingTuesday email can be beautifully written, carefully timed, and linked to a donation page nobody has tried on a phone.

We’d put the phone check on the calendar before another round of headline revisions.

GivingTuesday falls on December 1, 2026. There’s time to follow the route your supporters will take, find the awkward parts, and give someone a realistic chance to fix them.

You don’t need to begin with a new donation platform or a website redesign. Start with the campaign link, a phone, and a colleague who didn’t build the page.

Why the phone deserves its own check

The 2026 M+R Benchmarks website findings, reporting on 2025 activity, show mobile devices accounted for 52% of participating nonprofits’ website visits. Among people who reached a primary donation page, 8% of mobile users completed a gift, compared with 11% of desktop users. M+R’s mobile category includes phones and tablets.

Those figures describe study participants. They aren’t a forecast for your organization, and they don’t prove that page design caused the difference. Donor intent and audience mix matter, too.

They do give us a good reason to check the experience on an actual phone. A page fitting inside the screen is a fairly modest definition of success. We’d also like someone to understand it.

Start with the link your supporter receives

Open the donation link from your draft campaign email on your phone. If social posts use a different link, follow that route separately.

Check whether the destination carries the same appeal forward. For a hypothetical winter assistance campaign, the email might describe emergency heating support while the donation page opens with a generic “Support our work” heading. The visitor now has to decide whether they’ve reached the right place.

A short campaign heading and a clear explanation of how gifts will be used may be enough. You don’t necessarily need a separate page for every appeal.

If the donation form opens on another provider’s website, check the handoff. Does the organization’s name remain obvious? Is the campaign recognizable? Can the visitor find help?

Write down the exact point where the experience becomes uncertain. “The page feels confusing” is difficult to assign. “The campaign name disappears after tapping Donate” gives your team something to investigate.

Make the amount and frequency unmistakable

Choose a gift amount, then inspect the one-time and recurring options.

We recommend making the selected frequency easy to recognize before someone enters payment information. If monthly giving is selected, that choice should remain clear as the donor moves toward submission.

In a hypothetical interface, “Give $25 every month” communicates more than a button that says “Continue.” Whether you can change that button depends on your platform. A clearly displayed summary beside it can also help.

Check custom amounts, too. Can someone enter the amount they intended? Does switching between one-time and monthly giving change another selection unexpectedly?

Keep the test practical. You’re checking whether the donor can understand and control their gift. You don’t need six new payment options to resolve an unclear frequency label.

Try the form when an answer is missing

A form deserves a check when someone makes an ordinary mistake.

In a test environment, leave a required field empty and try to continue. Look at the response:

• Does it identify the field that needs attention?
• Does it explain how to correct the problem?
• Is the message readable on the phone?
• Are previously entered answers still there?

W3C’s form notification guidance recommends clear error messages with instructions for resolving them. A red outline alone gives the visitor little help.

Check the labels as well. A field’s name should remain available after someone starts typing. W3C’s form instructions tutorial explains why placeholder text inside a field isn’t a substitute for a label.

These checks can reveal issues worth fixing. A phone walkthrough doesn’t establish accessibility conformance; keyboard and assistive technology testing require their own attention.

Follow the journey through confirmation

Coordinate payment checks with whoever manages your donation platform. Use its supported test environment and test payment details. Never enter test card numbers into a live checkout.

If there’s no suitable test environment, ask your platform administrator how to verify payment and receipts safely. You can still review the public journey up to payment without making a donation.

For a completed test, check the confirmation message and email together. Do they accurately reflect the amount and gift frequency? Does the page explain what happens next? Is there a working contact route if the donor needs help?

Only promise an emailed receipt if that email is actually configured and verified. Likewise, the page should report a successful donation only when the transaction status supports that message.

A lovely thank-you page that disagrees with the payment record creates a very avoidable afternoon.

Give every issue an owner

Keep a short issue list with the page link, device, steps taken, expected result, and what happened. Add a screenshot where it helps, keeping donor and payment details out of it.

Then assign each issue to the person who can act. Campaign wording might belong to communications. A receipt setting might belong to the fundraising administrator. A form that becomes unusable on a phone may need your developer or platform provider.

Prioritize anything that prevents completion or makes the gift unclear. Cosmetic adjustments can follow. If the form already works well, keep it and improve the surrounding copy where needed. A platform migration five weeks before a campaign needs a stronger reason than a slightly dated button.

Your next step: Book 30 minutes with a colleague to follow your actual campaign link on a phone. Capture the problems precisely, assign an owner to each, and reserve time to check the fixes before the campaign goes out.