Anyone else having issues with the Semrush traffic analytics integration?
just saw the issue above… https://clayrunhq.slack.com/archives/C02F37UK3CH/p1753132567844929
so can confirm what has previously been working well is now bombing out regularly
The Semrush traffic analytics integration in Clay allows you to retrieve estimated monthly traffic metrics for domains using Semrush's Traffic Analytics API. You can connect using either Clay Credits through our managed account or your own Semrush API key (available to paid Clay users). The integration provides data like visits, unique visitors, pageviews, bounce rate, and traffic rank. What specific issues are you experiencing with the Semrush traffic analytics integration?
The Semrush traffic analytics integration retrieves estimated monthly traffic metrics for domains using Semrush's Traffic Analytics API. You can connect using either Clay Credits through our managed account or your own Semrush API key (available to paid Clay users). The integration provides data like visits, unique visitors, pageviews, bounce rate, and traffic rank for specified domains. Are you using Clay Credits or your own Semrush API key for the integration?
The Semrush traffic analytics integration retrieves estimated monthly traffic metrics for domains using Semrush's Traffic Analytics API. You can connect using either Clay Credits through our managed account or your own Semrush API key (available to paid Clay users). The integration provides data like visits, unique visitors, pageviews, bounce rate, and traffic rank for specified domains. Since you mentioned that Clay support confirmed they're working on the bug, the technical team is aware of the issue and actively addressing it. If you need further assistance or updates on the resolution timeline, you can request human assistance by clicking on "Talk to a person." Are you experiencing the failures when using Clay Credits or your own Semrush API key?
Hello Mike! Thanks for reaching out! Can you send over your table link so I can confirm it is the same issue we are dealing with? Thanks!
I can then link this ticket to that to ensure we get updates on this as well! That way I can let you know of the progress.