The two parts
The integration is a 2-part embed:-
fmv.js (~5 KB, no dependencies) — loaded directly on your page from
cdn.fitmyvehicle.com.au. This is a lightweight UI shell that creates an overlay and iframe when the user clicks the trigger button. -
Widget iframe — a full-page overlay iframe pointing to
cdn.fitmyvehicle.com.au/widget/. All API calls, database connections, and data processing happen inside this iframe.
postMessage for close events and optional analytics events. No sensitive customer data crosses the boundary.
Key details
What the script does and doesn’t touch
The embed script (fmv.js) reads only its own elements:
- Its own
<script>tag attributes (data-public-key,data-builder-id) - Click targets with
data-fmv-open-widget(via event delegation) window.location.origin— passed to the API as the host origin
<div> overlay and an <iframe>. That’s it.
It does not:
- Read page content, forms, user inputs, or any other DOM elements
- Set cookies or touch localStorage/sessionStorage on your domain
- Send any data from your site anywhere — it’s purely a UI shell
- Inject styles that affect your site’s appearance
- Load third-party scripts or tracking pixels on your page
FMV emits structured analytics events via
postMessage that you can optionally forward to your own tracking (GTM, GA4, etc.). No third-party tracking code is loaded by FMV itself.Optional performance optimization
Add DNS prefetch hints to your page<head> for marginally faster first-open times: