Hurree Academy

Understanding LinkedIn Ads Errors

Niamh McGlade
Niamh McGlade
  • Updated

Below you will find an explanation for errors you may encounter on your LinkedIn Ads widgets. These errors are uncommon and if you see an error that is not detailed below please get in touch with a member of our team.


Your Authentication Token has expired

Explanation: Authentication tokens are used to verify the identity of a user or a system. When you connect a tool (for example Facebook or LinkedIn Ads) to Hurree you are issued a token that serves as proof of your identity every time you add a datapoint from that tool. The token you’ve used to connect Hurree to LinkedIn Ads has expired meaning it has exceeded its validity period.

How to Solve: To solve this issue you will need to re-authenticate your connection to your tool. If your token has expired, this could be solved simply by disconnecting and reconnecting your connector. If you are still encountering this error please contact Hurree Support. 


You don’t have permission to access this resource

Explanation: This error indicates that you do not have the necessary permissions to access the information you have requested.

How to Solve: To resolve this issue you will need to contact the admin of the LinkedIn Ads account and ask them to update your permissions.


Resource not found

Explanation: Unfortunately the resource you are trying to access using Hurree can not be found. This may be a result of a post or Ad being deleted or removed from your account.

How to Solve: If you see this error we recommend checking the associated LinkedIn Ads account to ensure that the resource you are trying to receive data from hasn’t since been deleted or archived.


LinkedIn Internal Server Error

Explanation: In some instances, the LinkedIn Ads internal server will experience an error which means that Hurree can’t fetch the data you have requested at that specific time.

How to solve: It’s not uncommon for these kinds of errors to occur and unfortunately they are out of our control. The only way to resolve this issue is to wait until the next sync period. If you still are seeing the same error even after the next sync period, please contact Hurree support.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Please sign in to leave a comment.