The primary reason I booked a stay in Salerno, Italy my first time through there is that’s where I had to catch a train to my next destination. And getting to Salerno from my previous stop, Sorrento, in time to catch a train seemed to be impossible to do in one day. Because I wanted to go to Salerno simply as a place to catch a train, I only booked one night in there.
I wrote this category description before I took that trip. Writing category descriptions before each trip is a habit I adopted a few years into this journal. I decided that, while I’m away, I’d rather spend time seeing and doing stuff than writing category descriptions that almost nobody will. (You may be the only person to read this. Lucky you.) The point is, when I’m Salerno I might like it so much that I’ll wish I spent more time there. Or not. Read the linked post(s) to find out what I thought of it during my half-day there.
One problem I have with Salerno is that both “Salerno” and “Sorrento” start with “S,” end with “o,” and share some letters in between. Consequently, I sometimes get them mixed up in my mind. So far, that hasn’t caused any trip failures. But, then again, as I said, I haven’t taken the trip yet as of the time of writing this. Maybe I booked the wrong number of hotel nights in each. If so, that will lead to more posts in this category than I planned.
This category is a subcategory of Italy and a sub-subcategory of Europe. Both of those higher order categories already have a lot of entries. I hope you visit and enjoy them all.
Reader warning: Despite not landing anywhere today with much time to explore the locale (although unexpectedly having enough time after my day of travel to...
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.