Device Data Service
The Device Data Service (DDS) enables us to gather additional information about the device from which the request originated, utilizing the User Agent. This information is then used to update the Device object before forwarding it to the DSP and recording statistics.
If the service identifies the device as non-human, we filter such requests with the respective reason.
The logic for filling each field is as follows:
make; model: We remove the value from the request and use the one from the service. If DDS does not provide a value, we do not transmit the parameter.
os: We always use the value from DDS for both the event and the DSP request. If the value does not match the predefined OS list, we designate it as "Other" for the event and use the DDS value for the DSP request. If DDS doesn't provide a value, we designate it as 'Unknown' for the event and do not set the parameter in the output request.
osv: If DDS does not provide a value, we transmit the value from the request to the DSP; otherwise, we transmit the value returned by DDS.
h; w: If DDS provides "h" and "w" values, we use them; otherwise, the values from the request will be transmitted.
devicetype: We always use the value from DDS. If it doesn't match the predefined DeviceType list, we designate it as "Other" for the event and do not set the parameter for the DSP request. If DDS doesn't provide a value, we designate it as 'Unknown' for the event, and do not set the parameter for the DSP request.
ppi: We remove the value from the request and use the one from DDS. If DDS does not provide a value, we do not transmit the parameter.
List of Operating Systems defined with DDS:
- Android
- Chrome OS
- Firefox OS
- Linux
- Nintendo OS
- PlayStation OS
- Roku OS
- Tizen
- Wear OS
- Windows
- Windows Mobile
- Windows Phone
- iOS
- iPadOS
- macOS
- tvOS
- watchOS
- webOS
List of DeviceTypes defined (as per OpenRTB 2.6):
- Mobile/Tablet - General
- Personal Computer
- Connected TV
- Phone
- Tablet
- Connected Device
- Set Top Box
- OOH Device