Restrict for WordPress ships with a seamless Tickera integration, giving you Tickera content restriction across your entire website. If you sell event tickets with Tickera, you can make pages, posts, parts of content, categories, widgets and menu items visible only to attendees who purchased a ticket – any ticket, a ticket for a specific event, or a specific ticket type. By the end of this guide you will know how to configure every one of these options.
Before you start: enable Force Login in Tickera
For the integration to work, visitors must purchase their tickets as registered, logged-in users. If a customer buys a ticket while logged out, your website has no way to identify them later and check whether they meet the Tickera criteria you selected for your restricted content.
To make login mandatory:
- Go to Tickera Settings -> General tab.
- Check the option named Force Login.
This step is mandatory – without it, ticket buyers cannot be matched to user accounts and Tickera-based restrictions cannot be verified.
With Tickera and Restrict both installed, you can use Tickera-related criteria pretty much everywhere. Let us go through each area.
Custom messages for Tickera content restriction
When Tickera is installed and activated, an additional tab named Tickera appears within the Restrict settings.
Here you can enter the custom messages shown to users who try to access content restricted by Tickera criteria they do not meet:
- Any ticket type – shown to a user who has not purchased any Tickera ticket but is trying to access content that requires one.
- Specific ticket type – shown to a user who has not purchased the required ticket type. You can use the
[rsc_tc_ticket_type]placeholder to display the title of the required ticket type within the message. - Specific event – shown to a visitor who has not purchased a ticket for the required event. Use the
[rsc_tc_event]placeholder to display the event title, or[rsc_tc_event_links]to display the event title as a link leading straight to the event page where the visitor can buy the required ticket.
A helpful message with a purchase link turns every blocked page view into a chance to sell another ticket, so it is well worth taking a few minutes to customize these.
Restrict a whole page or post
When restricting the content of an entire page or post, the Content Available To dropdown menu now includes an item named Tickera Users.
Selecting it reveals three options:
- Any ticket type – makes the content available to any user who purchased any ticket.
- Any ticket type for a specific event – the content is available to users who purchased any ticket type for the selected event (you choose which event exactly).
- Specific ticket type – you select the exact ticket type a user must have purchased to access the content of this page or post.
This is perfect for attendee-only material: session recordings, speaker slides, workshop downloads, venue details or a live stream page that only ticket holders should see.
Restrict part of the content with shortcodes
If Tickera is installed and activated, you will find additional Tickera-related options within the Shortcodes area of Restrict.
In this area you select Tickera criteria – any ticket type, a ticket for a specific event, or a specific ticket type – and Restrict generates a shortcode you can wrap around any part of a page or post, as described in the shortcodes documentation. That way, part of the page stays public (for example, the event description) while the rest is reserved for ticket holders.
You can also add a custom message using the protected_message argument as part of the shortcode. For example:
[rsc_restrict_content allowed_to=”tickera” tickera_options=”anything” protected_message=”YOUR MESSAGE HERE”]Your content here[/rsc_restrict_content]Restrict post categories
Similarly to restricting a page or post, when creating a new category or editing an existing one, you can select Tickera Users and restrict a whole category using Tickera criteria:
Every post in the category inherits the rule automatically, which is handy when you publish a series of attendee-only posts – announcements, recaps or session materials – and do not want to configure each post separately. See the category restriction guide for details.
Restrict widgets
If you want a widget to be visible only to certain Tickera users, select Tickera Users from the dropdown menu when creating or editing the widget:
This option is available for every widget in every widget area, so you can control exactly which ticket holders see which widget.
Restrict menu items
You can restrict each menu item as well. When adding or editing a menu item, select Tickera Users from the dropdown menu and then choose the Tickera criteria required for the menu item to be displayed.
Visitors without the required ticket simply never see the link, keeping your navigation clean and avoiding frustrating dead ends.
Good to know
Restrict is made by the same team that builds Tickera, so the two plugins are designed to work together. If you also sell physical or digital products, note that Restrict offers the same kind of integration for WooCommerce and Easy Digital Downloads. The Tickera integration is part of Restrict for WordPress – check plans and pricing for 1-site, 5-site and unlimited licenses, available yearly or as a one-time lifetime purchase.