Organizations can now have more control over the VAN Source Codes they want to apply to the VAN events created by Mobilize, so that when new supporters sign up on Mobilize they get a relevant source code applied as their Origin Source Code.
By setting more granular Source Codes at the event type or event level, users of the VAN & Mobilize integration get a much more granular understanding of which activities are driving new supporter acquisition.
How Source Codes Sync to VAN
When a Source Code is synced, Mobilize first checks VAN for a source code with an exact, case-sensitive name match in the committee.
If a match is found, Mobilize reuses the existing source code rather than creating a duplicate.
If no match is found, Mobilize creates a new source code in VAN.
Set default Source Codes by Event Type
In Mobilize VAN Settings, Admin users can specify a default Source Code for each Mobilize event type:
Set Source Codes for Promoted events
For promoted events, Admin users can choose whether to use the pre-June 2024 default of the owning organization name as the Source Code OR whether to specify a Source Code for each promoted event type:
Set Source Code for One Event
Admins can set a specific VAN Event Source Code by selecting Customize VAN settings for this event only in the VAN sync section of the event form. If the Source Code is specified at the event level, this takes precedence over the Source Code specified in the VAN Settings page for that Event Type.
In Case of Change or Deletion
If a user changes or deletes the Event Source Code from the event in VAN, Mobilize will not override that change when the Event is next synced/updated by Mobilize (i.e., the Source Code will remain whatever the user chose in VAN).