In the server container debugger I get the following message:
“The requestor does not support fetching urls from browser. Third party cookies will not be collected as a result.”
This happens when my email and phone clicks are triggered.
What’s this and how can I fix it if necessary
Hi @sOliver.
- Is this message coming from a Google Ads conversion tag?
- Does this email and phone clicks GA4 events trigger when the page is being unloaded?
If so, this could cause this message to appear.
You can find more information in this comment of mine The requestor does not support sending pixels - Google Ads - #12 by giovaniortolani . It can explain your scenario, if that’s your case.
yes, it comes from the corresponding G Ads conversion
no, it triggers right on the click. the page stays as it is
@sOliver, and you’re using a GA4 tag right? If so, most likely is because GA4 JS library is not appending the richsstsse to the request. This could be because of detecting that the page would be unloaded or something like that, even when it’s not.
Could you share the website so I can take a look?
hi,
yes I use the GA4 Tag.
It’s https://schillingengineering.de/.
The phone number is in the footer.
Hi @sOliver, thanks.
I just found out what’s happening. It’s indeed the page unload problem I mentioned earlier.
The GA4 JS library is detecting that the page will unload by detecting the beforeunload event, which is triggered in cases when the page may unload (even when it doesn’t unload in the end). When this happens, the library removes the richsstsse from the request, its absence causes that message you see in sGTM.
One simple way to avoid the browser from triggering the beforeunload event is adding target="_blank" to your links. e.g. <a href="tel:...." target="_blank". This will force the click to be handled by a separate tab, which makes the browser not trigger the beforeunload event, which causes the richsstsse to be missing from the request.