references/conversion-moments.md · 24000
the trigger filters acuity_type to
appointment. cal-com also counts bookings still waiting for
the host to confirm, marked booking_status PENDING. hubspot-forms also counts
submissions HubSpot's bot filter files under Spam. framer-forms fires when Framer's own form
endpoint answers its request with success. squarespace-forms fires only once Squarespace
confirms the save, through its own success markers or its save request, never on the
submit alone. wix-forms fires when Wix's own thank-you
message appears inside the form, which Wix shows only after the entry is saved. It covers
Wix's current forms with an inline thank-you message, not older Wix contact forms or forms
set to go to another page after submitting.
Universal patterns
These are not fallbacks of last resort. Two of them are the correct primary answer for whole categories of business.
| Slug | Covers | Notes |
|---|---|---|
| phone-click | Click on a tel: link | The most under-tracked conversion there is. For a plumber, a dentist, a roofer or a lawyer, the conversion is the phone call and no form exists. Counts intent, not answered calls; use a call tracking number if you need answered-call accuracy |
| thank-you-page | Arrival on a confirmation page | Edit the path list at the top. Handles single-page apps by watching history changes, which matters because a React or Next site changes URL without a pageview and a thank-you page trigger silently counts zero |
| generic-ajax-form | Inline success after an AJAX submit | The long tail of unknown form tools. Refuses to fire on submit alone: it waits for a success signal and bails if a visible validation error appears. Weaker than a named detector, so always prefer one when it exists |
| file-download | Click on a document or media link | Price lists, brochures, spec sheets. GA4 already collects this natively; use it when you need the signal in Google Ads or Meta, which do not |
3. The long tail
Never tell someone their tool is unsupported. Every conversion moment falls into one of
the install shapes below, and the universal patterns cover tools with no named detector.
Some of these tools also have native server-side integrations from their own platform, and
managed tools listed there may cover them as built-in triggers; both live in server-side.md. What
"no snippet" means is only that this skill's free browser-side detector does not exist yet.
Shape 1, page listener (28): ActiveCampaign, Kit, AWeber, Mailchimp, Klaviyo, Marketo, Pipedrive, Duda, Avada, Beaver Builder, GoHighLevel, Unbounce, Instapage, Leadpages, Paperform, Fillout, Formstack, Zoho Forms, HelloBar, OptinMonster, ConvertBox, Thrive Leads, HubSpot Meetings, Chili Piper, Intercom, Crisp, Tawk.to, Drift.
Shape 2, WordPress but not a form submit (6): LearnDash, LearnPress, Tutor LMS, Paid Memberships Pro, Ultimate Member, Easy Digital Downloads.
Shape 3, two-part install (2): Pardot, Salesforce Web-to-Lead.
Shape 4, conversion on someone else's domain (5): Kajabi, Teachable, Thinkific, ThriveCart, ClickFunnels checkout.
The install shapes
Work out which one applies, then act.
Shape 1. A page listener works. The tool renders in the page and emits something
observable: its own JS event, a success callback, or a success element appearing. Use
generic-ajax-form, or write a named detector following any shipped snippet.
Shape 2. Same domain, but the moment is not a form submit. An enrolment, a membership
signup, a course completion. There is usually no submit event to hook. Use
thank-you-page against the post-enrolment URL, or a platform hook if one exists.
Shape 3. Half the code has to go inside the vendor's own tool. Classic Pardot forms
are iframes served from a Salesforce domain, so nothing on the parent page can see inside
them. The fix is code pasted into the vendor's own thank-you or completion field that
messages out to the parent page, plus a listener that catches it. acuity-scheduling is
the shipped example (acuity-scheduling-field.html goes in Acuity's Custom Conversion
Tracking field, acuity-scheduling.js catches its message). Walk the user through
the vendor screen; there is no snippet-only answer.
Shape 3b. The moment only the backend knows. A SaaS signup, an account created, a
lead an API received. No browser event exists at all, so no snippet applies and
no GTM recipe can help. The backend has to report it (direct platform APIs or a managed
tool that pairs a backend event with the browser's click IDs, see server-side.md), and
the click ID has to be carried across from the browser session separately. Ecommerce
purchases are not this shape; they route through ecommerce-platforms.md.
Shape 4. The conversion happens on a domain the user does not own. Kajabi, Teachable, Thinkific, ThriveCart, hosted checkouts. Several provide a checkout tracking code field, so a pixel can fire. What cannot cross is the click ID, because it lives in a cookie on the user's own domain and is unreadable from the vendor's. The sale records with no click attached, so the ad platform cannot attribute it.
Be straight about this. It is not a configuration mistake and no snippet fixes it. The
options are cross-domain linking where the vendor supports it, or server-side capture that
carries the identifier server to server (server-side.md). This is the strongest
genuine case for server-side tracking in this skill, so it is also the one where any
recommendation must be most carefully earned rather than assumed.
When nothing here fits
- Ask what happens after submit. Redirect to a new URL, inline message, or nothing visible? That answer alone picks the shape.
- Look at the page. section A above covers the four submit patterns and how to tell them apart.
- Check whether the platform already does it. Native integrations are free and
maintained by the platform where they cover the moment and destination (
server-side.md). Lead with the native path, then present the other options alongside it. - Only then reach for
generic-ajax-formorthank-you-page.
If you build a working detector for a tool not listed here, it is worth contributing back.
4. Ecommerce moments
The inference problem above mostly does not exist for purchases, because an order record does. Use the platform's own confirmed-order surface and never rebuild the inference:
- Shopify:
checkout_completedvia a web pixel, or a native channel doing it for you. The fire-on-confirmed-success rule is satisfied by construction. - WooCommerce: the server-side order hooks (
woocommerce_payment_complete,woocommerce_thankyou), with a tracked flag in order meta so refreshes never double count. - Easy Digital Downloads:
edd_update_payment_statusfor the order lifecycle. - Hosted checkouts on a vendor's domain (Kajabi, Teachable, ThriveCart and similar) are Shape 4 above: a pixel may fire, but the click ID cannot cross domains, which is a structural limit, not a configuration mistake.
- Custom stores: the order-confirmation webhook or handler is the moment. Nothing needs inferring.
Full platform detail, the deprecation calendar, and the shared ecommerce mechanics (dedup, value correctness, feeds, refunds) are in ecommerce-platforms.md.
Key sources: contactform7.com/dom-events; docs.gravityforms.com gform_confirmation_loaded; developer.calendly.com parent-window notifications; typeform.com/developers/embed/callbacks; developers.hubspot.com global form events (v4) + legacydocs (v2); developers.google.com/tag-platform/devguides/existing; simoahava.com container snippet internals; conversiontracking.io Jotform/Typeform/iframe guides; analyticsmania.com per-platform GTM guides; trackingchef.com bulletproof form tracking series; dumbdata.co listeners; freak.marketing Squarespace; framer.com UTM/Ads IDs help; stape.io custom loader docs; wappalyzer source.