Let us first provide a quick overview of how RSVPify works with multiple events and explain the difference between the ‘Primary Event’ vs. Secondary Events:

Primary Events vs. Secondary Events:

The Primary Event is the ‘event’ to which ALL of your guests are invited whereas Secondary Events are sub-events associated with the Primary Event. Secondary Events can be viewable to all guests/registrants or they can be set up to be invite-only – i.e. hosts can pre-determine which invitees on their invite list can are eligible to see (& RSVP/register!) for an invite-only Secondary Event. This article is going to provide an overview of how to set up an invite-only secondary event using the system’s tagging feature!

Step 1: Set up (likely import) your list of invited guests.

See HERE for a detailed guide for key considerations when importing your invite list. One of the key fields in the import file is the Tag(s) column. Tags are used to power a number of very important (and advanced!) functionality in the platform. For those hosting an invite-only secondary event, we recommend adding a custom tag for that event. For instance, if you were hosting a custom welcome event for guests or colleagues from traveling out town, you could add a custom tag such as “out of towner”. Note that the tag should be added to each invited guest to which it applies (i.e. all guests in a single Party should have the tag in their respective row!). Tags can be used for a myriad of other things but the focus of this support article is invite-only Secondary Events.

Tags can be added even after importing your invite list. See HERE.

Step 2: Set up your Invite-Only Secondary Events in the Form Builder

Drag a Secondary Event block to the main part of the form (in the desired location of the registration process). You will be prompted to add a number of details. One key / important setting is to let the system know that this Secondary Event should only be viewable to guests with a specific tag. See below:

Step 3: Test it out!

As always, we recommend testing out the end-to-end experience so 1) that you can be sure everything is working as desired and 2) there are no surprises!

Did this answer your question?