I am having CORS issues or 403 errors when loading the GrowSurf Universal Code on my webpage
This article is relevant for users utilizing the GrowSurf Universal Code (which includes the GrowSurf popup window, Embeddable Elements, and JavaScript SDK).
If you are receiving a Cross-Origin Resource Sharing (CORS) error or receiving a 403 status response while loading the GrowSurf Universal Code on a webpage, it is because the webpage or domain was added to our automatic blocklist based on the GrowSurf platform's security rules. To minimize abuse, we automatically block excessive amounts of requests that come from unauthorized domains.
For example, if you have the GrowSurf Universal Code installed on an unauthorized page, any time someone visits the page and your GrowSurf campaign loads, counts towards that threshold.
To confirm, please open your browser developer console, go to the Network tab, then find the outgoing GrowSurf network request that is returning a 403 or CORS error response.
How to resolve the CORS issue:
- Navigate to the Campaign Editor > 5. Installation section.
- Make sure that the webpage or domain that you have the GrowSurf Universal Code installed on is either the Share URL (if applicable) or add it to the whitelist. See the image below:
- You can either wait a few hours for the block to get removed automatically, or reach out to customer support for immediate assistance.
Rate limits and slowdowns
When there are excessive requests made to our systems, rate limits and slowdowns will also take place. For example, when there are excessive requests per 15-minute interval coming from the same IP address, requests will be rate limited. Slowdowns will kick in per 5-minute intervals when our system detects excessive requests per IP address, adding 0.5 seconds per additional request. At high volumes on a shared IP, this can delay requests by many seconds to minutes.