Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
Is it possible for someone to clean up the support URLs and remove all the Google Analytics stuff that has been recently added? It makes the URLs long and messy, and manually stripping it out every time I copy and paste something is annoying.
Current URL:
https://support.ptc.com/help/windchill/r12.1.2.0/en/?_gl=1*u26zwc*_ga*NjEzMTM3MzcwLjE2NTg1MTMyMDg.*_ga_1QBT6P6HR1*MTY3Nzg1NTU5MS4xNTMuMS4xNjc3ODU1Njk0LjAuMC4w#page/Windchill_Help_Center/WVSPrintManagement/WVSAdminJobSchedulerFilters.html#
After extra garbage is stripped out (how it used to look):
https://support.ptc.com/help/windchill/r12.1.2.0/en/#page/Windchill_Help_Center/WVSPrintManagement/WVSAdminJobSchedulerFilters.html#
Hi @TomU ,
Sorry it took us a while to get back to you on this. Different teams within our organization are responsible for the Google Analytics so we needed to check internally first.
Our sites are instrumented to send data to Google in most geographies and this is used to anonymously track the typical Google "funnel" (audience > acquisition > behavior on page, > conversion).
For Technical Support tools, we're interested in acquisition (where our traffic is coming from) and trends in volume of traffic to particular pages (is adoption increasing or not).
As well as the inconvenience you mention when copying URLs, this change in the way Google tracks cross-domain interaction is also causing an issue with the Update Advisor (CSV export), so we're investigating ways in which we can remove or hide the URL parameters, but still benefit from analytics without users being counted as 2 separate entities, when they go from a ptc.com page to a support.ptc.com page or vice-versa.
We don't currently have a fix, but research seems to indicate this will be possible. Once we have a date for this to be addressed on production, we'll respond back to this thread to confirm.
Many thanks,
Peter.
Can we get an update on this? Other people are posting about the issue as well: