With Device Detection you can input a User Agent, a TAC value, or a native app key. For Geolocation, latitude and longitude will give you the location result.
Data files for our Big, Bigger, Biggest, and Bespoke solutions are produced Monday through Thursday. Data files for our free service are produced once a month. This schedule may be disrupted by UK bank holidays. When this does happen there will be prior warning in the form of a blog or email.
If you use our cloud, the data is automatically updated for you. For on-premise users the data file is available on GitHub.
All of the data files along with the CSV files are located on our Distributor, please have your License Key to hand.
It's great that you want to remove the manual process of pulling the data file. Simply supply a License Key in your call to the Device Detection Pipeline or Engine builder and automatic updates for the Device Detection database will be enabled.
Usage sharing helps us maintain the accuracy of the data file via machine learning. We get data on all the devices, browsers, and operating systems you see in your ecosystem. When using the 51Degrees cloud service or on-premise pipeline, usage sharing is enabled by default. Usage sharing can only be disabled when using the on-premise pipeline.
Our Cloud Configurator contains all available properties. The properties you will need to pay for are shown with a dollar icon.
On rare occasions, we mark some of our properties as obsolete – this is dependent on their relevancy and popularity. Once a property has been marked as obsolete, it will remain in the data files but any new devices will contain default values for that property. If a property you frequently use has been marked as obsolete and is still required for your use case, please let us know and we may re-evaluate our decision.
Hopefully the answer is just hiding somewhere, but if you are having trouble then please contact us here.
All of our metadata can be found on our property dictionary. Can't find a certain property? Contact us and we'll help you out.
You can check out our handy migration guides for Scientiamobile, DeviceAtlas, and OpenRTB here.
We've created a table where you can view our published figures against those that our competitors choose to share in the public view.
Yes! We use a third-party billing service to handle all credit card orders for your monthly and annual subscriptions. If you would like to enter a bespoke contract, then that is still handled by us. Please contact us if you would like to set up a bespoke order.
We try to make it easy for customers to purchase and renew their contracts. You can pay by credit card instantly, or you can place a purchase order to receive an invoice for bespoke orders. Details are then supplied on the invoice on how to pay via bank transfer. Offline billing is available to all subscription levels.
To cover additional costs in the transaction process there is a $75 fee. Alternatively you can pay by credit card to avoid these fees.
American Express, VISA, and Mastercard are all supported.
There are a few reasons your User Agent might not be detecting correctly. It could be a brand new device or browser in development stage, or your data file could be out of date. If you have a User Agent that you'd like more information on, test it with our User Agent Tester. If there is no data on that particular User Agent, please email it to firstname.lastname@example.org and we'll investigate.
The SupportedBearers property values do not explicity give which generation of mobile networks the device supports, but rather it lists the radio technologies supported by the device for each generation of mobile networks. For example, 'LTE' (Long Term Evolution) for 4G and 'NR' (New Radio) for 5G.
We most likely haven't seen that exact User Agent string across all of our global deployments, therefore the algorithm is trying to make the closest match. Send us any data that has a difference higher than 15 and we'll investigate.
51Degrees provides a free public Lite data file which can be used for User Acceptance Testing. We no longer produce separate UAT data files.
You can reach us via GitHub, email, or our contact us form. We'll be happy to chat.
All of our documentation is available on the link below.
This depends on your target development language, but in .NET and Java you can switch easily between on-premise and cloud by calling the 'UseOnPremise' or 'UseCloud' Pipeline builder methods. For enterprise products, you must have a License for both on-premise and cloud.
You can refer to one of the many examples in our documentation.
A Pipeline is a customizable data processing system. At the most basic level, input data is supplied in the form of evidence. One or more flow elements in the Pipeline then perform processing based on that evidence and optionally, populate data values that are required by the user.
We support C, C++, C#, Java, Node, PHP, Python, Varnish, and NGINX. For further language-specific information, visit the documentation below.
For our free cloud service a License Key is not required and you can gain access to all of our free properties. If you want to trial or use one of our paid-for cloud subscriptions you will need a License Key. Progress through our pricing page to obtain a License Key.
Yes! Please keep your Resource Key in a safe place, this is helpful for troubleshooting if you come across an issue.
For those on our cloud solution, you will automatically be using the latest data. To start collecting UA-CH data, you will need to regenerate your Resource Key with our Cloud Configurator to include the three Accept-CH Headers for hardware, platform, and browser.
Review the products available on our pricing page to find the best plan for you. Once you have signed up for a trial and received a License Key, follow our migration documentation below to get started.
Enabling UA-CH will be dependent on how your configuration is called, e.g., via the Pipeline API, server-side code, or client-side code. We've described these various scenarios together with examples within our documentation. You will need to be using version 4.4.0 or later of our service to enable User Agent Client Hints.
Yes. In fact, this is recommended. The device detection algorithm will use the UA-CH data where possible. However, if a match cannot be found for the supplied UA-CH values, then the User Agent will be used as a fallback. See the Getting Started examples for a demonstration of how to supply UA-CH evidence in parallel with User Agents
It’s difficult to provide a concrete answer due to Google’s tendency to change the timeline to suit their needs. We are working towards the timeline provided by Google, but this is subject to change. Please refer to their official timeline for the latest dates.
In order to start collecting UA-CH data, your Resource Key needs to be regenerated to include the three Accept-CH Headers for hardware, platform, and browser.
The User Agent tester parses the information from the submitted User Agent (UA) – there is no exchange between the browser and server. To obtain User Agent Client Hints (UA-CH) data, the information is exchanged between the browser and server – it's not part of the UA string. To identify the UA-CH that are sent with your UA string, we recommend you use our Me page.
The 51Degrees plugin is free and open source. However, our Cloud Configurator contains both free and paid properties. As you select your chosen properties, the paid properties are shown with a dollar icon. You can see our various pricing tiers on our pricing page.
The 51Degrees plugin should not interfere with other plugins. You can continue using your installed plugins to send custom dimensions or view analytics data.
If you're experiencing any issues, use the WordPress.org support forums. If you have a technical issue with the plugin you can raise the issue with us directly by opening an issue on the GitHub repository.