Analytics and events

LaRecipe has no dashboards and stores no traffic. It feeds the tools you already use. To add one, name it under integrations.analytics in the set's entry in config/larecipe.php, and LaRecipe prints its script tags into the head of every page of the set:

'sets' => [
    'docs' => [
        // route, source and access as usual
        'integrations' => ['analytics' => [
            'plausible' => ['domain' => 'docs.acme.dev'],
        ]],
    ],
],

Script tags see readers whose browsers run JavaScript. Agents never run your analytics script, so LaRecipe also fires a Laravel event for every page, Markdown twin, llms.txt, skill and MCP call it serves. Listen to those events to see all of your traffic.

This site runs GA4: its config/larecipe.php sets ga4 under the docs set's integrations.analytics.

Analytics integrations

LaRecipe checks every value against the shape its provider uses before it reaches the page, and drops a tag whose values do not fit. Script sources must be https URLs, and no setting can add inline code to the page. When your app sets a Content Security Policy nonce with LaRecipe::useCspNonce(), every tag carries it.

A repository set may also declare integrations in its larecipe.json, with the same keys.

{
  "integrations": {
    "analytics": {
      "plausible": { "domain": "docs.acme.dev" }
    }
  }
}

Page feedback

Every page ends with "Was this page helpful?", a Yes and a No, and an optional comment of up to 2,000 characters. The widget needs JavaScript. LaRecipe stores no answer. Instead, each one:

1. Dispatches FeedbackSubmitted with the page, the answer, the comment and the request kind, with source set to reader. The MCP submit_feedback tool dispatches the same event with source set to agent, so feedback from agents arrives the same way.
2. Reports to your analytics, when an integration is configured. Analytics get the page, version, locale, the answer and the source. The comment goes only to your Laravel listeners.

Turn the widget off with feedback.enabled set to false in config/larecipe.php. That removes the widget, its route and the submit_feedback tool.

Answer feedback

When Ask AI is on, every finished answer has a thumbs up and a thumbs down. A vote posts to the same feedback route with the question the answer was for, so FeedbackSubmitted arrives with source set to ask and the question filled in, and the page is the one the reader asked from. Your analytics get the same larecipe:feedback event, with the source ask. The thumbs follow feedback.enabled too.

Events

LaRecipe fires a Laravel event for each kind of request it serves. They live in LaRecipe\Domains\Delivery\Events.

Every one of them carries a kind: human, crawler or agent, decided from the request's user agent and whether it asks for Markdown. The kind feeds events only; it never changes what LaRecipe serves. The events reference has the exact rules and every event's fields.

Listen to them like any Laravel event, and send them wherever you like: your analytics tool's server-side API, a row in your own table, or a log.

<?php

namespace App\Listeners;

use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Support\Facades\Log;
use LaRecipe\Domains\Delivery\Events\PageViewed;

class ForwardDocsTraffic implements ShouldQueue
{
    public function handle(PageViewed $event): void
    {
        // People already reach your client-side analytics. Skip LaRecipe's own export and doctor runs too.
        if ($event->kind === 'human' || str_starts_with((string) $event->userAgent, 'LaRecipe-')) {
            return;
        }

        Log::info('Docs page viewed', [
            'set' => $event->set,
            'version' => $event->page->version,
            'locale' => $event->page->locale,
            'path' => $event->page->path,
            'format' => $event->format,
            'kind' => $event->kind,
            'user_agent' => $event->userAgent,
        ]);
    }
}

Next

• Search: find questions your docs do not answer yet with SearchPerformed.
• Events reference: every event, its fields and how the request kind is decided.
• Agent surfaces: the files agents read, and the events each one fires.