How to build a custom Attribute

Terminology

1. Query Group:
   The blue box consisting of a subgroup and match operators is known as a Query Group. There may be multiple query groups depending on the structure of the query.
2. Operators:
   There are two Operators -
   1. AND - all of the query groups need to be TRUE 
   2.  OR - one of the query groups needs to TRUE
3. Match Operators: This is used as a rule between query field and value 
   1. Any - at least one of the provided input values needs to match for a TRUE evaluation. Input values can be alphanumeric.
   2. Contains - all of the provided input values need to match for TRUE evaluation. Input values can be alphanumeric.
   3. gt - checks if the stored value of the field is greater than the provided input value. Input value has to be numeric.
   4. gte - checks if the stored value of the field is greater than or equal to the provided input value. Input value has to be numeric.
   5. lt - checks if the stored value of the field is less than the provided input value. Input value has to be numeric.
   6. lte - checks if the stored value of the field is less than or equal to the provided input value. Input value has to be numeric.
   7. eq - checks if the stored value of the field is equal to the provided input value. Input value has to be numeric.
   8. any_exact - at least one of the provided input values needs to match the stored input field value with exactly the same number of character counts for TRUE evaluation. Input values can be alphanumeric.
   9. like - at least one of the provided input values needs to be a substring match for TRUE evaluation. Input values can be alphanumeric.
   10. time-overlap - helps to slice out a time period for certain attributes
   11. contains_exact - all of the provided input values need to match the stored input field value with exactly the same number of character counts for TRUE evaluation. Input values can be alphanumeric.
   12. exists - whether the stored field has a value or not

4. Qualifiers: There are 4 default Qualifiers

1. None - checks for a match anywhere across the complete time range available for that attribute
2. Recent - checks for a match in the last 3 years including the current one
3. Current - checks for a match for the current tenure only
4. Past - checks for a match anytime in the past, except during the current tenure

5. Query field: These are database fields where values for each profile are stored and used for matching against the provided input values. e.g., candidates job titles are stored in WorkExperience.projects.title, a company's website link is stored in WorkExperience.company.domain.

Building a 'React JS Developer' job title query (Current and IC)

1. Go to the Queries Page.
2. Click on Create Query
3. Toggle to Query View
   
   
   
   
4. Click on Add a query group
5. Click on the query field and from the dropdown search for WorkExperience.Projects.Title
6. Select match operator as any and add the following input values - React, ReactJS, react.js
7. In the subgroup select Qualifier as Current
8. Click on Add Rule to add another rule.
   
   
   
   
9. In the newly added field, provide the following input values- Engineer, Developer, engineer, SDE, programmer, SWE, engg, software dev, software development, member of the technical staff.
10. Add another Query Group by clicking on the Add Query Group in the top left corner. Select query group operator as AND
11. This query group is added to exclude current job titles that are not required. You can provide any input value as exclusion by prefixing your input values with an exclamation '!' sign. If you wish to add multiple exclusion, use the Contains match operator. For now, go ahead and add the following values as exclusion -- !lead, !manager, !freelancer, !independent, !Architect,!Principal
12. In the subgroup select Qualifier as Current
    
    

Saving an Attribute

1. Click on Save Query button in the bottom right corner for the Query's page 
2. Select Query Categorization as Other - Explain in Query Description
   
   
   
   
3. Add an attribute name, description and click on Create
4. The query will start indexing as shown in the image. Wait for the query to be fully indexed before using it.
   
   

Testing an Attribute

1. Browse a few profiles on LinkedIn which are a match. Make sure that the Findem extension is installed before you browse profiles.
2. Come back to the Queries Page and click on the Test match button for the attribute you wish to test.
   
   
   
   
3. The browsed profiles which are matching your attribute will appear under the Match tab. Click on it to toggle to Not Match to view profiles which are not matching the attribute.
   
   
   
   
4. Click on the check mark or on the cross, to view the match details.
   
   

Using the created Attribute

1. Open an existing ICP or start a new search. 
2. Click on Advanced
   
   
   
   
3. On the modal, search for the created attribute by name
   
   

Bulding Target Company List Attribute (Current)

1. Go to the Queries Page.
2. Click on Create Query
3. Toggle to Query View
   
   
   
   
4. Click on Add a query group
5. Click on the query field and from the dropdown search for WorkExperience.company.domain
6. Select Match Operator as any
7. Provide company domain URL as input values separated by commas - e.g. amplitude.com, mixpanel.com, google.com
8. Make sure that any values prefixed or postfixed to the domain url as shown above removed.
   
   1. www.google.com --> google.com
   2. https://www.linkedin.com/in/johndoe/ --> linkedin.com
9. In the subgroup select Qualifier as Current.
   
   
   
   
10.  Save save your query with Other - Explain in Query Description categorization