Module: Highest level hierarchical divider of the HubSpot toolkit (e.g. Marketing, Automation, Contacts, etc.)
Property / Field: A single data-point contained HubSpot-wide on a record (e.g. "Phone Number", "Email Address", etc.)
Contact: A HubSpot record for a human. A lot like a person's Facebook profile
Company: A HubSpot record for an organisation. A lot like an organisation's Facebook page
Workflow: A series of sequential actions automated through HubSpot
Pipeline: A progressive process divided into mutually exclusive and collectively exhaustive steps in the HubSpot sales module (e.g. Recruitment)
Active & Static List: Collections of contacts curated into a list based on meeting a custom set of criteria. Static lists remain as is from the time of their creation; i.e. new contacts that meet the criteria will not be added, nor will contacts on the list be removed if they cease to meet the criteria. Active lists automatically maintain a current version of the contacts that meet criteria, including those that newly satisfy them and excluding those that fall out of satisfying them
API: Application Programming Interface - the fancy way of saying "communication gateway" when talking about to tech platforms. In our context, the API refers to the data bridge between the Wavumbuzi Platform and HubSpot, enabling them to share a single version of live user data at all times
School Join Request: When a student registers for Wavumbuzi and selects a school under which they'd like to participate, this creates a request for a verified teacher at that school to confirm that the student is in fact registered at their school.
Merge fields / Personalisation Token: HubSpot emails enable you to include recipient-specific details in email copy such that an email can be sent to hundreds or thousands of people at once, but still be addressed to them and their unique context. These are based on HubSpot properties