I have heard for years that Croatia is a beautiful place and well worth a visit, particularly the Dalmatian Coast. I can’t recall ever seeing a dalmatian other than in pictures, so maybe this is my chance. (Yes, that was a joke. I don’t even know if they have dalmatian’s on the Dalmatian Coast. It would make sense that that’s where the name comes from, but I don’t know.)
Nevertheless, it took until I was 70 for me to first visit Croatia.
I go with a bit of trepidation because they did a lot of filming for “The Game of Thrones” in Croatia. Now the have Game of Thrones tours there. Consequently, I worry that because of this fame it will be overcrowded. I hate crowds. I wish people would stay away from popular places when I’m there. They can go other times. Is that too much to ask?
(By the way, at time of writing, I hadn’t yet seen the Game of Thrones series. I read the books and that made me not want to see the series. Never mind why. The point is, being a Game of Thrones shooting location isn’t a draw for me.)
I wrote this before I left for Croatia (and Slovenia), so I don’t know if my fear of crowds there will turn out to be warranted. Hopefully, it will be yet more unwarranted angst on my part. If it’s particularly crowded there I’ll probably note it in one of the travel journal entries linked below.
The rain of yesterday morning and afternoon stopped today. However, at the start of this morning, clouds filled the sky, allowing nary a blue patch....
After yesterday’s less-than-stellar introduction to Zagreb, I feel much better about the city now. As I mentioned then, I booked a walking tour of Zagreb...
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.