🔒 These fields control capacity, waitlisting, Mailchimp tagging, and spreadsheet routing.
These fields are not visible to someone filling out the form.
The ‘hike_id’ field is obtained from the URL for the web page where this form is embedded. DO NOT LEAVE BLANK. WHEN THIS FORM WRITES A RECROD, IT NEEDS TO PASS ALONG THE HIKE ID.
Fill in the maximum number of participants/hikers (not including any guides) for this hike. This should be an integer value. DO NOT LEAVE BLANK. [ NOTE: THIS FIELD WILL EVENTUALLY GO AWAY AS IT REALLY DOESN’T BELONG IN A REGISTRATION RECORD. ]
The Registration Status field is calculated and filled in prior to form submission.. YOU DO NOT NEED TO TOUCH THAT. It will be filled in with either ‘confirmed’ or ‘waitlisted’ depending on the size of the party and the remaining number of available hiker slots.
The Party Size field is calculated, so you should not touch that. It is always the number of additional adults + number of minors + 1.
Anyone filling out this form will automatically have a contact record created or updated in MailChimp. Follow-up communications are managed in MailChimp. They will be implicitly subscribed to Pelham Pathways newsletters. As they are signing up for a guided hike, the ‘mc_interest_CTC’ field is used to indicate that they have an ‘interest’ in the Community Trails Coalition newsletter. The contact can always update their newsletter interests or unsubscribe at any time.
Beyond setting the CTC ‘interest’ for this contact, their MailChimp record will also have tags added to associate them with this hike and to denote their registration status.
Finally note that the true ‘system of record’ for hike registrations is the ‘raw’ hike spreadsheet tab for this hike.
