AI Search

InMobi BURL: IP and User-Agent Signals

InMobi has a unique BURL implementation: BURLs are fired directly from the client side. Since the BURL originates from the client, the HTTP request received by the DSP exposes client-side network and device information, including:

  • The client’s User-Agent
  • The client’s public IP address, available through X-Forwarded-For

A DSP may want to fall back to the client IP observed through the BURL when the IP in the bid request:

  • Is IPv6 while a downstream system or use case requires IPv4
  • Has been truncated
  • Is invalid
  • Is temporarily unavailable because of an outage or processing issue
  • Otherwise fails the DSP’s signal-integrity checks

The same concept applies to User-Agent.

Client information available in an InMobi BURL

Consider the following example from an actual InMobi BURL request:

"user-agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 18_7 like Mac OS X) 
AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148", 
"x-forwarded-for": "59.144.134.146, 10.81.2.10, 127.0.0.1"

The user-agent is the user agent of the client from which the BURL was fired.

In the x-forwarded-for, the leftmost IP address represents the original client IP.

本页内容

最后更新于 : 17 Aug, 2026