Your website

Yes — Glovebox Sites gives you a full booking website with a choice of professionally designed themes. You set your brand colours, logo, SEO defaults and publishing status from Site settings, and your fleet, pricing and availability are already wired in.

Open this answer

Yes — your public booking site can run on your own custom domain, so customers stay on your brand the whole way through.

Open this answer

Yes. If you already have a website, you can embed the Glovebox booking widget into it — customers book directly on your site and everything flows into Glovebox the same way. See Adding the Glovebox booking widget to your own website for the snippet and the options.

Open this answer

You can drop Glovebox booking into any website you already run: WordPress, Squarespace, Webflow, Shopify, or hand-written HTML. It is two lines of markup and no build step.

The snippet

Copy your snippet from Glovebox rather than typing it out: it comes pre-filled with your workspace id and brand colour. In the admin, go to your widget embed page and copy what is shown there. It looks like this:

<script src="https://yourbusiness.getglovebox.co.nz/widget/v1/loader.js"
    data-tenant="your-workspace-id"
    data-colour="#1a6b4a"
    data-type=""
    async></script>
<div id="glovebox-widget"></div>

Paste both lines where you want the booking form to appear. The <div> is the mount point, and the widget renders into it. If you leave the <div> out entirely, the widget appends itself to the end of the page instead, which is rarely what you want, so keep it.

Options

All options are data- attributes on the <script> tag.

Everything except data-tenant is optional. Empty attributes are ignored, so you can leave them in place.

A common pattern is one general widget on your booking page, plus a pre-filtered one on each vehicle page:

<script src="https://yourbusiness.getglovebox.co.nz/widget/v1/loader.js"
    data-tenant="your-workspace-id"
    data-colour="#1a6b4a"
    data-vehicle="toyota-hiace-camper"
    async></script>
<div id="glovebox-widget"></div>

How it behaves on your page

The widget renders as an iframe that fills the width of its container, so it picks up your page's layout. It resizes itself as the customer moves through the steps, so you do not need to set a height or manage scrolling.

One widget per page. If you need booking in two places, link to a single booking page rather than embedding twice.

When a customer reaches payment, the page navigates to the payment provider's secure checkout and returns them afterwards. This is why the widget is allowed to navigate the top-level page, and it only ever does so to your own domain or the payment provider's.

Analytics

This is the part worth understanding before you rely on it.

Because the widget runs in an iframe, analytics on your page cannot see inside it. GA4, a Meta pixel or any other tag on your site will keep working normally, and they will record the pageview of the page holding the widget, but they will not automatically see steps taken within the booking flow, and they will not fire a conversion event when a booking completes. That is a property of how browsers isolate iframes, not a setting.

What you can rely on today:

• your existing page-level analytics keep working as they do now;
• Glovebox records the booking funnel on its side, so abandoned carts and completions are visible in your admin regardless of what your own tags see; and
• because payment sends the customer to a checkout page and back to a return URL on your site, that return URL is a reliable place to fire your own conversion tag.

If you need conversion tracking wired into your own analytics properly, get in touch and tell us which platform you use, because it is much easier for us to answer that against your actual setup than to guess.

Troubleshooting

Nothing appears. Check that your site is not stripping <script> tags. Some page builders do this in their basic text blocks; use the dedicated embed, custom HTML, or code block instead.

It shows but looks wrong. Check the container it sits in. A parent element with a fixed height or overflow: hidden will clip the widget and stop it resizing.

It works locally but not live. The snippet must be served over HTTPS, and the src must point at your Glovebox domain exactly as copied.

If it still will not behave, send us the page URL and we will take a look.

Open this answer