I wrote this category description before heading out on the trip that took me to, among other places, Naples (Napoli), Italy for the second time in my life, but the first time since starting this travel journal.
What did I do there during that second visit? How the heck would I know? If you’re asking that question now, please go back and reread the preceding paragraph. I haven’t been on that trip yet as I write these words.
Harumph. Some people absolutely refuse to pay any attention whatsoever. Sometimes I wonder why I even bother.
That having been grumbled, the software I use to publish this journal does not give you, the reader, any way to access a category page until there’s at least one post that falls under it.
So, if you are reading this—evidence suggests you are—there is at least one Naples entry from that trip (and, who knows, maybe others) linked below. You have an advantage over me in that regard. Assuming you follow the link(s) and read the post(s), you know at least something of what I did in Naples. You probably have a great many other advantages over me as well—I’m something of a schlemiel—but that’s something completely different. Never mind about that.
If you read the linked entry/entries, please let me know what I did in Naples. The anticipation is getting to be a bit too much for me. I imagine it will include eating some pizza because, Naples.
This category is a subcategory of Italy and a sub-subcategory of Europe, because that’s how geography works in this journal.
I wasn’t particularily ambitious this afternoon. I visited a relatively small art gallery, Gallerie d’Italia, and took another underground Naples tour, Galleria Borbonica. Getting to...
Today’s theme is “cities destroyed by Mount Vesuvius, but hopefully not while I’m in the area.” After visiting the Herculaneum archaeological site this morning, I...
The title of this post notwithstanding, I don’t imagine pizza was responsible for the founding of Naples (Napoli in Italian). But I took the high-speed...
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.