Navigation
Page activity supplies route context around explicit product events.
App analytics
App analytics for browser-based SaaS products
Vectr4 provides event-based analytics for browser applications and SaaS products. Its JavaScript browser SDK captures page activity, custom events, properties, identity, and session context for analysis in funnels and user journeys.
01
Separate app analytics from website traffic reporting
Traffic reporting explains visits, referrers, campaign context, and page popularity. App analytics explains what users do after they enter an interactive product: complete setup, create an object, use a feature, or move through a conversion path.
Vectr4 is designed around that second job. Page activity remains useful context, but named product events provide the meaning needed for product analytics.
02
Capture browser-app activity with explicit events
Review event tracking implementation for the collection workflow and validation sequence.
- Initialize the JavaScript browser SDK against the customer-operated ingestion endpoint.
- Track stable event names for meaningful completed actions.
- Attach only the bounded properties needed to interpret an event.
- Use page activity and browser autocapture deliberately rather than collecting sensitive form values.
03
Associate authenticated activity through identity
The browser SDK supports identify calls so future activity can be associated with a stable internal user ID after authentication. Anonymous browser and session context supports analysis before that point.
Do not send passwords, authentication tokens, payment details, or unnecessary personal data in identifiers, event names, URLs, or properties.
04
Analyze app workflows with funnels and sessions
A funnel measures progress through the expected order. Session activity provides context around users who stopped, repeated a step, or took a different route. This helps a team focus investigation without claiming that the data proves motivation.
Use event analytics for the underlying signals and behavior analytics for sequences across the product.
Vectr4 example
account_created → project_created → integration_connected → first_result_viewed
05
Follow user journeys through a browser-based product
Feature use
Named events mark meaningful actions inside a workflow.
Session sequence
Activity is grouped into visits with timing context.
Identified path
Identify calls connect authenticated activity to a deliberate internal ID.
06
Understand the current mobile-app boundary
Vectr4 currently documents a JavaScript browser SDK. It does not provide native iOS or Android mobile SDKs, so this page should not be read as a native mobile-app analytics claim.
A browser-based mobile web app can use the supported browser integration. Teams building native applications should choose an analytics SDK designed for their runtime or wait until native Vectr4 support is explicitly shipped and documented.
07
Deploy app analytics on infrastructure you control
Vectr4 runs as a customer-operated Docker Compose stack. The model can suit technical teams that prefer infrastructure and data-location control and accept responsibility for security, backups, updates, capacity, and legal configuration.
Compare the operating tradeoffs on self-hosted product analytics and the interface on the analytics dashboard.
Product proof
Inspect the Vectr4 product analytics workflow
The hosted demo shows real Vectr4 product views for event activity, funnels, sessions, and user paths. Preview values are illustrative and are not presented as customer benchmarks.
Event activity
Inspect named product actions and the bounded properties sent with them.
Funnels
Connect ordered events to examine progress and drop-off between steps.
Sessions
Review activity as a timed sequence without relying on screen recording.
User journeys
Follow paths through a product for anonymous and identified activity.
FAQ