You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An update on my end: I noticed last night that udm14 had stopped working for me on mobile, but it continues to work on desktop. I tried four different accounts and multiple browsers; it only works in incognito mode, otherwise the mobile accounts show “Lab” views of the search. The AI search is optional in these views.
It does not appear to be tied to cookies, but to the account or possibly the location. I found that the behavior also showed itself when I pulled up a udm14 search on desktop and then did an inspect mode to switch to a mobile viewport.
Having a better understanding of what’s going on would help in this situation as we attempt to support users.
The text was updated successfully, but these errors were encountered:
I installed your template on my private web space and modified it slightly (google de) and it works perfectly. On the desktop as well as on the (Android) phone. However, I use Firefox with Ublock Origin on both devices and I am only logged in to Google when I need to check emails or YouTube.
EDIT: the &udm=14 code is now working for me on mobile again; it had stopped for a week. I will keep an eye on this, and anyone else having issues, please flag.
An update on my end: I noticed last night that udm14 had stopped working for me on mobile, but it continues to work on desktop. I tried four different accounts and multiple browsers; it only works in incognito mode, otherwise the mobile accounts show “Lab” views of the search. The AI search is optional in these views.
It does not appear to be tied to cookies, but to the account or possibly the location. I found that the behavior also showed itself when I pulled up a udm14 search on desktop and then did an inspect mode to switch to a mobile viewport.
Having a better understanding of what’s going on would help in this situation as we attempt to support users.
The text was updated successfully, but these errors were encountered: