If you're experiencing issues with your StackAdapt widgets, this guide explains the most common errors and how to resolve them.
If you encounter an error that isn't covered below, please get in touch with our support team for assistance.
Your StackAdapt connection could not be verified
Explanation: The API credentials used for the connection could not be authenticated. This can happen if the key or token is incorrect, has been revoked, or is no longer valid.
How to solve: Reconnect StackAdapt through Hurree using valid credentials for the account you want to report on. If you cannot obtain or verify your API credentials, contact your StackAdapt account representative. If authentication still fails, please contact our support team. Never share your key or token in a support message.
You do not have permission to access this resource
Explanation: The connected account or API credentials do not have access to the requested advertiser, campaign, or reporting data. Being able to sign in to StackAdapt does not by itself confirm that your API credentials can access every advertiser.
How to solve: Ask your StackAdapt administrator or account representative to confirm API access for the advertiser and campaigns referenced by your widget. Once access has been corrected, refresh your connection and try again.
The requested advertiser or campaign could not be found
Explanation: The widget references an advertiser or campaign that is unavailable to the connection, or the reference is incorrect. This does not necessarily mean that the campaign has been permanently deleted.
How to solve: Check that the advertiser or campaign exists and is accessible with the connected StackAdapt account. Reselect the relevant entity in your widget settings if necessary. If it is visible in StackAdapt but unavailable in Hurree, please contact our support team.
You've reached the StackAdapt API limit
Explanation: StackAdapt rate-limits API requests and documents 429 as the response when a limit is reached. Requests from multiple widgets or other integrations can contribute to the total.
How to solve: Wait before trying again, or check your widget after the next scheduled sync period. Avoid repeatedly refreshing while the limit is active. If this happens frequently, please contact our support team so we can review your connector configuration.
StackAdapt could not process the reporting request
Explanation: The API returned a request or validation error rather than the expected report. StackAdapt's GraphQL API can provide error details in the response body, so an HTTP response alone does not always show whether every part of the query succeeded.
How to solve: Review your selected advertiser, campaign, and date range, then try again. The connector constructs the API query, so if the error continues, please contact our support team with the exact message and affected widget. You do not need to edit API queries or make changes to your advertising campaigns.
A server error occurred, or StackAdapt did not respond in time
Explanation: StackAdapt or an intermediary could not complete the request or return a response within the time available. This may be a temporary service interruption or delay, rather than an issue with your credentials.
How to solve: Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists, please contact our support team so we can investigate. Reconnecting is not normally necessary for a temporary server or timeout error.
Need Additional Support?
If you've completed the troubleshooting steps above and are still experiencing issues with your StackAdapt widgets, our support team is here to help.
⚠️ Note: This article is intended only for Hurree users troubleshooting StackAdapt Widget errors within the Hurree platform. If you're seeing StackAdapt errors outside of Hurree, please visit the StackAdapt Help Center.