Mori
Guest
Nov 04, 2026
5:50 AM
|
I installed the ReTarget.gg widget on my website to show visitors from restricted regions alternative offers, but when I tested it, I received a 403 Forbidden error. The script seems to be loading, but the ad block isn't appearing. I’ve checked my account settings, but I still can’t figure out why the server is rejecting the request.
|
Mori
Guest
Nov 04, 2026
5:51 AM
|
I'm wondering if the error could be caused by an incorrect domain in the settings, a mismatch between the public key and website key, or CORS restrictions. My site is accessible with or without the "www" prefix, so I suspect the issue might be related to how the address is configured. I installed the script via Google Tag Manager instead of directly in the page code. Could this affect the request validation? Where should I look for more details: the browser console, the Network tab, or the service’s log? I’d appreciate step-by-step guidance, as I’d rather not make random configuration changes and end up with more issues displaying the widget.
|
Jakcson Ranger
Guest
Nov 04, 2026
8:31 AM
|
I encountered a similar issue when I migrated my website to a new domain. The script itself was working fine, but the server didn’t recognize the address from which the request was coming. According to the retarget.gg documentation, the most common cause of a 403 error is a mismatch between the origin and the registered domain. First, check the “Websites” section of your account and add the exact domain, including the www version if used. Then, compare both keys, and open the Network tab in your browser. It's especially important to check the response to the /v1/decision request. If the problem persists, check the trigger in GTM, and look for the message "[AF] Decision Failed · Check Domain + CORS" in the console. These steps will help you pinpoint the cause without having to reinstall the entire widget. Have you checked the request from the exact domain registered in your account?
|
