TutuMargin

How to See Class & Event Registration Revenue From Jotform

Jotform counts registrations, not dollars. Here's how to get total revenue from a class, course, or event signup form — summing the registration-fee field, handling ticket tiers and add-ons, and filtering out unpaid holds and test registrations.

Jotform tells you how many people registered — not how much money you collected. A class, course, or event form counts submissions, so a full session looks the same as an empty one until you add up the fees yourself. To see registration revenue you sum the payment / registration-fee field: the fast manual way is a column sum in Jotform Tables (or a spreadsheet after exporting); the no-spreadsheet way is a tool that reads the fee field and totals it — across ticket tiers and add-ons — for you.

Registration forms have the exact same blind spot as a bakery order form: Jotform is excellent at capturing signups and payments, but it never rolls them into a “total collected” number. Worse, event forms usually mix things that arerevenue (paid tickets, paid add-ons) with things that aren’t (free RSVPs, waitlist holds, comp tickets). Here are the three real ways to get an accurate registration total, from most manual to most automatic.

Method 1 — Sum the fee column in Jotform Tables

If your form collects payment through a payment element or a numeric “Registration Fee” field, Jotform Tables can total it in place:

  1. Open your registration form and go to the Tables view.
  2. Find the column holding the paid amount (your Stripe/PayPal/Square element, a Product List total, or a “Registration Fee” number field).
  3. Filter first — set payment status = Paid (or your order-status field) so unpaid holds and abandoned checkouts drop out.
  4. Click the summary area at the bottom of the fee column and choose Sum. That’s revenue for everything currently visible.

This is the quickest path to one number. Its limit: it’s a single sum. It won’t split revenue by session, by ticket tier, or by add-on, and it can’t compare this event to your last one.

Method 2 — Export and total by tier, session, or add-on

For anything richer than one total, export and use a spreadsheet:

  1. In Jotform, open Submissions (or Tables) and choose Download / Export → Excel (or CSV).
  2. Clean the fee column: strip currency symbols and commas so the cells are plain numbers, and delete rows for test/sandbox registrations and refunded or cancelled signups.
  3. Decide what counts. Exclude free RSVPs and unpaid waitlist holds from a revenue total; keep paid tickets and paid add-ons.
  4. Total it: =SUM(F2:F999) on the fee column for gross revenue.
  5. For the breakdown, insert a PivotTable and drag the session or ticket-type field to rows and the fee total to values. If add-ons (materials fee, meal, workshop) are separate line items, pivot those too so you can see which add-ons actually sell.

The tricky part is multiple ticket tiers. If early-bird, general, and VIP each ran through the payment element, the paid amount already encodes the tier and your SUM is correct. If the tier was just a dropdown choice with no price attached, you’ll have to map each choice to its price and multiply by its count — error-prone, and the reason a single numeric payment field is worth building in from the start.

Method 3 — Skip the export entirely

If you run events regularly and rebuild that pivot every time, the point of a tool like TutuMarginis to remove the chore. It reads your Jotform registrations (read-only), detects the payment field, and shows total revenue, average ticket value, revenue by session, and top add-ons the moment your form connects — no CSV, no pivot. You can also just ask in plain English (“revenue by session”) and get the chart. It’s a new tool, so the honest framing is: it does the summing and grouping you’d otherwise do by hand, and your registration rows stay in your browser.

See it on live sample data ▸

Getting an accurate registration total — the gotchas

  • Separate paid from free. Free RSVPs and comp tickets are real registrations but zero revenue. Count them for headcount, not for money.
  • Exclude unpaid holds.“Reserve my spot” submissions that never completed payment inflate a naive total.
  • Remove test registrations. The signups you made while building and testing the form will otherwise pad the number.
  • Subtract refunds and cancellations.A cancelled attendee is still a row in your export; the refunded fee isn’t revenue.
  • Mind add-ons and bundles.If one registration includes a ticket plus a materials fee, the row total is the combined amount — splitting ticket vs. add-on revenue needs the line items, not just the order sum.

Bottom line:for a single “how much did we collect” number, Jotform Tables’ column sum on paid registrations is enough. For revenue by session, by tier, and by add-on — especially across recurring events — a purpose-built reader is faster and harder to get wrong. Related: the same three methods for a general order form and tracking event signups over time by date and session. If you also collect membership dues or donations through Jotform, see tracking membership dues & recurring payments.

Frequently asked questions

Does Jotform show total registration revenue?

No. Jotform's Submissions page and Jotform Tables show a registration count and list each signup as a row, but there is no built-in 'total collected' figure. To get registration revenue you sum the payment or registration-fee field yourself — in Jotform Tables' column summary or a spreadsheet — or use a tool that reads that field and totals it for you.

How do I total revenue when I have multiple ticket tiers?

If each tier (early-bird, general, VIP) is priced through one Product List or payment element, the paid amount per registration already reflects the tier, so summing the payment column gives correct revenue. If tiers are separate radio/dropdown choices with no payment field, you have to map each choice to its price in a spreadsheet (a lookup or a pivot by tier) and multiply by the count — which is why a single numeric payment field is worth setting up.

How do I stop unpaid holds and test registrations from inflating the number?

Filter to completed payments before you total. In Jotform Tables, filter by payment status = Paid (or your order-status field), and delete or exclude any test/sandbox registrations you made while building the form. Free RSVPs and 'reserve my spot' holds with no payment should be excluded from a revenue total even though they are real registrations.

Can I break registration revenue down by session or by add-on?

Not from the submissions page alone. Export with the session field and any add-on line items, then build a pivot table grouping the payment total by session or by add-on — or use a reader tool that detects those fields and charts revenue by session and by product automatically.