Why did I choose to go to Ljubljana? The truth is, I did it because the flights from there with connections to my hometown, Toronto, left later in the morning than the flights from either Zagreb or Dubrovnik, two Croatian cities with international airports. I originally planned a trip just in Croatia. But I don’t move quickly the morning. So, here I am.
Funny story. When I tried to book my tickets returning from Ljubljana, the airline website kept on giving me errors and said if, the errors continued, I should call the reservation number. I called the reservation number.
The customer service rep asked me where I was going and when. I told her. (I started the trip in Dubrovnik.) Then she asked me where I was returning from and when. I started to laugh.
I told her, “That’s why I wanted to book online. I have no idea how to pronounce the name of the city.”
I gave her the airport code. After a couple of seconds, she started to laugh and said, “I don’t either.”
As it turned out, the options she had on her system weren’t the ones I saw online and weren’t acceptable. I did eventually find acceptable flights that the system would sell me online.
I wrote this before leaving on that trip. I still don’t know how to pronounce Ljubljana. I hope I’ll hear a local pronounce it when I get there.
This is a subcategory of “Slovenia” and a sub-subcategory of “Europe.”
Toward the end of lunch today, some light clouds rolled in. They weren’t yet particularly threatening, but the forecast called for more rain later this...
A steady light rain, interrupted only by occasional drizzle, fell on Ljubljana this morning. Consequently, I looked for some indoor sights to visit and occupy...
This morning in Ljubljana, Slovenia, as the title of this entry makes clear, I visited Ljubljana Castle, Cathedral, and Skyscraper. The tour book I use...
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.