# SPO.expert — Complete Reference

> SPO.expert is an agentic AdTech platform — an AI agent that analyzes, validates, and optimizes programmatic supply paths, turning raw impression data into clear, actionable insights. Deterministic IAB rules decide what's verified; AI explains why — and what to do next.

## Company Overview

SPO.expert is a supply path optimization (SPO) platform for the programmatic advertising industry. It shows where a platform's programmatic supply paths leak money, transparency and control — and proves it at impression level.

The platform checks every hop of every supply path against the files that are supposed to authorize it (sellers.json, ads.txt, app-ads.txt) and against the IAB OpenRTB SupplyChain specification, maps the result as an interactive supply-path graph, and turns findings into three action-oriented reports plus an AI analyst that answers questions from the client's own data.

Website: https://spo.expert/
Contact: message the SPO.expert LinkedIn page — https://www.linkedin.com/company/spo-expert/ (there is no contact form; the website stores nothing visitors type)

## What Is Supply Path Optimization (SPO)?

Supply Path Optimization (SPO) is the process of evaluating and streamlining the routes through which digital ad impressions travel from publishers to advertisers. SPO removes redundant intermediaries, reduces fees, and improves transparency in the programmatic supply chain. It is a critical strategy in modern programmatic advertising for both buyers and sellers seeking to maximize return on ad spend.

## Who SPO.expert Is For

Platforms that sit inside the programmatic supply chain and receive inventory from partners ("senders"): SSPs, ad exchanges, ad networks and DSPs — and the AdTech, supply, programmatic and partnerships teams that run them. The platform speaks to the client as a node in the chain: "your senders", "your sellers.json", "publishers that list you as DIRECT or RESELLER".

## The Problem SPO.expert Solves

Every impression that reaches a platform travels through a chain of sellers it didn't choose. Each hop is a fee, a claim and a risk — and most of that chain is declared, not proven. SPO.expert checks every hop of every path against the files that are supposed to authorize it, and shows — impression by impression — where the leaks are:

- **Chains that break before they reach you** — the declared chain never names the client's node, or the party that actually delivered isn't the last seller in the chain. Revenue the client can't defend.
- **Sources that reach you only through middlemen** — inventory one of the client's own senders could deliver straight, arriving through two or three intermediaries instead, each taking a cut.
- **Publishers that list you as RESELLER — or not at all** — ads.txt / app-ads.txt files where the client is authorized only as a reseller, under the wrong seller id, or missing. Each line is revenue waiting on a single email.
- **Traffic with no supply chain at all** — senders passing impressions without a schain object: impossible to verify, impossible to defend to a buyer.

None of this shows up in a revenue report. All of it shows up in SPO.expert — with the paths, the senders and the dollars behind each line.

## Why It Matters — Visibility Is Control

What you can't see, you can't negotiate, fix — or defend.

Without SPO.expert:
- Several hops sit between an app and the client; half of them can't be named — let alone judged.
- A sender quietly routes a top app through two extra resellers; the margin shrinks and it's noticed at month-end.
- A publisher's ads.txt lists the client as RESELLER; buyers' SPO filters skip the client and nobody tells them.
- A path fails verification — which hop, which error, whose fault and what to fix is anyone's guess.
- Partners the client routes serious revenue through but has never talked to stay invisible — so does the direct deal they could have.
- There's a gap in the client's own sellers.json; paths break at the client's own node and they're the last to know.
- A sender routes a source badly; which other sender could carry it instead — nobody knows.

With SPO.expert:
- Every hop is named and checked against its sellers.json — the client decides who stays in the chain.
- The client sees the same app arriving straight from one sender and through three resellers from another — and asks for the short path by name.
- The client gets the exact ads.txt line the publisher needs to add, and how much revenue verifies once it's there.
- Every error is pinned to a hop and a party — the client's node, the sender or the publisher — with the fix spelled out.
- Every indirect partner is ranked by the money flowing through it, tagged new or worked-with-before — so the client knows whom to call first.
- Failures at the client's own node are flagged with the exact sellers.json entry to add.
- Alternative routes through current or former senders are proposed, with the account id to request traffic under.

Control isn't a dashboard you look at once. It's knowing — day by day, week by week, month by month — which of your paths you can prove.

## How It Works — Deterministic Rules Decide, AI Explains

- **IAB specifications as the rulebook.** Every check is written from the IAB OpenRTB SupplyChain object specification, sellers.json, ads.txt and app-ads.txt.
- **Impression-level evidence, not samples.** A 1×1 tag on the client's impressions carries the actual schain object each impression travelled with.
- **AI that explains — and never decides.** Every figure, table row and recommendation is computed deterministically from the client's data before the AI sees it. The AI writes the explanation, answers questions and cites the specifications.

Processing:
1. **Collect** — impression-level data arrives via a 1×1 tag carrying the schain (supply chain object).
2. **Validate** — 15 deterministic checks confirm the schain object is present, complete and conformant to the IAB OpenRTB SupplyChain specification (version, complete flag, nodes, asi, sid, hp, duplicates, encoding).
3. **Verify** — 40 deterministic checks confirm every hop against sellers.json (seller present, seller type, domain match), the publisher's ads.txt / app-ads.txt (DIRECT vs RESELLER, seller id, authorization of resellers), the chain of authority between hops, whether the chain ends at the client, and whether the party that actually delivered matches the declared sender.
4. **Classify** — every impression lands in one of four buckets: verified / not verified / not validated / not analyzed — per sender, for every period the client runs (daily, weekly, monthly).
5. **Deliver** — an interactive map, three reports and an AI analyst.

## What Users Get

### The supply-path map
An interactive map of every supply path: source → every hop (seller) → the client → advertisers. Line thickness shows impressions or revenue; colour shows status (verified, failing validation / bypass, low-volume tail). Filter by source, seller, sender, publisher, advertiser and period. Click any path for its hops, sellers.json identities, advertisers, revenue and error codes. Every path, sender and publisher has an "Ask AI" entry that opens the analyst with that exact scope loaded.

### Three reports — on screen and as CSV
- **Errors** — everything that blocks verification, organized by who can fix it: the client (their own node in the chain, their own sellers.json), the sender (per sender: every upstream issue with the party at fault named and money at stake) or the publisher (ads.txt / app-ads.txt files that don't authorize the client, with the literal lines to add and the revenue that verifies once they're in). Plus the full error map ranked by money.
- **Optimization** — every path of the client's top sources ranked shortest to longest, one suggestion per path (prioritize, prefer the shorter verified path, fix, or connect directly), which senders could deliver straight what now arrives through middlemen, and which publishers list the client DIRECT.
- **New Connections** — partners the client pays through indirectly, ranked by the revenue and impressions routed through them, tagged new or worked-with-before, plus publishers where the client is RESELLER-only or missing.
The screen shows the top of each list; the CSV carries the full registry.

### The AI analyst
Ask in plain English; get an answer with the denominator attached. The analyst:
- answers from the client's own data — never from benchmarks or industry averages — and states its scope with every answer;
- explains any error code and quotes the IAB specifications by document and page;
- finds alternative paths for a source through the client's current or former senders, with the account id to request traffic under;
- breaks down revenue, impressions, CPM and verified rate by source, sender, publisher or advertiser, over days, weeks or months, and explains what drove a change;
- can be asked from the chat or straight from any path, sender or publisher on the map.

Example questions: "What share of impressions is verified for each of my sources?" · "Why are these impressions bypassing verification — and who should I contact?" · "Explain this supply path hop by hop." · "Find alternative paths for this source."

## What SPO.expert Does Not Do

SPO.expert is supply-path intelligence. It does not score invalid traffic (IVT) or fraud, does not measure viewability, and does not report geography, device or audience data. It does not mix one client's data with another's: every query is scoped to the client's own account, and there are no cross-client benchmarks.

## Getting Access

Access is requested by messaging the SPO.expert LinkedIn page (https://www.linkedin.com/company/spo-expert/) — there is no contact form, and the website stores nothing visitors type. Onboarding requires one 1×1 impression tag; no changes to the client's DSPs, SSPs or reporting. The tag carries data about the impression's supply chain only — no cookies, no device or user identifiers, no personal data. No commitment required.

## Frequently Asked Questions

**Is the analysis done by AI?**
No. Verdicts come from a fixed set of deterministic checks written from the IAB specifications. The AI analyst explains the results, answers questions and cites the specifications — it cannot state a number that isn't in the client's data.

**What does a client need to send?**
A 1×1 impression tag carrying the schain (supply chain object). No changes to the client's DSPs, SSPs or reporting.

**Who benefits from using SPO.expert?**
Platforms inside the programmatic supply chain that receive inventory from partners — SSPs, ad exchanges, ad networks and DSPs — and the AdTech, supply and programmatic teams that run them.

**Can SPO.expert integrate with existing ad tech stacks?**
Yes. SPO.expert works alongside existing DSPs, SSPs and reporting. It ingests impression-level data via a standard 1×1 tag and requires no changes to current infrastructure.

**How does SPO.expert visualize supply paths?**
It maps the complete path from source through every seller to the client and on to advertisers, classifies every path (verified / not verified / not validated / not analyzed), and lets users filter by source, seller, sender, publisher, advertiser and period.

**What is Supply Path Optimization (SPO) in AdTech?**
Supply Path Optimization (SPO) is the process of evaluating and streamlining the routes through which digital ad impressions travel from publishers to advertisers. SPO removes redundant intermediaries, reduces fees, and improves transparency in the programmatic supply chain.

## Legal

- Privacy Policy: https://spo.expert/privacy.html
- Terms of Service: https://spo.expert/terms.html
- Data Processing Addendum: https://spo.expert/dpa.html