Track what platforms your applicants are using to submit their applications by creating a custom field to store their application type. You can use this data point in tandem with other data, such as Origin Sources, to identify subsets of applicants by application type, such as stealth applicants.
Creating a field for application sources
To create a custom field to track application source:
Go to Database → Prompts.
Select Insert.
Configure the following settings:
Key: Give this a computer-friendly name (all lowercase, no spaces), like
app_source.Value: Enter one of your application sources. For example, Imported Application, Application Creation Form, or Standard Slate Application.
Select Save.
Repeat the previous two steps until you've created a prompt in your chosen key for each of your application sources.
Go to Database, then select Fields. (Alternatively, follow the link in the right sidebar of the Prompts tool for Fields.)
Select New Field. Configure the following settings:
Scope: Application
Name: Application Source
Field Type: Multiple Values
Prompt: Select the prompt key you created in Step 2 (e.g.
app_source)
Select Save.
Relating the field to applications
To use the field you’ve just created, relate it and the appropriate prompt value to each of your application types:
For imported applications, use a static mapping to set the field and prompt values.
For applications created using the Slate application or an application creation form, use a hidden field or a rule.
Example: Tracking stealth applicants by application type
A stealth applicant is one that enters your admission funnel for the first time via an application, as opposed to other recruitment efforts. To track stealth applicants by their application type:
If you haven’t already, configure the Origin Source for Application Creation.
Create a query on the Person base.
Add the filter Origin Source, Source Type: "Application Creation".
Add the filter Application Type with your desired types selected.
Slate calculates Origin Sources overnight in production environments for person records updated within the past 48 hours. Origin Source calculations do not run in test environments. To include an older person record in the next calculation, the person record must be updated. Changing an Origin Source configuration does not recalculate all older records.