Not every client wants to send buyers to a separate website.
Some clients already have a project website, an investor portal, a campaign landing page, or a partner marketplace. They want the interactive sales experience to live inside their existing digital journey, not as a disconnected link.
That is why RegalScene supports both standalone and embedded viewing.
Standalone vs embedded
In standalone mode, RegalScene serves the interactive experience on its own branded URL. The client shares a link, and the buyer opens a full-screen viewer with navigation, detail panels, compare, and lead capture.
In embedded mode, RegalScene lives inside the client's existing page. A small script tag or SDK integration places the interactive viewer inside a section of the client's website. The buyer never leaves the client's domain.
Both modes use the same viewer, the same project data, the same templates, and the same lead capture. The only difference is where the experience is hosted.
How embedding works
Embedding RegalScene into an existing website requires a small code snippet. The client's development team adds a script tag and a container element to the page. RegalScene handles the rest.
The embedded viewer:
- Loads the project configuration from the RegalScene backend
- Renders the interactive master plan inside the container
- Supports scene navigation, overlay clicks, and detail panels
- Captures leads with full context and placement attribution
- Tracks analytics and buyer journeys
- Adapts to the container size and responds to mobile viewports
The client's website does not need to know about project templates, inventory structure, asset types, or CTA configuration. All of that is managed in the RegalScene admin dashboard and delivered through the backend.
What the host website controls
The host website controls:
- Where the viewer appears on the page
- The container size and layout
- The surrounding content and branding
- Which project or placement is loaded
- Campaign attribution parameters
What RegalScene controls
RegalScene controls:
- The interactive experience inside the container
- Scene navigation and overlay rendering
- Inventory data and template-driven display
- CTA buttons and lead form fields
- Analytics tracking and session attribution
- Asset detail loading and data filtering
This separation means the client's website team does not need to update their site when the project template changes, new inventory is imported, or CTA labels are updated. Those changes happen in the RegalScene admin and are reflected automatically in both standalone and embedded viewers.
Template-driven projects work automatically
With the recent Asset Template Engine upgrade, RegalScene projects can be configured for different domains: residential, logistics, commercial, mixed-use, or custom.
When a logistics free zone project is embedded into an investor portal, the viewer automatically shows:
- Asset types like warehouses, land plots, and build-to-suit parcels
- Domain-specific fields like clear height, loading docks, and bonded access
- CTA labels like "Request Details" and "Schedule Site Visit"
- Lead forms that capture company name, required space, and intended use
No template configuration is needed on the host website. The project template is resolved from the backend.
Lead capture and analytics still work
Embedded viewers capture leads the same way standalone viewers do. When a buyer submits an enquiry from an embedded viewer, the lead includes:
- The buyer's contact information
- The asset they were viewing
- The action they took
- The placement, campaign, and source attribution
- The full exploration journey
This means sales teams can see not only who enquired, but which embedded page, campaign, or partner site generated the lead.
Public-safe data delivery
Embedded viewers use the same public-safe data delivery as standalone viewers. The viewer receives only summary data for linked assets. Full asset detail is loaded on demand when the buyer clicks an overlay. Pricing, attachments, and custom attributes are filtered based on admin settings.
This ensures that sensitive commercial information is not exposed in the page source, even when the viewer is embedded on a third-party website.
Use cases for embedded viewing
Embedded RegalScene experiences work well for:
- Project marketing websites — add an interactive master plan section to an existing property or development site
- Investor portals — embed a logistics or commercial zone explorer inside an investment platform
- Campaign landing pages — create a focused launch page with an embedded viewer for a specific project or phase
- Partner marketplaces — allow property portals or agent networks to embed project experiences on their own sites
- Roadshow follow-up pages — give event visitors a branded page to revisit the project after leaving the booth
Interactive sales without rebuilding the client website
The goal of embedded viewing is simple: let RegalScene live inside the client's existing digital journey.
Clients do not need to replace their website, rebuild their marketing pages, or adopt a new platform. They add a small integration, point it at their project, and the interactive sales experience appears inside their existing page.
The same project. The same data. The same templates. The same lead capture. Just embedded where the client needs it.