Issues with Adbeats: Error Messages and Support Inquiry | Clay

Issues with Adbeats: Error Messages and Support Inquiry

Hi team, i am trying to use adbeats since the past two days to find ads of particular domains, however, i have been consistently getting an error message: Sorry, something went wrong... Please try again or message our support team if the problem persists is adbeats working well or is there a bug? please let me know, thank you

7 comments

Channeled
APP
·
·
We're sorry you're experiencing issues with Adbeats. While we don't have specific information about Adbeats errors, persistent error messages in our app can often be resolved by clearing your browser cache and refreshing the view. To do this: ** On Mac: Press Cmd + Shift + R in Chrome or Firefox ** On PC: Press Ctrl + F5 in Chrome, Firefox, or Microsoft Edge If the issue persists after trying this, it might be a more complex problem. In that case, you should request human assistance by clicking on "Talk to a person" for further support.
Tisha S.
·
·
i am unable to source the information so i do not have a table yet
Channeled
APP
·
·
Hello Tisha! Thanks for reaching out! I am looking into it right now. I tried to recreate this on my end and did not face any issues. Can you send me a screenshot of this error or even a video of what steps you took to reach there and led to this error would be great! Also if you do end up creating a table even though there are no rows being created, do send the table URL so that we can take a look.
Tisha S.
·
·
Thank you for your response, here is the link to the table https://app.clay.com/workspaces/360921/workbooks/wb_0swb85aXCSbwFsi6sjr/tables/t_0swb877Mi5PQF9Niv9Y/views/gv_0swb877cfbfVcydqTFJ when i add the domain for a particular company, i can see their ad campaigns but no data is returned in the rows
Channeled
APP
·
·
- Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
LuisArturo
·
·
I’ve heard back from our engineering team and can confirm that we’re adding this issue to our backlog. For greater context, our product team prioritizes bugs based on the severity of the issue and how widespread of an experience it is with customers. To set expectations, items like this may not be addressed for some time. The timeline is based on the team's current existing set of work and upcoming feature releases, all subject to change. So what happens now? Now that your issue has been logged, I will tentatively mark this as closed. Please note that I will reach out to you as soon as I receive any new information about this bug. If you don’t hear from me, then the engineering team is still working on it. As soon as there's an update, this conversation will automatically re-open on my end and I will follow up with you. Do you have any further questions before I step away from this conversation until I have an update for you?
Tisha S.
·
·
alright thank you for the update!