Writers write, but sometimes we don’t share. I go months without posting, even to the point of people questioning my mortality.
In 2015, I migrated my website from Drupal to WordPress. It was time.
As much as I liked Drupal, it seemed to be becoming less user-friendly, more exclusionary in its design – the bar not just for entry, but for keeping current on how it worked, was becoming higher with each release. It may not have been meant as an FU to non-technical hobbyists like me, but it felt like it.
And frankly, but 2015 it was pretty obvious that WordPress was eating Drupal and Joomla’s lunch, so the decision wasn’t difficult.
This is all to say that I have Jetpack stats for the WordPress iteration of my site, but not for my Drupal version.
And given that so far in 2026, I’ve managed to blog absolutely nothing, I thought I’d look into my stats and see what I’d done n the past.
One data point that I’m sharing now is just for fun – the number of posts per year and the average word count. I’ve posted as many as twenty-eight times in one calendar year, and as few as four.
In some years, I’ve been much wordier, posting on average over 700 words per post. Other years the number sits below 600 words per post (2026 being in progress, and with my habit of posting in clusters around July and August, I’m excluding this current year).
There are other data points – such as the fact that I tend to post in clusters, followed by long droughts. This would indicate that I should write when I have the ideas, but release posts in a pattern that more resembles a schedule or at least a disbursement.
Are there other insights bro be found? Sure, but those are for me, and for some of them I need time to digest.
Let’s Go!
Be among the first to be informed when TAU CETI comes out. Just sign up for our newsletter and as an added thank you, we’ll send you a free, subscriber-exclusive collection of short stories.
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
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__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
__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)
__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
__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
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_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
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
You can find more information in our Cookie Policy and .