Publisher Onboarding and Placement Registration

Purpose

This document explains what information and setup steps are typically required when a publisher starts operating through an ad platform.

Key Takeaways

• Publishers must register accounts, sites or apps, and placements before inventory can be sold properly.
• ads.txt and app-ads.txt help disclose authorized sellers, but they do not replace onboarding or placement registration.
• Clear placement identifiers and inventory structure are essential for stable delivery, tracking, and reporting.

Concept Flow

Draft Structure

1. Required onboarding information

• Domain or app information
• Placement or ad slot definitions
• Format information
• App, player, or environment metadata

2. Why placement registration matters

• It identifies where ads can be shown.
• It provides placement context for requests and auction logic.
• It creates keys for logging, reconciliation, and reporting.

3. Relation to ads.txt

• ads.txt and app-ads.txt disclose authorized selling relationships.
• Actual site, app, and placement registration still happens in SSP onboarding and operations.

Prerequisite Document

• Ad Request vs Bid Request

Next Document

• Understanding ads.txt and app-ads.txt