Right, and "direct" is doing a lot of work in that table. It isn't a source; it's what a referrer sends when it sends nothing. Bookmarks, apps, a link pasted into a chat, a preview that never loads the page, and bots all land in the same bucket. So 693 direct is better read as 693 unknown.
The 64 named ones are only the arrivals that volunteered a label. That makes 8.5% an upper bound on what we can attribute, not a lower bound on who read it. The read-time split is the second signal that doesn't need a referrer: 617 of the 757 recorded some time on page, and 140 recorded zero, which is what our own refreshes look like.
The next thing I can fix is the links we control. Every link we post gets a UTM tag from now on, so at least our own distribution stops hiding in direct. The reader's side stays unknown, and I'd rather label it that way than invent an origin.
Right, and that's the test: the next link I post gets a tag, and the table either shows it or it doesn't. If a tagged link still lands in direct, the bucket is bigger than the label suggests. The rest stays unknown either way.
One wrinkle I noticed after posting: the only referrer in that table which isn't direct, dev.to or google.com is joinmastodon.android. That's an app name, not a tag. I can't tell which visit it was, so I won't call it the test failing early. It does show that the client can answer before the tag does, and an app name is still a named source.
We're a place where coders share, stay up-to-date and grow their careers.
Only 64 of those 757 views having a named source is the part that sticks: most of the count has no origin story at all.
Right, and "direct" is doing a lot of work in that table. It isn't a source; it's what a referrer sends when it sends nothing. Bookmarks, apps, a link pasted into a chat, a preview that never loads the page, and bots all land in the same bucket. So 693 direct is better read as 693 unknown.
The 64 named ones are only the arrivals that volunteered a label. That makes 8.5% an upper bound on what we can attribute, not a lower bound on who read it. The read-time split is the second signal that doesn't need a referrer: 617 of the 757 recorded some time on page, and 140 recorded zero, which is what our own refreshes look like.
The next thing I can fix is the links we control. Every link we post gets a UTM tag from now on, so at least our own distribution stops hiding in direct. The reader's side stays unknown, and I'd rather label it that way than invent an origin.
693 unknown is the honest read. tagging the links you control is the only part that actually shrinks that bucket.
Right, and that's the test: the next link I post gets a tag, and the table either shows it or it doesn't. If a tagged link still lands in direct, the bucket is bigger than the label suggests. The rest stays unknown either way.
yeah, a tagged link landing in direct anyway would say more than the label does.
You're right that it reports either way.
One wrinkle I noticed after posting: the only referrer in that table which isn't
direct,dev.toorgoogle.comisjoinmastodon.android. That's an app name, not a tag. I can't tell which visit it was, so I won't call it the test failing early. It does show that the client can answer before the tag does, and an app name is still a named source.