Selling event tickets with Tickera and building your pages with Elementor? With Restrict for Elementor you can show Elementor content to Tickera users only — or hide it from them — based on the tickets they have purchased. Tickera is the event ticketing system that makes it easy to sell tickets on your own website, and Restrict for Elementor integrates with it so you can use Tickera-specific criteria to control the visibility of any Elementor section, column or widget. Both plugins are made by the same team, so the integration works seamlessly.
What you need before you start
- The Tickera plugin installed and activated — the Tickera criteria only become available when Tickera is active on your website.
- Restrict for Elementor installed and activated. If you are just getting started, the quickstart guide covers the setup basics.
- Elementor page builder, because all restrictions are applied from within the Elementor editor.
How to show Elementor content to Tickera users
- Edit your page with Elementor and add or select a section, column or widget.
- In the Content area of that element, select Tickera Users as the restriction criteria.
- A new dropdown menu labeled Who will appear with three options that define which ticket buyers the rule applies to.
- Choose the option that fits your scenario (all three are explained below) and save the page.
The three Tickera visibility conditions
Purchased any ticket
This condition shows or hides the content to users who purchased any Tickera ticket on your website. For example, if you want to thank your customers for buying tickets, you can create a text widget saying Thanks for choosing our event! and show it to ticket buyers only. Or reverse the logic: create a widget that showcases your events, but hide it from customers who have already purchased any of the tickets.
Purchased a specific ticket type
When this option is selected, another field appears where you pick exactly which ticket type should serve as the criterion for showing or hiding the content. You can also select multiple ticket types, in which case the same restriction applies to users who purchased any of the selected types. This is useful if, for example, you want to offer a discount code for another ticket: create a text widget containing the code and display it only to customers who purchased a specific ticket type.
Purchased a ticket for specific event
With this option, another field appears allowing you to select the event for which a customer must have purchased a ticket in order for the content to be shown or hidden. You can select multiple events here as well — the restriction then applies to users who purchased tickets for any of the selected events.
This comes in handy when you want to pitch an early bird ticket for your next event. Create a section containing Tickera’s add-to-cart button that adds the early bird ticket to the cart, and display that section only to users who already purchased a ticket for your current event.
Ideas for using the Tickera conditions
Because the visibility rule is set per element, you can combine several restricted sections, columns and widgets on a single page — each with its own Tickera criterion. A few practical ways event organizers use this:
- Attendee-only information — show practical details meant for confirmed attendees only to visitors who purchased a ticket for that event.
- Upsells between ticket tiers — display an upgrade offer only to buyers of a standard ticket type.
- Early bird promotion — pitch next year’s early bird ticket to people who attended this year, as described above.
- Cleaner marketing — hide event promotion widgets from people who already bought a ticket, so they see a thank-you message instead.
Show alternative content to everyone else
If you choose not to show the content to visitors who don’t meet one of these criteria, you can serve them alternative content instead — for example, an invitation to buy a ticket. You will find the full walkthrough in the displaying alternative content guide.