\r\n

51Degrees API Documentation  4.2

Search

Documentation

• Quick Start
• Device Detection

Device Detection

C C++ C# Java Node.js PHP Python Varnish Nginx

Select a language.

C does not have a Pipeline implementation or the ability to use the cloud-based version of Device Detection. To get started with C device detection on-premise:

1. Clone the GitHub repository.
2. Ensure you have Git LFS installed. The device data files are large binary files that can cause problems if stored in a Git repository directly so Git LFS is used.
3. Ensure all submodules are checked out by running git submodule update --init --recursive in the repository.
4. Follow the installation instructions to get set up with the project.
5. Follow the linked example here: Getting Started.
6. (optional) Obtain a license key by starting a free trial and download a data file with access to more devices and properties, see our pricing page for details.

C++ does not have a Pipeline implementation or the ability to use the cloud-based version of Device Detection. To get started with C++ device detection on-premise:

1. Clone the GitHub repository.
2. Ensure you have Git LFS installed. The device data files are large binary files that can cause problems if stored in a Git repository directly so Git LFS is used.
3. Ensure all submodules are checked out by running git submodule update --init --recursive in the repository.
4. Follow the installation instructions to get set up with the project.
5. Follow the linked example here: Getting Started.
6. (optional) Obtain a license key by starting a free trial and download a data file with access to more devices and properties, see our pricing page for details.

Standalone pipeline / off-line processing

1. Install the FiftyOne.DeviceDetection package via Nuget.
2. Follow the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.

ASP.NET Core integration.

1. Install the FiftyOne.DeviceDetection and FiftyOne.Pipeline.Web packages via Nuget.
2. Follow the web example to add the Pipeline middleware.
3. Configure the pipeline using the configuration from the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.
4. (optional) Configure client-side evidence to get better results. Particularly for iPhone and iPad.

ASP.NET integration.

1. Install the FiftyOne.DeviceDetection and FiftyOne.Pipeline.Web packages via Nuget.
2. Follow the web example to add the Pipeline middleware.
3. Configure the pipeline using the configuration from the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.
4. (optional) Configure client-side evidence to get better results. Particularly for iPhone and iPad.

Standalone pipeline / off-line processing

1. Install the com.51degrees.pipeline.device-detection package via Maven.
2. Follow the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.

Web servlet integration.

1. Install the com.51degrees.device-detection and com.51degrees.pipeline.web packages via Maven.
2. Follow the servlet example to add the Pipeline filter.
3. Configure the pipeline using the configuration from the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.
4. (optional) Configure client-side evidence to get better results. Particularly for iPhone and iPad.

Spring MVC integration.

1. Install the com.51degrees.device-detection and com.51degrees.pipeline.web packages via Maven.
2. Follow the Spring MVC example to add the Pipeline filter.
3. Configure the pipeline using the configuration from the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.
4. (optional) Configure client-side evidence to get better results. Particularly for iPhone and iPad.

1. Install the fiftyone.devicedetection package from NPM.
2. Follow the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.

Cloud

This implementation of device detection makes use of 51Degrees' cloud service. In PHP, the cloud version is much easier to work with than the on-premise implementation as well as having much lower memory and CPU requirements. However, it is slower due to Internet latency. If you want faster detections, you should consider on-premise.

1. Install the 51degrees/fiftyone.devicedetection package using Composer.
2. Follow the Cloud Example.

On-premise

Device detection processing is performed locally using a data file that must be kept updated. Due to the restrictions imposed by Composer and Packagist, we cannot supply the on-premise engines through the usual package management ecosystem. Instead, you'll need to clone the repository from GitHub and follow the instructions there in order to build and use the on-premise implementation.

1. Install the fiftyone_devicedetection package from pypi.
2. Follow the appropriate example from the options below:
   • Cloud Example - Negligible processing and memory overhead but slower due to Internet latency.
   • On-Premise Example - Device detection processing is performed locally using a data file that must be kept updated.

Varnish does not have a Pipeline implementation or the ability to use the cloud-based version of Device Detection. To get started with Varnish device detection on-premise:

1. Clone the GitHub repository.
2. Ensure you have Git LFS installed. The device data files are large binary files that can cause problems if stored in a Git repository directly so Git LFS is used.
3. Ensure all submodules are checked out by running git submodule update --init --recursive in the repository.
4. Follow the installation instructions to get set up with the project.
5. Follow the linked example here: Getting Started.
6. (optional) Obtain a license key by starting a free trial and download a data file with access to more devices and properties, see our pricing page for details.

Nginx does not have a Pipeline implementation or the ability to use the cloud-based version of Device Detection. To get started with Nginx device detection on-premise:

1. Clone the GitHub repository.
2. Ensure you have Git LFS installed. The device data files are large binary files that can cause problems if stored in a Git repository directly so Git LFS is used.
3. Ensure all submodules are checked out by running git submodule update --init --recursive in the repository.
4. Follow the installation instructions to get set up with the project.
5. Follow the linked example here: Getting Started.
6. (optional) Obtain a license key by starting a free trial and download a data file with access to more devices and properties, see our pricing page for details.

Generated by doxygen 1.8.15