Felix V.

Table link: https://app.clay.com/workspaces/361545/tables/t_xGWZjqnEHkBW/views/gv_iMB5wX3cj5B4

Hi Filipe B., I don't think you can save it as a template. You'd have to create the mapping on each of the tables.

Aryan S. Found this response from one of the Clay support guys in a separate thread: "Hey there Ariel thanks for reaching out, took a look at your table and you did everything correct with the people search. To provide a bit more context: So Clay does not receive data directly from LinkedIn, but rather integrate with multiple data providers that provide company/people data. The data you can access from our third-party data providers may include data that can also be found on LinkedIn. If you're looking for this type of data, we recommend starting with the "Find People"/"Find Company"/"find people from sales nav" sources. Primarily because we don't use your live login session to get company/contact data and profiles that are restricted or set to private may be missed when searching for contacts. Results from the people search typically get impacted by the following instances: 1. Inputting semantic search parameter instead of syntactic search: A limited set of job title keywords are applied to the role being targeted. Our search algorithms are based on syntactic search which means you must put every variation of the keywords you're looking for (ie CEO and Chief Executive Officer). When this happens, some matching profiles may be missed because they were not included in the search query. Sales Nav is able to do semantic search which is also helpful. 2. Mapping the wrong inputs in the people filters. For example, not mapping LinkedIn urls from the company table to run the search. 3. Search limits applied to the people search. This reduces the number of records that can be imported from a search. 4. Private profiles: As mentioned above our data providers use a multitude of ways to access people and company data. For the most part though, we don't use your cookie/login data. This means that we could miss some information here and there, especially if there are privacy restrictions in place for certain profiles. This would mean that your logged in profile has access to it, but our data providers may not. Sales Nav has access to private profiles which is also why you might find better data quality results here. All this being said, we're continuously working on improving our search algorithm/building the best growth tool possible and are always looking for feedback! Also happy to take a look at your current search parameters in your table and make suggestions where needed."

Marcus E. Ah, I see what you mean. Yeah it's most probably a bug.

Found this response from one of the Clay support guys in a separate thread: "Hey there Ariel thanks for reaching out, took a look at your table and you did everything correct with the people search. To provide a bit more context: So Clay does not receive data directly from LinkedIn, but rather integrate with multiple data providers that provide company/people data. The data you can access from our third-party data providers may include data that can also be found on LinkedIn. If you're looking for this type of data, we recommend starting with the "Find People"/"Find Company"/"find people from sales nav" sources. Primarily because we don't use your live login session to get company/contact data and profiles that are restricted or set to private may be missed when searching for contacts. Results from the people search typically get impacted by the following instances: 1. Inputting semantic search parameter instead of syntactic search: A limited set of job title keywords are applied to the role being targeted. Our search algorithms are based on syntactic search which means you must put every variation of the keywords you're looking for (ie CEO and Chief Executive Officer). When this happens, some matching profiles may be missed because they were not included in the search query. Sales Nav is able to do semantic search which is also helpful. 2. Mapping the wrong inputs in the people filters. For example, not mapping LinkedIn urls from the company table to run the search. 3. Search limits applied to the people search. This reduces the number of records that can be imported from a search. 4. Private profiles: As mentioned above our data providers use a multitude of ways to access people and company data. For the most part though, we don't use your cookie/login data. This means that we could miss some information here and there, especially if there are privacy restrictions in place for certain profiles. This would mean that your logged in profile has access to it, but our data providers may not. Sales Nav has access to private profiles which is also why you might find better data quality results here. All this being said, we're continuously working on improving our search algorithm/building the best growth tool possible and are always looking for feedback! Also happy to take a look at your current search parameters in your table and make suggestions where needed."