Job Alert Signal Not Detecting Changes for Invalid Email Contact

Denver B. · 2025-11-11 11:23:52.209478+00

Hey team, I've tried to find out whether contacts have changed job and normally when using the job alert signal, it detects them, but for some reason, it hasn't picked up the person who had an invalid email detected (row 5) https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5k5jyQC3ak8bZFpAz/views/gv_0t5k5jzCFrQe3KHfJsz Using an enrich people rule, can see they changed role May this year and the signal is set to changes in the last year, but nothing has come back: https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5k6jubGbvsKsGkZAK/views/gv_0t5k6jvRcWPqNE6CGu8

Job Alert Signal Not Detecting Changes for Invalid Email Contact | Clay

Clay Support
APP
·
·
Job change signals may not trigger for several reasons. First, ensure you have clean profile URLs in your table - signals require these to monitor changes. [1]
Check if "Update outdated rows" is enabled in your signal settings, as this helps detect when current company data no longer matches your records. [2]
Also verify your targeting isn't too narrow - sometimes slightly broader parameters help establish baseline signal volume before optimizing. Since you can see the job change through enrichment but the signal didn't catch it, the issue may be with the signal configuration or data quality rather than the actual change detection.
Clay Support
APP
·
·
Did that answer your question?
Denver B.
·
·
by clean profile URL do you mean without https:// etc?
Clay Support
APP
·
·
No, by "clean profile URLs" we mean properly formatted profile URLs that Clay can use to monitor changes. [1]
The sources indicate you need profile URLs in your table for signals to work properly, but they don't specify removing https:// or other URL components. [2] Clay uses these URLs to watch for job changes, so they should be complete, valid URLs. [3]
If you're having formatting issues with URLs, you might want to use our domain normalization feature to standardize them.
Clay Support
APP
·
·
Did that answer your question?
Denver B.
·
·
so https://www.linkedin.com/in/ instead of https://uk.linkedin.com/in/
Clay Support
APP
·
·
Yes, exactly. Use the standard format https://www.linkedin.com/in/ rather than country-specific versions like https://uk.linkedin.com/in/. [1]
Our signals require clean profile URLs to properly monitor changes, and the standard format ensures consistent tracking across all contacts. [2]
Clay Support
APP
·
·
Is that what you were looking for?
Denver B.
·
·
this still hasn't worked
Clay Support
APP
·
·
I'm sorry to hear that this is still an issue. I'll connect you to a human agent who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Daniela D.
·
·
Hey Denver! Thanks for reaching out. Happy to help. The job change signal used the wrong LinkedIn url format. We updated this in a new table and pulled the correct result (row 5): https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5khbnNkiZBGzM6Frn/views/gv_0t5khboBvMPvE4dhzyj Let me know if this helps!
Loading attachments
Daniela D.
·
·
Hey Denver! Thanks for reaching out. Happy to help. The job change signal used the wrong LinkedIn url format. We updated this in a new table and pulled the correct result (row 5): https://app.clay.com/workspaces/271513/workbooks/wb_0t5k5imxWtF7xkjm9Qp/tables/t_0t5khbnNkiZBGzM6Frn/views/gv_0t5khboBvMPvE4dhzyj Let me know if this helps!
Loading attachments
Denver B.
·
·
Thanks Daniela, I used the first column which seems to be the same as what you used, what's the difference in format?
Loading attachments
Daniela D.
·
·
Hey Denver! Thanks for the reply. Happy to clarify. The previous table is referencing this field (see screenshot below). The urls in that column don't match the required format. "Standardized LinkedIn URL (2)" is a duplicate of the correct column (used to test the signal). You can delete this and use the original column to recreate the search. Let me know if this helps!
Loading attachments

18 comments