Start free trialSign in
Free trial
Coverage

Where this works —
and where the browser stops us.

One script goes on any website that lets you add code to every page. Pick your platform to see where it goes.

Pick your platform ↓

northgate-dental.example/bookONE JOURNEY, FOUR MECHANISMS
A form that answers in place
Email
dana@example.com
Request an appointment
Booking confirmed — Tuesday 10:00
A button that calls an API
Book appointment
POST /api/booking
Booking confirmed — Tuesday 10:00
An in-page step
/book/book/confirmed
Booking confirmed — Tuesday 10:00
A dialog
Choose a timeTuesday 10:00
Booking confirmed — Tuesday 10:00
SiteAirbag · one taught journey
judged the same way
Journey taught once · 3 steps
Step caused by this action
Completion matches what was taught
No plugin, theme or framework consulted
Success · no backup shown
Illustrative simulation. The mechanism changes four times; the judgement does not.
Where the line goes

Where do you build your website?

Paste the script into a site-wide header setting: your theme's header code option or a header-and-footer code plugin.

Supported. Confirmed by the SiteAirbag founder, 09 oct 2026.

Script tag
<script async src="https://siteairbag-web-staging.abrarkanekar12.workers.dev/v1.js" data-site="YOUR_SITE_ID" data-install-token="sa_it_ONE_TIME_CODE"></script>

  • WordPress.com sites need a plan that allows plugins or custom code.
  • Clear any caching plugin or host cache after installing. Optimisation plugins that delay or combine scripts may need SiteAirbag excluded.

YOUR_SITE_ID and sa_it_ONE_TIME_CODE stand in for your website's ID and one-time install code. The setup wizard fills in the real ones after you sign up. If the install check fails, contact support and we will help you get set up.

What we protect

Coverage is a question about mechanics, not brands.

SiteAirbag judges how a browser completes a journey, not which plugin drew it.

Forms that answer in place

Covered

A contact, quote or booking form that submits in the background and answers without reloading the page.

Success needs the confirmation taught during setup. A background answer on its own is progress.

Last tested: 16 sep 2026

  • The confirmation has to appear in the page; a reply that only reaches your inbox cannot be observed from a browser.

Forms that reload or redirect

Covered

A classic submission that posts the page and lands somewhere else, including post-redirect-get.

Success needs the destination taught during setup, and the run continues onto that page.

Last tested: 16 sep 2026

  • The destination page has to load SiteAirbag as well, or the run ends where the page did.

Buttons that call an API

Covered

A Book, Checkout or Send control wired to JavaScript rather than to a form.

Success needs the confirmation. A request that answers without one is progress.

Last tested: 16 sep 2026

  • A control wired to nothing at all is reported as unknown rather than failed, unless your page shows an error.

In-page steps in client-rendered apps

Covered

React, Next.js and similar apps that move between steps without a full page load.

A step this journey caused is progress. Success still needs the completion taught with it.

Last tested: 16 sep 2026

  • Only steps the journey itself caused count; a visitor using your navigation earns it nothing.

Dialogs and multi-step journeys

Covered

A journey that opens a panel, takes a step or two inside it, and confirms there.

Opening the dialog is progress; the confirmation inside it is the completion.

Last tested: 16 sep 2026

  • Steps rendered inside a frame from another domain fall under the boundary below.

Phone, email and download hand-offs

Up to a limit

tel:, mailto:, sms: and download links that hand the visitor to another application.

Reported as progress when invoked, never counted as a success, and never used as failure evidence.

Last tested: 16 sep 2026

  • What happens after the hand-off is outside the browser, so no outcome can be confirmed either way.

Embedded booking and payment widgets

Up to a limit

A scheduler or checkout embedded on your page from another company.

Events the widget publishes to your page are read as evidence, and are never required for a verdict.

Last tested: 16 sep 2026

  • The contents of a frame from another domain are closed to every script by browser design, SiteAirbag included.
  • A widget that publishes nothing leaves the journey judged on what your own page does.
Fail-open, even here

If the runtime never loads, your site keeps working.

SiteAirbag cannot operate if the host page or runtime never loads, JavaScript is disabled, or a Content Security Policy blocks the configured runtime. If SiteAirbag is unavailable, the original site action remains in control.

Read the installation guide →

northgate-dental.example/bookRUNTIME UNAVAILABLE
runtime.siteairbag.com/v1.jsrequestingblocked by Content-Security-Policy

Request an appointment

Name
Dana Whitlock
Email
dana@example.com
Request an appointment
Thanks, Dana — we'll confirm within the hour.
SiteAirbag · not running
0 protected actions
Runtime asset never loaded
Nothing observed, nothing recorded
Original form stays in control
Your website is unchanged
Illustrative simulation. Every failure of ours has to land here: the visitor's own path, untouched.

Where browser observation stops

Where browser observation stops

Most of these limits are the browser's, and no vendor integration removes them. Publishing them is how you can tell what the rest of this page is worth.

northgate-dental.example/bookOBSERVATION BOUNDARY
Your page
your control
Book appointment
your confirmation
Booking confirmed
scheduler.example · another domainObservation stops at this edge
tel:+1 555 0100leaves the browser
What can be judged
Your own page · observed
Events a widget publishes to you · read as evidence
Inside a frame from another domain · closed to every script
After a hand-off · outside the browser
Completions that only reach your inbox · never claimed
What the visitor typed · never read
The boundary belongs to the browser, not to a setting. Where SiteAirbag cannot see a completion it reports progress instead of claiming one.

Inside a frame from another domain

An embedded scheduler or checkout is a separate document, and the browser closes it to every script on your page. Whatever it publishes to you is read as evidence; nothing else can be.

After a hand-off

A phone call, an email client or a downloaded file leaves the browser. SiteAirbag records that the hand-off happened and stops there — never a success, never a failure.

Completions that only exist off the page

If the journey really finishes in your inbox, CRM or phone system, the browser has nothing left to confirm. SiteAirbag reports progress rather than claiming a completion it never saw.

What the visitor typed

Field contents, keystrokes and page replays are never read or stored. That is a deliberate limit, not a missing feature.

Not sure your journey is covered?

The install guide walks through each platform step by step. If something does not work, support will look at your actual setup.

Read installation stepsContact support