---
title: "Server-to-Server: Why Append User Agent amd IP Address to Ad Requests?"
slug: "server-to-server-why-append-user-agent-amd-ip-address-to-ad-requests"
updated: 2025-07-04T17:35:12Z
published: 2025-07-04T17:35:12Z
canonical: "help.tritondigital.com/server-to-server-why-append-user-agent-amd-ip-address-to-ad-requests"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.tritondigital.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Server-to-Server: Why Append User Agent amd IP Address to Ad Requests?

Triton Digital needs to have visibility of the user-agent and the IP address of the listener at the HTTP level. With player-to-server implementations, this information comes directly from the player (and thus, the listener). But with server-to-server implementations, it refers to the server, not the listener.

For this reason, server-to-server implementations must be explicit with this information. **You must configure your implementation so that the listener's user agent string and IP address are appended to the ad request**. For more information, see [Ad Request Parameters](/user/docs/od-ad-request-parameters) and [Custom Streaming Environments](/user/docs/custom-streaming-environments) in the *Triton Digital On-Demand Specification.*