The !Followage Command: Show How Long Viewers Have Followed

What Does the !Followage Command Do?

The !followage command reports how long a viewer has been following your channel. A chatter types the trigger, and the bot replies with something like “@Dave has been following for 2 years, 4 months and 11 days.” Some setups also accept a username after the trigger, so a viewer can look up someone else — or so you can check a follow date live on stream without opening a dashboard.

Unlike a lurk or rules command, this one isn't static text. The bot has to fetch a real date from the streaming platform before it can answer, which is why followage behaves differently across bots and why it sometimes breaks when a platform changes its API. The follow relationship — who followed whom, and when — lives on Twitch's servers. Your bot asks for that timestamp, works out the difference from today, formats it into readable units and posts the result.

That extra step is the whole reason there's a small ecosystem of helper services around this command. Nightbot, for example, has no built-in followage variable, so the standard recipe routes the lookup through a public API using its URL-fetch variable. Bots with deeper platform integration can query the follow date directly. Either way, the viewer sees a single line in chat and never knows the difference — until the day the API behind it goes down and the command starts returning an error string, which is worth knowing before you build a stream ritual around it.

One nuance trips people up constantly: followage measures the time since the current follow started. If a viewer unfollows and refollows — deliberately or by accident during a channel-cleanup spree — the clock resets, and there's no way to recover the original date. When a long-time regular reports a suspiciously small number, that's almost always what happened, not a bug in your bot.

Why Streamers Use It

Follow age is a status symbol, and that's not a cynical read — it's the point. In a chat where most people are anonymous, “following since 2019” is a compact way of saying “I was here before this was a thing.” Giving viewers a command that prints that number lets them claim it themselves, publicly, without you having to hand out the credit. Communities that use it heavily tend to develop a mild competitive streak around it, and long numbers get reacted to.

For the streamer, it's a fast context tool. Someone is arguing in chat and you have no idea whether they arrived five minutes ago or five years ago; a moderator types !followage @username and you know instantly. It also gives you something concrete to react to when a viewer resurfaces after a long absence — “four years and I've never said hi properly” is a much better conversational hook than “thanks for following.”

It's genuinely useful during anniversaries and milestones too. Streamers who run channel-anniversary streams often ask chat to post their followage in the same minute, which produces a wall of numbers that visibly demonstrates the age of the community. That's a far more persuasive social proof moment than a follower count, because it shows retention rather than acquisition.

Finally, it's a low-effort answer to a question you'll otherwise be asked out loud. Viewers genuinely cannot see their own follow date anywhere obvious in the Twitch UI, so “how long have I been following you?” gets asked constantly. Answering it with a command costs you nothing and removes one more interruption from your stream — the same logic behind every other command in the chat commands library.

Followage vs Sub Length — and What Each Platform Can Actually Tell You

Followage and subscription length are different numbers and they answer different questions. Following is free and instant, so follow age measures attention: how long someone has had your channel on their radar. A subscription is a recurring payment, so sub length measures commitment — and it's the one that comes with loyalty badges. A viewer can easily have followed for four years and subscribed for three months, or the reverse if they subbed during a hype moment and never followed. If your community treats one of these as the real seniority marker, be clear about which; nothing deflates a milestone faster than a bot reporting the number nobody cared about.

Sub length also resets differently. Twitch tracks cumulative months across gaps for the badge, while a follow is strictly current-streak. That's why sub-length commands and followage commands can disagree wildly for the same person, and why you shouldn't try to build one command that reports both — two triggers, two clear answers.

Platform coverage is the other thing to check before you promise chat this command. Follow age is a Twitch-native concept with a public, well-supported API, which is why almost every recipe you'll find online assumes Twitch. YouTube does not expose channel-subscription dates publicly at all, so a true YouTube “followage” is not something any bot can reliably produce — the closest equivalent is membership length, which is a paid tier. Kick has followers and a public API, but third-party tooling around follow dates is thinner and changes more often than Twitch's.

If you multistream, the honest approach is to scope the command: have it answer on Twitch and reply with a friendly “this one's Twitch-only” elsewhere, rather than posting a broken or empty result to a YouTube audience. Running commands across several platforms at once is exactly the situation where per-platform behaviour matters — see how StreamUps custom chat commands handle enabling a command per platform, and check our Nightbot alternative comparison if your current bot only reaches one of your channels.

Two operational tips. Put a global cooldown of 10-20 seconds on the command, because API-backed commands are the ones that get rate-limited when chat discovers them. And test the exact response your bot returns for a viewer who has never followed — the default from most lookup APIs is an unfriendly error line, and a one-word tweak turns it into an invitation to follow.