Analytics tools count a visit once the tag fires. Most leave out crawlers that announce themselves and count everything else. An AI agent driving a real browser loads the page and runs the JavaScript like anyone else, so it's counted as a user, and a rise in visits may have nothing to do with people.
You can split that out yourself by sending Human Confidence and the crawler properties to your analytics as custom dimensions. Then you can filter any report by them. We record it this way for every visit to 51degrees.com.
Get a License Key with Human Confidence: buy the Pro plan online for the cloud service, or talk to us about the Bespoke plan to run it on your own servers in a Docker container. Compare plans.
What to send🔗
| Property | What it tells you | Example values | Custom dimension name |
| HumanConfidence | How likely it is that a person is looking at the page. | High, Medium, Low, Unknown | derived_humanconfidence |
| IsCrawler | Whether the request says it's an automated process. | true, false | device_iscrawler |
| CrawlerName | Which crawler. | OpenAI GPTBot, NotCrawler | device_crawlername |
| CrawlerUsage | What the crawler uses your content for. | Train, Input, Index, Search, N/A | device_crawlerusage |
| IsArtificialIntelligence | Whether the crawler works for an AI purpose. | True, False, N/A | device_isartificialintelligence |
Each name is the engine, then the property, in lower case. The 51Degrees WordPress plugin uses the same names, so a WordPress site and a hand-coded one can share one set of dimensions.
What your tool calls a custom dimension varies. Matomo calls it a custom dimension, Adobe Analytics uses an eVar or a prop, and Google Analytics 4 takes an event parameter that you register as a custom dimension.
Get the values into the page🔗
- Create a Resource Key from this link. It opens with the properties in the table, and the ones Human Confidence needs, already ticked. Add the License Key from your plan.
- The key sits in your page where anyone can read it, so limit it to your own domains. Otherwise someone else could use it and spend your requests.
- Add the 51Degrees script after your analytics tag and pick up the values when it finishes.
- Hand
valuesto whatever call your tool uses for custom dimensions or event properties. For GA4 that's onegtagevent, and Google Analytics 4 (GA4): human and bot traffic walks through it.
What to look at🔗
Put Human Confidence next to the reports you already read.
- Filter conversions to High to get a conversion rate for people, and compare it with your overall rate.
- Chart Medium and Low by month and by page, alongside High.
- Use CrawlerName, CrawlerUsage and IsArtificialIntelligence to see which crawlers read which pages, and whether they index, train or answer questions with them. Then set your robots.txt rules from what you see.
This chart comes from a demonstration site, with known crawlers removed. From July, Low and Medium grew and High fell.
Crawlers that never run the page🔗
Plenty of crawlers don't run JavaScript. They never reach your tag, so your analytics never counts them. IsCrawler picks up the ones that do run it. You can keep them in, to see which AI crawlers read your pages, or send the values only when device.iscrawler is false. Either way, an agent that hides what it is still gets counted. Filter on Human Confidence to separate those visits from people.
Find out more🔗
- Google Analytics 4 (GA4): human and bot traffic
- Deploy Human Confidence with the cloud, to act on the value on your server
- Client-side Evidence, for how the 51Degrees script works in the browser
- Human Confidence in the property dictionary
Human Confidence needs the Pro plan, which you can buy online, or the Bespoke plan for your own servers. Ask us about Bespoke through the contact page.
