-
Notifications
You must be signed in to change notification settings - Fork 10.4k
feat: Add PostHog event tracking for booking flow monitoring #22187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Add PostHogBookingTracker for client and server-side event tracking - Integrate tracking into booking creation, calendar events, payments, webhooks - Add comprehensive event properties for debugging and analytics - Create PostHog dashboard queries and integration documentation - Enable monitoring of booking conversion funnel and error tracking Co-Authored-By: udit@cal.com <udit222001@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
✅ No security or compliance issues detected. Reviewed everything up to b0697f4. Security Overview
Detected Code ChangesThe diff is too large to display a summary of code changes. Reply to this PR with |
- Add BookingPostHogProvider with team-based feature flag control - Implement simplified funnel tracking for 4 key booking steps: - booking_started: Initial booking attempt - form_filled: User completes booking form - payment_initiated: Payment process begins - booking_completed: Successful booking creation - Enable session replays only for booking pages when feature flag active - Remove complex distributed event tracking in favor of focused analytics - Add comprehensive documentation for setup and usage - Maintain backward compatibility with existing logging systems Behind feature flag: posthog-booking-tracking Co-Authored-By: udit@cal.com <udit222001@gmail.com>
This PR is being marked as stale due to inactivity. |
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
feat: Add PostHog booking funnel analytics and session replays
Fixes: https://linear.app/calcom/issue/CAL-6220/posthog-tracking
Fixes: #22971
Summary
This PR implements focused PostHog integration for Cal.com booking flows, replacing the previous comprehensive event tracking approach with targeted funnel analytics and session replays. The integration is controlled by a team-based feature flag (
posthog-booking-tracking
) and only activates for booking pages when enabled.Key Changes:
booking_started
,form_filled
,payment_initiated
,booking_completed
posthog-booking-tracking
flagThe implementation focuses on actionable insights for conversion optimization rather than comprehensive event logging, leveraging PostHog's built-in funnel analysis capabilities.
Review & Testing Checklist for Human
Recommended Test Plan:
posthog-booking-tracking
feature flagDiagram
Notes
posthog-booking-tracking
feature flag must be created and enabled for teams before this integration will activateSession Details:
Testing Screenshots:
