README

Self-hosted mouse, click and scroll tracker for Symfony 5.4 / 6.4 / 7.x. Captures mousemoves, clicks, scroll positions, form-blur values and DOM snapshots, then ships them to your own database for Mouseflow-style heatmaps and session replay. No jQuery.

Requirements

Installation

composer require benmacha/mousetracker:^2.0

If you don't use Symfony Flex, register the bundle in config/bundles.php:

return [
    // ...
    benmacha\mousetracker\TrackerBundle::class => ['all' => true],
];

Routing

config/routes/mouse_tracker.yaml:

mouse_tracker:
    resource: '@TrackerBundle/Resources/config/routes.yaml'
    prefix: /tracker

Configuration (optional)

config/packages/mouse_tracker.yaml:

mouse_tracker:
    record_click: true
    record_move: true
    record_keyboard: true
    percentage_recorded: 100
    disable_mobile: false
    ignore_ips: []

Database

php bin/console doctrine:schema:update --force
# or, with migrations:
php bin/console doctrine:migrations:diff
php bin/console doctrine:migrations:migrate

This creates three tables: tracker__client, tracker__page, tracker__data.

Publish assets

php bin/console assets:install --symlink public/

Copies the tracker JavaScript to public/bundles/tracker/js/tracker.js.

Usage

Inject the tracker snippet right before the closing </body> tag of any page you want to record:

{# templates/base.html.twig #}
        {{ mouse_tracker_service.build()|raw }}
    </body>
</html>

Expose the service as a Twig global in config/packages/twig.yaml:

twig:
    globals:
        mouse_tracker_service: '@mouse_tracker'

That's it — the tracker boots on DOMContentLoaded and starts batching events to /tracker/createClient and /tracker/addData.

Backend (replay UI)

The bundle ships a basic backend at /tracker/back/ for listing sessions and replaying recordings.

⚠️ Security — read this before deploying. The /tracker/back/* routes (replay UI + getPages/getClients/getData JSON endpoints) are public by default. Anyone who can reach your app can browse every recorded session, including form values, click coordinates, and DOM snapshots — which often contain PII.

Gate them behind your security.yaml firewall before you ship. Example:

# config/packages/security.yaml
security:
    access_control:
        - { path: ^/tracker/back, roles: ROLE_ADMIN }
        # the ingest endpoints below must stay reachable from the public site
        - { path: ^/tracker, roles: PUBLIC_ACCESS }

The same goes for GDPR/consent: /tracker/createClient and /tracker/addData are intentionally public so the tracker can post from any page, but you are responsible for getting visitor consent before loading tracker.js.

Settings

Client-side settings are forwarded from PHP config into a window.MouseTrackerConfig.settings blob. You can also override them after the script loads via UST.settings:

<script>
    window.UST && (UST.settings.delay = 100);
</script>

Upgrading from 1.x

v2 is a breaking rewrite. See CHANGELOG.md for the migration path. Highlights:

• Drops Symfony 2.8, Assetic, Sensio Framework Extra Bundle, jQuery
• Doctrine/route annotations replaced with PHP 8 attributes
• services.yml → services.yaml; new routes.yaml resource
• mousetrackerService global → mouse_tracker_service
• Tracker JS is now plain vanilla — no jQuery to load first

License

MIT — see Resources/meta/LICENSE.