The customer activation platform.Every interaction becomes a qualified contact. Book a demo

Embedding

Choose when to embed Pages inside an existing website or app, and where to find the detailed implementation guides.

Use embedding when the OmniLab experience should appear inside an existing website, WordPress page, kiosk shell, or mobile app instead of opening as a standalone full-page destination.

Embedding is usually the right choice when you want OmniLab to live inside an existing customer journey. Standalone deployment is usually the better choice when you want a shareable full-page URL, printed QR codes, or a public Pages surface that stands on its own.

Choose the right embedding pattern

PatternBest forStart here
Manual iframeWebsites that already know the exact OmniLab URL to loadIframe embedding
JavaScript tag embedReusable host pages that read a campaign path from a page parameterIframe embedding
WordPressEditors who need a CMS-friendly implementation pathWordPress integration
Mobile app WebViewNative apps or wrappers that keep OmniLab inside the app shellWebView integration

Plan the domain before you embed

The domain decision matters early. If you simply need a fast launch, the default OmniLab-hosted domain is often enough. If the embedded experience must sit under the same branded domain family as your host website, plan a delegated custom domain before go-live.

For manual iframes, use an embed-aware OmniLab URL. For JS tag embeds, use the campaign path or touchpoint path expected by the tag. In both cases, retest cookies, permissions, redirects, and mobile layout inside the real host page.

Need kiosk-style message handling?

If your host app must listen for inactivity or other parent-window events, read the Kiosk articles as well. Kiosk integrations add extra message-handling and device requirements on top of standard embedding.

Next steps

Was this helpful?

Optional comments help us improve this page for future authors and readers.

On this page