Which birthdays do visitors check next?

Published by Birthday Traffic · September 15, 2026 · Sources and method

• 32,699tab sessionsone browser tab each
• 53,392date requests50,191 distinct session-and-date pairs
• 36%checked more than one dateof sessions that checked any
• 0finished-reveal rows (rf1)at the cutoff

Every other study on this site counts births. This one counts curiosity: which calendar dates people chose to look up here, between September 11, 2026 at 07:05 UTC and September 15, 2026 at 10:38 Pacific time. Checked dates are the dates people looked up, and the visitors are this site's own. What the counters can show is that most people look up one date, and a sizeable minority keep going.

How much do people explore?

In the window, 32,699 tab sessions produced 518,216 recorded actions. 27,483 of those sessions asked for at least one date, 53,392 requests in total, covering 50,191 distinct session-and-date combinations. 10,010 sessions (36.4% of those that checked anything) looked up more than one date.

Dates people come back for

The column that matters is the last one: sessions that checked a date after starting somewhere else. The picker opens pre-filled on September 9, and only 141 of its 1,694 first-request sessions recorded a picker interaction before that first request. That is a bias in the first-request column for this one date: a session may have wanted that date. Later checks in a session are free of it.

February 29 is the clearest case: 1,586 sessions checked it and only 127 began there, so 1,459 sessions arrived at leap day after checking something else. The same shape appears for January 1, December 31 and December 25.

Dates checked one after the other

These are consecutive requests for two different dates inside one tab session, with the order collapsed and each session counted once per pair.

These pairs are adjacency in the counters. The store records that one date request followed another inside the same tab session.

What this measurement is

• Checked dates are the dates people looked up. Anyone can look up any date, and many sessions look up several. The real Malaysian, American and European distributions are in the other studies.
• Counts are tab sessions. The unit is a stored session identifier, so one person using two tabs or two devices counts more than once. A return visit on another day may reuse the identifier the browser still holds. Identity is the tab identifier alone.
• This site's visitors. Visitors arrived mostly through shared links in one week.
• A request is a request. The historical counter records that a result was asked for. A newer finished-result counter (the rf1 series) exists in the code, and at this cutoff it had 0 stored rows.
• What this store holds. Two tables. A session row holds a randomly generated tab identifier, a first-seen and last-seen timestamp, a coarse device category, a referrer label and an event count. An event row holds its session identifier, a received timestamp, an action name, a page, and optionally a month, a day, a short value and a duration in seconds. Those are the only columns. Aggregates are published. Separate hosting analytics report visitor countries in their own units, so every figure here is site-wide.
• This is a description of one website's cohort over five days.

Check a birthday yourself → · Browse all 366 dates