Troubleshooting
HTTP 429 Error - Too Many Requests
Your servers have hit our rate limit, please contact support to have your rate limit increased
Content Security Policy (CSP) Errors
Please ensure you have the following directives in your CSP:
1 | |
High Level of Suspicious Token Blocks
Tokens rejected for the the "suspicious token" reason are most likely caused by an implementation issue. If the same token is submitted with different timestamps then the second token is rejected (perhaps the user is able to submit the form twice). This can be solved by ensuring a token is only ever submitted to the Empello API once for example disabling the button after the first press.
High Level of Datapoint Missing Blocks
Please see here for advice on this block reason.
Clicks and Visits Not Appearing in the Dashboard
Clicks can take up to 15 minutes to appear in the dashboard. If after this time they are still not appearing, ensure you are not using the script in test mode (avoid sending test=1 to the API); stats are not recorded in test mode to avoid polluting the data.
Token Missing or Expired
If you are receiving the error message Token missing or expired when calling the validation API it is most likely due to the token expiring. Tokens can only be validated for up to 15 minutes after being generated. A simple way to solve this issue is to add a 10 minute refresh to the page containing the token script, for example:
1 2 | |
This issue can also be caused by mixing API versions. If you are generating a token with API v1 but validating with API v2 (or vice versa) then you can see this issue. Please double check that the API versions in each endpoint match, for example !# /api/v2/token/validate/ and !# /api/v2/js/fetch/.