How is DeviceAtlas utilized?
DeviceAtlas is used to provide high speed redirection decision-making, to underpin content adaptation solutions, for demanding content delivery and targeting environments such as ad networks, and to support analytics offerings. See here for more information of example use cases.
Does DeviceAtlas have worldwide coverage?
Yes; the wide range of partners of DeviceAtlas helps ensure that coverage is global, and increasingly the growth of worldwide traffic to our own network of mobile properties ensures that intelligence on mainstream and emerging market devices is captured in DeviceAtlas. There are DeviceAtlas customers in over 130 countries, many of whom provide inputs also.
Is DeviceAtlas based on standards?
Yes; DeviceAtlas complies with the recommendations of the W3C Device Description Working Group. For W3C CC/PP, DeviceAtlas leverages the User Agent Profiles that are readily available from OMA.
How Frequent Are The Updates?
The API software is not updated very frequently, we want to make sure that the load on developers is as low as possible. The JSON file is updated daily.
Do you support desktop user agents?
Yes. DeviceAtlas can identify desktop browsers, robots, crawlers and other traffic types through a set of virtual properties, which are Boolean. See the full Property List for more information.
Do you support TVs?
DeviceAtlas includes TVs and set top boxes as hardware types.
Do you track support for secure connections over HTTPS on devices?
Yes, with mobile commerce usage growing exponentially, we feel it is an important property to report on.
Some devices use different User-Agent strings, will you detect them?
The association between a HTTP request and a device is not one to one, but many to one, so yes, we can detect devices that use different user-agent strings and HTTP request headers.
What's the API performance?
We have rigorously tested our API performance. Results are published in the API section for Enterprise API performance and for Cloud API performance.
What are the design priorities for the APIs?
- Speed (a few 10's of ms at start-up, depending on language)
- Throughput (10,000's of recognitions per second)
- An efficient file size for regular updates
Will the API connect to your servers for every request?
For Enterprise customers a compact, lightweight file of our data is placed on your web server. The API offers high speed, optimized access to the data.
For Cloud deployments, the API connects to DeviceAtlas servers, presents the user agent, and receives back the device informationThe UserAgents and associated device data are then cached to identify subsequent requests.
I have my own device profiles, can i merge them into your JSON?
We like to think of DeviceAtlas as the place to share information, knowledge and experience about devices and mobile in general. Our preferred method to collect device data is via our test site, TA-DA.
We have also turned our website in a real read/write website so if you are registered you may add information about devices simply using your web browser. If you have a large amount of data already stored in some database or file such as XML, get in touch with us, because we have some import API's available. As a last resort, if you really cannot share the information because, for example, you do not own it, let us know, because we have a 'Private Data' model which keeps such data in a secure repository, where it is only accessible by the provider.