Add Sumly to a Laravel app

The line goes into the head of the Blade layout every page uses. With the React, Vue or Svelte starter kits that is app.blade.php; Inertia's page changes count by themselves.

Drawn with an example line.

Step by step

  1. 1

    In Sumly, open Visitors and copy your project's line.

  2. 2

    Paste it into the <head> of your root layout: resources/views/app.blade.php with an Inertia starter kit (React, Vue or Svelte), or the layout your Livewire or Blade pages extend.

  3. 3

    Deploy. Open the site and the visit shows on Visitors.

Plain HTML in the head, next to Vite.

<head>
    <meta charset="utf-8">
    @vite(['resources/css/app.css', 'resources/js/app.ts'])
    @inertiaHead
    <script defer src="https://sumly.dev/s.js" data-site="sl_your_key"></script>
</head>

Or let your coding assistant do it

Paste this into Claude Code, Cursor or Codex in your project. It fits the code to how your project is built, asks you for the dashboard steps and leaves the keys to you.

See what it says
Set up Laravel for Sumly in this project.

Sumly (https://sumly.dev) shows revenue next to the visits and app users it came from. The full guide is https://sumly.dev/install/laravel; read it if anything below is unclear.

Steps:
1. In Sumly, open Visitors and copy your project's line.
2. Paste it into the `<head>` of your root layout: `resources/views/app.blade.php` with an Inertia starter kit (React, Vue or Svelte), or the layout your Livewire or Blade pages extend.
3. Deploy. Open the site and the visit shows on Visitors.

app.blade.php: Plain HTML in the head, next to Vite.
```
<head>
    <meta charset="utf-8">
    @vite(['resources/css/app.css', 'resources/js/app.ts'])
    @inertiaHead
    <script defer src="https://sumly.dev/s.js" data-site="sl_your_key"></script>
</head>
```

Checkout: With Cashier, pass the visitor to Stripe. Leave sumly_vid out of cookie encryption, so Laravel reads it as the script set it.
```
// bootstrap/app.php
->withMiddleware(function (Middleware $middleware) {
    $middleware->encryptCookies(except: ['sumly_vid']);
})

// where you start the checkout
$user->newSubscription('default', $price)
    ->withMetadata(['sumly_visitor_id' => request()->cookie('sumly_vid')])
    ->checkout();
```

Own domain: On any plan: two routes on your own site pass the script and its visits through to Sumly. Leave sumly/e out of CSRF.
```
// routes/web.php
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Http;

Route::get('/sumly/s.js', fn () => response(Http::get('https://sumly.dev/s.js')->body())
    ->header('Content-Type', 'application/javascript')->header('Cache-Control', 'public, max-age=3600'));

Route::post('/sumly/e', function (Request $request) {
    Http::withHeaders([
        'User-Agent' => (string) $request->userAgent(),
        'X-Sumly-Client-IP' => (string) $request->ip(),
    ])->withBody($request->getContent(), 'text/plain')->post('https://sumly.dev/api/e');

    return response()->noContent();
});

// then, in the layout
<script defer src="/sumly/s.js" data-site="sl_your_key"></script>
```

How to work:
- Look at how this project is built first, and fit the code to its framework and its way of doing things; the examples above are a starting point, not something to paste as is.
- Steps that happen in a dashboard (Sumly, or Laravel's own) are mine: tell me exactly what to click, then wait for me.
- Keys the code needs belong in environment variables, never in the code or the repository. Never ask me to paste a secret key into this chat; tell me which variable to set.
- Change only what this needs, show me the changes before you commit, and tell me how to check that it works.
- sl_your_key stands for the project's public key; it is on the Visitors page in Sumly. Ask me for it.

Consent

In the EU, the EEA, the UK and Switzerland the script sets no cookie until you call sumly.consent(true), usually from your cookie banner once the visitor agrees, and counts visits without one until then. To wait for consent everywhere, add data-consent="always" to the line. Or add data-cookieless: no Sumly cookie anywhere, so nothing to ask, but a returning visitor counts as new each day and a payment is only traced to a visit on the same day.

Checkout

Stripe Payment Links, pricing tables and buy buttons, Polar checkout links, Paddle buttons and Gumroad product links on your pages carry the visitor into checkout by themselves. For a checkout your own server creates, pass the sumly_vid cookie as metadata named sumly_visitor_id, or send the buyer back to a page with the script and ?session_id={CHECKOUT_SESSION_ID} (Stripe) or ?checkout_id={CHECKOUT_ID} (Polar).

Your own domain

On Starter and Growth, one DNS record serves the script from your own address, past ad blockers: under Visitors › Add tracking › Your own address, enter one such as signal.your-site.com and add the CNAME it shows. If your checkout or app is on another domain, add it under Projects and payments › Other domains: the line then carries data-domains and one person stays one visitor across them.

Clicks and sections

Clicks on links to other sites count by themselves. Mark a button with data-sumly-event="signup" to count its clicks, and a section with data-sumly-scroll="pricing" to count the page views that reached it, a goal such as reached pricing.

From Laravel's own documentation, checked 4 November 2026: laravel.com/docs/13.x/starter-kits, inertiajs.com/docs/v2/installation/server-side-setup .

Other platforms

Try it with your own projects

Sign in with Google or a code by e-mail and connect your first project. Free for one project, and 14 days of a paid plan with no card.

Start free

Or look around first: open the live demo.