Web analytics
Explains acquisition: pages, referrers, campaigns, devices, and traffic trends.
Product analytics
Product analytics for teams that want useful behavior data without losing control of it
Vectr4 turns product events into a focused view of how people move through a SaaS product. Track meaningful actions, connect them into funnels and sessions, and inspect user journeys from a Docker Compose deployment on infrastructure you operate.
01
Product analytics explains what happens after the visit
Product analytics is the practice of using product activity to understand adoption, activation, conversion, and friction. Instead of stopping at a visit or pageview, it follows meaningful actions inside an application.
A useful setup starts with a small measurement plan: define the decisions your team needs to make, capture the events that represent those decisions, and review sequences rather than collecting everything by default.
02
Product analytics and web analytics answer different questions
Teams often need both. Vectr4 is designed primarily for product behavior. If your only question is how visitors reached a marketing page, a focused web analytics tool may be a better fit.
Product analytics
Explains behavior: events, activation steps, funnels, sessions, and paths inside the product.
03
Measure actions that represent real product progress
- Analyze product events such as account creation, project creation, checkout starts, and completed workflows.
- Associate known activity with a deliberate internal user identifier after authentication.
- Use event properties for plan, product area, workflow step, or other necessary context.
- Review page activity alongside custom actions without treating every click as a product outcome.
Vectr4 example
landing_viewed → demo_opened → signup_submitted → workspace_created → install_started
04
Connect events into funnels and behavior sequences
Funnels turn separate actions into an ordered path. They help a team locate the step where a signup, activation, or checkout flow loses users. Sessions provide the surrounding sequence, while user journeys connect activity across the product.
Vectr4 uses captured events as inputs for funnel, session, and journey views. Start with event tracking, then use user behavior analytics to interpret what those sequences mean.
05
Use behavior data to answer focused product questions
Activation
Which meaningful actions do successful new users complete?
Conversion
Where does the path from demo to signup or checkout break?
Feature use
Which named product actions appear in real user sessions?
Journey friction
Where do users loop, backtrack, or leave a workflow?
06
Treat cohort and retention questions as a capability boundary
Cohort tables and dedicated retention reports are distinct analytics capabilities. Vectr4 should not be presented as providing those reports until they are verified in the shipped product.
Vectr4 can capture the repeat events and identity context that future cohort or retention analysis would depend on. For now, use its verified event, funnel, session, and journey workflows rather than implying a dedicated cohort suite.
07
Run the analytics stack on infrastructure you control
Vectr4 is delivered as a Docker Compose stack for your VPS. You operate the application, event ingestion services, and supporting data services, which gives you deployment control and direct responsibility for security, backups, updates, availability, and retention.
Review self-hosted product analytics for the deployment tradeoffs, or compare evaluation criteria on the product analytics tools page.
08
Built for technical founders and small SaaS teams
Vectr4 fits teams that need a focused product analytics layer and are comfortable operating Docker Compose. It is not intended to replace a warehouse, CRM, qualitative research system, or broad enterprise data suite.
Use the hosted demo to inspect the workflow before purchasing or deploying anything.
Product proof
Inspect real product activity in Vectr4
The hosted demo shows the same focused workflow described on these pages: captured events, funnel steps, session activity, and user paths. The values shown in marketing previews are illustrative, not customer benchmarks.
Event activity
Review named product actions and the context sent with them.
Funnels
Connect ordered events to see progress and drop-off between steps.
Sessions
Group activity into visits so isolated actions have sequence and timing.
User journeys
Follow the paths users take through your product over time.
FAQ