Skip to content

Plan gate

By the Eventrise team

Last verified

A plan gate is a feature that exists on a software platform but costs a higher-priced plan or a paid add-on to use. On an event ticketing platform the gated feature might be email tools, removing the platform's branding, or API access. You see the feature in the demo. You meet the gate when you try to turn it on.

Also called: feature gating, paywalled feature

How does a plan gate work?

Software sold in tiers puts each feature on a plan. The lowest plan sells tickets. Other features sit on the plans above it, or are sold one at a time as add-ons, each with its own price.

Tiered pricing is a normal way to sell software, and a plan gate is not a trick. It becomes a problem when the feature you need is the one behind the gate, and you find out after the season is on sale and switching is hard.

The cost of a gate is the plan price, not the feature. If one feature you need sits on the top plan, you pay for every other feature on that plan too.

What should organizers know about plan gates?

Ask for the feature list of the plan you would be on, not the top one. Then name the features you will use and get the answers in writing: the seat map, an embedded checkout on your own site, the attendee export, the API, and who answers on show night.

Check the attendee export first. Your first-party data behind a gate makes it harder to leave.

Then compare a full season, not a month: the plan price plus the per-ticket platform fee at your real ticket count.

Plan gates on Eventrise

Eventrise charges a 5% platform fee plus Stripe processing at cost (2.9% + $0.30). Fees are added at checkout by default, so you keep 100% of the ticket price. Reserved seating adds $1 per seated ticket, shown to the buyer at checkout. Email and SMS marketing, in early access, will be a paid add-on. Everything else is included.

How to choose an event ticketing platform for venues, theaters, festivals, and conferences

  • Platform fee

    What a ticketing platform charges, and keeps, for selling tickets through its software: a percentage, a flat amount per ticket, or both.

  • Embedded checkout

    An embedded checkout is a ticket checkout that runs inside your own website, inline or in a popup, so buyers never leave your page.

  • First-party data

    First-party data is information a business collects directly from its own customers; for an organizer, the attendee list from ticket sales.

  • Merchant of record

    The merchant of record is the business that takes a customer's payment and is responsible for it, including refunds and chargebacks.

Run your next event on Eventrise