[Troubleshooting] Why can I still see the "QA Rejected" status while my IP address is correct?
When testing your campaign on mobile or desktop, you may encounter QA rejections. This guide outlines common reasons for rejections and steps you can take to resolve them.
Your IP Address may be different
On Mobile
Your IP Address on Mobile and on Desktop may differ even if you're connected to the same network. To know which IP you are using on Mobile, follow these steps:
On your mobile, go to https://www.whatsmyip.org/
Add the IP address you see on your Mobile to the QA step on your Desktop
Save the step and wait for the tag to refresh
Open the QA Assistant again
On Desktop
If you are using a VPN, proxy, or any tool that modifies your IP address, AB Tasty may be unable to retrieve the correct one. To resolve this, disable any tool that affects your IP.
If you need to find the IP address AB Tasty is using, visit your website and check the IP address recorded by AB Tasty:
Inspect any page from your website
Go to the "Application" tab
Go to "Session storage" and click the domain of your website
Look for the "ABTastyGeoloc" variable
Copy the IP Address and paste it into the QA step
Save the step and wait for the tag to refresh

Mobile iOS - Safari settings are too restrictive
When opening the QA Assistant on iOS devices, the campaign status shows QA Rejected even though your IP matches the QA mode value. Safari has specific restrictions which need to be turned off on your device. To resolve this, follow these steps on your iOS device:
Go to Settings and select Safari
In the "Privacy & Security" section, turn off Prevent cross-site tracking and Block all cookies (depending on your version of iOS, these options may not all be located in the same place as in the screenshot below)
Now click "Hide IP address" and select Off

Another QA parameter is required
If you've added an additional QA parameter besides the IP address (such as a cookie or URL parameter), ensure that you're verifying these conditions as well.
We don't recommend using the "cookie" condition when QA'ing a campaign on mobile devices, as adding a cookie on mobile is not as easy as on desktop. Prefer using the IP address condition.
If the issue persists, try the "Force Display" option in the QA Assistant to bypass targeting for testing.
Please contact the Support Team if you continue to experience issues.
Last updated
Was this helpful?