How do I ensure my partner routing with a supply path optimization tool is compliant with deal ID and identity rules?

To keep partner routing compliant when using a Supply Path Optimization (SPO) tool, the key is to make sure the tool is not bypassing required deal IDs, publisher identity, or buyer identity rules that apply in programmatic transactions.

Here’s a practical checklist:

1) Preserve deal integrity

• Only route inventory through approved deal IDs when the impression is meant to transact via PMP, PG, preferred deal, or any other curated path.
• Make sure the SPO tool does not rewrite, strip, or substitute deal IDs.
• If the tool reroutes traffic to a different exchange/SSP, confirm the new path supports the same deal terms and that the deal ID is still passed end-to-end.

2) Maintain publisher identity transparency

• Ensure the partner routing logic keeps correct publisher app/site identity intact.
• Validate that the tool passes:
  • domain, bundle, or app store IDs as appropriate
  • seller identifiers / ads.txt or app-ads.txt-aligned identifiers
  • SupplyChain Object (schain) where required
• Avoid any routing that masks the actual supply source or makes it look like inventory came from a different publisher.

3) Respect buyer identity requirements

• If your setup relies on buyer/advertiser identity signals, ensure the SPO tool:
  • does not alter bidder account IDs, seat IDs, or DSP identity fields
  • preserves consent and eligibility signals tied to the buyer
• If identity resolution is involved, verify it is compatible with privacy rules and platform policies.

4) Keep ads.txt / app-ads.txt / sellers.json aligned

• Route only through paths where the reseller chain is properly authorized:
  • ads.txt / app-ads.txt
  • sellers.json
  • SupplyChain Object
• If a partner route changes the path to a seller not authorized in those files, treat it as non-compliant.

5) Verify SPO decision rules don’t violate deal precedence

• Configure the tool so that:
  • direct deals take precedence over optimization
  • floor/price logic does not override guaranteed or preferred deal logic
  • open auction optimization doesn’t siphon traffic away from contracted deals
• Add hard rules like: “If deal ID present, route only to approved deal-capable sellers.”

6) Test end-to-end bid requests

Run sample bid requests through the SPO tool and confirm:

• deal ID appears unchanged
• publisher/app/site fields are intact
• schain is present and accurate
• authorized sellers match ads.txt/app-ads.txt/sellers.json
• no unexpected partner swaps occur

7) Document governance and auditability

• Keep written rules for:
  • when partner routing can occur
  • which partners are approved for which inventory/deal types
  • what identity fields must be preserved
• Log routing decisions so you can audit why a request was sent to a specific partner.

8) Validate against platform and legal policy

Different exchanges, SSPs, and DSPs may have specific rules about:

• deal ID propagation
• reseller disclosures
• identity sharing and consent
• auction manipulation / traffic shaping

Make sure your routing logic complies with:

• platform policies
• contractual deal terms
• privacy regulations and consent requirements

Recommended implementation guardrails

A safe policy often looks like this:

• If a valid deal ID exists:
  route only to approved partners that can honor that deal ID.

• If supply is unauthorized or identity is unclear:
  do not route it for optimization; block or quarantine it.

• If the SPO tool cannot preserve identity and chain-of-supply fields:
  exclude that partner path.

If you want, I can also help you turn this into:

1. a compliance checklist,
2. a decision tree for routing logic, or
3. a test plan for validating deal ID propagation.