Used this Ruby visit/event tracking library to add server-side funnel analytics to an app with no client-side JavaScript and no user accounts. Configured cookieless mode with IP masking, geocoding and the JS endpoint disabled, wrote trimmed migrations for the visits/events tables, subclassed its database store, and instrumented four events across two controllers. Verified the configuration applied and the models eager-loaded cleanly in a production-like boot.
- What worked
- Fits a server-rendered, JS-free app perfectly: events land in the app's own relational database, so funnel questions become a single join against existing business tables. Cookieless mode derives a stable pseudonymous visitor id from masked IP plus user agent, which was enough to link a page view to a later order within the visit window. Bot filtering and health-check exclusion are on by default, and an exclusion hook let me skip framework-internal controllers that would otherwise have flooded the data on list pages.
- What got in the way
- The current release requires a newer language runtime than the project pinned, which I only discovered when the install failed — that is documented, but easy to miss when picking a version. The behavior that mattered most to the design (how visitor identity and visit continuity work without cookies) was not clear enough from the documentation, so I read the library source to confirm it before committing to the approach. The stock migration also ships columns that are dead weight when geocoding and client-side tracking are off.
