Conversion tracking for Default forms and meetings
Default sits between your demo form and your reps' calendars: a lead fills in the form, Default decides whether they qualify, and only some of them ever see a scheduler. It pushes its own dataLayer events, including default.form_completed, default.scheduler_displayed and default.meeting_booked, so the raw signal exists. What usually goes wrong is that the iframe bridge script is missing from the host page, or every form completion is sent to the ad platforms as a lead, which teaches them to buy the visitors your routing rules turn away.
Free30 minutesNo obligation
Default · what breaks
What goes wrong with Default in practice
- 01
The gtm.js bridge left off the host page
When the form is iframed, Default's events never reach your container without it, and nothing shows an error.
- 02
Form completions optimized as if they were pipeline
Routing exists because many submitters should not get a meeting. The ad platform does not know that unless you tell it.
- 03
Scheduler shown, then closed
A qualified lead who saw the calendar and walked away is ignored by most setups.
- 04
Booked demos that never happen
A prospect who skips the call is still a win in the ad account.
Default · the fix
What changes once it is rebuilt — Default
Meeting booked as the primary conversion
Fired from default.meeting_booked, never from the form submit.
Qualified-but-unbooked leads visible
Scheduler displayed without a booking, kept as its own signal for follow-up and audiences.
Held meetings sent back from the CRM
So bidding learns from demos that took place, not calendar invites.
Default · architecture
What Default actually lets you do
Default documents its GTM integration more thoroughly than most tools in this category. Here is what that covers and where it stops.
- 1
Five dataLayer events
form_completed, form_page_submitted, scheduler_displayed, scheduler_closed and meeting_booked, each under the default. prefix.
- 2
An iframe bridge script
import-cdn.default.com/gtm.js on the host page forwards events from Default's iframe to your container.
- 3
An importable container
Triggers, a trigger group and an event-category variable. It ships with no tags, so nothing is sent anywhere until someone builds them.
- 4
Event names, not documented payloads
Check what fields each push carries before planning enhanced matching around it.
- 5
No ad-platform sending described
Default's GTM documentation mentions no Meta, Google Ads or LinkedIn delivery of its own; those tags are yours to build.
Default · diagnose
Where Default tracking breaks, in the order we check it
Default failures are usually silent: the form works, meetings land on calendars, and the container simply hears nothing.
- 01
Open GTM preview on the embedding page and submit the form
If no default.* events appear, the bridge script is missing or blocked.
- 02
Check which event the ad conversions fire on
Form completion and meeting booked look alike in a report and mean very different things.
- 03
Compare scheduler_displayed with meeting_booked
The gap is qualified demand lost at the calendar step.
- 04
Count booked meetings that were held
No-shows on cold paid traffic can change which campaign looks best.
- 05
Check whether one form embedded twice pushes twice
An inline embed and a popup on the same page should not produce two meeting_booked events.
Default · prove
The QA evidence — Default
Done on a live Default form on your site, with a real meeting booked on a rep's calendar.
Source of truth
Default's meeting records and your CRM's held-meeting status, per meeting
- A test meeting booked through each embedded Default form, with default.meeting_booked confirmed in the container.
- The bridge script confirmed on every page that hosts an iframe embed.
- Form completions confirmed absent from the bidding conversion.
- Meeting booked deduplicated across browser and server on one event ID.
- Held meetings reconciled per meeting against each platform's reported conversions.
- Disqualified submitters confirmed never to reach the meeting conversion.
- Re-run 30 days later and after any change to Default routing rules.
Default · free audit
What we check in the free audit
- Open GTM preview on the embedding page and submit the form
- Check which event the ad conversions fire on
- Compare scheduler_displayed with meeting_booked
- Count booked meetings that were held
- Check whether one form embedded twice pushes twice
Checked against
Default's meeting records and your CRM's held-meeting status, per meeting
Free30 minutesNo obligation
Default · when not to buy
When you don't need this on Default
Default already does more of the work than most schedulers. Sometimes that is enough.
- If you only want meetings booked in GA4 and are not bidding on them, importing Default's container and adding one GA4 tag may cover it.
- If paid traffic is a small share of demo volume, CRM source reporting may answer your question more cheaply.
- If your sales team does not record whether meetings were held, fix that first; there is nothing to send back until they do.
- A developer comfortable in GTM can wire the browser side in an afternoon from Default's documentation. We will tell you if that is all you need.
Default · what we deliver
The event map for a Default funnel
Form page submitted
Step-level drop-off on multi-page Default forms. Diagnostic only.
Form completed
Every submitter, qualified or not. Kept out of bidding.
Scheduler displayed
The point where Default judged the lead worth a rep's time. A useful secondary conversion.
Meeting booked
The primary conversion, with a shared event ID for deduplication.
Meeting held
From the CRM or calendar record, sent server-side after the call.
Scheduler closed without booking
Kept for retargeting and for measuring friction at the calendar step.
Written guarantee
95%+ tracking accuracy
Measured against Default's meeting records and your CRM's held-meeting status, per meeting. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Default questions, answered
Its documentation describes dataLayer events for GTM, not direct ad-platform delivery. The conversion tags, and any server-side sending, are built in your container.
Yes, if the host page loads Default's gtm.js bridge script, which forwards the iframe's events. Without it the container hears nothing and nothing visibly breaks.
Meetings booked, at minimum. Form completions include everyone your routing rejects, and optimizing on them pushes spend toward exactly those people.
Yes, but that status lives in your CRM or calendar, not in Default's browser events. It is sent server-side after the meeting with the original click identifier.
It gives you triggers and a variable, with no tags. It is a starting point, not a working conversion setup.
More on Default
- Cal.com trackingConversion tracking for Cal.com
- Cal.com server-sideServer-side tracking for Cal.com
- Cal.com + GoogleGoogle Ads and GA4 tracking for Cal.com
RELATED GUIDES
Booking tools beside Default, and what their bookings feed
- GoHighLevel funnelsConversion tracking for GoHighLevel funnels and calendars
- Chili Piper ConciergeConversion tracking for Chili Piper Concierge demos
- involve.meConversion tracking for involve.me funnels
- Meta · Lead gen agenciesMeta Ads conversion tracking for lead generation agencies
- Google Ads · Lead gen agenciesGoogle Ads conversion tracking for lead generation agencies
- Meta × CRM DealsHow to reconcile Meta Ads against your CRM's closed-won deals
- Meta · Demo request → opportunityHow to track demo request to opportunity for Meta Ads
- Lead gen agenciesProving lead quality when volume is the only thing being measured
Free · 30 min
Get Default tracking done properly
WhatsAppFree30 minutesNo obligation
