Smartwaiver conversion tracking: the waivers pile up, but Google Ads says nothing happened
Your ads send people to sign the waiver before they show up, and then the trail goes cold. The signature happens on Smartwaiver's form, walk-ins sign on the front-desk kiosk, and Google Ads and Meta are left counting clicks on a "Sign waiver" button while bidding guesses. We wire Smartwaiver's auto-tagging, redirect URL and webhooks into a first-party setup, so online signings and the check-ins that follow go back to the ad that earned them, counted once per group.
Free30 minutesNo obligation
Smartwaiver · what breaks
What goes wrong with Smartwaiver and your ads
- 01
"Google says nobody signed up, but the park was packed"
The waiver is signed on waiver.smartwaiver.com, a page your tags don't run on, or in Smartwaiver's Waiver Widget, where we check whether your tags see the submit at all. Usually your ad accounts see the button click and nothing after it, so bidding learns from people who opened the form and left, and you pay for more of them.
- 02
"One family shows up as five customers"
A parent signs, then taps "Anyone else need to sign?" for the rest of the party. Smartwaiver says its auto-tagging uses cookies, so several waivers can end up with the same tag, and a setup that fires on every waiver tells Meta one birthday party was five new customers.
- 03
"Meta takes credit for our regulars"
Front-desk kiosk signings and returning climbers renewing an expired waiver land in the same list as online pre-signs. Send all of them to Meta and it claims walk-ins it never brought, which makes the wrong campaign look worth scaling.
- 04
"Booked in FareHarbor, signed in Smartwaiver, counted twice"
Zipline, boat rental and tour operators often take the booking in one tool and the waiver in another. When both fire a conversion, Google Ads doubles your results and you can't tell which ads actually sell trips.
Smartwaiver · the fix
What changes once it's fixed — Smartwaiver
Online signers tied back to the click
A short first-party key rides in the waiver link's auto_tag value and comes back on the signed waiver, so the match to the original Google or Meta click happens on our server, not in a cookie the browser can drop.
One visit, one conversion
Waivers sharing a tag collapse into a single arrival. Minors, extra participants, kiosk signings and renewals are labeled and kept out of acquisition.
Bidding on arrivals, not button clicks
Smartwaiver's check-in webhook becomes the conversion Google Ads and Meta optimize on, with the booking value added once we've confirmed your reservation or POS system links to the waiver.
Smartwaiver · architecture
What Smartwaiver actually lets you hook into
These come from Smartwaiver's help center and API documentation. We didn't find a native Google Analytics, Google Ads or Meta Pixel connection there, so that part is something we confirm on your account rather than assume.
- 1
Auto-tagging on the waiver URL
Smartwaiver documents an auto_tag value of up to 64 characters added to the waiver link and saved on the signed waiver. It relies on cookies, so several waivers can carry one tag.
- 2
Redirect URL after signing
Sends the signer to a page you choose right after they submit, with separate handling for signers who still have to verify their email, and fills in the [waiverid] and [autotag] placeholders.
- 3
Webhooks for new waivers and check-ins
Smartwaiver posts the waiver's ID and the event name (new waiver, email verification or check-in) within seconds, retries failed sends, and can fire before email verification, after it, or both.
- 4
API v4 lookups and prefill
Returns the signed waiver with its auto tag, kiosk flag, participants, minor status and marketing opt-in. Prefill links can carry an external ID from your own system.
- 5
Booking and email integrations
FareHarbor, Rezdy, Xola, Rock Gym Pro, Mailchimp and Constant Contact are listed by Smartwaiver. They move waiver data, not ad conversions.
Smartwaiver · diagnose
Where Smartwaiver tracking breaks, in the order we check
We start with how a signed waiver gets counted, because on a Smartwaiver setup overcounting is as common as missing data.
- 01
Sign one waiver from an ad-tagged URL
Then open it in the console and see whether an auto tag arrived at all.
- 02
Check where the signer lands afterward
Without a redirect URL, the session ends on Smartwaiver's page and your tags never see the finish.
- 03
Count conversions for one family signing
Three waivers under one tag should produce one conversion, not three.
- 04
Split kiosk signings from online ones
The kiosk flag on each waiver tells us which signings no ad could have caused.
- 05
Compare check-ins with reported arrivals
Day by day for a closed week, using the check-in tool's counts against what Google Ads and Meta report.
Smartwaiver · prove
How we prove it on your Smartwaiver account
Run on real signings through your live waiver links and widget, plus one test on the front-desk kiosk.
Source of truth
Smartwaiver records: signed waivers exported by date range, check-ins from the check-in tool, and each waiver's auto tag, kiosk flag and participants read through the API
- One online waiver signed from an ad-tagged link, with the auto tag visible on the signed record.
- The redirect page firing once per signing with the waiver ID as the shared event ID.
- A family signing three waivers producing exactly one conversion in Google Ads and in Meta Events Manager.
- A kiosk signing confirmed absent from ad conversions.
- A check-in arriving server-side within the webhook window and matched to the original click.
- Online signers and check-ins reconciled record by record across a closed week.
- The family, kiosk and check-in tests rerun 30 days on, and again whenever the waiver template or redirect changes.
Smartwaiver · free audit
What we check in the free audit
- Sign one waiver from an ad-tagged URL
- Check where the signer lands afterward
- Count conversions for one family signing
- Split kiosk signings from online ones
- Compare check-ins with reported arrivals
Checked against
Smartwaiver records: signed waivers exported by date range, check-ins from the check-in tool, and each waiver's auto tag, kiosk flag and participants read through the API
Free30 minutesNo obligation
Smartwaiver · when not to buy
When you don't need this on Smartwaiver
Plenty of venues using Smartwaiver don't have an ad tracking problem worth paying to fix.
- If almost everyone signs on the kiosk at the counter and you don't run paid ads, the Waiver Console's own counts tell you what you need.
- If your booking system already reports paid bookings to Google Ads and Meta correctly, the waiver is housekeeping, and adding it as a second conversion would only double your numbers.
- If your ad spend is small and steady, comparing the check-in tool's daily totals with spend once a month may be all the tracking you need.
- If the only problem is a stray tag firing on your "Sign waiver" button, removing it is a quick fix and we'll tell you to do it yourself.
Smartwaiver · what we deliver
The event map on Smartwaiver
Waiver link or widget opened
Fired on your own site, with the first-party key written into the auto_tag parameter on the waiver link.
Waiver submitted online
The redirect URL lands the signer on your confirmation page with [waiverid] and [autotag], so the browser event and the server event share one ID.
Email verified
Used only if your template requires verification; the webhook and redirect timing are set to match.
Checked in
The arrival conversion, sent server-side from the check-in webhook after a lookup of the waiver through Smartwaiver's API.
Booking or sale matched
Value taken from FareHarbor, Rezdy, Xola or your POS where it links to the waiver; we confirm the link on your account first.
Excluded from acquisition
Kiosk signings with no online visit, minors and extra participants under one signer, and returning guests renewing an expired waiver.
Written guarantee
95%+ tracking accuracy
Measured against Smartwaiver records: signed waivers exported by date range, check-ins from the check-in tool, and each waiver's auto tag, kiosk flag and participants read through the API. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Smartwaiver questions, answered
We didn't find a documented native connection in Smartwaiver's help center or API docs. What it does document is auto-tagging, a redirect URL, webhooks and an API, and those are enough to build accurate tracking on your own domain.
For walk-in venues like trampoline parks, climbing gyms and shooting ranges, an online pre-sign or check-in is the closest thing you have to an arrival, so yes, once per group. If you take bookings in FareHarbor or another reservation tool, the booking is the conversion and the waiver should stay secondary.
Auto-tag holds up to 64 characters, and we don't rely on Google or Meta click IDs fitting inside it. We pass a short first-party key instead and keep the full click ID on your server, where the match happens.
Usually because every waiver, or every participant on it, fires: a parent and their kids, a whole bachelor party, or kiosk walk-ins. Rolling waivers up by tag and dropping kiosk signings fixes most of it.
Smartwaiver's webhook can fire before verification, after it, or both, and the redirect handles unverified and verified signers separately. We choose that timing on purpose, so a conversion isn't lost when someone never clicks the email.
Redirect URLs are set per waiver in the Waiver Editor, so a new waiver template needs its own redirect before it tracks anything. We retest after every template change and again a month on, and the server-side check-in feed reads Smartwaiver's API, so a layout edit won't touch it.
More on Smartwaiver
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Smartwaiver, and what their bookings feed
- Google FormsWhy can't I track my Google Form in Google Ads or Meta?
- HIPAAtizerPatients fill out your HIPAAtizer form. Why can't Google Ads tell which clicks became admissions?
- HubSpot FormsYour HubSpot form fills up, but which ads bring clients you'd actually call back?
- HIPAA FormsGoogle Ads stopped seeing intakes after you installed HIPAA Forms
- FormstackYour Formstack intake forms get filled, but which ads bring patients who actually book?
Free · 30 min
Find out which ads actually fill your sessions
WhatsAppFree30 minutesNo obligation
