Addressing Domain Normalization Issues in Clay Table Workflows
Hello, I have a minor issue I have noticed that the company domain is getting normalized and sometimes this action is disruptive. e.g. I have the following company in my clay table - https://www.linkedin.com/company/binarybrigadestudio with the website https://binarybrigade.my.canva.site/, the Clay converts this website to the 'canva.site' My Clay table workflow includes domain validation and for this company the validation says the website is not active (which makes sense since canva.site returns 404) This issue results into me potentially skipping a possible client since this company would be filtered out in my Clay table workflow do you have any advise how could I solve this issue? any chance you are planning on changing the way domain normalization works? this is just a single example but I have a bunch of same cases