To properly deliver and track ads through the Adtelligent Ad Server, certain parameters must be passed in each ad request. These parameters ensure accurate targeting and reporting. Below is a breakdown of required parameters for CTV/In-App and Desktop/Mobile Web traffic types.
📌 Parameter Table
Parameter | CTV / In-App | Desktop / Mobile Web | Description | Required |
|---|---|---|---|---|
width | ✔️ | ✔️ | Ad slot width in pixels | Yes |
height | ✔️ | ✔️ | Ad slot height in pixels | Yes |
ua (User Agent) | ✔️ | ✔️ | User device’s User Agent string | Yes |
uip (IP address) | ✔️ | ✔️ | User IP address | Yes |
app_name | ✔️ | — | Application name (for in-app/CTV traffic) | Yes |
app_bundle | ✔️ | — | App bundle identifier (e.g., com.publisher.app) | Yes |
idfa (Device ID) | ✔️ | ✔️ | Advertising ID (for in-app/CTV) or equivalent identifier for web | Yes |
app_store_url | ✔️ | — | Link to app store page (for app verification) | Yes |
cb (Cachebuster) | — | ✔️ | Random number to prevent ad caching | Yes |
content_page_url | — | ✔️ | Full URL of the page where the ad is displayed | Yes |
📌 Example Ad Request URLs
Example for CTV / In-App:
Example for Desktop / Mobile Web:
📌 Integration Notes:
Do not omit required parameters — missing them may result in no ad fill or inaccurate reporting.
For CTV/In-App traffic, passing idfa or platform-specific identifiers (e.g., gaid for Android) is highly recommended for better demand matching.
Always use a cachebuster (cb) on web to avoid creative caching by browsers or CDNs.
Ensure page URLs and app bundle names are URL-encoded where necessary.
IP addresses and User Agents must be real values for proper geo-targeting and device-based targeting.