> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.pixalate.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pixalate.com/_mcp/server.

# CTV and OTT reporting

> How Pixalate Analytics defines OTT and CTV, classifies traffic by the device the ad was served on, detects server-side ad insertion (SSAI) and decides whether SSAI traffic is invalid, plus common CTV IVT types.

Pixalate classifies over-the-top (OTT) advertising by the **device the ad was shown on**, not by the content being watched. This page explains the definitions, how mirrored and cast content is classified, and how Pixalate handles server-side ad insertion (SSAI), which is common in connected TV (CTV).

## OTT and CTV

Pixalate's definitions generally follow the IAB Tech Lab's CTV and OTT definitions.

| Term        | Meaning                                                                                                                                                                                                              |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OTT         | "Over-the-top": accessing TV content without a regular TV set-top box. The content is delivered over an internet connection rather than through a traditional cable or broadcast provider.                           |
| OTT content | Content that can be consumed on many devices, including desktops, laptops, mobile devices and CTV devices.                                                                                                           |
| CTV device  | Any device that isn't a desktop, laptop or mobile device and is used to consume OTT content. Examples include smart TVs, Apple TV, Chromecast, PlayStation, Xbox, Amazon Fire TV sticks and other streaming devices. |

In short, CTV describes the **device** connected to the internet: either a TV with internet capabilities or a device that connects to the internet and uses a TV to display content. OTT describes the **content** delivered over the internet, which can also reach mobile devices and browsers.

Pixalate avoids the term "OTT device", because it mixes the two ideas.

## How traffic is classified

Pixalate categorizes OTT ad inventory based solely on the device on which its measurement tags fire.

| Scenario                                                                     | Classified as                                                                           |
| ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Watching Sling TV on a smartphone                                            | Mobile. It's OTT content, but not on a CTV device.                                      |
| Watching Sling TV on an Apple TV                                             | CTV                                                                                     |
| Watching on a smart TV                                                       | CTV                                                                                     |
| Mirroring a laptop to an Apple TV while watching OTT content                 | The laptop, not CTV. The ad is served on the laptop, so the laptop is the device.       |
| Pressing **Cast** in YouTube on a laptop to send the content to a Chromecast | CTV. The Chromecast becomes the primary device, so ads it serves are classified as CTV. |

Mirroring and casting differ in which device serves the ad. When you mirror, the laptop still plays the content and serves the ads, and the TV only displays the laptop's screen. When you cast, the streaming device, such as Chromecast, takes over through its integration with the app.

## MRC accreditation for CTV

Pixalate is currently MRC accredited for OTT / CTV in the following areas:

* Display Served Impressions
* Video Served Impressions
* SIVT detection and filtration for both Display and Video Impressions

For Pixalate's full, current accreditation scope, see [MRC accreditation](/trust/mrc-accreditation).

## Server-side ad insertion (SSAI)

SSAI, also known as dynamic ad insertion or ad stitching, delivers ads from the server side. Traditionally, video content comes from a content delivery network (CDN) on the server side, while video ads come from a third-party ad server on the client side. With SSAI, the video provider stitches the content and the ads together on the server side.

Impressions are typically tracked on the client side: a tracking pixel in the creative fires when the creative renders. SSAI makes this more complex, depending on the architecture, because:

* The proxy server takes over some client functions, such as firing tracking pixels on behalf of the client.
* The standard HTTP headers that identify a client, such as the IP address and user agent, belong to the proxy server instead. Additional headers, which are currently optional, are needed to pass the user's information to third-party measurement companies.

### Legitimate use

Video content providers use SSAI for a more seamless viewing experience. If CTV ads keep buffering, viewers may move back to traditional TV. SSAI serves the content and ads without interruption.

### How fraudsters use SSAI

Mismatched IP addresses have traditionally been a risk signal, but in CTV there's a legitimate reason for them: SSAI. Fraudsters use this. The easiest way to change an IP address is through a proxy server, so fraudsters hide behind SSAI and spoof or fake inventory by altering the information in the ad request. Because the request comes from a proxy, it's hard to verify that the information is legitimate.

Depending on the SSAI architecture, an SSAI proxy server may compose all HTTP requests on behalf of the end user. Machines can act as proxies and fake the user's request headers, such as `X-Forwarded-For`, `X-Device-User-Agent` and the `Forwarded` HTTP extension. SSAI detection that relies only on `X-Forwarded-For` headers is therefore extremely error prone.

### How Pixalate detects SSAI and decides whether it's IVT

Pixalate doesn't treat all SSAI as invalid traffic (IVT), because SSAI is used for both legitimate and fraudulent purposes. It decides for each transaction.

When Pixalate detects SSAI, it takes an additional step to determine whether the traffic is invalid. Pixalate has created and analyzed more than 30 composite signals that characterize the behavior of an SSAI server and its interactions with the publisher (for example, apps) and the client (for example, device ID). These signals let Pixalate tell real SSAI from fake, estimate the reputation of an SSAI server, and determine whether an SSAI proxy generates valid or invalid traffic.

To see your SSAI traffic in reports, use the [SSAI metrics](/analytics/metrics#server-side-ad-insertion-ssai).

## Common IVT types in CTV

| Reported type          | What it looks like in CTV                                                                                                                                                           |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Proxy                  | Invalid SSAI. For example, the client's IP doesn't match the IP detected when the ad renders, and the proxy IP is determined to be invalid.                                         |
| Video Impression Fraud | Statistically significant outlier user behavior, detected with Pixalate's algorithms and machine-learning models. It can occur on any device, including CTV.                        |
| Datacenter             | Traffic from an IP address identified as a data center. For example, hundreds of jailbroken CTV devices set up to play content continually on a specific app or group of apps.      |
| IP Obfuscation         | A proxy IP is discovered, but a cookie extends to a statistically inflated number of unique device IDs or IPs. This can be a sign of a desktop device masquerading as a CTV device. |
| App Spoofing           | Traffic from apps that appear to be spoofed, at the impression level or at more macroscopic levels.                                                                                 |

For each type's class and its match in IVT Taxonomy 2.0, see [Reported IVT types](/analytics/ivt-types).

## Protect CTV traffic

* **Measure:** Analytics detects and monitors CTV IVT in your traffic. See [Run and customize reports](/analytics/reports).
* **Block pre-bid:** the [CTV device ID feed](/data-feeds/ctv-device-ids), [IP block lists](/data-feeds/ip-block-lists) (IPv4 and IPv6), [High Risk CTV Apps 2.0](/data-feeds/high-risk-ctv-apps), [delisted CTV apps (DEFASE)](/data-feeds/defase), [malformed CTV bundle IDs](/data-feeds/malformed-ctv-bundle-ids) and [MFA CTV apps](/data-feeds/mfa).
* **Research apps:** see [CTV bundle IDs](/mrt/ctv-bundle-ids) in the Media Ratings Terminal (MRT).

## Related

* [Reported IVT types](/analytics/ivt-types)
* [Metrics](/analytics/metrics)
* [MRC accreditation](/trust/mrc-accreditation)

Questions? Contact [support@pixalate.com](mailto:support@pixalate.com).