How to add participant fundraising pages to a paid charity event

Someone buys a place at your charity walk, sets up a fundraising page and sends it to their friends. One friend donates. Another buys a ticket. A third asks whether their donation includes admission. Then the participant changes their plans, and nobody is quite sure what happens to the money already raised.

Participant fundraising can work well alongside a paid event, but you need to explain those relationships before asking people to share a link. Sell admission through the event registration process, collect donations through the charity's approved fundraising arrangement, and connect each participant's page to the right campaign. Keep the payment records separate even when you report the results together.

This guide walks through that setup, including the agreement with the charity, the participant briefing, a worked budget and the checks before you announce a total. The recommendation is to start with optional fundraising and a small supported group. Make the process work for them before opening it to every ticket holder.

Decide what a participant page is meant to do

Peer to peer event fundraising means participants ask people they know to support a cause through their own fundraising pages. The participant explains their connection to the event and shares their page. Donations are recorded against that page and, where the chosen arrangement supports it, included in the wider campaign total.

That personal explanation is the useful part. Your event page can describe the programme and beneficiary, but a participant can explain why they chose to take part. Someone may donate because they care about their friend, because they support the charity, or both. They don't have to attend the event themselves.

Start by choosing the job you want the pages to do. Are walkers raising voluntary donations alongside their entry fees? Are table hosts inviting friends to support the charity before a gala? Are participants accepting a fundraising obligation in exchange for a subsidised place? Those are different offers, with different financial and support requirements.

For a first campaign, I'd choose paid entry with optional participant fundraising. You know what admission costs, the participant knows what they have bought, and the charity can approve a separate giving process. You can encourage a suggested target without turning a disappointing fundraising result into an unexpected bill.

A compulsory minimum needs considerably more explanation. State the amount, deadline, any personal payment obligation and the treatment of withdrawals before someone registers. Ask the charity and appropriate advisers to review those terms. A suggested target in an encouraging email should never become a debt after the event.

Also decide who may create a page. You might allow confirmed participants only, or welcome supporters who won't attend. If non-attending supporters can join the campaign, say so and use a different label for them. A fundraising-page count cannot tell your operations team how many people will arrive.

Our paid-entry charity walk guide covers the route, participant operations and event budget. This post deals with the additional fundraising work. You still need a properly planned event, even when the fundraising pages attract more attention than the ticket offer.

Agree who controls the campaign and receives the money

The first conversation should be with the charity, before you choose software or send a page template to participants. Confirm the beneficiary's legal identity, the authorised campaign contact and permission to use its name and approved materials. Establish whether you are delivering its event or independently organising an event in its aid.

Write down who receives ticket payments and who receives donations. Prefer an approved arrangement that sends donations to the charity rather than asking participants to collect money in personal accounts and transfer it later. That recommendation is about reducing uncertainty. You still need to verify the actual payment route, deductions and transfer arrangements.

The US Federal Trade Commission's guide to donating through fundraising platforms explains why this matters. Depending on the arrangement, money can go to a campaign organiser or an intermediary before reaching the intended cause. A familiar participant's photograph doesn't explain who controls the funds.

Ask the charity to approve a short statement that answers the donor's questions. Name the beneficiary, explain the purpose, identify who handles the payment and describe any deductions that affect the amount received. If the platform asks donors for a separate optional contribution to support the platform itself, make sure the distinction is understandable.

Then agree your commercial arrangement. An event business may charge for planning and delivery. A charity may pay that fee, or it may be included in specified event costs. Document it and explain the public fundraising promise accurately. Avoid saying that all proceeds go to the charity when some revenue covers an organiser fee or other costs.

For UK activity, the Fundraising Regulator's online fundraising standards address matters including clarity about fees and the route money takes. Their requirements depend on the role each organisation performs. The charity should identify the provisions that apply to the event operator, fundraising service and participant arrangement.

Allocate the less exciting decisions too. Who approves a page with an inaccurate claim? Who handles a donor complaint? Who can suspend a page, change a campaign description or authorise a refund? Agree a backup contact so the campaign doesn't depend on one person answering their phone during event setup.

Make the agreement useful to the team. Keep a controlled copy of the approved beneficiary description, payment explanation, contact details and escalation process. Participants can personalise their story without rewriting the financial promise. When the charity changes approved wording, someone must know which pages and messages need checking.

Keep the ticket offer clear before introducing the donation ask

A buyer should be able to understand the event without opening a participant's fundraising page. Describe what admission includes, when and where the event happens, who can attend and what the buyer must do next. Explain optional fundraising in a separate paragraph with a clear route to set it up.

This matters even when the cause is familiar. In Loopyah's Worth It Event Index, a February 2026 Pollfish survey of 500 US consumers, respondents described how clear they usually felt about an event's experience before buying. The chart shows the raw answers to that single-choice question. It measures general event clarity, rather than charity-event behaviour or donation intent.

Those answers don't establish whether participant fundraising increases donations. They do give us a reason to take the paid experience seriously. The cause doesn't remove a buyer's need to understand what their ticket provides. A donor supporting a friend may need quite different information from someone deciding whether to attend.

A straightforward event description might say that admission includes the organised walk, specified support and a finish refreshment. It can then explain that participants may also raise voluntary donations through an approved page. State explicitly that donating to a participant does not provide admission and buying a ticket does not create a fundraising obligation.

In Loopyah, ticket types and quantities let you define the admission options people can purchase. Use that process for the event place. Arrange participant donation pages through the charity's approved service, and verify that service's capabilities independently. Don't describe those pages as a Loopyah integration unless you have confirmed that exact connection.

After registration, make the optional next action easy to find. A confirmation page or appropriate follow-up can explain where to create a fundraising page, what information the participant needs and where to ask for help. Keep their ticket confirmation available independently, so they can still find event details after creating the page.

Someone should test the opposite journey too. A donor lands on a participant page, decides they'd like to attend and follows the event link. That route should lead to admission information and a real purchase process. It shouldn't imply that the donation has reserved a place, especially if the event is already sold out.

Choose the fundraising arrangement by testing real tasks

Begin with the charity's existing approved service. It may already have verified beneficiary details, finance procedures and staff who can resolve donor questions. Adding a new service creates work, so there should be a specific reason the current arrangement cannot support your campaign.

Write a small test plan before a demonstration. Create a participant page, personalise it, make an authorised test donation using the service's supported method and check the confirmation. Find out what appears on the public page, the participant's view, the charity's records and the payment report. A polished demonstration can hide a confusing handover between those views.

Check whether individual pages can belong to one event campaign. Ask how team pages work and whether an individual gift is included in an individual total, a team total and the campaign total. Those displays may all be correct, but they are overlapping views of the same money. Your finance report must not add them together.

Find out how the service handles offline gifts. If a participant records cash collected elsewhere, does the campaign total label it separately? Does entering that amount create a promise to pay, a record of money already received, or simply a public progress update? The answer determines whether you can include it in a received-funds announcement.

Test a refund and an unsuccessful payment through supported procedures. Check who has authority to approve the refund and how it changes the visible total. Ask about payment disputes and delayed settlements. The participant may still see an encouraging amount while the charity's finance team has a different available balance.

Check page ownership as carefully as payments. A participant needs enough control to write their story and share updates, while the charity needs a way to correct misuse of its identity. Establish what happens if a participant loses access, leaves a team or asks for their public page to be removed.

Use a phone for these tests. Follow the shared link in the sort of message your supporters will actually receive, and read the page while signed out. Check the beneficiary explanation, payment labels and confirmation without relying on a staff account. Someone unfamiliar with the setup should be able to explain where the donation goes.

The W3C's guidance on form labels explains how labels identify the purpose of controls, including for people using assistive technology. Ask the service about accessibility and test the actual process. If a person can't complete it, agree a supported alternative rather than telling them to ask someone else to donate for them.

Give participants a page they can confidently personalise

A participant needs a clear starting point, not a blank editor and a message telling them to be inspiring. Supply approved factual copy about the cause, the event and the donation process. Leave space for their own reason for taking part, and explain which parts must stay accurate.

A useful page has a recognisable title, the participant's chosen public name, an approved description of the beneficiary and a personal explanation. It should also include the event date, an accurate link to admission information, a voluntary target where appropriate and a clear donation action. Keep the most useful information visible without requiring a long scroll.

For example, a participant might write that they are joining the community walk because the charity's local services matter to their family. They can explain what they are preparing to do and why they would appreciate support. They don't need to describe a private medical history or publish someone else's experience to justify asking.

Give participants permission to keep their story brief. A short, comfortable explanation is better than a dramatic account they later regret sharing. Offer to help with spelling, images and layout without taking over their voice. The point of a personal page is that the reader recognises the person making the request.

Protect the people whose stories appear. Get the charity's approval for supplied beneficiary accounts and images, and establish that the relevant permissions cover this use. A participant's permission to discuss their own experience doesn't automatically cover another family member, a child or someone receiving support from the charity.

Write the target explanation carefully. A target can help someone make a concrete request, but it is not a forecast or a guarantee. Let participants understand whether they can change it, what happens when they exceed it and whether it carries any personal obligation. For this guide's optional model, it creates no compulsory payment.

Avoid invented claims about what a particular donation buys. If the charity supplies an approved cost illustration, use its exact conditions and explain whether donations are restricted to that purpose. Otherwise, describe the work in broader factual terms. A persuasive page doesn't need to promise that every donor's money purchases a specific item.

Provide a short review route. Participants should know how to ask whether wording is acceptable, how quickly they can expect an answer and whom to contact if a donor reports a problem. A review request sitting unanswered for days can stop an otherwise willing participant from sharing their page at all.

A short brief you can adapt

Send participants one approved reference they can return to. Begin with the campaign name and beneficiary, then explain the event and their role in ordinary language. For this optional model, the first paragraph can say that their ticket covers admission and that creating a page is a voluntary way to invite additional support.

Follow that with the page setup instructions. Name the approved campaign link, explain how they know their page belongs to the correct campaign and tell them which information will be public. Ask them to check the beneficiary and their chosen display name before sharing. Include an alternative support route for anyone who cannot use the page editor.

Next, explain the money. Use the charity's approved description of the receiving organisation, deductions and payment process. State that a donation does not buy an event ticket. Explain whether any offline amount appears in the visible total and how it will be verified. Avoid replacing that explanation with a vague assurance that everything is secure.

Finish with the practical questions. Include the support contact, expected response arrangements, event link and donation closing date. Say how participants can withdraw or report incorrect information. A version date helps staff identify an old brief after a campaign detail changes. This is a working reference, so keep it short enough that a participant will actually read it.

Plan the numbers without spending promised donations

The event budget and participant fundraising forecast should be connected, but kept distinguishable. Your suppliers need paying whether or not a participant shares their page. An optimistic target is not money you can use for deposits, and donations paid directly to the charity may never be available to the event operator.

Here's a fictional example in USD. These figures are planning assumptions, not supplier quotes, fundraising benchmarks or recommended prices. Suppose your paid community event has fixed delivery costs of $2,400. The amount retained from each ticket after ticket payment charges is $30, and each attending participant costs another $5 to serve.

Each paid place therefore contributes $25 towards fixed costs. With 100 paid participants, retained ticket income is $3,000 and participant delivery costs are $500. Subtract the $2,400 fixed costs and the event leaves $100. The whole-ticket break-even point is 96 paid places, assuming those costs stay unchanged.

Now add participant fundraising. Suppose 40 of the 100 participants choose to create pages, and each chooses a $150 target. Those targets add to $6,000. That is an expression of their intentions. It doesn't establish the amount that will be donated, received by the charity or available after deductions.

For a separate settlement example, suppose completed online gifts total $4,000. Refunds total $100, and the service's actual fees in this invented example total $120. That leaves $3,780 from those online gifts. An additional $200 in offline donations has been received and verified separately, making $3,980 in net donation funds under these assumptions.

If the event's $100 surplus is also contractually due to the charity, its combined benefit is $4,080. Report the components. The $6,000 of participant targets is not added to that figure. Neither is a team-page total that already includes some of the $4,000 in gifts.

Now test weaker ticket sales. At 80 paid participants, retained ticket income is $2,400 and participant delivery costs are $400. The event loses $400 against the same fixed costs. If donations are paid directly to the charity, those donations do not automatically cover the operator's loss. Your agreement must say who carries it.

You could change the delivery budget, secure confirmed support for existing costs or choose a different admission price. Our event budget guide helps work through those choices. Don't quietly deduct the shortfall from donations after promising donors that their money would follow a different route.

Add the cost of supporting participant pages. If you spend another $300 on approved campaign setup and support, fixed costs become $2,700. At the same $25 contribution per paid place, the event needs 108 paid places to break even. At 100 paid participants, the earlier $100 surplus becomes a $200 loss.

That doesn't mean participant fundraising is a bad idea. It means the charity and operator need to agree who pays for the extra work and why it is worthwhile. Budget staff time honestly, even when a salaried employee or volunteer will do it. A campaign can raise useful funds while making the event contract financially unattractive for its organiser.

Recruit a small group and support the work they actually do

For the first campaign, invite a manageable group of willing participants to try the process. Choose people who can give useful feedback, rather than assuming the most visible supporter will be the best tester. Explain that you're testing the page setup and support process, with no promise about how much they will raise.

Walk through the process with them. Can they find the invitation after buying a ticket? Can they create a page without re-entering confusing event details? Do they understand who gets the money and how to share the correct link? Fix repeated problems before sending the invitation to everyone else.

Offer a short welcome message that covers the cause, the optional nature of fundraising and the first task. Ask them to create and review their page before sharing it. Include the support contact in the message itself, so they don't have to search a separate handbook when something goes wrong.

Then help them write a first request. A useful message explains what they are doing, why the cause matters to them and where someone can choose to donate. It can also say that sharing the page is appreciated. Avoid guilt, invented urgency or language suggesting that friends owe a contribution because of their relationship.

You can supply an example without asking people to paste it unchanged. For instance, the participant can name the event, describe their reason for joining and explain that donations through the linked page support the approved campaign. Ask them to check the link before sending. Their story should sound like them, including when it is quieter than your campaign copy.

Supporters may want to use email, messaging apps, workplace groups or a printed card. Explain any permissions required for workplaces and shared groups. Don't encourage bulk messages to people who haven't agreed to hear from them, and don't ask participants to upload their address books into an unfamiliar service.

Plan your own support around observable problems. A page created but not shared may need a wording check. A participant reporting a donor payment error needs a technical response. Someone who has chosen not to fundraise needs their choice respected. Sending the same reminder to all three won't help them equally.

Avoid a public ranking as the default. A participant with a small personal network may put considerable effort into a modest total. If the campaign includes recognition, explain it beforehand and let people decline public mentions. You can recognise participation or a helpful contribution without turning private financial circumstances into a competition.

Set a communication schedule people can use

Choose a campaign opening date, the event date and a donation closing date with the charity. These dates don't need to be the same. Participants may want to share preparation before the event and a completion update afterwards. The charity also needs time to resolve unsettled payments before reporting a final result.

Use a short sequence that follows those real moments. Start with setup guidance, then help participants make their first request. Before the event, send information they need for attendance separately from any fundraising encouragement. Afterwards, offer an approved update they can share with people who supported them.

An example campaign might open participant pages six weeks before the event, check setup problems during the first week and offer a progress update two weeks before the date. Donation pages might remain open for two weeks afterwards, followed by financial reconciliation. Those are illustrative choices, not evidence of an optimal campaign length.

The content matters more than filling every date with a reminder. If you have no new information, don't invent an emergency. A useful update could explain what participants have prepared, confirm an event detail or share an approved account of the charity's work. Keep the donation request proportionate to that information.

Be precise about a closing date. Does it mean pages stop accepting gifts, the published total is calculated or the charity expects the funds to settle? If those happen on different dates, name them separately. Participants shouldn't discover that their link has stopped working immediately after sending a final update.

Keep operational messages easy to recognise. A route change, arrival instruction or cancellation announcement must reach the relevant participants even if they aren't fundraising. Someone should not have to read a donation appeal to discover that the start time has changed. Use attendee email tools for relevant ticket-holder communication, with the audience and permission checked for the message you intend to send.

The UK rules for electronic fundraising messages need current attention. The ICO's April 2026 update on charity messages explains a conditional charitable purposes soft opt-in. It is not blanket permission for an event business to market to everyone who donates. Have the responsible organisation check its eligibility, the collection process and the required choices before using that exception.

Agree who sends donor acknowledgements and who sends participant updates. Your charity partner may have the donation relationship while the event operator has the ticket relationship. Sharing the same campaign name doesn't mean the organisations can exchange contact lists or send each other's marketing without an appropriate basis.

Make tax, privacy and public recognition deliberate decisions

Keep tax statements out of participant improvisation. The charity should approve any wording about deductibility, tax relief and acknowledgements for the relevant location and arrangement. An event ticket, an unrestricted donation and a payment connected with a benefit can have different treatment even when they support the same cause.

In the US, the IRS's quid pro quo contribution guidance explains payments that partly buy goods or services and partly make a charitable contribution. The deductible element is generally limited to the amount above the value of the benefit, and specific disclosure requirements apply. Don't tell ticket buyers their entire payment is deductible simply because the event benefits a charity.

The same caution applies to a participant's sponsored place. If fundraising is connected with a subsidised benefit, ask the charity to check the arrangement before using standard donation wording. This guide's optional model deliberately keeps admission as a separate purchase, but that separation doesn't replace a proper review of the actual facts.

Choose which identity information becomes public. A participant may be happy to display a first name and story while keeping other details private. A donor may want to support them without appearing in a visible list. Test those choices while signed out and check what remains visible in search results, shared previews and campaign exports.

Give people a way to correct a mistake. If someone accidentally publishes another person's name or photo, they need a clear support route and a prompt response. Explain the limits of removing material already shared elsewhere. Deleting the original page may not remove screenshots, message previews or copies posted by other people.

Restrict staff access to what their jobs require. The person helping participants with page wording doesn't necessarily need donor addresses or financial reports. The finance lead needs transaction references and settlement information, while a sponsor may need only an aggregate result. Plan those views before exporting a complete database to a shared folder.

Treat children's participation separately. Agree with the charity how adults manage pages, images, stories and contact details where children are involved. Avoid inviting children to publish personal information or contact strangers to meet a target. Your event's safeguarding arrangements must address the fundraising activity as well as attendance.

For recognition, ask what permission you actually have. Being thanked privately doesn't imply consent to a public profile, a sponsor presentation or a future advertising campaign. You can report the overall result without identifying every donor. Let people support the cause without accepting a publicity obligation they didn't choose.

Prepare for withdrawals, incorrect pages and payment problems

Write the withdrawal explanation before the first participant needs it. A cancelled ticket and an existing donation are separate transactions, potentially controlled by different organisations. Tell the participant who handles each question. Don't promise that one cancellation request automatically reverses everything attached to their page.

If someone cannot attend, ask whether they want to continue fundraising as a non-attending supporter, close their page or update its story. The charity must check whether the change affects the purpose donors were told they were supporting. A personal challenge that never takes place may need a different response from a general campaign donation.

Likewise, event cancellation needs an agreed campaign response. Confirm how the ticket terms apply and ask the charity to decide what happens to the appeal. Review what donors were promised, the service's process and applicable rules. Avoid treating donations as the operator's reserve for cancellation costs.

An inaccurate page needs a correction process, not an argument in its comments. Save the details needed to investigate, contact the participant through the approved route and involve the charity's authorised person. If the page falsely says all money is paid directly to a beneficiary, correct that claim before encouraging more sharing.

For suspected impersonation, use the fundraising service's reporting and suspension channels. Tell participants how to verify official campaign links from the event or charity website. If a fake page is circulating, publish a clear approved correction through channels likely to reach affected supporters. Don't repeat unverified allegations about an individual.

Payment problems should go to the organisation that can investigate them. Ask for the transaction reference and relevant timing through a secure support route. Staff should never request card details in a public comment or shared participant chat. The participant doesn't need to become a payment investigator because the donor knows them personally.

Keep a short incident record with the date, issue, responsible person and outcome. Record whether an incorrect public total, misleading description or donor communication needs correcting too. Closing the support request isn't enough if the original mistake is still visible on a page people continue to share.

For a campaign-wide outage, decide who communicates and what participants should do meanwhile. A pause on sharing may be better than encouraging gifts through personal bank accounts. Resume once the approved route works and any missed or duplicate transactions have been checked with the service and charity.

If participants also collect offline donations

Online pages don't make cash handling disappear. Someone may receive a cheque from a relative or collect a permitted cash gift through another approved activity. Decide beforehand whether your campaign accepts those funds and, if so, how the charity wants them delivered and recorded. Never assume that entering a number on a page completes that process.

Give each offline record a reference that the finance lead can match to a receipt or confirmed transfer. Record the participant or team it belongs to, the amount, the date received by the responsible organisation and its verification status. Collect donor information only where needed for the agreed purpose, through the approved process. A participant's public update is not the place to publish a cheque image or donor contact details.

Check whether that offline gift has already been entered elsewhere. A participant could log a cash amount and later pay the same money through the online page. If both entries remain in the campaign total, the gift appears twice. Agree how the original offline entry is corrected and retain enough explanation for the charity to understand the change.

Tell participants where their responsibility ends. They need a receipt or confirmation that the approved recipient has taken over the funds. Staff need a way to investigate an unmatched amount without repeatedly asking every volunteer. If money is still outstanding at the reporting cutoff, list it separately and follow up through the agreed process rather than silently including it in the final result.

Reconcile gifts once, then explain the result

Agree the report before launch. You need to distinguish participant targets, completed gifts, refunds, fees, verified offline funds and money still in transit. Team and campaign totals should be understood as views of the underlying gifts. A transfer between accounts is a movement of money already raised, not a new donation.

Return to the fictional example. The participants' $6,000 in targets sits outside the received-money calculation. Online gifts of $4,000 less $100 in refunds and $120 in fees leave $3,780. Adding $200 in verified offline funds gives $3,980 in net donations. The event's separate $100 surplus brings the combined charity benefit to $4,080 only if that surplus is actually due and transferred as agreed.

If the $200 offline amount is merely reported by participants and hasn't been received, show it as outstanding instead. The verified net donations are then $3,780, with $200 awaiting confirmation. That distinction is useful to the charity's finance team and fair to supporters who expect an announced result to mean something specific.

Use transaction identifiers to find duplicates. The same gift may appear in a participant report, team export and campaign statement. Match records to their original transaction instead of treating each export row as fresh money. Keep a documented adjustment when you correct a duplicate so another person can follow the calculation.

Check the cash timing too. The service may show completed gifts before the charity receives a transfer. Report what the displayed total represents and confirm the actual settlement separately. If an amount remains disputed or subject to a refund, explain that the result is provisional and name the next reporting date.

Participants deserve an understandable close. Thank them for the work they did, tell them the approved result and explain whether their pages remain available. Supply a short final update they can share. It should distinguish the campaign's total from an individual's result and avoid claiming impact the charity hasn't yet delivered.

For the next event, review the effort as well as the amount. Count how many people were invited, created pages and chose to share them, using records you can substantiate. Ask where they needed help, what donors misunderstood and whether the charity wants to repeat the arrangement. Those observations are more useful than assuming every ticket buyer will fundraise next time.

Before opening another campaign, correct the setup problems and agree the support budget. Confirm the beneficiary, payment route, participant wording and report again. Then invite the next group with a process you can explain clearly to someone buying a ticket, someone raising money and someone deciding whether to donate.