Embedding options overview

Choose when to embed OmniLab 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.

Embed when you want OmniLab to live inside an existing customer journey. Choose a standalone deployment when you want a shareable full-page link, printed QR codes, or a public OmniLab Pages experience 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

Decide on the domain early. For a fast launch, the default OmniLab-hosted domain is often enough. If the embedded experience must sit under your own branded domain, plan a custom domain before go-live.

Whichever pattern you use, your dev team will need the right OmniLab link for it. After you embed, 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