TMP for Retail Media
Retailers manage sponsored product placements across search results, category pages, and carousels. TMP’s catalog refinement capabilities make it a natural fit — buyers can specify which products to feature, which promotions to highlight, and which items to suppress, all within the bounds of pre-negotiated packages.How It Works Today
Retail media networks use internal recommendation engines to decide which sponsored products appear. Buyers set campaign-level targeting (keywords, categories, budgets) but have limited real-time control over which specific products appear in which contexts. Each retailer has its own API and optimization logic.Context Match
When a shopper views a search results page or category page, the retailer sends a Context Match request:Identity Match
The retailer sends an Identity Match request with the shopper’s loyalty token and the retailer’sseller_agent_url. The buyer resolves its active package set from seller_agent_url; when the retailer sends package_ids explicitly (as below), composition MUST be independent of the current page — either all-active (every active package for this buyer at the retailer) or fuzzed (a random sample padded with synthetic non-existent IDs the buyer silently drops). The page-specific subset is forbidden — it would let the buyer correlate this request with the context match by comparing package sets:
Activation
The retailer joins both responses:- Accept the coffee sponsored offer
- Use the inline creative manifest from the offer for catalog items, promotion badges, and rendering assets
- Check Identity Match: is the package in
eligible_package_ids? - The retailer’s own recommendation engine integrates the sponsored results alongside organic results