Tracking Registration Sources

If you advertise your volunteer opportunities using different avenues (such as email or social media), or with different organizations (like affiliates or partner organizations), you may want to use registration source tracking. This feature will allow you to view and report on the exact link your volunteers use to register for a specific opportunity. 

To utilize Registration Source Tracking, you will simply add a tag to the end of the registration links you use for different “sources” (e.g. Facebook, Twitter, email, etc.). The system will then use this source tag to track and store information about the link each volunteer used to register for a particular event. You can use as many sources as you need (i.e. 1 for your website, 1 for email, 1 for Facebook, etc.) and you can employ one or multiple words as your source. The source must be less than 15 characters and if it is more than one word, they must be connected using an underscore. 

For information about where to find specific event links, refer to the knowledge base article linked HERE. You can use either the Event ID or Event Registration Code link, in either the short or long version, the tag format is slightly different depending on which version of the link you use. For a long link, you will use the tag, "&source=source_name" at the end of the link. For the short version, you will add a forward slash and the source to the end like this, “/source”.

As an example, if you want to track how many volunteers click on the event link that you plan to share on Facebook, you would want to modify your link to look like something like this:

Long Version: 

https://www.cervistech.com/acts/console.php?console_id=XXXX&console_type=event_list&ht=1&event_id=nnn&source=facebook

Short Version:

http://cerv.is/m?XXXXxnnn/facebook

Please note that these links are purely examples and the variables in both of the links need to be modified for your organization and your event.

For information on how to run reports of this information, see the knowledge base article linked HERE.