Track Calendly booking conversions from the credentialing RCM landing page
Set up GA4 so we can measure booking conversions that start on the Credentialing Guarantee landing page. The page links out to a Calendly scheduler, so the booking completes on calendly.com. These steps make GA4 capture that booking and attribute it back to the campaign. Takes ~30 min plus one test booking.
What's already true
- Landing page is
www.carepatron.com/campaign/credentialing-guarantee. - It is not an inline embed. The page links out to Calendly's hosted scheduler (hero CTA and bottom CTA), tagged
utm_content=guarantee_lp_heroandutm_content=guarantee_lp_cta. - Calendly's GA4 integration is already configured with Measurement ID
G-SFCSMGTCE3(Calendly → Integrations & apps → Google Analytics). Calendly fires its events into that property. - The landing page loads through Google Tag Manager container
GTM-W2SWJXF. There's no hard-coded GA4 ID in the page source; GTM injects the GA4 config tag at runtime. - The event that fires when a booking completes is
invitee_meeting_scheduled. That's the one to track. - GA4 renamed "Conversions" to "Key events" in 2024. The toggle you'll look for is labelled Mark as key event.
The Calendly → GA4 event funnel
| Event name | Funnel stage |
|---|---|
invitee_scheduling_page | Landed on scheduler |
invitee_event_type_page | Viewed event type |
invitee_select_day | Picked a day |
invitee_select_time | Picked a time |
invitee_meeting_scheduled | Booking complete — the key event |
invitee_visits_routing_form and invitee_submits_routing_form only fire if routing forms are used. They're not part of this flow.
The checklist
Confirm both sides report into the same GA4 property
Do this first. Everything else depends on it. Calendly fires into G-SFCSMGTCE3. The landing page fires through GTM container GTM-W2SWJXF, which injects a GA4 config tag. Confirm that tag's Measurement ID is also G-SFCSMGTCE3. If GTM loads a different property, the booking event and the landing-page traffic sit in two separate properties and can never be reconciled.
Check it one of these ways:
- Open GA4 → Admin → Data Streams, and open GTM container
GTM-W2SWJXF, then read the Measurement ID on the GA4 Configuration / Google Tag. - Or use GA4 DebugView / Realtime while loading the landing page and confirm hits land in the
G-SFCSMGTCE3property.
Decision point — resolve before moving on
If GTM already loads G-SFCSMGTCE3 → you're good. Proceed to Step 2.
If GTM loads a different property → pick one:
(a) Repoint Calendly's GA4 integration (Calendly → Integrations & apps → Google Analytics → Edit) to the landing page's property ID, or
(b) Add a second GA4 config in GTM that also sends to G-SFCSMGTCE3.
Whichever you choose, the landing page and Calendly must end up in the same property before continuing.
Turn on cross-domain tracking
The booking happens on calendly.com, so by default GA4 treats it as a new session referred by "calendly.com" and loses the landing-page source and UTMs. Cross-domain measurement stitches the two domains into one session so the booking keeps its credentialing-LP attribution.
- GA4 → Admin → Data Streams → select the web stream for
G-SFCSMGTCE3→ Configure tag settings → Configure your domains. - Add both domains with a "contains" match.
- Save.
Fire a test booking so the event appears in GA4
GA4 only lets you mark an event as a key event after it has seen the event at least once. Do a real test booking end-to-end from the landing page so invitee_meeting_scheduled registers.
- Open the landing page, click the Calendly CTA, complete a test booking.
- Watch GA4 → Admin → DebugView (or Reports → Realtime) and confirm
invitee_meeting_scheduledfires. - Ideally confirm the session source/medium reflects the campaign (
utm_source=carepatron/utm_campaign=managed_billing_launch) rather than "calendly.com / referral". If it still shows the referral, recheck Step 2.
Mark invitee_meeting_scheduled as a key event
- GA4 → Admin → Events (under Data display).
- Find
invitee_meeting_scheduledin the events list. It only shows up after Step 3. - Toggle Mark as key event on.
Add an on-page "click to book" proxy conversion
Recommended. This is fully attributable to the landing page with no cross-domain dependency, and it lets you compare the hero CTA vs the bottom CTA. It also exposes Calendly-side drop-off (clicks vs actual bookings). Pick one of these two approaches.
Simplest (GA4 Enhanced Measurement): outbound clicks are already captured as the click event with a link_url parameter. Create a key event or audience from click where link_url contains the Calendly path below.
Cleaner (GTM): in GTM-W2SWJXF add a Click trigger on links containing the Calendly path, firing a GA4 Event tag named book_call_click. Pass utm_content (or the click URL) as an event parameter so guarantee_lp_hero and guarantee_lp_cta stay distinguishable. Then mark book_call_click as a key event in GA4.
Report on it
- Build a GA4 Exploration (or a simple report) filtered to the credentialing campaign. Segment booking conversions by
utm_contentto compareguarantee_lp_herovsguarantee_lp_cta. - The gap between
book_call_click(Step 5) andinvitee_meeting_scheduled(Step 4) is Calendly-side drop-off worth watching.
G-SFCSMGTCE3 is also the property used by the Learning Centre, so credentialing bookings land in a shared property. Always apply the campaign UTM filters when reporting to isolate credentialing-LP conversions.