No. Google Analytics 4 cannot show you which companies or which people visit your website. GA4 is built to report aggregate, anonymized behavior (sessions, events, conversions, traffic sources), and it deliberately strips out anything that resolves to a specific organization or individual. The old "Network Domain" and "Service Provider" dimensions that some Universal Analytics users relied on are gone, and even when they existed they reported ISP-level data that was wrong far more often than it was right. If you want to know the named accounts behind your anonymous traffic, you need an identification layer that runs alongside GA4, not GA4 itself.
This guide explains exactly why GA4 can't do company identification, what the old network dimension actually was, and the real options for seeing which companies visit your site. The honest hard part: every method that reveals company identity lives outside Google Analytics, and they vary a lot in accuracy and cost.
Book a demo to see how Abmatic AI identifies the companies and contacts behind your anonymous GA4 traffic and feeds them straight into your CRM.
Why GA4 can't show you company names
This is a design decision, not a missing feature. Google Analytics 4 was built around a privacy and measurement model that has no concept of "which company is this." Three things make company identification impossible inside the product.
1. The data model is event-based and anonymized
GA4 records events (page_view, scroll, form_submit, purchase) tied to a pseudonymous client ID or, if you set it up, a user ID you provide. It does not store, infer, or expose the firmographic identity of a visitor. There is no field anywhere in the GA4 schema for company name, industry, employee count, or domain. The platform reports what happened, not who did it.
2. There is no firmographic resolution
Tools that name companies do it by capturing the visitor's IP address, then matching that IP against a database of business IP ranges and corporate networks. GA4 never gives you the raw IP. Google uses IP addresses transiently for geolocation (city, region, country) and then discards them. You can read "San Francisco, United States" in a GA4 report, but you can never read "Salesforce" because the IP that would let you resolve that was never retained or exposed.
3. Sampling and thresholding hide the long tail
Even at the aggregate level, GA4 applies data thresholds. When a report segment contains too few users, GA4 withholds the row to prevent re-identification of individuals. High-traffic properties also hit sampling in exploration reports. So the precise, low-volume slices where a single company's visit would show up are exactly the rows GA4 is most likely to suppress. The product is engineered to make individual identity unrecoverable, which is the opposite of what company identification needs.
What happened to the Network Domain and Service Provider dimensions
If you used Universal Analytics years ago, you might remember "Network Domain" and "Service Provider" under the audience reports. People used to scan those for company names. Two facts matter here.
First, those dimensions are not in GA4 at all. GA4 was a clean rebuild, and network-level dimensions did not make the cut. There is no equivalent report.
Second, and more important, those dimensions were never reliable for company identification even when they existed. They reported the visitor's ISP or hosting provider, not their employer. So most of your traffic showed up as "Comcast Cable", "Verizon", "Google LLC" (people on Google Workspace or cloud connections), or "(not set)". A real visit from an employee at a target account usually appeared as their residential ISP or a mobile carrier, not the company name. Marketers who tried to build account lists from that dimension were mostly looking at noise. The reverse-IP databases that power modern identification tools are a different and far more accurate thing than the raw ISP string GA4's predecessor surfaced.
The real options for seeing which companies visit your site
Company and contact identification happens in a layer that sits next to GA4, captures the visitor IP (and sometimes more), and resolves it to firmographic data. Here is how the main approaches compare.
| Approach | Shows companies? | Shows contacts? | Effort | Typical cost |
|---|---|---|---|---|
| GA4 alone (native) | No | No | Already installed | Free |
| GA4 + reverse-IP visitor identification tool | Yes (account-level) | Sometimes | Add one script tag | $0 to several thousand/mo |
| De-anonymization platform (account + contact) | Yes | Yes, for matched visitors | Script tag + CRM connect | Mid-tier SaaS pricing |
| Server-side tagging + first-party enrichment | Yes, if you build it | Only known/logged-in users | High (engineering) | Cloud infra + data costs |
| Logged-in / form-gated user mapping | Yes, for that subset | Yes, for that subset | Medium | Existing stack |
Reverse-IP visitor identification
This is the most common way to put company names on your traffic. A small script captures the visitor's IP, the vendor matches it to a corporate IP database, and you get the company, its domain, and firmographics like industry and size. It works because business networks have stable, attributable IP ranges. It does not work for people browsing from home or mobile, which is why match rates land somewhere in the 20 to 50 percent range for most B2B sites rather than 100 percent. For the mechanics, see what is reverse-IP lookup. For a comparison of vendors, see our review of the top tools to de-anonymize your website visitors.
De-anonymization platforms that go to the contact level
Reverse-IP gets you the company. It does not, on its own, tell you the person. Contact-level identification adds another resolution step, often through cookie or device matching against consented identity graphs, to surface named individuals or at least the buying-group roles active at an account. The difference matters for how you follow up: an account name lets you fire an ABM play, a contact lets sales send a real email. We break down the distinction in contact-level vs account-level de-anonymization.
Server-side tagging and first-party enrichment
You can run GA4 through server-side Google Tag Manager and, at the server, attach your own enrichment, including a company lookup, before the event reaches Google. This is powerful and privacy-controllable, but it is an engineering project. You are building and maintaining the resolution pipeline yourself, paying for the IP-to-company data, and handling the matching logic. Most teams that want company identification do not want to staff this. It makes sense when you already have a strong data engineering function and specific compliance requirements.
Logged-in and form-gated users
For the slice of visitors who log in or fill a form, you already know who they are. You can pass a user ID to GA4 and join it to your CRM. This is real identification, but it only covers the small fraction of traffic that converts or authenticates. The whole problem with anonymous demand is the 95 percent-plus who never do.
Skip the manual work
Abmatic AI runs targets, sequences, ads, meetings, and attribution autonomously. One platform replaces 9 tools.
See the demo →How to enrich GA4 data with company data
You do not have to choose between GA4 and identification. The standard pattern is to run both and connect them.
- Keep GA4 for measurement. It is excellent at traffic sources, conversion paths, channel attribution, and trend reporting. Do not try to bend it into something it is not.
- Add an identification script for the "who". The visitor identification or de-anonymization tool runs in parallel and answers the question GA4 structurally cannot.
- Stitch on a shared key. Many tools let you pass the company or visitor identifier into GA4 as a custom dimension or user property, so you can segment GA4 reports by identified accounts. You can also push GA4 conversion events back into the identification platform so account scoring reflects real behavior.
- Route to action. The point is not a prettier dashboard. It is getting the named account or contact into your CRM and in front of a human, or into an automated play, while the intent is fresh.
If you want a primer on what to do with the company once you have it, our guide to product-qualified leads and the overview of website personalization cover how identified accounts feed scoring and tailored experiences.
What to do instead of fighting GA4
A practical sequence if you are starting from a clean GA4 setup and want company visibility:
- Confirm GA4 is capturing your key events correctly first. Identification is only useful if you also know what those accounts did on site.
- Pick an identification layer based on whether you need account-level or contact-level data. If sales needs to email a person, account-level alone will frustrate them.
- Check match rates honestly. Ask any vendor for their match rate on B2B traffic and treat numbers above 60 percent with skepticism. Higher claims usually mean looser matching that produces wrong companies.
- Wire the output into your CRM and your alerting, not just a separate dashboard. The fastest follow-up wins the deal.
- Use GA4 to validate. Once identified accounts flow in, segment GA4 to see which sources bring in the best-fit companies, then double down there.
How Abmatic AI handles this
Abmatic AI is the identification layer that GA4 is missing, and we are direct about the division of labor. GA4 measures. Abmatic AI tells you who.
Abmatic AI uses reverse-IP plus contact-level and account-level identity resolution to de-anonymize the companies and the people behind your anonymous traffic. It then enriches each one with firmographics and intent, scores the account, and routes it into your CRM or an agentic play (chat, outbound, personalization) so the signal actually reaches a human while it is warm. The recurring problem for B2B teams is that most demand is anonymous and the buying signal never surfaces. GA4 is part of why: it is doing exactly what it was designed to do, which does not include telling you that an engineer at a target account read your pricing page twice this week.
We are not replacing Google Analytics, and you should not turn it off. Run GA4 for trends and attribution, run Abmatic AI for identity and action, and connect the two. If you have outgrown Clearbit-style enrichment or want a single platform instead of stitched point tools, see our take on Clearbit alternatives.
Frequently asked questions
Can GA4 show which companies visit my site?
No. Google Analytics 4 has no company or organization dimension and never exposes the visitor IP address that would allow company resolution. It reports anonymized, aggregate behavior and city-level geography at most. To see company names, you need a separate reverse-IP or de-anonymization tool running alongside GA4.
What happened to the GA4 network/ISP dimension?
The old Universal Analytics "Network Domain" and "Service Provider" dimensions do not exist in GA4 at all. Even in the old days they reported the visitor's internet service provider or hosting company, not their employer, so they showed mostly residential ISPs, carriers, and "(not set)" rather than usable company names. They were never a reliable source of company identification.
How do I see what companies visit my website?
Add a reverse-IP visitor identification tool to your site. It captures the visitor IP, matches it against a corporate IP database, and returns the company name, domain, and firmographics. Expect match rates around 20 to 50 percent on typical B2B traffic, since home and mobile visitors cannot be resolved to a company. To also get named contacts, use a platform that does contact-level resolution.
Is identifying visitors via GA4 possible at all?
Only for visitors you already know. If a user logs in or submits a form, you can pass your own user ID into GA4 and join it to CRM data. For the anonymous majority who never convert, GA4 cannot help, and you need an identification layer. You can then feed the identified company back into GA4 as a custom dimension to segment your reports.
Does adding company identification break GA4 or violate its terms?
Running a separate identification script alongside GA4 does not break GA4. Keep the two systems separate at the data layer, do not push personally identifiable information into Google Analytics (that does violate Google's terms), and pass only a non-personal company identifier as a custom dimension if you want to segment. Handle consent and regional privacy rules through your identification vendor and your consent management platform.
