Recruitment Engine User Data Dictionary
Collected for all users
| Data Fields |
Definitions |
| id |
unique id that identifies the record |
| email |
email address of the user |
| address |
residential address that the user entered |
| created_at |
date and time of the user's visit in UTC |
Collected for users who select "I want to run"
| Data Fields |
Definitions |
| phone |
phone number entered by the user |
| first_name |
first name entered by the user |
| last_name |
last name entered by the user |
| position_id |
BallotReady database id that identifies the position a user was looking at when they selected "I want to run." |
| wants_to_ run_for |
position user enders in the free-form box |
| your_story |
free form content from the user |
| custom_q_ answers |
contains the answers to each custom question included in the "I want to run" form, in the order they appear on the form. |
UTM codes
| Data Fields |
Definitions |
| utm_source |
Identify the advertiser, site, publication, etc. that is sending traffic to your property. |
| utm_medium |
The advertising or marketing medium that is sending traffic to your property. |
| utm_campaign |
The individual campaign name, slogan, promo code, etc. for a product. |
| utm_content |
Used to differentiate similar content or links within the same ad. For example, if you have two call-to-action links within the same email message, you can use utm_content and set different values for each so you can tell which version is more effective. |
| utm_term |
Identify paid search keywords. If you're manually tagging paid keyword campaigns, you should also use utm_term to specify the keyword. |
Check out our article about setting up UTM codes for more information.
For more information about our Recruitment Engine, reach out to your Customer Success Lead.
