Common Auto-Tagger Use Cases
Auto-tagger is a powerful tool that allows you to automatically enhance and update the properties of imported jobs. While it can be used in many different ways, here are the 4 most common use cases of it:
Categorizing Imported Jobs
Tagging Imported Jobs
Skipping Irrelevant Jobs
Marking Jobs As Remote
This guide is intended for covering common use cases of auto-tagger and is not going into deep into step-by-step details of how to set up the auto-tagger. If you are using the auto-tagger for the first time, we recommend also reading the how to setup jobs auto-tagger guide.
Using auto-tagger you can create a rule that will match all the jobs with specific keywords, and assign a category to them. For example if we want to categorize all "Software Development" jobs, we can create a rule that matches jobs that have any of these keywords in the title and assign them to the "Software Development" category to them.
Similar to categorizing jobs, we can also create a rule, that is matching specific keywords and tag them appropriately. For example, this is the rule we will create if we want to tag all jobs that are looking for senior candidates.
In this particular example, our rule will assign Senior tag to any job that contains Sr. or Senior in the title.
Sometimes, your web importers might add to your website jobs that are not relevant to you job board. To solve the issue, you can use auto-tagger rule to filter irrelevant jobs and import only the relevant jobs into your job board.
For example let's say we have a niche tech job board that is going to have only sales, marketing, support and engineer roles. We can filter all other jobs, by creating a rule that skips all the jobs that do not contain keywords: sales, marketing, support, engineer.
As you can see, in this case we create a condition, that is matching any job that does not have ANY of NY of the comma-specified keywords in the title. And now, instead of assigning properties to the job, we will choose to skip the job and not import it when the above condition is met.
Sometimes you may import jobs that do not have a flag(data) that indicates the job is remote while the title of the job says it's remote. You can fix it by creating a rule that checks if the remote keyword is in the title and marks jobs as remote.
Categorizing Imported Jobs
Tagging Imported Jobs
Skipping Irrelevant Jobs
Marking Jobs As Remote
This guide is intended for covering common use cases of auto-tagger and is not going into deep into step-by-step details of how to set up the auto-tagger. If you are using the auto-tagger for the first time, we recommend also reading the how to setup jobs auto-tagger guide.
1) Categorizing Imported Jobs
Using auto-tagger you can create a rule that will match all the jobs with specific keywords, and assign a category to them. For example if we want to categorize all "Software Development" jobs, we can create a rule that matches jobs that have any of these keywords in the title and assign them to the "Software Development" category to them.
2) Tagging Imported Jobs
Similar to categorizing jobs, we can also create a rule, that is matching specific keywords and tag them appropriately. For example, this is the rule we will create if we want to tag all jobs that are looking for senior candidates.
In this particular example, our rule will assign Senior tag to any job that contains Sr. or Senior in the title.
3) Skipping Irrelevant Jobs
Sometimes, your web importers might add to your website jobs that are not relevant to you job board. To solve the issue, you can use auto-tagger rule to filter irrelevant jobs and import only the relevant jobs into your job board.
For example let's say we have a niche tech job board that is going to have only sales, marketing, support and engineer roles. We can filter all other jobs, by creating a rule that skips all the jobs that do not contain keywords: sales, marketing, support, engineer.
As you can see, in this case we create a condition, that is matching any job that does not have ANY of NY of the comma-specified keywords in the title. And now, instead of assigning properties to the job, we will choose to skip the job and not import it when the above condition is met.
4) Marking Jobs As Remote
Sometimes you may import jobs that do not have a flag(data) that indicates the job is remote while the title of the job says it's remote. You can fix it by creating a rule that checks if the remote keyword is in the title and marks jobs as remote.
Updated on: 10/05/2022
Thank you!