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

Studio vs. Pages

Learn what happens in Studio, what happens in Pages, and how both surfaces work together.

OmniLab has two front-end surfaces: Studio and Pages. Understanding which one you are looking at removes a lot of confusion from the rest of the help center.

Quick check

Use Studio to build and manage campaigns. Use Pages for the participant-facing experience.

Studio

Studio is the back-office interface used by marketing teams, admins, agencies, and other authorized operators. This is where you create campaigns, add touchpoints, configure rewards, manage forms and notifications, validate setup, publish, and review performance.

You access Studio through your sign-in URL and work inside the organisations you have permission to use. In practice, Studio is where the campaign is built and governed.

Pages

Pages is the consumer-facing layer where end users actually participate. This is where they open landing pages, start games or other touchpoints, submit forms, accept terms, receive outcomes, and follow calls to action.

Pages can be delivered as a standalone web application on a dedicated subdomain or embedded into an existing website with a lightweight JavaScript tag. In kiosk projects, the same Pages experience can also be loaded inside an iframe or WebView.

Studio and Pages together

Think of the relationship like this:

SurfacePrimary userMain jobTypical access
StudioMarketing teams, admins, and agenciesBuild, configure, validate, publish, and measureStudio sign-in URL
PagesConsumers and participantsDiscover, participate, submit, win, and redeemSubdomain, embedded page, or kiosk surface

The flow is straightforward:

  1. A marketer or agency configures the campaign in Studio.
  2. The team publishes it.
  3. Consumers interact with it in Pages.
  4. Results flow back into campaign data, analytics, and connected systems.

A single campaign can therefore live across multiple surfaces at the same time: standalone Pages, an embedded website experience, and project-specific kiosk delivery when needed.

Was this helpful?

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

On this page