railroad/railtracker

Tracks user actions in your application.

v5.0.1 2024-09-05 19:36 UTC

Requires

• php: ^8.2
• doctrine/dbal: ^3.3
• doctrine/orm: ^2.19
• guzzlehttp/guzzle: ^7.2
• jenssegers/agent: ^2.5
• laravel/framework: ^11.9
• predis/predis: ^2.2
• ramsey/uuid: ^4.2.2
• symfony/cache: ^6.4

Requires (Dev)

• orchestra/testbench: ^9.2
• phpunit/php-code-coverage: ^11.0.1
• phpunit/phpunit: ^11.0.1

MIT

• login
• tracking
• tracker
• pageview

README

Tracks user interactions with your site including, page views, logins, custom actions, etc.

Requests/Responses

Railtracker looks at incoming server responses and stores information about it in our database. It stores the following for all requests:

• user id
• cookie id (for anonymous visitors)
• url
• laravel route
• device info
• agent info
• request method (PUT, PATCH, etc)
• referring url
• language
• ip
• date

It stores the following for all responses:

• request id
• status code returned
• response duration (how long it took the server to respond)
• date

Exceptions

Railtracker also stores any error/exception information that happens while the server processes the request:

• request id
• exception code
• exception line
• exception class
• exception file
• exception message
• exception trace

Media Playback

The last part of railtracker is media playback tracking. It tracks how many seconds of any given content that a user watches/consumes. The data it stores looks like this:

• media id (usually a vimeo video id or youtube video id)
• user id
• seconds played
• current second (where the user currently is in the video)
• date

Final Note

Railtracker is purely a tool for storing the above information, it does not process or analyze the information in any way.