Chauffeur Circle Docs

Widget

Theme & events

Colours and fonts

Set your colours, corner radius and font in Widget in the dashboard; they apply everywhere the widget is shown. To override them on one page, set CSS custom properties on the element:

chauffeur-circle-booking {
  --sl-primary: #b8860b;   /* buttons, selected items */
  --sl-bg: #0f0f10;        /* background */
  --sl-surface: #1a1a1c;   /* cards and inputs */
  --sl-text: #f4f4f5;
  --sl-muted: #a1a1aa;
  --sl-radius: 4px;
  --sl-font: "Playfair Display", Georgia, serif;
}

The widget uses Shadow DOM, so your site's other CSS does not leak in. For finer control, style these parts:

chauffeur-circle-booking::part(panel) { box-shadow: none; }
chauffeur-circle-booking::part(button) { text-transform: uppercase; }
chauffeur-circle-booking::part(vehicle) { border-width: 2px; }
chauffeur-circle-booking::part(input) { font-size: 16px; }

Available parts: panel, button, vehicle, input, payment-frame, footer.

"Powered by Chauffeur Circle" in the footer is removed on the Business plan.

Events

The widget fires DOM events that bubble up to document, so you can connect analytics or your own code:

Event detail When
chauffeur-circle:ready { mode, test_mode } The widget loaded your settings
chauffeur-circle:quote { quote } Prices were shown
chauffeur-circle:step { step } The passenger moved to trip, vehicle, details, review, payment or done
chauffeur-circle:booked { reference, status, quote_request, card? } A booking was made (card saved), or a quote request was sent
chauffeur-circle:error { code, message, fields? } Something went wrong (see error codes)
document.addEventListener('chauffeur-circle:booked', (e) => {
  gtag('event', 'purchase', { transaction_id: e.detail.reference });
});

Tracking where bookings come from

The widget records the page's UTM parameters and referrer with each booking. You see them on the booking in the dashboard.