<< Higher Sales
Quantum Data >>
Hopefully, you're interested in pulling back the curtain on DetectRight. We're happy to oblige: we think DetectRight is a system that looks even better the closer you look at it.
Any system which is used for detecting devices (or storing information about them) has a number of parts chained together: and a chain is only as strong as its weakest link.
Takes incoming information and calculates which of the entries in the device knowledge are applicable. There's a white paper about how DetectRight's detection engine compares to others here
Profile generation engine
Uses the results of the detection engine to produce a profile for output. DetectRight uses a Quantum Data Engine, Quantum Data Trees and Quantum Messages to generate profiles: it's not just a cute name: read about it on the next page here
We offer a customised bulk data service to organisations who would like to bulk load our catalogues into their systems.
The job of the Device Detection engines is to match the website visitor with meaningful results from whatever knowledge sources are available.
Most solutions will include one or more of the following knowledge sources.
A collection of metadata about a device catalogue, such as useragents, UAProfile URLs, TACs or other data. Metadata points to devices or entities. DetectRight has more types of metadata than anyone else, and a bigger library of metadata (which is cleverly compiled to avoid producing gigabyte-size database files).
An indexed collection of devices, each of which can hold information. The industry seems to have settled on assuming there are around 15000 devices in the world, ever. They're wrong. We have over 41,000 handsets, over 4000 tablets and over 3,000 other objects, and the gap gets bigger every day. What's more, we store information about components such as chipsets, CPUs, JVMs, OS Versions, Hardware Platforms, Browsers, Developer Platforms, GPS and more. Our catalogue is capable of holding anything, of any type.
How devices and entities in the data relate to one another: DetectRight models more of these relationships (such as the knowledge that a device contains a certain chipset, browser, or other component) than any other database. Many of the other systems cannot even model these relationships properly because their core infrastructure makes their system incapable of having a system contain more than one component.
Actual capability data covering a subset of possible device characteristics. DetectRight not only contains more raw data than any other system, but the range covered by the data is ten times wider, and even covers datapoints which might not have been named yet, but which may be invaluable in the future.
Override, preference or extended data
There will always be something that an organisation wants to do differently: to change a value of a device, to add new data to it, or make another adjustment.
Most device detection solutions allow this to happen, either with local files you create yourself, or from server-side storage of private data. However, only DetectRight has four different override methods at various levels of the data, from a local end-patch to a deep customisation of the system data.
Capabilities that happen when devices or entities interact: handling this realistically is more challenging than overlaying data onto other data - DetectRight is capable of building an interactive, dynamic virtual device to mirror the one being seen, taking into account component versions, the overall relative importance of each, and the overall importance of the data coming in. Our Quantum data tree and validation engines also generate new data from incoming data.
Any data specific to the connected user and their device, such as extra headers, or connection metadata.