Guides
Set up a ticketed event#
A ticketed event is a Campaign with its subtype set to Event Fundraiser — built through the Fundraisers console wizard, not the standard "New Campaign" button. This walks through creating one, adding ticket tiers, and publishing.
This assumes the package is installed, a Payment Account is connected, and you have the
Fundraising_Admin permission set. See Installation and
Connecting Stripe if you haven't done those yet. It
also assumes your Experience Cloud Donate page is already built — event registration renders
on that same page, so there's nothing extra to build in Experience Builder for the ticket
sale itself. See Set up your Experience Cloud site.
1. Start the wizard#
Open the Pledgivo app → Fundraisers tab. Click New to launch the creation wizard, and on the Type & basics step choose Event Fundraiser as the campaign subtype. Choosing this adds an extra Tickets step to the wizard, between Options and Publish — every other subtype skips it.
There's no separate Campaign Record Type for events
Every campaign — donation appeal or ticketed event — shares the one packaged Fundraising
record type. What actually switches an event's behavior on is the Campaign Subtype
picklist, which is why events are built through this wizard rather than the standard
Salesforce "New Campaign" flow.
2. Add venue and capacity details#
Still in the wizard, fill in the event's venue (name, address, city/state/country, timezone) and choose a Capacity Mode:
| Mode | What it caps |
|---|---|
| Unlimited (default) | No cap at all |
| Per Tier | Each ticket tier's own Capacity__c |
| Event Total | A single headcount across all tiers (Event Capacity) |
| Both | Per-tier caps and an overall event-total cap |
Optionally turn on Allow Donation Add-on if you want to offer an extra donation at checkout on top of the ticket price.
Set Event Capacity above what the tiers have already sold
On Event Total or Both, the cap is compared against the campaign's Tickets Sold roll-up. A cap lower than that number closes registration on the spot — the public page shows the sold-out notice instead of the ticket list, even though each tier still has stock of its own. See When the seats run out for exactly what a buyer sees as an event fills up.
3. Add ticket tiers#
On the Tickets step, add one row per tier — General Admission, VIP, Table of 8, and so on. The wizard seeds one empty tier to start from. You can't advance past this step until at least one tier has both a name and a price.
For each tier, set:
| Field | Notes |
|---|---|
| Name | Shown to the public as the tier label |
| Price | Per-ticket price |
| Capacity | Leave blank for unlimited; only enforced when the campaign's Capacity Mode is Per Tier or Both |
| Sale start / end | Leave blank for no time bound — useful for early-bird pricing or a cutoff before the event date |
| Attendees per ticket | 1 by default; set higher for tickets that seat a group (a table of 8 creates 8 attendee records per ticket sold) |
| Deductible amount | Either a flat Fair Market Value (the non-deductible portion, e.g. the cost of a included meal) or a percentage — which one applies is set org-wide in Settings, see below. The tier editor labels whichever one your org uses and greys the hint on the other; in Percentage mode the Deductible % is required and the tier will not save without it (enter 0 if none of the price is deductible) |
| What's included | A line or two of what the buyer gets, shown under the tier name on the public page ("Two premium seats, sparkling reception, and your names in the programme"). Blank shows nothing |
| Highlight this ticket | Puts a badge on the tier to steer buyers toward it. Switching it on seeds "Most popular" — replace it with anything that fits ("Best value", "Table of 10"). Only one tier per event can be highlighted; badging one clears the rest |
| Active | Uncheck to pull a tier from public sale without deleting its sales history |
See What a tier can say for itself for how the description and highlight render on the public page.
4. Finish and publish#
Complete the remaining wizard steps (page design, publish) the same way as any other campaign — see Set up your first campaign for the Page Canvas composer if you're new to it. Publishing an event campaign is what makes its ticket tiers purchasable on the public Donate page; the page itself doesn't need any special component added, since it renders the ticket-selection flow automatically based on the campaign's subtype.
On the design record, Column ratio sets how the ticket page splits between the checkout column and the story column — the same field, and the same three values, a donation page uses. See The column ratio. Leave it alone to inherit the design's proportion; override it on the campaign when one event wants a different split from the appeals sharing its theme.
5. Set org-wide event defaults (optional)#
Settings → General → Events controls two org-wide behaviors:
| Setting | Effect |
|---|---|
| Deductible Amount Mode | Fair Market Value (default) or Percentage — which of the two per-tier deductible fields (above) is used to calculate the tax-deductible portion of every ticket sold, org-wide |
Switching to Percentage after tiers already exist
Ticket types created before the switch keep whatever they had, and the deductible percentage was optional then. Any tier still missing a percentage records its sales as 0% tax-deductible — the whole ticket price non-deductible — and writes a warning to the log each time. That is the deliberate safe direction: a receipt that understates a deduction can be corrected, one that overstates it is a problem for the donor. Open each existing tier and set its Deductible % (0 is a valid answer) before selling under the new mode.
| Sync Campaign Members | When on, each attendee who resolves to a Contact also gets a CampaignMember record on the event Campaign |
No seat-hold setting to configure
Seat reservation (holding a seat for the ~30 minutes a checkout is in progress, then releasing it if abandoned) is built-in, fixed behavior — there's nothing to turn on or tune here. See Events & ticketing for how it works.
6. Manage tickets and check-in after publishing#
Open the event from the Fundraisers console list to open its detail drawer — two tabs there are event-only (they don't appear on non-event campaigns):
- Tickets — add, edit, or deactivate tiers after launch, same fields as step 3.
- Check-In — a lane board for flipping each attendee's status at the door on event day.
7. Give attendees their tickets#
If you send attendees a link to their tickets (for printing or showing a QR code at the door),
build the Tickets page in Experience Builder with the exact URL tickets — the Donor
Dashboard links here on every event order, so skipping this page or renaming its URL breaks
that link even if you don't otherwise share it directly. See
Set up your Experience Cloud site.
Related#
-
Events & ticketing concept
How seat reservation, refunds, and deductible amounts work under the hood.
-
Set up your first campaign
The Page Canvas composer and publishing flow every campaign shares.
-
Set up your Experience Cloud site
Where the Donate and Tickets pages live.