Data Supply
For publishers, agencies, licensed vendors and owners of first-party or operational data. Say what you hold; the marketplace lists it, enforces its consent and license inline, and delivers it to KYC-verified buyers with your attribution on every surface.
Photo by Zoshua Colah on Unsplash
Start from what you hold.
Four kinds of partner supply the marketplace, and each enters it differently. Find yours; the products that take that input are named on the card.
You hold first-party or operational data
Publishers, platforms and operators with consented records they own. List it once; each buyer is entitled separately, and consent is enforced inline before anything moves.
You publish official statistics or licensed series
Agencies, exchanges and licensed data vendors. Series are ingested against a registry that records each one's license posture, so what may be done with a series travels with it, and the index that uses it names you on every surface.
You own media inventory or audience signals
Publishers and app owners with programmatic supply. Signals are enriched and routed to demand in real time through RealSynq, with Leanback Digital as the programmatic vendor.
You run an institutional API or public dataset
Civic, governmental and regulatory sources. We access only through your sanctioned method, publish only transformed aggregates, and attribute you with access date and transformations applied.
What the marketplace accepts, counted from its own vocabulary.
Every value on this page is a literal from the schema, so these are counts of options, not estimates. When the schema grows, the figures follow.
View as a table
| Category | Count |
|---|---|
| Source categories | 15 |
| Formats | 7 |
| Cadences | 7 |
| Destination types | 6 |
| Source statuses | 4 |
| Entitlement statuses | 4 |
lib/portal/vocab.js, literals from the schema migrations
How to read it
A listing is normalized to this vocabulary, which is why a buyer can compare two sources before requesting either. The category list is the widest field because it is the one a buyer browses by; the status fields are the narrowest because each state has to mean one thing to the review queue.
Counted at build time from the product registry (components/site.js) and the marketplace vocabulary (lib/portal/vocab.js, literals from the schema migrations).
List and monetize your first-party data.
From governed storage to consent-aware delivery, we give data owners the controls and the monetization pathways to participate in a KYC-verified marketplace.
Data Management
Governed pipelines, catalogs, and lifecycle controls for first-party and operational data.
First-party profiling
Build durable, consented profiles you own, with no third-party dependencies.
Systems integrations
Connect your stack to warehouse and programmatic destinations through clean APIs.
Storage
Scalable, secure storage orchestration tuned for query-ready delivery.
Consent curation
Capture, enforce, and audit consent inline before any data moves.
Opt-in / opt-out UX
Drop-in preference and opt-out interfaces that keep users in control.
Inputs we expect, and how a listing is presented.
The marketplace runs on one schema. These are its terms for the data you supply, the rights that travel with it, and what buyers will see once it is listed.
Data
- Formats
- APIJSONCSVRSSExceloRTB / VAST for programmatic feeds
- Cadence
- Real-timeDailyWeeklyMonthlyQuarterlyAnnualPeriodic
- Schema
- Stable record keys, an observation timestamp on every row, and a provenance field naming the originating filing, agency or source: the standard our own indexes are held to.
- Transport
- Push to an API endpoint we provision, a scheduled file drop into S3-compatible storage, or a warehouse share.
Rights
- License posture
- Storage, redistribution and model-training grants stated separately, plus the attribution rule. "Undetermined" is its own state; we never fold it into "denied".
- Consent basis
- The lawful basis the data was collected under and the opt-out path you honor. Consent is enforced inline before anything moves.
- Identity
- Suppliers are KYC-verified before a listing goes live: optional for domestic suppliers, required for international ones.
Presentation
- Listing
- A title, category, description. That is the whole form. Review moves it pending → processing → completed, or rejected with a reason.
- Catalog card
- Once approved, buyers see a source card: name, category, cadence, formats and a status of livebetaplannedretired, exactly the card in the portal.
- Review
- We check provenance, the license posture against the fields above, cadence claims against a sample, and that the consent basis holds for the destinations buyers will route to.
What happens next
Listing review
Your listing is read against the inputs above; we come back with questions or an approval.
Catalog entry
The approved listing becomes a source card in the buyer catalog, with its cadence, formats and status.
Entitlements per buyer
Each buyer requests access separately; an approval is an entitlement scoped to that buyer and that source.
Delivery telemetry
Rows, bytes and deliveries per destination are recorded on every run, the same figures buyers see.
Describe the data you'd offer through the marketplace; we'll review and route it to demand. International participants complete identity verification first.
Monetize your data.
Tell us what you hold and we'll design the storage, consent, and delivery pathways around it.