Soko
Soko
The Fair Marketplace
Back to Docs
Quickstart

Getting Started with Soko

A quick guide to integrating your publisher inventory with the Soko marketplace.

Overview

Soko enriches your existing supply with identity resolution, dynamic pricing, and automated deal creation. You don't replace anything — Soko sits alongside your existing stack.

Prerequisites

  • Publisher inventory serving programmatic ads
  • Willingness to enable identity resolution

Integration Steps

1. Connect Your Inventory

Contact the Soko team to begin the integration process. We'll work with your team to establish the connection with zero disruption to your existing workflows.

2. Enable Identity Resolution

Soko needs access to device and session signals from your inventory. We'll configure identity resolution on your supply, enriched with household-level data from trusted data partners.

This step typically takes 2-3 days and requires no changes to your ad server or page tags.

3. Activate Intelligence

Once connected, Soko begins processing your bid stream — mapping your content, resolving identities, discovering audience segments, and generating pricing recommendations.

Initial results typically appear within the first week.

4. Run Launch Readiness Checks

Before enabling full demand, run a short readiness pass with your Soko team:

  • Confirm placement-to-opportunity mapping is complete
  • Validate request/response capture for filled and no-fill cases
  • Assign owners for monitoring and incident response

5. Review and Activate

The Soko dashboard shows your yield analysis, discovered audience segments, and recommended actions. You review and activate:

  • Dynamic floor pricing (auto-adjusting or approval-based)
  • PMP deals mapped to your exchange partners
  • Audience segment packaging for buyer access

Next Steps

Integration Placement Note

Use VAST tags in your ad delivery stack, not on your marketing website.

  • Configure VAST in your player/ad-server integration where pre/mid/post opportunities are requested.
  • For server-to-server flows, place VAST calls in the ad request service that forwards listener context.
  • Keep website pages focused on documentation and onboarding guidance only.