-
Notifications
You must be signed in to change notification settings - Fork 283
@segment/analytics browser actions [email protected] #3196
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
@segment/analytics browser actions [email protected] #3196
Conversation
…, including tests and generated types
… browser action destination
Hi @mohamadhase thanks for raising this PR for a new Web Integration. Best regards, |
Thank you for reviewing the PR. I’ve booked a meeting through your Calendly link. Best regards, |
… type definitions, and enhance test cases for identifyUser and visitPage actions.
Hi @joe-ayoub-segment , |
Hi @mohamadhase we still have some failing tests. Are you able to take a look please? |
PR Summary: Add FullSession Browser Destination
Overview
This PR introduces a new browser-mode destination for FullSession, a session recording and analytics platform. The destination enables customers to stream Segment events to FullSession for user identification, event tracking, and page visit recording.
🚀 New Features
1. FullSession Browser Destination
@segment/analytics-browser-actions-fullsession
2. Three Actions Implemented
Identify User Action
identify
events to FullSession user identificationRecord Event Action
track
events to FullSession custom eventsVisit Page Action
page
events to FullSession page visit trackingTest Coverage
🔧 Configuration
Required Settings
Default Subscriptions
type = "identify"
→ Identify User actiontype = "track"
→ Record Event actiontype = "page"
→ Visit Page actionTest Coverage
33 total tests across all actions and main destination
100% action coverage with edge cases and error scenarios
Added unit tests for new functionality
Tested end-to-end using the local server
[If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
[Segmenters] Tested in the staging environment
[Segmenters] [If applicable for this change] Tested for regression with Hadron.