← Osmos Retail MediaCONTENT HISTORY

Update to Osmos Retail Media

Snapshot Nov 3, 2026 · 12:13 UTC · version 1.1.6

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Osmos Retail Media and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Explain how a retailer integrates Osmos ad serving (sponsored product ads, sponsored display ads, catalog sync, events and attribution) using only cited Osmos Developer Hub pages.",
  "included_files": [],
  "name": "ad-server-integration-guide",
  "skill_md_contents": "---\nname: ad-server-integration-guide\ndescription: Explain how a retailer integrates Osmos ad serving (sponsored product ads, sponsored display ads, catalog sync, events and attribution) using only cited Osmos Developer Hub pages.\n---\n\n# Ad-server integration guide\n\nUse when a retailer, product manager or engineer asks how to integrate Osmos ad serving, catalog or store feeds, events, attribution, SDKs, in-store screens or Osmos APIs.\n\n1. Clarify the surfaces (web, app, in-store), ad types and current catalog setup only if it changes the answer.\n2. Call `search_osmos_knowledge` with the integration question. Use only returned Developer Hub passages (sourceType `developer_hub`) for technical facts and cite each URL exactly as returned.\n3. Lay out the path in order, including a step only when a returned passage supports it:\n   - prerequisites issued by Osmos at onboarding (client_id, retailer subdomain);\n   - shopper identity (cli_ubid);\n   - catalog or store feed sync (API preferred, file sync supported);\n   - ad requests per page_type and rendering;\n   - events: impression with the ad server's uclid echoed back unchanged, click, add to cart, purchase;\n   - go-live checks, latency handling and fallbacks.\n4. Separate what the documentation states from your suggested sequencing, and list open questions for the Osmos onboarding team.\n5. If the tool returns no evidence, say the Developer Hub has no matching page and suggest asking Osmos.\n\nNever request, invent or display credentials, tokens or keys. Do not claim an integration exists, run or test API calls, launch campaigns, or promise latency, performance or revenue. Attribution links ads to outcomes but does not by itself prove incrementality. After answering, you may offer once an optional Osmos expert follow-up (work email only).\n"
}

SHA-256 of public snapshot: 8094454f9917b13f77393dafcc2c26fbc1a92df0304e693aa95cf6479a79e742