Introduction
When a candidate creates a candidate job notification and chooses a particular schedule, Evolve Recruitment Marketing (RM) will perform the check on a fixed schedule, depending on the frequency chosen.
Audience
All Users
Schedule
Frequency | Schedule | Note |
Daily | Every day at midnight UTC |
• When creating a New Candidate Job Notification, the initial alert is sent at midnight UTC. • UTC is typically 4 hours later than ET or 7 hours later than PT. For example, midnight UTC = 8 pm ET or 5 pm PT on June 21. This can vary due to daylight savings time and the time of year. • If the month doesn't have a particular day (i.e., 29, 30, 31), the schedule does not run on that day. • Currently, the generation and sending of candidate job notifications is on a fixed schedule. |
Every two days | At 1 am UTC on the 1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29 and 31st of every month | |
Every three days | At 2 am UTC on the 1, 4, 7, 10, 13, 16, 19, 22, 25, 28 and 31st of every month | |
Weekly | At 3 am UTC every Monday | |
Monthly | At 4 am UTC on the 15th of every month |
Candidate Job Notifications FAQ
Q: How does a Candidate Job Notification get created?
A: Prerequisites need to be met first, including:
- Career Site Module On.
- Job Notifications are configured on the Career site.
- Liquid drop on the Job Search results page for Job Notification.
The following are the steps that a candidate would go through:
The candidate performs a search on a career site and then clicks Create a Job Alert based on your Search. NOTE: This phrasing could differ depending on how the text/link/button is configured on your site.
The candidate sees the Create Job Notification popup. The candidate will enter their email address and update the frequency. They can also update the suggested job notification name.
The candidate will complete the reCAPTCHA challenge (if necessary).
The candidate will get confirmation that the notification has been set up.
The candidate will receive a welcome email with details of the job notification, frequency, and a link to see the search results.
Based on the candidate's frequency, Evolve RM will check for new jobs that match the criteria of the job notification. If they match, an email is sent to the candidate.
If the candidate no longer wishes to receive the notification, they have two options to stop the job notification.
- If the Candidate Portal is OFF/not configured, they can click the link in the email to unsubscribe from the specific job notification.
- If the Candidate Portal is ON and Configured, the candidate can go to the company's candidate portal and update their preferences, including the Job Notification section and specific notifications.
Q: What happens to the subscriptions when you turn the toggle off the feature in the Account? What happens when you turn off the feature on a career site?
A: When the feature is turned off at the account level, all currently scheduled job notifications are disabled. No more notifications will be run, and no new emails will be sent. The same is true for turning it off at the career site level - all candidate job notifications created from that career site will be disabled, no new searches will be run, and no new email notifications will be sent.
However, these disabled job notifications have not been deleted. If you turn the feature toggle back on at the account level or the career site level, those notifications will be rescheduled and will start to run in the next regular window.
Q: How can you disable all subscriptions in a test account after testing?
A: If there are multiple career sites, the best option might be to turn off the Account Setting (Admin > Applications > Career Sites > Candidate Job Notifications OFF). If you are testing a specific career site (or a career site upgrade), the best option might be to turn it off at the career site level (Apps > Career Sites > Edit Site Information for the specific career site > Enable Candidate Job Notification OFF)
Q: What happens with bad emails?
A: Bad emails (i.e., the status of dropped, bounced, global unsubscribed) are treated the same way as any other email Evolve RM sends via the Campaign module. It is tracked via the product. You can see the number of emails that bounced or dropped during the reporting period from the Email Activity or Email Pipeline reports. At the time of each subscription run, Evolve RM will attempt to deliver the email. If the email was previously dropped or bounced, then the email will not be delivered again. There is a limitation in that in Source/CRM; a recruiter could search for a candidate who had an invalid email and reset that flag (in the case where the candidate corrected their email account problem). However, since these are only email addresses, this is not currently possible without going through Support and DevOps to correct that specific email address.
Q: What does unsubscribe to a candidate job notification mean to other communications?
A: When Evolve RM sends out communications to emails regarding candidate job notifications, there is a specific unsubscribe link that is only related to the specific candidate job notification. Clicking on the link will disable that specific notification and does not affect that email address for other communications from Evolve RM (i.e. emails from Source/CRM). However, if a candidate does a full unsubscribe from all emails, this will also include job notifications (i.e. they will be dropped/not sent)
Q: If a candidate’s email is unsubscribed in Evolve RM (Campaign, Source/CRM), can they receive candidate job notifications?
A: If a candidate was sent email communications from Evolve RM via Source/CRM and Campaign and chooses to Unsubscribe, the email address is recorded in Campaign in the Unsubscribed list for that specific company. This automatically unsubscribes that email from all previously created job notifications. If the candidate later creates a new job notification using the same email address, that address will be removed from the Unsubscribed list, and the new job notification will now be sent to that email. Previously unsubscribed notifications will not be resumed.
Q: How does the captcha behave differently (different devices, etc.)?
A: Evolve RM candidate job notifications leverage reCaptcha, a Google offering that helps prevent bots and other nefarious means from creating invalid notifications. reCaptcha behavior and design, as well as browser support, is controlled by Google. For more information, please see this link.
reCaptcha browser support is here: https://support.google.com/recaptcha/?hl=en#6223828
reCaptcha FAQ here: https://developers.google.com/recaptcha/docs/faq
With the newer reCaptcha logic, it is not always necessary to prompt the user to confirm they are not a bot because it is leveraging past behavior on that browser/session. If, at some point, there is no browser history, the user will be prompted to complete a simple test. For example:
When a candidate chooses to create a job notification.
The visitor will be prompted for another test if the answer is incorrect.
After the test is completed correctly, the notification will be created, and the Welcome email will be sent to the email address.
Q: What career site search criteria (facets, etc.) can factor into the candidate's job notification?
A: Typically, a candidate job notification can be created based on the search results page of a career site. That means that all of the criteria that they have entered and that are supported by search in career sites are supported. This includes:
- All defined facets (custom fields cfm1-10 defined in the career site sync)
- job_tags_seo
- location_seo
- lat long distance
- All the standard search criteria as defined in confluence (example: q= location= location_city= cf[field_name] if you are doing old-style searches)
Q: Can the visitor change the name of a search?
A: Yes. The search name is generated automatically based on the search criteria (facets, etc.) chosen when making the candidate job notification, but the visitor can change it.
The default naming logic is:
- JOBS matching "keywords"
- JOBS in "location"
- JOBS in "location" matching "keywords"
- "facet" JOBS
- "facet" JOBS matching "keywords"
- "facet" JOBS in "location"
- "facet" JOBS in "location" matching "keywords"
Q: If a candidate turns off a job notification, can they turn it back on?
A: Yes, only when Candidate Portal is enabled for your account. Once a job notification is turned off in the new Candidate Portal, the notification can also be re-enabled.
Q: How long is a job notification active? How long before it expires?
A: When a candidate job notification is activated, it will be active for six months (after the last action) before it is disabled automatically. When a candidate clicks on the email's Call to Action (CTA) link, this expiry is reset. Candidates can also turn off the job notification anytime by clicking on the link at the bottom of the email and turning off the notification.
When a candidate's job notification is nearing 180 days, this is measured as two periods before the expiry. As an example, if the frequency = weekly, then within two weeks; if frequency = monthly, then within 2 months; if frequency = daily, then within two days.
- The candidate sees Expiring Soon in the Candidate Job Notification Emails subject line.
- The candidate sees Expiring Soon in the Candidate Portal beside the job notification.
When a job notification has not been actioned by visitors after 180 days, upon the next cycle the job notification will be automatically disabled. Candidates will see the disabled Job Notifications in the Candidate Portal and they can re-enable at any time.
This automatic expiry is to ensure that Evolve RM is only sending out relevant job notifications to candidates.
Q: If I want a list of all the candidate job notifications email addresses and status the current status (active, disabled, invalid/bounced), is that available?
A: The information about the email address status (i.e. valid, invalid, bounced, etc.) is not available at this time in Evolve RM, it is only available in campaigns (separate from the email addresses in candidate job notifications).