--- mw_bundle: 1 type: hub_digest slug: ba331s0y author: "박현덕" url: https://memory.wiki/hub/ba331s0y concept_count: 12 updated: 2026-06-24T08:16:21.303Z source: "memory.wiki" --- # 박현덕's knowledge — concept digest _12 concepts extracted across this hub. Each entry links to the supporting documents — fetch any of them as `https://memory.wiki/raw/?compact=1` for the dense full text._ ## Concepts ### Criteo *entity • weight 5 • 1 doc* > The demand partner and DSP receiving the S2S BidRequest from Wisebirds for ad auctions. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ### OpenRTB 2.6 Custom S2S *concept • weight 5 • 1 doc* > The core technical specification and integration framework that Wisebirds is implementing with Criteo for programmatic ad requests. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ### BidRequest Structure *concept • weight 5 • 1 doc* > The JSON schema and field composition for Web and App banner ad requests being sent to Criteo, the primary subject of validation. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ conforms to specification → **OpenRTB 2.6 Custom S2S** ### Wisebirds *entity • weight 5 • 1 doc* > The SSP/partner ad platform acting as intermediary aggregating inventory from multiple publishers (B, C) to Criteo. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ transmits bid requests to → **Criteo** · aggregates from → **Publisher Inventory** ### Supply Chain (schain) *concept • weight 4 • 1 doc* > The seller path representation required to map Wisebirds and publisher relationships through source.schain nodes with asi/sid values. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ must align with → **ads.txt / sellers.json** ### ads.txt / sellers.json *concept • weight 4 • 1 doc* > Authorization files that must align with schain node values to validate the supply chain path and seller credentials. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ### Publisher Inventory *concept • weight 4 • 1 doc* > Web and App placements from contracted publishers that Wisebirds forwards to Criteo, requiring publisher.id mapping. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ### Placement Identification *concept • weight 3 • 1 doc* > The distinction and usage of tagid (internal placement UUID) versus gpid (global placement identifier) for inventory mapping. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ maps inventory via → **Publisher Inventory** ### User Identification *concept • weight 3 • 1 doc* > Strategy for populating user.id, buyeruid, and determining if regs object should be included for Korea-only traffic. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ populates fields in → **BidRequest Structure** ### Phase 1 Implementation Scope *tag • weight 3 • 1 doc* > The bounded first release targeting Korea traffic, banner-only ads, 300-350ms tmax, and delayed User Sync. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _Related:_ constrains composition of → **BidRequest Structure** ### Device & Geo Data *concept • weight 2 • 1 doc* > User agent, IP, device OS, IFA, and geographic targeting parameters for auction relevance and compliance. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ### App Banner Implementation *concept • weight 2 • 1 doc* > Specific app-level fields including displaymanager, rwdd, and their configuration for non-rewarded placements. - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. ## Concept relations _7 highest-weight edges between the top concepts._ - **Wisebirds** transmits bid requests to **Criteo** - **BidRequest Structure** conforms to specification **OpenRTB 2.6 Custom S2S** - **Supply Chain (schain)** must align with **ads.txt / sellers.json** - **Wisebirds** aggregates from **Publisher Inventory** - **Placement Identification** maps inventory via **Publisher Inventory** - **User Identification** populates fields in **BidRequest Structure** - **Phase 1 Implementation Scope** constrains composition of **BidRequest Structure** ## All documents _1 public document, ordered by recency. Each entry includes a one-paragraph gist for quick scanning. Fetch any as `https://memory.wiki/raw/?compact=1` for the full body._ - [Criteo TAM 메일 초안](https://memory.wiki/ZtT6QNyO) Wisebirds is seeking clarification on OpenRTB 2.6 field interpretations and BidRequest sample structure before implementing Criteo Custom S2S integration, particularly regarding supply chain configuration, inventory mapping, user identification, and which fields are critical for bidding performance. _sections:_ 메일 제목 후보: text | 메일 본문: text; 트래픽은 한국에서만 발생할 것으로 예상; 초기에는 배너 광고만 요청 예정; tmax는 기존 답변 주신 300~350ms 범위로 개발 예정; User Sync는 별도로 확인 후, 일정 내 개발 가능하면 buyeruid를 포함할 예정 | … --- _Need everything? [Full hub index](https://memory.wiki/raw/hub/ba331s0y?compact=1) lists every public document. [llms.txt manifest](https://memory.wiki/hub/ba331s0y/llms.txt) explains how to crawl this hub._