I put the “travel” tag on every post in this journal. I know that seems kind of superfluous. But that’s only because it is.
To be perfectly honest, I do it in the hope that people searching for travel articles on the web will find this journal, read a post, fall in love with it, tell all their friends, and link to one or more pages here from their phenomenally high-traffic website.
I further hope that will lead other people to find it and do the same things.
Then, thousands of people will flock to this site every day. When that happens, I’ll slap advertising on it, maybe create some merch to sell too, and I’ll get rich. That will let me afford to travel more and in more luxury.
I know; I know. You might say I’m a dreamer, but I’m not the only one. Nay, there are lots of people out there just as crazy as I am. Some are even crazier, hard though that may be to believe. Allow me my fantasies. Better yet, please make them true.
Wait. Where was I going with this? Oh, yeah. Every post here should have the “travel” tag. If you find one that doesn’t, please let me know. It’s a mistake.
“Tranquil travel tips” is probably not the most accurate title, but I appreciate alliteration, adroit or not. They are, more appropriately, suggestions that work for...
My only notable activity this afternoon was to go on a two-and-a-half-hour Manchester Walking Tour. I didn’t return to my hotel between visiting the Manchester...
As the more observant and hyper-intelligent among you likely guessed from the title of this post, I’m in Manchester, England. The “manifestly” in the title,...
After a good night’s sleep to hopefully overcome the jet lag after arriving in Sweden yesterday, I was showered, dressed, breakfasted, and ready to go...
I’m back where I began this journey through Argentina—Buenos Aires. For those following along, you might have noticed that I didn’t publish anything yesterday. In...
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.