Skip to main content
WaiverForeverForms

WaiverForever conversion tracking: guests sign before they arrive, and your ads never hear about it

Your ads push riders, jumpers and renters to sign ahead, and WaiverForever collects the waivers fine. The trouble is where they get signed: a hosted link on app.waiverforever.com, a pop-up widget that closes itself 10 seconds after submit, or the tablet kiosk at the counter. None of those report back to Google Ads or Meta on their own. We wire the widget's signed callback and WaiverForever's webhooks into a first-party setup, so each online signing and each check-in reaches the ad that earned it, once.

Free30 minutesNo obligation

WaiverForever · what breaks

What goes wrong with WaiverForever and your ads

  1. 01

    "We get waivers all day, but Google Ads shows zero conversions"

    The off-site signing link and its QR code send guests to app.waiverforever.com, and WaiverForever documents no place there for your Google tag or Meta Pixel. Your ad accounts see a tap on "Sign your waiver" and then nothing, so bidding chases people who open the form and leave, and cost per booked rental creeps up.

  2. 02

    "The pop-up disappears and takes the conversion with it"

    The waiver widget lets guests sign without leaving your site, then shuts itself 10 seconds after they submit. No thank-you page ever loads, so a page-view goal never fires, and the usual patch, a click trigger on the sign button, reports every opened form as a finished waiver.

  3. 03

    "One booking, a party of five, six conversions"

    Bookeo and Acuity bookings, and FareHarbor bookings through Zapier, can open a request group in WaiverForever and email the customer a signing request, and the group tracks how many members have signed. If every member's signature fires a conversion on top of the booking, Meta reads one five-person kayak tour as six new customers and shifts budget toward whatever looks busiest.

  4. 04

    "Meta keeps taking credit for walk-ins"

    Kiosk waivers from the iOS or Android app, which can sign offline and upload later, land in the same list as online pre-signs. A Zapier zap on "New Waiver Signed" sends all of them out, so the trampoline park's Saturday walk-ins show up as ad results and the wrong ad set gets scaled.

WaiverForever · the fix

What changes once it's fixed — WaiverForever

  • Every website signing counted once

    A browser event fires from the SDK's onSigned callback on your page, and the matching new_waiver_submitted webhook sends a server copy. Both carry the same first-party key, so Google and Meta dedupe instead of doubling.

  • Bidding on guests who showed up

    WaiverForever's waiver_checkin webhook becomes the arrival conversion, valued from the Bookeo or Acuity booking or a Square payment taken on the waiver, wherever we can confirm that amount reaches our server.

  • Walk-ins and party members labeled, not counted

    Each waiver carries a signing-device field and a request ID. Once we confirm how your account fills them, kiosk signings and extra party members stay in your reports but out of the numbers ad platforms learn from.

WaiverForever · architecture

What WaiverForever actually lets you hook into

From WaiverForever's own help center and API docs. Where they go quiet, it's listed as a test.

  1. 1

    Off-site signing link and QR code

    Hosted on app.waiverforever.com. No documented way to add your own tags, so we treat it as blind to your analytics.

  2. 2

    Redirect URL

    Set under Template Settings, Online Signing, it sends link signers to a page you own afterward. We test whether anything identifying the waiver comes along.

  3. 3

    Waiver widget and JS SDK

    A script on your site; SDK mode adds show() for your own button and an onSigned callback. Widget and SDK modes can't run together.

  4. 4

    Waiver Embed

    A code snippet from the template's Embed tab. We confirm whether your tags can see its submit before relying on it.

  5. 5

    Webhooks, API and prefill links

    Webhooks for submitted, accepted, PDF generated and check-in, signed with an X-WaiverForever-Signature header. The API also generates prefill links with expiry dates.

  6. 6

    Zapier, no ad connectors

    Zapier offers a New Waiver Signed trigger. No native Google Ads, GA4, Tag Manager or Meta connection is documented.

WaiverForever · diagnose

Where WaiverForever tracking breaks, in diagnostic order

Start with the widget: on most adventure and rental sites, that's where online signings happen and counts go most wrong.

  1. 01

    Count conversions on one widget signing

    Zero means a page-view goal waiting for a page that never loads. Several means a click trigger.

  2. 02

    Sign once through the hosted link from an ad-tagged URL

    Then check whether the redirect lands on your page and whether the click ID survives.

  3. 03

    Separate kiosk waivers from online ones

    We start with the signing-device field on each waiver and confirm on your account that it actually tells a counter tablet from a phone browser.

  4. 04

    Compare request groups with bookings

    Bookeo, Acuity or FareHarbor sales against the waivers they triggered.

  5. 05

    List every Zapier zap on New Waiver Signed

    And where each one sends its data.

WaiverForever · prove

The QA evidence — WaiverForever

Every check below uses a guest-style signing on your public widget, hosted link and counter tablet. Template previews in the WaiverForever dashboard don't count.

Source of truth

WaiverForever's waiver list and CSV export: signed waivers by date and template, with request groups, check-ins and the signing device

  • One widget signing from an ad-tagged URL producing exactly one Meta and one Google conversion.
  • One hosted-link signing landing on your redirect page.
  • Submitted and check-in webhooks logged on our server with valid signatures.
  • A kiosk signing confirmed absent from ad conversions.
  • A request group of several riders counted as one arrival.
  • Check-ins reconciled per waiver against Google Ads and Meta across a closed week.
  • Rerun a month after launch, and again whenever you edit a waiver template or swap widget mode for SDK mode.

WaiverForever · free audit

What we check in the free audit

  • Count conversions on one widget signing
  • Sign once through the hosted link from an ad-tagged URL
  • Separate kiosk waivers from online ones
  • Compare request groups with bookings
  • List every Zapier zap on New Waiver Signed

Checked against

WaiverForever's waiver list and CSV export: signed waivers by date and template, with request groups, check-ins and the signing device

Get my free conversion tracking audit

Free30 minutesNo obligation

WaiverForever · when not to buy

When you don't need this on WaiverForever

Some accounts have nothing worth attributing.

  • If almost everyone signs on the kiosk at the counter, there's no online signing to tie to an ad. Track the booking instead.
  • If your booking engine already reports purchases correctly and the waiver is only a follow-up email, keep the waiver out of your ad conversions entirely.
  • If you're a tattoo or piercing studio collecting consent forms at the counter after clients book by DM or phone, the waiver isn't where the ad conversion happens. Track the inquiry instead.
  • If the only fault is a GTM click trigger on your "Sign waiver" button, delete it and move the conversion into onSigned. We'll show you where, and you won't need to pay us for it.

WaiverForever · what we deliver

The event map on WaiverForever

  • Sign button opened

    Fired on your site in SDK mode, with click IDs stored first-party before the waiver opens.

  • Waiver submitted online

    onSigned in the browser plus new_waiver_submitted from the server, deduplicated on a shared key.

  • Waiver accepted

    Used in place of submitted only if your staff review pending waivers; sent from new_waiver_accepted.

  • Guest checked in

    The arrival conversion, sent server-side from the waiver_checkin webhook.

  • Paid or booked

    A Square payment taken on the waiver, or the linked Bookeo or Acuity booking, counted once with its value after we confirm where that amount can be read.

  • Excluded from acquisition

    Kiosk signings with no web visit, extra signers in a request group, and revoked waivers.

Written guarantee

95%+ tracking accuracy

Measured against WaiverForever's waiver list and CSV export: signed waivers by date and template, with request groups, check-ins and the signing device. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

WaiverForever questions, answered

Not natively, based on its own docs. It lists Zapier, booking tools like Mindbody, Bookeo and Acuity, and an API with webhooks, but no Google Ads, GA4, Tag Manager or Meta connection, so that link has to be built.

Free · 30 min

Get your WaiverForever signings counted right

Free30 minutesNo obligation