What is Event Ticketing?
Event Ticketing is a functionality that allows you to offer ticket sales or seat reservations for any type of event directly from your store campaigns or lead landing pages, in a simple, secure and integrated way with the platform. You won't need external tools to manage capacity or attendee registration.
This functionality is available in Settings → Event Ticketing within store campaigns and lead landing pages.
Key concepts: event and session
Event: the event itself: a charity gala, an open house day, a medical conference. Everything that happens under the same name and date. On the platform, it groups all the information about the event: name, organizer, location, date and total capacity. An event can have one or more sessions.
Session: each different access or modality within that event. For example: morning shift and afternoon shift for a day, general entry and VIP entry for a gala, or day 1 and day 2 of a conference. Each session will have its own price, schedule and/or ticket stock.
What type of campaign do you need?
Before you start, choose the campaign type based on your event's characteristics:
Feature | Store Campaign | Lead Landing Page |
Event type | Paid events/with donation | Free events/without donation with access control |
Number of sessions | Multiple sessions | Single session only |
Session actions | Translate, duplicate, reserve tickets, release tickets, delete | Translate only |
Ticket email configuration | Yes | Yes |
Mobile app QR validation | Yes | Yes |
Use a store campaign if... your event is paid or has an associated donation. It allows you to manage multiple sessions or time slots, associate rewards with stock and charge for tickets directly from the platform.
Use a lead landing page if... your event is free/without associated donation, but needs access control: attendee registration, QR ticket delivery and door validation, with a single session.
Ticketing in E-commerce Campaigns
Ticketing in store campaigns allows you to create multiple sessions for paid events and associate rewards with stock as event sessions.
Step 1 – Create the event
Go to Settings → Event Ticketing and create a new event. In the Event Data tab, complete the following fields in your campaign's base language and other languages if applicable:
Event name
Organizer name
Maximum capacity (capacity)
Event start and end date
Venue (location)
Event description
Step 2 – Create or configure sessions
In the Event Sessions tab you can add sessions in three ways:
Creating an event session directly from this tab: Add Session to event.
Creating a session to sell packs of tickets (a table, a box, a family pack): Add session with packs.
Associating an existing reward to the session: Create Session from Reward.
Add Session to event (recommended approach in most cases)
The recommended way is to create sessions directly from Event Sessions, using the Add Session to event button.
To create the session, you must specify:
Session name (maximum 100 characters)
Start date and time, and end date and time
Number of tickets (❗Important: it cannot be increased once the session is created; you can only reduce it with the Release tickets option)
Price and donation amount
Description (maximum 500 characters)
In the Presale Configuration block: the sale start date, and Waiting Days and Duration Days (if applicable)
Add discount (coupon) field to reward (if applicable), a checkbox just above the Other settings drop-down: it adds a detail called DESCUENTO to the e-commerce item, so that buyers or donors can enter a discount code. It only works if StockCrowd sets up and validates the code first: if you want to use it, write to us at [email protected] and we will set up the discount for you.
In the Other settings drop-down:
Call to Action button text: the text of the session button that the buyer sees. By default it shows "View details".
Call to action URL (if applicable): the page that button leads to. If you leave it empty, the button takes the buyer to the e-commerce item to add it to the cart; if you enter a URL, the button takes them to that page.
Session location
Make this a featured product
Hide number of available units
Hide requested
Hide from landing and shopping cart
Image associated with the session
ℹ️ When you create sessions from this tab, corresponding e-commerce items are automatically generated in Content → E-commerce items, as these sections are connected.
⚠️ Free sessions (cost 0) in e-commerce: It is not possible to create sessions with cost 0 (free) for e-commerce campaigns. If you create a session with price 0, the system will accept it, but in the landing and for the donor/buyer it will show a cost of 0.01 €. If you need to offer free sessions, see the "Free events in e-commerce campaigns" section below.
Add session with packs: selling ticket packs
A session with packs lets you sell packs of tickets instead of individual tickets: a table at a gala dinner, a box, a family pack. You create it from the event's Sessions tab, using the Add session with packs button.
This is how a session with packs works:
You decide how many packs you sell (Number of packs) and how many tickets each one includes (Tickets per pack). For example, 10 packs of 8 tickets are 10 tables of 8 seats: 80 tickets in total.
The donor buys the whole pack and receives all of its tickets, each with its own QR code, to share among their guests.
The price you enter is the price of the whole pack, and it is split across its tickets: a pack of 8 tickets at €400 shows €50 on each ticket.
The amount to donate is also set per pack.
Stock is counted in packs: each pack bought takes one pack off the available stock, not the number of tickets it contains.
More than one pack can be bought in the same order, as long as packs are still available.
Pack names
By default, each pack is given the session name followed by its number: in a session called "Mesa 1", the packs are called "Mesa 1 1", "Mesa 1 2", and so on. That name appears on every ticket in the pack. When you finish creating the session, the platform suggests renaming the packs. If you prefer to do it later, click the tag icon (Packs) on the session thumbnail: in the Packs window, enter the new name of each pack and click Save. We recommend using a name the donor will recognise, such as "StockCrowd Table" or "StockCrowd Box".
Allocation order
Packs are allocated in order of purchase: the first pack bought is number 1, the second is number 2, and so on. Whoever buys a pack receives all the tickets it includes.
Tracking sales
The session shows how many packs and how many tickets have been sold, for example "2 of 10 packs purchased" and "16 of 80 tickets". In the Packs list, each pack is shown as Available or Sold.
Practical case: a race with a family ticket
Suppose a race where you sell a family ticket for 4 people, with a special price for the family. The family ticket is set up as a session with packs:
Create the session with the Add session with packs button, in the event's Sessions tab.
Tickets per pack: 4. Number of packs: the number of family tickets you want to sell.
The price is the price of the whole family ticket, and it is split across its 4 tickets: a family ticket at €60 shows €15 on each ticket.
Upon completing the purchase, the buyer receives the 4 tickets by email, each with its own QR code, one per person.
Keep in mind, when working with sessions with packs:
When you edit a session with packs, Number of packs and Tickets per pack are visible but cannot be changed.
A session with packs can only be created with the Add session with packs button: it cannot be created from an e-commerce item.
A session with packs does not let you collect data per ticket (each participant's name, bib number, comments): since it is not created from an e-commerce item, it does not support Custom fields. If you need to collect that data, create the session from E-commerce items, without packs (see "When should you create the session from E-commerce items?").
A session with packs cannot share capacity with individual-ticket sessions.
Create Session from Reward
You can also create an e-commerce item first in Content → E-commerce items and then associate it with a session.
However, keep in mind that ⚠️ only rewards with stock can be associated (other reward types cannot be associated), and any option configured in the reward that is not editable from Sessions will be cancelled and/or not editable once associated.
ℹ️ Sessions and e-commerce items are synchronized: creating a session directly from Sessions automatically generates an e-commerce item in Content → E-commerce items. Similarly, deleting a session from here also deletes the associated e-commerce item in that section.
When should you create the session from E-commerce items?
Although direct creation from Sessions is recommended in most cases, there are specific situations where it's best to create the e-commerce item first from Content → E-commerce items and then associate it:
When you need to set a minimum and maximum number of tickets per purchase. From E-commerce items you can define how many minimum and maximum units the donor can add to their cart in a single order. This option is not available when creating the session directly.
When you need to collect additional donor information through Custom fields. This option adds a free text field, list of values, date and/or email to the purchase process when selecting the ticket to add to the cart. It's useful for collecting custom data per ticket. Sessions with packs do not support Custom fields.
ℹ️ To customise the button of a session, you no longer need to create it from E-commerce items. When you create or edit any event session, including sessions with packs, you can change its text (Call to Action button text) and the page it leads to (Call to action URL) in the Other settings drop-down. By default, the button shows "View details" and takes the buyer to the e-commerce item to add it to the cart.
❗ Remember that when you associate a reward with a session, any option not editable from Sessions will be cancelled and/or not editable. So make sure to have the e-commerce item fully configured before associating it.
Session Editing
Each session is displayed in a block with its date, start and end time, number of tickets purchased and its wait and duration days:
Using the pencil icon you can edit:
Name, start date and time, and end date and time (the date and time cannot be changed while the session shares capacity with other sessions)
Price and donation amount
Description
Session location
Call to Action button text and Call to action URL, in the Other settings drop-down
Start date, Waiting Days and Duration Days, in the Presale Configuration block
Make this a featured product
Hide number of available units
Hide requested
Hide from landing and shopping cart
Image associated with the session
⚠️ The number of tickets in a session cannot be increased once created: it is fixed with the stock configured when the session or the original e-commerce item was created. You can reduce it, by releasing tickets that have not been sold with the Release tickets option. If you need more tickets, the session must be deleted and created again (only possible if no ticket for that session has been purchased yet).
⚠️ In a session with packs, Number of packs and Tickets per pack cannot be changed once the session is created: when you edit it, they are visible but locked. If you made a mistake, the session must be deleted and created again (only possible if no pack has been sold yet).
From each session you also have these additional actions:
Translate – add translations using the corresponding icon.
Duplicate – creates a copy of the session.
Reserve tickets – sets aside tickets for internal use, promotional or as a gift. You can define the ticket type (promo, internal or gift), the price (0 if it's a gift), the beneficiary's name and email. The ticket will be automatically sent to the recipient.
Release tickets – ticket icon with an ✕: removes unsold tickets from the session, and the session's number of tickets goes down by that number. Released tickets are no longer part of the capacity. For example, if you planned 100 tickets and 30 have been sold, 70 are left to sell: if you release 50, the session has 50 tickets (30 sold and 20 left to sell); if you release all 70, it stays at 30, all sold. Only unsold tickets can be released, and the option is not available in sessions that share capacity.
Delete – removes the session from the event (not available once the first ticket is purchased).
Packs – tag icon, only in sessions with packs: opens the list of the session's packs, where you can rename each pack and see whether it is Available or Sold.
Sharing capacity between sessions
The Share capacity option lets several sessions in a store campaign sell against the same limit of places. It works really well for selling the same place with different extras, for example "Single session", "Single session + sandwich" and "Single session and lunch" for the same event. Each unit sold in any session in the group reduces the places available in all of them.
To share capacity, the sessions must have exactly the same start date and time and the same number of tickets. If no sessions meet these requirements, the button to share capacity does not appear.
To create a shared capacity group:
In the event's Sessions tab, click Share capacity.
In the Share capacity between sessions window, choose Create new group.
Enter the Capacity group name, for example "Shared capacity 21/05 10:00". This name helps you identify which sessions share the same capacity.
Select the sessions that will share capacity. The window shows the shared capacity, the units already sold and the units available.
Click Share capacity.
To add a session to a group that already exists, choose Add to an existing group in the same window, select the group and select the session. Each session in the group shows a label with the group name on its thumbnail.
Keep in mind, when sharing capacity:
While a session belongs to a shared capacity group, you cannot change its date or time, because matching start date and time is the requirement for sharing capacity. If you need to change the date or time of a session in the group, first undo the group with the Unlink capacity button.
Tickets cannot be released in sessions that share capacity.
A session with packs cannot share capacity with individual-ticket sessions.
You can also share capacity between sessions created from an e-commerce item.
Unlink capacity
The Unlink capacity button removes the group: the sessions stop sharing availability and each one goes back to managing its own capacity independently. Sales already made are not changed.
Free events in e-commerce campaigns
It is not possible to create sessions with cost 0 in e-commerce campaigns. If you try to create a session with price 0, the system will allow it, but the landing and the donor/buyer will see the price as 0.01 €.
If you need to offer one or more free sessions within an e-commerce campaign, the recommended solution is as follows:
Create a reward with external URL from Content → E-commerce items for each free session. This type of item acts as a CTA that redirects to another URL, with no associated price.
Create a lead landing page with ticketing for each free session. This landing will manage attendee registration, capacity control and QR ticket delivery.
Link each lead landing page in the URL of its external URL item. This way, the donor who clicks on the free item will go directly to the registration landing for that session.
ℹ️ This flow allows you to combine paid sessions (managed as event sessions in e-commerce) with free sessions (managed as independent lead landing pages).
Step 3 – Configure the ticket email
In the Email Format Configuration tab you customize the email that the attendee will receive with their QR ticket:
Sender name and email subject
Confirmation message (show/hide): hides or shows the fixed thank-you text that appears right below the greeting.
General colors and styles
Header text and image (show/hide, image URL, alt text)
ℹ️ Header image requirements
Horizontal format (width greater than height)
Maximum size: 600 × 400 px
Maximum weight: 300 KB
This allows us to generate the ticket faster and with optimal quality for all devices.
Payment summary (show/hide): hides or shows the full block with amount and total paid. Within this block, you can also hide just the discount row.
Zone/Seat and Ticket type (show/hide each box): controls whether these information boxes appear on the attendee's ticket.
Additional footer text (show/hide, additional text and custom CSS styles for the text)
Company information: name and logo (show/hide, logo image URL)
Legal links: privacy policy and terms of service.
You can preview the result at different scales. Remember to save each time you make changes.
Step 4 – Configure the mobile app to validate tickets
Event tickets are validated with an Android phone that acts as a scanner: the phone reads the QR code on each ticket with the Lector QR Stockcrowd app, which opens inside the Expo Go app. In the Mobile App Configuration tab, after generating the access code, you will find the QR code to install the reader on the phone.
❗Important: the Expo Go app has changed its authentication process on iOS devices. The way it works now, allowing that authentication could compromise data security, so we do not allow it: we would rather protect your data and your attendees' data. As a result, scanning the QR codes sent from our platform is no longer available on iOS. We are very sorry for any inconvenience this may cause. Scanning the QR codes sent from our platform is currently only available on Android devices.
How to install the reader, enter the event access code and validate tickets, step by step: How to validate event tickets with the Lector QR Stockcrowd app.
Ticketing in Lead Landing Pages
Setting up ticketing in a lead landing page is the mode for free events or without associated donation that need access control: attendees register, receive their QR ticket by email and their entry is validated on the event day. There is no charge for tickets.
The sections under Event Ticketing in this type of campaign are virtually identical to those in e-commerce campaigns, with one key difference:
👉 In Sessions, for a lead landing page it is only possible to configure a single session. This mode is designed for one-time events with a single time slot.
Also, the capacity is linked to the campaign objective: when you set the maximum capacity in ticketing, the campaign objective in General Data automatically adjusts to that value and cannot be different.
Other differences compared to the e-commerce campaign
Session editing: when editing the session in Settings → Event Ticketing → Sessions you can only modify the name, start date, end date, start time, end time and description.
Available actions for sessions: from the session in Settings → Event Ticketing → Sessions you have the option to translate the session. Unlike sessions in e-commerce campaigns, the actions to duplicate, reserve tickets, or delete session are not available.
The rest of the functionality (event data, email and mobile app) is exactly the same as in the e-commerce campaign.
⚠️ Important: Once a lead campaign is linked to event ticketing, this action cannot be undone.
❓Frequently Asked Questions
What is the difference between using an e-commerce campaign or a lead landing page?
The main difference is the event type: the e-commerce campaign is for paid events/with associated donation and allows multiple sessions. The lead landing page is for free events/without associated donation that need access control via QR ticket, and only allows a single session.
When is it best to create a session from E-commerce items instead of directly from Sessions?
It's best to create the e-commerce item first from Content → E-commerce items when you need to configure options that are not available when creating the session directly:
Define a minimum and/or maximum number of tickets that the donor can add to the cart in a single purchase.
Add Custom fields (text field to collect donor information per ticket: name, bib number, comments, etc.).
In other cases, it is recommended to create the sessions directly from the event's Sessions tab.
How do I sell a table, a box or a pack of tickets for an event?
To sell several tickets together as a single product (a table at a gala dinner, a box, a family pack), create a session with packs from the event's Sessions tab, using the Add session with packs button. You set how many packs you sell and how many tickets each one includes, and the price you enter is the price of the whole pack. The donor buys the whole pack and receives all of its tickets, each with its own QR code.
How do I make several sessions share the same capacity?
Several sessions in a store campaign can sell against the same limit of places with the Share capacity option, as long as they have exactly the same start date and time and the same number of tickets. Each unit sold in any session in the group reduces the places available in all of them. You will find the step-by-step guide in the Sharing capacity between sessions section.
Can I share capacity between a session with packs and an individual-ticket session?
A session with packs cannot share capacity with individual-ticket sessions. Shared capacity only joins sessions of the same type that match in date, start time and number of tickets.
Why can't I change the date or time of a session?
The date and time of a session are locked while the session belongs to a shared capacity group, because matching start date and time is the requirement for sharing capacity. To change them, first undo the group with the Unlink capacity button: the sessions go back to managing their capacity separately, and you can then edit the date and time.
Can I customise the button text of a session?
Yes. When you create or edit any event session, including sessions with packs, you can change the button text in Call to Action button text, inside the Other settings drop-down. By default, the button shows "View details". In the same drop-down, Call to action URL decides where the button leads: if you leave it empty, to the e-commerce item to add it to the cart; if you enter a URL, to that page. You do not need to create the session from E-commerce items.
What is the Release tickets option for?
The Release tickets option, on the ticket icon with an ✕ of each session, is for reducing a session's number of tickets: it removes unsold tickets from the session, and those tickets are no longer part of the capacity. For example, if you planned 100 tickets and 30 have been sold, releasing 50 leaves the session with 50 tickets: 30 sold and 20 left to sell. Only unsold tickets can be released, and the option is not available in sessions that share capacity.
Can I create free sessions (cost 0) in an e-commerce campaign?
Not directly. If you create a session with price 0 from Sessions, the system allows it but will show the cost as 0.01 € in the landing. To offer free sessions in an e-commerce campaign, the recommended approach is:
Create an external URL item (Content → E-commerce items) for each free session.
Create a lead landing page with ticketing to manage registration and QR for that free session.
Link that landing page URL in the external URL item.
Can I undo the ticketing link in a lead landing page?
No. Once you link a lead landing page to event ticketing, the action cannot be undone.
What e-commerce items can I associate with ticketing in an e-commerce campaign?
Only e-commerce items with stock can be associated. Other item types will not appear in the selection list.
Can I edit an e-commerce item after associating it with a session?
Not from Content → E-commerce items. Once associated, the item is frozen and can only be edited from the Sessions tab of the event within Event Ticketing.
What happens if I delete a session from the event?
Deleting a session from the Sessions tab also automatically deletes the associated e-commerce item in Content → E-commerce items. This action cannot be undone.
Can I create a session without first creating an e-commerce item?
Yes, and it's recommended in most cases. You can create sessions directly from the event's Sessions tab. When you do, a corresponding e-commerce item will be automatically generated in Content → E-commerce items.
Can sessions have any date, or must they fall within the event's date range?
The event can be configured with a date range (start date and end date) spanning multiple days. This allows you to create sessions on different days, as long as each session falls within that range.
However, each individual session must have the same start and end date, meaning it must take place within a single day. It is not possible to create a session that spans multiple days.
In short: the event's date range defines the overall period in which sessions can exist, and you decide on which specific day each one is placed.
Can the number of tickets in a session linked to an e-commerce item be modified?
It can only be reduced. The number of tickets is fixed with the stock configured when the session is created and cannot be increased later. You can reduce it by releasing tickets that have not been sold, with the Release tickets option. If you need more tickets, the session must be deleted and created again (only possible if no ticket for that session has been purchased yet). If you can't delete it because tickets have been purchased, you can hide it from the landing (see Session Editing).
How are tickets validated on the event day?
Tickets are validated on the day of the event with the Lector QR Stockcrowd app, on an Android phone: validation with Expo Go does not work on iOS devices (iPhone). Download the Expo Go app from Google Play, scan the QR code in the Mobile App Configuration tab from Expo Go and enter the event's access code. From there you can confirm attendees' QR tickets in real time. You will find the step-by-step guide in How to validate event tickets with the Lector QR Stockcrowd app.
Can I include a row 0 or symbolic donation in an event with ticketing?
Yes, but you don't need to configure it as a session in Event Ticketing. Row 0 doesn't require access control or a ticket, so you can create it directly as an e-commerce item in Content → E-commerce items within your e-commerce campaign, independently from ticketing, without associating it.
What does the maximum capacity indicated in the event data represent?
It depends on the campaign type:
In store campaigns, the capacity set in Event Data does not represent the total combined capacity across all sessions, but rather the maximum capacity allowed per individual session. No session can be configured with more tickets than the number indicated in this field. At this time, the platform does not manage a cumulative global capacity across all sessions, but you can use this field to indicate the overall event capacity as a reference and manage each session's capacity independently and dynamically. If several sessions have the same start date and time and the same number of tickets, you can make them sell against the same limit of places with the Share capacity option (see the Sharing capacity between sessions section).
In lead landing pages with ticketing, the capacity set in Event Data does represent the total event capacity, since this campaign type only supports a single session. Therefore, the number indicated will be the maximum number of tickets that can be acquired for that session/event.
If I turn on ticketing for a campaign that already had registrations or donations, are tickets sent to people who registered earlier?
No: ticket sending isn't retroactive, whether it's a store campaign or a lead landing page. Once you activate ticketing, tickets are only generated and sent for registrations or purchases made from that point onward. Anyone who registered or purchased the reward before activation won't automatically receive their QR ticket.
⚠️ Keep capacity in mind before activating it. Registrations and units purchased before activation already count toward capacity. Adjust capacity before activating ticketing, since the number of tickets for a session can't be increased once it's created.
In store campaigns
If you link a reward to ticketing that already has units purchased, that stock is already used up: before linking it, increase the reward's quantity to cover the tickets already sold plus any you still want to offer. To get the ticket to people who already purchased, they don't need to submit their details again. Use the Reserve tickets option from the session, entering the person's name and email: the ticket will be sent automatically to their inbox.In lead landing pages
Lead landing pages don't have a reserve-tickets option, so anyone who registered before ticketing was activated will need to register again to receive their ticket. Since their earlier registration still counts toward capacity, you have two options:
Delete the old registration for each person who registers again, so only their new, ticketed registration counts.
Increase the maximum capacity in Event Details to absorb those duplicate registrations. Keep in mind that for this campaign type, capacity is linked to the campaign goal, so the goal will adjust automatically to the new value.
If you already know your event will need access control, activate ticketing before publishing the campaign and before you start receiving registrations or sales. That way you avoid having to manage retroactive registrations.
Does Event Ticketing have any extra cost?
Yes. Ticketing applies your plan's standard commission plus a fixed cost per ticket sold. It is billed monthly at month end. For free events (lead landing pages) the cost per registered ticket also applies.
Write to us at [email protected] if you need to know the exact cost associated for your organization.
Need more help? Contact us at [email protected] or via the chat icon 💬 on this page.























