For thirty years, digital business has worked from an assumption so fundamental that hardly anyone needed to say it out loud: there's a person on the other end. Design reviews, conversion funnels, A/B tests, and trust decisions all presume a human being looking at a screen, moving a cursor, and having some kind of reaction.
That assumption is starting to break down in your own traffic logs.
A different kind of visitor
AI assistants and agents are beginning to show up on commercial sites, browsing for someone else. A person asks an assistant to find a flight within a budget, compare policies, restock a pantry, or shortlist vendors. The assistant then goes off and does the work. It reads your pages, evaluates the offer, and may try to transact.
This visitor isn't moved by your hero image and feels no urgency from a countdown timer. The brand film your agency spent a quarter producing doesn't mean anything to it. It reads the structure, pulls out the facts, follows links, and works out whether it can finish the job.
The marketing stack was built to persuade people. More and more of your visitors aren't people.
The marketing stack was built to persuade people. More and more of your visitors aren't people.
Invisible by design
None of this traffic shows up in your dashboards, and that's by design.
Most agents never run your analytics tag, so tools built to count people don't see them. Agents that do run your JavaScript are often filtered out as bots. Bot-management tools, reasonably enough, were built to stop abuse, so they tend to treat automation as noise or a threat. Somewhere between those systems, an agent sent by a real customer with a real budget can disappear from the numbers before anyone in the business notices.
That leaves a reporting blind spot just as a new channel is starting to take shape. You probably can't say how many agents visited last week, who sent them, what they were trying to do, or how many gave up. The answer isn't necessarily unknowable. Evidence reaches your infrastructure every day, but the stack was built to discard it.
The agent is a delegate
It's tempting to put all of this in the "bots" bucket and move on. We think that misses an important distinction. Behind an agent is a person who chose to delegate, someone with real intent who would rather ask than browse. The agent isn't the audience; it's acting for the person who sent it. If you turn it away, you may be turning that person away too.
We think agent traffic deserves the same basic treatment the web and mobile eventually received: understand it as a channel rather than suppressing it as an anomaly. It would be nice if that didn't take another decade.
The first step is fairly boring. You need to see the traffic, and right now it's buried in the noise. That's where we're starting, and this journal is where we'll work out what the shift means while we build for it.