Core Capabilities
Conversational Advertisement Widgets
Render interactive product advertisement components that adapt to context such as page type, user intent, campaign configuration, and placement rules.
Typical placements include:
- Home page discovery modules
- PDP companion placements
- Editorial or content page inserts
- Search and collection overlays
- Cart and checkout upsell surfaces
- In-app promotional cards and modal experiences
Dynamic Product Selection
The SDK retrieves promoted products automatically from the Nohi advertisement service at runtime. The platform resolves which products to display based on runtime signals such as:
- Placement identifier
- Page context
- Session metadata
- Device platform
- Locale and currency
- Customer segment
- Product catalog context
- Campaign or merchant targeting metadata
Conversational Interaction Model
Widgets can present products in a guided, conversational format rather than a static banner or grid. Supported interaction patterns include:
- Product recommendation prompts
- Multi-step product discovery cards
- Comparison and variant selection
- Context-aware call-to-action flows
- Checkout-driven follow-up actions
Conversion Paths
The SDK supports two conversion modes:
PDP Redirection
The widget opens the product detail page in the host application or website.
Instant Checkout
The widget launches an embedded purchase flow that supports direct transaction completion without leaving the current surface.
See Conversion Flows for a detailed walkthrough of each mode.
Eventing and Analytics
The SDK emits lifecycle and commerce events that can be forwarded to internal analytics or marketing infrastructure.
Common events include:
- Impression — Widget rendered on screen
- Viewability reached — Widget entered the viewport
- Product click — User tapped a product
- Conversation step viewed — User advanced the conversation
- CTA clicked — Call-to-action interaction
- Redirect started — Navigation to PDP initiated
- Checkout opened — Embedded checkout launched
- Checkout completed — Purchase transaction succeeded
- Checkout abandoned — User exited checkout
- Error surfaced — Runtime error occurred
See Event Handling for integration details.