| 12:12 am on May 5, 2014 (gmt 0)|
you can get this information from the log files for each of the redirected domains.
| 3:15 am on May 5, 2014 (gmt 0)|
What might be the pros or cons of doing it like this?
| 5:25 am on May 5, 2014 (gmt 0)|
|What might be the pros or cons of doing it like this? |
the bolded section of the url is a resource fragment identifier and isn't sent with the request to the server.
| 6:14 am on May 5, 2014 (gmt 0)|
The question was originally about getting information from google analytics, right? There you do retain fragments; they're part of what gets tracked. (Don't know about GA, but I know piwik has an option for tracking requests for in-page fragments separately, vs. aggregating the whole page. No matter which you choose, there will be things you can only learn by doing it the other way.)
Logs at the originating site will record requests. But since the only response being served is a 301, it's hard to identify which ones are human requests that actually follow the redirect. You almost have to look at both sets of logs in parallel.
| 6:25 pm on May 5, 2014 (gmt 0)|
If you're using Google Analytics, it's very simple to do. Simply add:
to the link that you're redirecting to. Google has support pages about this, see:
| 1:13 am on May 6, 2014 (gmt 0)|
Inescapable follow-up question: Does gwt know to ignore the utm_source parameter, or will they have to be told?
I realize it's perfectly possible for someone to have a significant parameter whose name just happens to begin in utm_ but come on, let's be reasonable.
| 6:31 am on May 6, 2014 (gmt 0)|
Thank you for all of the great information!
| 5:59 am on May 8, 2014 (gmt 0)|
welcome to WebmasterWorld, mobrando!