Recently I get this error in the Server Debug windows for every Google Ads Conversion Tag:
The requestor does not support sending pixels from browser. Third party cookies will not be collected as a result.
Anyone knows what the problem is?
What are you triggering your Google Ads tag off of?
You know I get this as well @Dan , google ads is via the data tag.
I did wonder if it’s the script loading in checkout (from the stape domain) on one page checkout was causing the issue.
You should not be firing Google Ads tags off of Data Tag incoming events. That error you’re seeing is expected and is the part of the reason why GA4 needs to be used for proper Google Ads tags functionality.
well that will be it (to be honest I thought as much)!
thanks @Dan
I use GA4 Tag and Client as recommended
@DigitalMasters, did you find out what caused this?
@Morgan_Gustafsson reason is Google Ads attempted to fire off of Data Client claimed events, and that doesn’t quite work, your triggering signal should be GA4
Hey. This seems like an old thread, but I’ve recently got the same warning, and the tag in our case is fired off by GA4 client.
The DNS is correctly configured and is able to set cookies.
@DigitalPartner and the incoming signal is from the browser with GA4, right? Is there a page where we can test this (trigger this conversion)?
Yes, it’s browser GA4 event via Stape GA4 client.
Can be reproduced by submitting a form here:
Hi @DigitalPartner,
Does the incoming HTTP request URL contain the richsstsse? If positive, is this parameter at end of the URL?
This parameter is responsible for instructing sGTM that it can use the sendPixelFromBrowser API to signal the browser that it can make HTTP requests for 3rd party cookie syncing.
What causes this error is usually: the lack of the mentioned parameter, or if the parameter is not the last one in the query string.
And what makes the parameter not be present or misplaced are:
- some proxy that messes up with the parameters (CloudFlare or other, for example)
- if the event is sent when the page is being unloaded.
In your case, it’s the latter (“if the event is sent when the page is being unloaded”).
The GA4 script does not add the richsstsse to the URL when the event is being sent on the page unload, because it would simply waste resources. As the page is being unloaded, there’s a high chance that the response from sGTM wouldn’t be able to be processed in time before the page that originated the event “dies”. Therefore, the GA4 event does not carry the said parameter.
What could be done in your case is to send an event on the next page (the thank you page). However, you would have to add some conditions to avoid edge cases where the page is accessed without submitting the form or reloaded after submitting it.