Channel Overview
Email Integration
Insert a single image tag (or HTML embed code) in your ESP template. The tag URL encodes the Workflow ID and a customer identifier as a query parameter.Web Integration
Two options depending on your rendering strategy:Server-side SDK (recommended for SEO / SSR)
Available for Node.js frameworks. The SDK calls the Runner at page-render time and injects personalised Content into the HTML response. Supported frameworks:- Next.js (App Router and Pages Router)
- Nuxt (Nuxt 3)
- Remix
- SvelteKit
- Generic Node.js (Express, Fastify, or any HTTP server)
Client-side script
A lightweight JavaScript snippet that fetches and renders Content in the browser. Suitable for static sites, SPAs, or when SSR is not available.Mobile Integration
Native SDKs handle initialisation, Content fetching, identity management, and view lifecycle:
A JSON API fallback is available for custom implementations or platforms without native SDK support.
JSON API (Headless)
For headless integrations (push notifications, in-app messages, custom frontends), the JSON API returns structured payloads matching a JSON Template schema defined in the platform. The response shape is deterministic and typed — your client code can rely on the schema without runtime type checking.Content Delivery Formats
Next Steps
Web SDK Reference
Full server-side and client-side SDK documentation.
Mobile SDK Reference
iOS, Android, and Flutter SDK guides.
JSON API
Headless JSON API integration guide.
API Reference
Full REST API documentation.