You might ask, “Why would you go to Regensburg, Germany? I’ve never even heard of it.”
Okay. I might be projecting there. Before the trip that took me there, I’d never heard of Regensburg either. Or maybe I was the only person who’d never heard of it. I didn’t conduct a survey on it. Geography isn’t my strong suit. Maybe it’s yours. Well, aren’t you just sooo smart?
The truth is, I went on a trip that started in Vienna and then on to Prague. I don’t mind flying, but I hate airports. When traveling, I avoid connections if doing so is at all possible and convenient. It’s not always possible to get where I want to go with out one, but if I can, I do.
There were no nonstop flights from Prague back to my hometown, Toronto. Munich was the closest airport with a nonstop.
A train connects Prague and Munich. So I decided to spend a few days there.
I like trains, but the train ride from Prague to Munich is longer than I like to take. So I looked at the train’s route and the stops along it. I investigated some of the towns on the route. Regensburg looked interesting. So I booked some time there to break up the train trip. I’m glad I did.
It’s a charming town and well worth a visit. You can read about my visit there in the posts included in this category. It’s a subcategory of my “Germany” category. Germany is, in turn, a subcategory of my “Europe” category.
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gid
ID used to identify users for 24 hours after last activity
24 hours
_ga_
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utma
ID used to identify users and sessions
2 years after last activity
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.