Integration Patterns

Web and Mobile Applications

Use a provider-based SDK setup at application bootstrap, then mount widgets by placement ID wherever sponsored product experiences are needed.

Commerce Ownership Model

The Nohi platform owns all product selection, catalog mapping, and commerce orchestration. Developers do not need to supply product data or maintain inventory state — the SDK resolves products automatically at runtime based on placement configuration.

The platform’s commerce integration layer handles:

• Product ID normalization
• Variant resolution
• Checkout payload generation
• Redirect route consistency

Campaign Management Model

Manage widget behavior server-side through placement definitions rather than shipping campaign logic inside the client application.

This keeps the frontend integration stable while allowing targeting, prioritization, and conversational behavior to evolve independently.

Minimal End-to-End Integration Flow

1. Provision an API key for the target application.
2. Add the SDK package for the desired platform.
3. Initialize the SDK with the API key and environment.
4. Define one or more server-side placements.
5. Mount a widget with a placement ID and page context.
6. Configure redirect or instant checkout behavior.
7. Subscribe to events for reporting and analytics.
8. Validate impressions, clicks, redirects, and checkout completion.