Our customers
51Degrees works with publishers of all sizes to enhance user experience, drive better advertising yields, and manage the impact of bots and AI harvesting.
From an independent local newsbrand looking to monetize the use of their content by AIs through to a global publisher looking to maximize their CPMs through enhanced advertising data, 51Degrees can support publishers across the board.
Our products
51Degrees offers a range of precision data and tools to help publishers grow revenue and protect their content.
- Device Detection. 51Degrees' Device Detection can give you key information about the device being used to access your service, from the make and model through to its age and price band. This provides the information you need to optimize service delivery, guaranteeing fast loading pages that perform well in search as well as enabling content and advertising enrichment and targeting options.
- IP Intelligence. IP Intelligence can give you a nuanced insight into the approximate location of a device accessing your website, letting you personalize content and advertising services. As well as enriching the advertising data that you can share with the supply chain via Prebid, thus driving better ad yield, this also enables you to deliver personalized content, encouraging greater engagement and loyalty.
- Bot management. 51Degrees offers a full suite of tools for managing bots on your site. Its range of crawler identification properties allows publishers to filter the bots they do want, such as search engines that drive traffic, and the ones that they don't, such as AIs that take content without permission. Additionally, using the Movement for an Open Web's Search Only Contract, 51Degrees can help implement and manage simple terms and conditions that enable you to easily charge AIs that use your content without permission.
“We chose 51Degrees to supply the device database for Seznam.cz because it delivers stable up-to-date information, high performance, and the flexibility to include our own rules. A great benefit is the NGINX API that will help us integrate the new solution into our systems.”
Tomáš Werner
Seznam
48%
of mobile websites pass Google's Core Web Vitals for loading, responsiveness, and visual stability, according to the HTTP Archive Web Almanac 2025.
9%
increase in CPMs from enriching advertising inventory with 51Degrees' data, in pre-release trials of our Prebid module.
13%
of website sessions (not total traffic) came from AI bots in May 2026, up by more than 60% in a year, according to 51Degrees' analysis.
3 ways to increase ad revenue and manage crawler traffic
Richer device data in every OpenRTB auction
Most bid requests arrive without a full device description. We add the make and model, screen details, price band, and operating system, together with a verified 51Did, before the auction starts.
Bidders get more device detail. That extra context can increase bid density and CPMs.
"device": {
"devicetype": 4,
"make": "Samsung",
"model": "Galaxy S25",
"os": "Android",
"osv": "15",
"w": 1080,
"h": 2340
}
Who it serves. Publishers, SSPs, DSPs, and exchanges enriching the bidstream.
Pairs well with Prebid bidstream enrichment, for adding the device data through Prebid.
Integration time. One sprint in your bid path.
Ingredients, 17
- HardwareVendor
- HardwareModel
- DeviceType
- PlatformName
- PlatformVersion
- PlatformVendor
- BrowserName
- BrowserVersion
- NativeBrand
- NativeModel
- ScreenPixelsWidth
- ScreenPixelsHeight
- PixelRatio
- PriceBand
- ThirdPartyCookiesEnabled
- HumanConfidence
- 51Did
Hero ingredient. HumanConfidence Know how likely it is that a person will see your ad.
- Deploy the 51Degrees Pipeline API in your bid path
- Add the device properties and 51Did to the OpenRTB request
- Send the enriched request to bidders
- Track bid density and CPMs after adding the data
Chef's tip. A reduced User-Agent gives bidders less device detail. Add the missing context to the request.
Tell each crawler which uses of your pages you allow
Crawlers collect pages for different uses. Some build a search index that sends you visitors, while others train AI models that answer questions using your content. robots.txt tells named crawlers what you allow, but new crawlers appear every month.
Choose the uses you allow and our robots.txt generator writes the file for you. It emails a new version when crawlers or their uses change.
Who it serves. Publishers, retailers, and any website whose pages crawlers collect.
Pairs well with Suspicious traffic management, for investigating visits from crawlers that ignore your file.
Integration time. 10 minutes, with no code.
Ingredients, 4
- IsCrawler
- CrawlerName
- CrawlerUsage
- CrawlerProductTokens
Hero ingredient. CrawlerUsage Choose whether crawlers can use your pages for search indexing or AI training.
- Choose the uses you allow on the robots.txt generator
- Publish the file at the root of your website
- Replace it when we email you an update
- Compare CrawlerUsage on each request with the uses allowed in your file
Chef's tip. Keep the email address current, because the generator sends a new file when crawlers or their uses change.
Filter non-human traffic before you spend on it
Start with the crawler properties to identify traffic that gives its name and purpose. Use Human Confidence to decide how to handle the remaining visits before counting them as ad impressions. The network properties also let you review traffic from VPNs, proxies, and data centers.
Who it serves. Teams checking bot traffic in analytics and ad spending.
Pairs well with Spot the fake, for a closer look at the device in a suspicious request.
Integration time. 30 minutes in any Pipeline API integration.
Ingredients, 10
- IsCrawler
- CrawlerName
- CrawlerUsage
- CrawlerProductTokens
- IsArtificialIntelligence
- HumanConfidence
- IsVPN
- IsProxy
- IsHosted
- HumanProbability
Hero ingredient. HumanConfidence Know how likely it is that a person will see your ad.
- Check IsCrawler on every request
- Filter named crawlers according to their name and usage
- Use IsArtificialIntelligence to identify AI traffic
- Use HumanProbability or the HumanConfidence property to review the remaining traffic
Chef's tip. Check named crawlers first, then use Human Confidence to decide how to handle the remaining traffic.
Start with your revenue or crawler problem
Each recipe explains the business use, followed by the properties and steps your developers need. It also includes a link to create a Resource Key.
