---
title: "Checklist: SSP preparation"
slug: "ssp-checklist-preparation"
updated: 2025-07-11T09:45:14Z
published: 2025-07-11T09:45:14Z
canonical: "docs.grassfish.com/ssp-checklist-preparation"
---

> ## 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 preparation

Use the following checklist to prepare for setting up SSP.

## General information and requirements

- [ ] You’ve clarified the objective of the SSP connection (e.g., increase reach, monetize remaining spaces).
- [ ] You’ve identified specific requirements (e.g., reporting, tracking, data protection).
- [ ] You’ve identified target regions or restrictions.
- [ ] You’ve examined alternatives (e.g., DOOH booking function in IXM One).
- [ ] You’ve identified suitable SSPs (e.g., Framen, VIOOH, SSP1).
- [ ] You’ve checked which SSPs or standards (e.g., VAST) are currently supported and suitable.
- [ ] You’re aware that the contract with the SSP provider must be concluded by the customer.

## Considerations for IXM configuration

- [ ] Is IXM One already in use? - [ ] If **no**, a basic setup of IXM One is required.
- [ ] You’ve specified an existing or new spot group for SSP assignment.
- [ ] You’ve determined a playlist to be populated programmatically.
- [ ] You know which category should be used for SSP assignment.
- [ ] You’ve documented all IDs relevant for technical configuration.

## Optional inventory synchronization

- [ ] You’ve clarified whether player or location inventory must be synchronized: - [ ] If **yes**: - [ ] You’ve clarified the synchronization method (SSP retrieves / provisioned by Grassfish). - [ ] You’ve clarified the format or interface. - [ ] If **no**: - [ ] You’ve clarified that the customer manages inventory manually via SSP.

## Technical information from the SSP provider

- [ ] The SSP endpoint is available (e.g., VAST URL, API endpoint).
- [ ] You’ve clarified authentication (token, API key, basic auth, etc.).
- [ ] You’ve checked other technical parameters (if relevant): - [ ] LiveTag URLs are available. - [ ] Custom header is defined. - [ ] SspType is identified (e.g., Framen, VIOOH). - [ ] You have access to technical documentation/specifications.