Laravel
VerifiedBackend Frameworks · Script tag
Add Pulse analytics to your Laravel app via Blade templates.
First-class, hand-verified install path (script tag or official plugin).
resources/views/layouts/app.blade.php
<script defer data-domain="example.com" src="https://js.ciphera.net/script.js"></script>
Set data-domain to the domain you registered in Pulse. Configure feature toggles, SRI, and storage from the install panel in your dashboard.
01 · Laravel + Pulse
Why cookieless analytics fits Laravel
Laravel serves rendered HTML from Blade, so analytics belongs in the layout, not in a client bundle. Add the Pulse script once to your main Blade layout and every server-rendered page carries it — a couple of kilobytes, loaded async, with no impact on your response time and no client-side state to manage.
Cookieless suits a server-rendered PHP app well. You are not setting an analytics cookie through Laravel’s cookie handling, adding consent middleware, or rendering a banner partial on every view. Pulse collects no personal data and needs no consent, which for an EU-facing Laravel app removes the compliance layer rather than configuring it.