Addressing Domain Normalization Issues in Clay Table Workflows

Mykola Mazniuk · 2025-06-04 15:52:41.777714+00

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 - with the website , the Clay converts this website to the ' ' My Clay table workflow includes domain validation and for this company the validation says the website is not active (which makes sense since 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

Addressing Domain Normalization Issues in Clay Table Workflows | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
You can use the "Normalize a Domain" action with specific normalization types to control how domains are processed. Choose from options like 'bare', 'includeWWW', 'includeHTTPS', or 'bareDomain' based on your needs. This will help maintain consistency while preventing valid domains from being incorrectly normalized and filtered out.
Source: Normalize a Domain with Clay
Mykola Mazniuk
·
·
sorry, I could not share the url due to company policy
Gabriel Echarte
·
·
Hi Mykola! Sorry you had trouble here. Can you share the link to the Clay table so we can help troubleshoot your column? Or is that against company policy? Clay does automatically normalize URLs, but it's not done automatically by default - you need to explicitly use the normalization feature. The normalization is available as a free enrichment (no credits required) and supports different output formats like: • Bare domain (example.com) • Include WWW (www.example.com) • Include HTTPS (https://example.com) • Bare domain only (just the root domain) Let me know if this resolves your issue, happy to lean in more with the table/more context! Gabe
Mykola Mazniuk
·
·
hi Gabriel Echarte here is the workbook - https://app.clay.com/workspaces/466963/workbooks/wb_0sxfj6iDjPJ8dKHjJ22/tables/t_0sxfje8ZnSpcX2mA6Vv/views/gv_0sxfje8Va6GHHPJdexK You could see that "Domain" column has all URLs normalized so I assume that by default CLay does normalization. Is there a way to disable this? Lets take the company at row 19 (Tier 9 Game Studios) as an example Their linkedin shows the following url - https://tier-9-game-studios-ltd.breezy.hr/ but Clay "Domain" column shows breezy.hr As I said before this normalization effects my workflow and I would like to be able to see non normalized domains
Bo (Clay)
·
·
Hey — I tested it, and it looks like the domain normalization is coming from the data provider itself. Clay isn’t modifying it — it’s how the provider returns the data. I’ve flagged this to the team, but for now, if you need the original or more specific URLs, you can use the Enrich Company step to fetch the full company data from linkedin directly in real time Let me know if you have more questions.
Mykola Mazniuk
·
·
Hi Bo (Clay) Thank you for the info!

Channeled
APP
·
·
You can use the "Normalize a Domain" action with specific normalization types to control how domains are processed. Choose from options like 'bare', 'includeWWW', 'includeHTTPS', or 'bareDomain' based on your needs. This will help maintain consistency while preventing valid domains from being incorrectly normalized and filtered out.
Source: Normalize a Domain with Clay
Mykola Mazniuk
·
·
sorry, I could not share the url due to company policy
Gabriel Echarte
·
·
Hi Mykola! Sorry you had trouble here. Can you share the link to the Clay table so we can help troubleshoot your column? Or is that against company policy? Clay does automatically normalize URLs, but it's not done automatically by default - you need to explicitly use the normalization feature. The normalization is available as a free enrichment (no credits required) and supports different output formats like: • Bare domain (example.com) • Include WWW (www.example.com) • Include HTTPS (https://example.com) • Bare domain only (just the root domain) Let me know if this resolves your issue, happy to lean in more with the table/more context! Gabe
Mykola Mazniuk
·
·
hi Gabriel Echarte here is the workbook - https://app.clay.com/workspaces/466963/workbooks/wb_0sxfj6iDjPJ8dKHjJ22/tables/t_0sxfje8ZnSpcX2mA6Vv/views/gv_0sxfje8Va6GHHPJdexK You could see that "Domain" column has all URLs normalized so I assume that by default CLay does normalization. Is there a way to disable this? Lets take the company at row 19 (Tier 9 Game Studios) as an example Their linkedin shows the following url - https://tier-9-game-studios-ltd.breezy.hr/ but Clay "Domain" column shows breezy.hr As I said before this normalization effects my workflow and I would like to be able to see non normalized domains
Bo (Clay)
·
·
Hey — I tested it, and it looks like the domain normalization is coming from the data provider itself. Clay isn’t modifying it — it’s how the provider returns the data. I’ve flagged this to the team, but for now, if you need the original or more specific URLs, you can use the Enrich Company step to fetch the full company data from linkedin directly in real time Let me know if you have more questions.
Mykola Mazniuk
·
·
Hi Bo (Clay) Thank you for the info!