---
title: "Checklist: SSP installation"
slug: "ssp-checklist"
updated: 2026-05-06T05:59:24Z
published: 2026-05-06T05:59:24Z
canonical: "docs.grassfish.com/ssp-checklist"
---

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

# Checklist: SSP installation

Use the following checklist to review the key steps of the SSP installation and ensure that you have completed all relevant tasks.

## System requirements

- [ ] You are using at least IXM One version 11.11.0 and Grassfish Server version 11.11.0.
- [ ] You have the .NET 6 Hosting Bundle installed on the server if you are using a version prior to 11.18.

[Read more about the system requirements here](https://docs.grassfish.com/docs/install-ssp#system-requirements).

## Installation

- [ ] You have installed and connected the AdServing API on IIS.
- [ ] You have correctly set the path to the user.config and master.config files in the AdServing API.
- [ ] You have configured the IIS Application Pool for the AdServing API and set the idle timeout to 0.
- [ ] You have configured the config.json file.
- [ ] You have made general settings for the AdServing API in the master.config file.
- [ ] You have defined the SSP provider in a separate SSP configuration file.

[Read more about the installation steps here](https://docs.grassfish.com/docs/configure-server-ssp).

## IXM One setup

- [ ] You have created an SSP-specific spot group.
- [ ] You have created and configured an SSP playlist.
- [ ] You have created a standard playlist with filler content.
- [ ] You have configured the standard playlist so that it can be interrupted by programmatic advertising.
- [ ] You have created an empty DOOH playlist.
- [ ] You have created a program scheme and assigned the playlists to it.
- [ ] You have created a category for SSP and assigned it to locations and players.

[Read more about setting up the IXM One here](https://docs.grassfish.com/docs/ixm-platform-setup).

## Special setup for Windows and Linux Player

- [ ] You have installed the DOOHPlayback add-on.
- [ ] You have installed MQTT.
- [ ] You have installed and configured the UDC Importer if you are using DOOHPlayback add-on version 2.5.1 or earlier.

[Read more about setting up the Windows and Linux Player here](https://docs.grassfish.com/docs/configure-winlin-player-ssp).

## Setup for all players

- [ ] You have adjusted the player configuration or configuration group.
- [ ] You have activated SSP on the player or in the configuration group.
- [ ] You have set the airtime ratio for SSP.
- [ ] You have made a `/GetNextSpot` API call via Swagger for testing and received a correct SSP response.
- [ ] You have tested whether an SSP spot is being played correctly on the player.
- [ ] You have verified proof of play and tracking.
- [ ] You have enabled monitoring of player logs and AdServing API logs.

Read more about setting up the [Android Player](https://docs.grassfish.com/docs/configure-android-player-ssp) or the [Windows and Linux Player](https://docs.grassfish.com/docs/configure-winlin-player-ssp).

## Definition of the SSP provider

Ensure that you have specified at least the following information for each provider:

- [ ] SspPriority (request order)
- [ ] SspUrl (SSP endpoint)
- [ ] SspCategoryId (category ID in the IXM One)
- [ ] SspPlaylistId (playlist ID for spot assignment)
- [ ] SspSpotGroupId (spot group ID for uploads)
- [ ] SspServiceUserId (user for SSP uploads)
- [ ] Optional: LiveTag URLs, custom headers, SspType (e.g., Framen or Viooh)

[Read more about configuring the SSP provider in the AdServing API](https://docs.grassfish.com/docs/configure-server-ssp#configure-the-adserving-api).

Universal Data Controller, a system component that manages the import of external data into the IXM system.

An API call or API request is a message to a server that requests an API to provide a service or information.