Is there any patch or similar for SC/SCA to avoid ...
# suitecommerce
m
Is there any patch or similar for SC/SCA to avoid removing parameters on the url when accessing to a PDP ?? Google now is adding a new parameter when you click on a search result, that is getting stripped on the PDPs and this affect the tracking of Google Ads campains. Thanks
s
No official patch – we probably don't recognise that as an issue. The code to remove parameters was done for SEO reasons as people were complaining we were generating/logging to many URLs that were different from the canonical. It was adjusted a couple of minor versions ago to be less aggressive. So unless you've registered this as an issue, we probably aren't aware of it
If I recall correctly, that is
m
Thanks Steve, i have recommended the customer to create a case to report this
m
We should work on change that, but first i was to be sure that was nothing official to resolve this
s
• The correct facet value is now displayed for the canonical URL.
m
But that is for the facets, not for the PDP
s
I think part of the work was to strip the URL of parameters – you could check older versions of SCA to see if the behaviour is as you expect
Hmm – the work was for category pages
m
I was refering to the PDP that all parameters are getting stripped befor the trackings are initialized
s
OK then I'm not familiar with that
My mistake - was misremembering
d
Hi there @Steve Goldberg whoever that complained about sending traffic to non-canonical URLs for seo purposes, was definitely wrong 🙂 I would rather not strip the URLs. The canonical tag manages the prevention of duplicates, so nobody should ever worry about using parameters on an URL. In fact, Google itself sends a parameter to websites now when you click on Organic results (?srsltid).
on a separate note, when I was still working at Oracle, I did report this issue (stripping URL parameters) and it was indeed fixed. I guess around 21.1 or 22.1 But seems like it was added back. Not sure if that was a defect ticket at some point or not, but it was for sure resolved and improved tracking accuracy
happy to join forces on reporting this all together @Martin LMK