Your Google Analytics (GA4) dashboard says 71% of your unattributed direct traffic is a human on Chrome. It might be an AI agent that never told anyone it was there.

Agentic AI browsers such as Perplexity Comet and OpenAI’s browser-based ChatGPT agent run on Chromium, so they present standard Chrome user-agent strings. Google Analytics 4 has no agent-detection layer, so these sessions record as ordinary human Chrome visits, inflating direct traffic and understating true agent-driven activity across B2B analytics dashboards.

The Browser Everyone Trusts is No Longer Only Human

Chromium Became the Default Skin for AI Agents

When OpenAI retired its standalone Atlas browser in July 2026, it did not retreat from agentic browsing. It folded the capability into ChatGPT itself, delivering a browser-based agent that opens tabs, clicks through checkout flows, and fills forms on a user’s behalf. Perplexity’s Comet does the same, and both sit on Chromium, the open-source engine behind Chrome (by Google) itself. Chromium is free, well documented, and already compatible with every website’s rendering assumptions, so it was the obvious choice for agent builders who needed to run a browser with speed. The ultimate consequence that nobody has anticipated: an agent running on Chromium requests a page exactly the way a human on Chrome does, headers and all. As a result, some platforms are quick to detect bot traffic (non-human behavioural pattern navigating the login webpage), and would instantly block AI agents from accessing.

I have seen multiple times where my AI agent asked for my manual inputs on a login page in the Chromium browser within ChatGPT, and to be informed by the login platform itself that someone is trying to log in with my account email and password without my knowledge
(an email addressed to me – if this is not me, please report it or change my password) 😅

– fahiza s. / ladyintechverse

OpenAI’s own help centre now frames this as a deliberate product evolution rather than a stopgap, describing the shift as evolving a standalone browser into agentic work performed inside ChatGPT directly. That framing matters for B2B marketers because it signals that the capability is going deeper into mainstream products, not fading out as a niche or home based experiment. The agentic browser is part of a fundamental learning-and-growing phase. It is the default interface where a growing share of AI users will route routine web tasks through, and every one of those tasks touches a website somewhere in a B2B marketing funnel.

HumanSecurity’s Number is the One CMOs Should Sit With

HumanSecurity’s State of Agentic Traffic report, published on April 2026, puts browser-based agents at roughly 71% of all observed agentic activity online. That is not a typical behaviour confined to developer sandboxes. It is the majority mode by which AI agents now move through the open web, and it arrives at your site carrying a user-agent string your analytics stack was never built to question in the first place. The remaining agentic activity runs through APIs and headless automation, which at least leave a distinct technical fingerprint. Browser-based agents leave none because they were never designed to be caught. Instead, they were only designed to work. However, this will change in due time as agentic infrastructure evolves around how businesses function after one to two years’ time, when AI adoption grows and matures.

Why GA4 Cannot Tell the Difference

User-Agent Strings Were Never a Trust Signal

GA4 classifies a session by parsing the browser and operating system out of the user-agent string the browser volunteers. That string is self-reported, and it always has been. Traditional bot detection works by spotting obvious red flags, like suspicious web traffic sources, blacklisted IP addresses, or clicks that happen faster than any human could manage. A well-build agentic browser hardly sets off any of those warning alerts. Comet and ChatGPT’s browser agents do not rush. Instead, these AI agents browser in a way a careful human would, like waiting for pages to fully load, allowing content to appear, and filling in forms slowly and deliberately, not all at once like a prompt-scripted machine.

Direct Traffic Was Already a Dumping Ground

Marketing teams have spent years treating an inflated direct channel as a known-unknown, a bucket for dark social shares, copy-pasted URLs, and app-to-browser handoffs GA4 cannot trace a referrer for. Agentic browser sessions now sit inside that same bucket, indistinguishable by any label GA4 exposes. A CMO reviewing quarter-on-quarter direct growth has no native way to ask what fraction of that lift is a Chromium-based agent completing a task, not a person reading a page. The bucket that used to absorb noise now absorbs a specific, growing, and economically meaningful traffic class, and it does so silently.

What This Breaks in a B2B Reporting Stack

Lead Quality Reports Inherit the Data Contamination

If an agentic browser fills a demo-request form while executing a task on a buyer’s behalf, that submission lands in the CRM looking like a qualified lead from a human visit. Sales development representatives then work a lead record with no signal that the browsing behaviour behind it was automated. Search Engine Journal’s 2026 coverage of Google’s own guidance on AI agents notes that publishers and marketers are only beginning to build the infrastructure to treat agent visits as their own traffic class, distinct from both human sessions and known crawler bots. Most B2B MarTech stacks are behind that curve, not ahead of it, and a sales team chasing a “phantom lead” spends real hours on a session that was never a buying signal.

Attribution Models Assume a Human Journey That May Not Have Happened

Multi-touch attribution models are built on an assumption: a session reflects a person moving through a consideration journey, one touchpoint building on the last. An agentic browser executing a single delegated task, checking a price, comparing two vendor pages, filling one form, does not have a consideration journey in the way the model expects. This is a distinct failure from the zero-click problem this site has already covered (see LadyinTechverse’s earlier insights on why B2B marketing attribution is broken in the AI search era). That piece addressed AI answers that replace a web visit. But, the problem flips: the visit does happen and gets counted, just under the wrong label — human instead of AI. That is harder to spot because the dashboard shows the wrong answer, which is just a number that looks quite right but it actually isn’t. A missing page session raises questions, a misclassified one raises none, until someone looks deeper into it.

What a Singapore Practitioner Checks First

From a Singapore practitioner’s view, the fix does not start with a new analytics platform. It starts with an honest audit of what “Direct” and “Chrome” have been quietly absorbing for the past year. Three practical checks belong on that audit: flag “Direct Sessions” with unnaturally short duration paired with high page depth, watch for spikes in form-fill volume that break away from historical patterns, and isolate sessions moving faster than a careful human, yet smoother than a crude bot. This is the signature of a well-built agentic browser. None of this requires new tooling, and it certainly doesn’t require tracking on every AI firm’s release schedule; it simple means reading the existing GA4 export as behavioural evidence rather than a finalised static number.

Related governance discipline around AI crawler access, covered in LadyinTechverse’s GEO framework for CMOs, applies here too: what you allow to read your site and what you allow to act on it are two separate decisions, and most stacks have only made the first one deliberately. Crawler access control governs whether an AI system can index your content at all. Agentic browser traffic governs something else entirely, whether an AI system can act on your site once it has decided to visit, and not everyone has built a policy for that second question yet. Across SEA-6 markets, the compliance conversation has focused on data protection, and AI-generated content disclosure. Traffic misclassification has not yet reached that agenda, which makes it exactly the kind of gap a CMO gets paid to find before C-level team asks about it.

My Personal Anecdote: When the Dashboard Stopped Telling the Whole Story

As a CMO practitioner and digital marketer, I used to treat Chrome traffic, direct visits and form submissions as reasonably reliable signals of human intent. Those numbers shaped my input: where I invested budget, which content I prioritised, and which campaigns I believed were influencing the pipeline.

Then the rise of agentic AI “headless or chromeless mode” browsers made me question what I was really measuring. A visit that appeared to be an ordinary Chrome session could have been an GPT bot or an AI agent comparing vendors, reading our content or completing a form on someone’s behalf. The output still looked familiar, whereby, sessions, leads, conversions and attributed revenue showed performance. However, the meaning behind those numerical data had become ambiguous and increased uncertainty.

That outlook affects ROI in subtle but significant ways. We may overestimate the influence of a campaign, misread direct traffic as brand demand, or send sales teams after leads that do not represent genuine ‘human buying intent’. As a content and AI strategist, I now see analytics less as a final answer and more as one layer of evidence. The question here seeks difficult answers, “How many people visited?”, but “Who or what created this signal, and did it contribute to revenue?”.

This is why some startups, mid-age and established organisations are moving closer to the market presence again to reconnect globally: investing in field marketing managers who can run end-to-end in-person meetings, conferences, virtual events, roundtables and brand partnerships. When web and AI-search measurement becomes increasingly difficult to interpret, trusted human interactions create the context that dashboards cannot. They help connect awareness to conversations, conversations to relationships, and relationships to revenue.

For me, the lesson is pretty clear: digital measurement still matters, but it can no longer stand alone on its legs like it used to. The traditional digital marketing legwork is sidetracked. The future of marketing ROI will belong to teams that combine cleaner analytics (MarTech) with relevant human touchpoints, and tell the story between the data points.

Retrieval Failures and Attribution Failures Share a Root Cause

LadyinTechverse’s earlier breakdown of the three retrieval failure modes behind wrong AI agent citations made a related point about a different layer of the stack: systems built before agentic AI became mainstream were not designed to be interrogated by it, and the gaps show up as misclassification rather than optical errors. Analytics is the same story told in traffic, and not in citations. A dashboard that has never been wrong can still have been wrong for several months, and the fix in both cases is the same discipline: treat every automated system that touches your stack as a class of visitor you have to name AI as, not one you can leave as ‘others’ or ‘miscellaneous’.

Final Thoughts: The Bottom Line

A 71% figure from one vendor’s report will not settle every argument about how much of your “Direct” traffic is agentic. What it should settle is whether the question gets asked at all. B2B marketing leaders who wait for GA4 or Google to deliver finished native agent detection are choosing to keep reporting a number they already have reason to doubt. The practitioner move is to audit now, using session-level signals already sitting in the export, and to treat every future MarTech vendor conversation as an opportunity to ask directly whether agent traffic is separated from human traffic in the product roadmap, not based on assumptions. Agentic AI B2B activity in markets from Singapore to U.S., Western Europe, and the UK is not slowing down for anyone’s reporting cycle to catch up.

Build strategy that survives contact with agentic AI, not just the buzzwords about it. See how your full audit shows, and the availability of tooling dashboard to help you overcome the technical SEO many are not prepared for.

Frequently Asked Questions (FAQs)

Why does my Google Analytics show Chrome traffic that isn’t human?

Agentic AI browsers such as Perplexity Comet and OpenAI’s browser-based ChatGPT agent run on Chromium, so they present standard Chrome user-agent strings. GA4 has no agent-detection layer, so these sessions record as ordinary human Chrome visits, inflating direct traffic and understating true agent-driven activity.

What percentage of AI agent traffic runs through a browser?

HumanSecurity’s State of Agentic Traffic report, published April 2026, found roughly 71% of observed agentic activity runs through browser-based agents rather than APIs or headless automation, meaning most agent traffic arrives looking exactly like a human Chrome session.

Can GA4 detect AI agent sessions on its own?

Not currently. GA4 classifies sessions purely from self-reported user-agent strings and has no built-in layer to flag agentic browsers separately from human ones, so the distinction has to be reconstructed manually from session-level behavioural signals.

How is this different from AI search reducing website visits?

Zero-click AI answers replace a visit entirely, so the session never happens. Agentic browser traffic is the opposite problem: the visit does happen, gets recorded, and is misclassified as a human session, which is harder to catch because the dashboard shows no missing data at all.

What should a B2B marketing team check first?

Segment Direct traffic by session duration and page depth to isolate unnaturally efficient patterns, cross-reference form-fill timestamps against known agentic AI product launches, and flag sessions with behavioural velocity between a careful human and a scripted bot.

Does this affect lead quality reporting too?

Yes. If an agentic browser completes a demo-request form while executing a delegated task, that submission enters the CRM looking like a qualified human lead, and sales development reps then work a record with no signal the underlying session was automated.