Architecture

A standard integration consists of the following components:

Host Application

Your frontend application, such as a web storefront, native mobile app, or hybrid client.

SDK Runtime

The platform-specific SDK package responsible for:

Authentication
Widget rendering
Placement orchestration
Request signing headers
Event emission
Redirect and checkout actions

Advertisement Service API

The backend service that:

Authenticates API access
Resolves placements
Selects products and creatives
Returns conversation definitions and commerce actions
Supports campaign targeting and runtime personalization

Commerce Integration Layer

A connection point used to:

Redirect to PDPs
Open native or web checkout flows
Perform instant checkout
Map products and variants into purchasable line items

Integration Diagram


┌──────────────────────────┐
│     Host Application     │
│  (Web / Mobile / Hybrid) │
└────────────┬─────────────┘
             │
     ┌───────▼─────────┐
     │   SDK Runtime   │
     │  (per platform) │
     └───┬────────┬────┘
         │        │
   ┌─────▼──┐  ┌──▼───────────────┐
   │  Ads   │  │    Commerce      │
   │  API   │  │ Integration Layer│
   └────────┘  └──────────────────┘

The SDK Runtime sits between the host application and the backend services, handling authentication, widget rendering, event emission, and conversion actions.

See Backend Connections for the full list of required services.