Peer-to-Peer Pledge Rules
Per-Unit Pledges, Caps, and Deferred Billing
Campaign Pledge Rules control how supporters make activity-based pledges and whether they provide a card when pledging. Configure these rules before inviting supporters to pledge, and explain how your organization will finalize activity totals and collect payments.
Before you begin
For activity-based fundraising, enable Peer-to-Peer activity tracking on the parent campaign and configure the activity types and units participants will use, such as miles, laps, or minutes.
The activity unit determines how a per-unit pledge is calculated. Review your setup before collecting pledges to help prevent incorrect totals.
Where to configure pledge rules
Open the parent campaign's dashboard and locate Campaign Pledge Rules in its Peer-to-Peer settings.
To update pledge rules:
-
Open the campaign’s Event Dashboard
-
Go to Peer-to-Peer Settings
-
Select Campaign Pledge Rules
-
Adjust the options described below
-
Click Save
Per-unit pledges
A per-unit pledge ties the supporter's donation to a participant's recorded activity.
For example, if a supporter pledges $5 per mile and the participant completes 10 miles, the calculated pledge is $50, before any applicable cap.
Enable per-unit pledges if you want supporters to give based on activity. Make sure the activity type and unit match what participants will record.
How is a flat-amount pledge different?
A flat-amount pledge stays the same regardless of activity. For example, a $50 flat pledge remains $50 whether the participant completes 2 miles or 20 miles.
For more details, see Peer-to-Peer Activity Tracking Pledges: Per-Unit vs. Flat Amount.
Pledge caps
When pledge caps are enable, supporters can set a maximum total for a per-unit pledge
For example
-
Pledge: $5 per mile
-
Maximum cap: $100
-
Activity completed: 30 miles
The activity-based calculation is $150, but the pledge is limited to $100.
Caps help supporters understand and control their commitment. Preview the pledge form to confirm the cap option is available when you intend to offer it.
Deferred billing and cards on file
Deferred billing lets supporters pledge before payment is collected. This is useful for per-unit pledges because the final amount depends on the activity completed.
The published pledge rules describe three options:
Optional card on file:
Supporters can choose whether to provide a card when they pledge. Plan how your team will collect payment from supporters who do not leave a card on file.
Card Required:
Supporters must provide a card to submit a pledge. A saved card provides a way to collect payment later; review the applicable collection workflow and activity totals before charging.
No card on file:
Supporters do not provide a card when pledging. Your organization will need to arrange payment collection separately, such as sending a checkout link after reviewing the final pledge total.
Finalize activity and collect payments
Review participant activity before collecting payment. Missing or duplicate logs and incorrect units can affect per-unit pledge totals.
The published collection guide describes adding selected pledge to guest carts, then either sending payment instructions or using the available checkout options for cards on file. Recording a pledge and collecting its payment are separate steps.
For the collection workflow, see How to Collect Payment for Peer-to-Peer Pledges.
Check the supporter experience before launch
Preview the pledge experience and confirm:
- The displayed activity unit is correct.
- Supporters see the intended pledge options.
- The maximum cap option appears when enabled.
- Card requirements match your selected billing option.
- Your campaign explains when totals will be finalized and how payment will be collected.
If supporters can select multiple participants, also confirm how the amount and cap apply before describing the total commitment to them.
Need additional help?
We're here to help. Contact support@betterunite.com if you need assistance configuring pledge rules or collecting pledge payments.