Before getting started
Interest Forms, Pledges, Petitions, and Groups versus scheduled events
Interest Forms, Pledges, Petitions, and Groups differ from scheduled events in that they don’t have timeslots. Instead, they have a start and end date, allowing supporters to sign up at any point during that window.
Unlike scheduled events, Interest Forms, Pledges, Petitions, and Groups can sync with only an activist code applied to sign ups. This reduces the amount of events created in VAN, improving data integrity for these long-standing events.
Required VAN configuration
The event types and activist codes may not exist in VAN. You will need to have access to or know who can configure event types, roles, statuses, and activist codes in VAN. You should also familiarize yourself with our VAN integration resources.
Option 1: Configure the Event Type in VAN Settings tab
How the data shows in VAN:
If the Event Type is configured in VAN Settings, the form will always sync as one event in VAN/EA per day that has at least one sign up. It is important to note that if this is a long standing form, there could be many events created over time. Event creators can choose to also add an activist code at the event level to be applied to contact records who sign up for the form.
The sign up will sync to VAN/EA with the attendance status corresponding to ‘Registered’ in Mobilize and any subsequent attendance status changes in Mobilize will sync to VAN/EA. If an activist code was configured in the Custom VAN Settings drop down section, the activist code will be applied to the contact record.
How to configure:
Step 1: Configure the event type, roles and attendance statuses in the VAN Settings tab.
Step 2: Create the new form and Publish.
Optional: Event creator can choose to add a custom 'VAN event name' for the event in the Basic information section or add an activist code for the form in the Custom VAN Settings drop down section.
Option 2: Configure an activist code for the event
How the data shows in VAN:
When the event creator configures an activist code at the event level, sign ups on the form will have an activist code applied to the corresponding contact record in VAN/EA. There will not be an event or participation created in VAN/EA. VAN/EA users can identify sign ups for the form by creating a list for the activist code in VAN/EA.
How to configure:
Step 1: Ensure the activist code is configured in VAN/EA in the integrated committee. Read the FAQ here.
Step 2: Customize VAN Settings (for this event only) and select the activist code you want to the contact record in VAN.
Tips:
To ensure the specific form sign ups can be identified in VAN/EA, use a unique activist code.
Adding a custom 'VAN event name' for the event in the Basic information section will not sync the form as an event in VAN. Only the steps outlined in Option 1 will create events in VAN.
