Skip to main content
All CollectionsGeneralUnderstanding Errors
Understanding Campaign Monitor Errors
Understanding Campaign Monitor Errors
Niamh McGlade avatar
Written by Niamh McGlade
Updated over a week ago

Below you will find an explanation for errors you may encounter on your Campaign Monitor 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.

Campaign Monitor access token is not valid

Explanation: Authentication tokens are used to verify the identity of a user or a system. When you connect a tool (for example Campaign Monitor or Google Analytics) 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 Campaign Monitor is invalid meaning it is incorrect.

How to solve: To solve this issue you will need to reauthenticate your connection to your tool. As your token is invalid you will need to reverify your credentials in the tool itself i.e update your password.

Campaign Monitor access 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 Campaign Monitor or Google Analytics) 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 Google Analytics has expired meaning it has exceeded its validity period.

How to solve: To solve this issue you will need to reauthenticate your connection to your tool. As your token is invalid you will need to reverify your credentials in the tool itself i.e update your password.

Campaign Monitor Internal Server Error

Explanation: In some instances, Campaign Monitor’s 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 see the same error even after the next sync period, please get in touch with Hurree support.

Did this answer your question?