Placements

Each widget resolves products and behavior using a placement ID. A placement represents a server-managed contract describing:

• Widget type
• Product selection strategy
• Campaign constraints
• Display rules
• Conversation script or response model
• Conversion mode
• Tracking configuration

Example Placement Usage

<ConversationalAdWidget
  placementId="home-sponsored-feature"
  context={{
    pageType: "home",
    locale: "en-US",
    currency: "USD",
    campaign: "spring-launch",
  }}
/>

How Placements Work

Placements are defined and managed server-side. The client SDK references them by ID, and the advertisement service resolves the appropriate products, creatives, conversation scripts, and conversion modes at runtime.

This approach keeps the frontend integration stable while allowing targeting, prioritization, and conversational behavior to evolve independently without client-side code changes.

Best Practices

• Keep placement IDs stable and server-managed.
• Pass page and product context explicitly for improved targeting.
• Use descriptive naming conventions for placement IDs (e.g., home-hero-sponsored, pdp-upsell-checkout).
• Define separate placements for different conversion modes (redirect vs. instant checkout).