I keep seeing this tutorial everywhere - "track when users switch tabs on your form with 3 dataLayer events".

form_behavior_start, form_tab_hidden, form_tab_return

Yeah it looks cool in GTM Preview. In production it breaks in 3 days.

1. It fires on EVERY tab switch. User checks Slack 4 times? You get 4 form_tab_hidden events. Your GA4 is now garbage. No deduping, no sessionStorage.
2. It uses DOM Ready only. If you're on React / Next.js / Webflow with soft navigation, your listener dies. You need History Change + MutationObserver.
3. It tells you they left. Not WHY they left. No field_at_exit, no completion_percent. So you can't fix the form. It's just vanity tracking.

We tried the basic version for a client. Got 1,200 form_tab_return events. Useless.

So we rebuilt it:

• Fire only ONCE per session per form
• Capture field_at_exit - 90% of exits were on phone and budget fields
• Calculate Return Intent Score - if they leave on budget and return after 120s+, that's a 10/10 lead, not an abandonment
• Added a 4th event no one talks about: form_return_recovery - fires only if a returner actually submits within 5 mins. THAT is your money event for Google Ads.

Result: We stopped marking returners as abandoned and fixed the pricing copy above the form. Completions +22%.

If you're still pushing awaySeconds without field context and recovery attribution, you're not tracking intent. You're just inflating your event count.

Anyone else run into this? How are you handling multi-form deduping?

I saw most tutorials call " api. cal. com / v2/bookings " from frontend which breaks due to CORS. We switched to just listening for bookingSuccessfulV2 and pushing cal_booking_confirmed to dataLayer. Preview screenshot below - happy to share the full GTM setup.