{{--
    Loaded from partials/head, so every layout that uses it is measured —
    marketing, the signed-out pages and the client-facing journey alike.

    It previously sat in layouts/app only, which left registration invisible:
    the one page you most need to watch was the one page not reporting.

    Skipped in local and testing so development traffic never lands in the
    property, and skipped for signed-in staff so studios browsing their own
    CRM do not look like prospects.
--}}
@if(config('services.google_analytics.id') && app()->environment('production') && ! auth()->check())
    <script async src="https://www.googletagmanager.com/gtag/js?id={{ config('services.google_analytics.id') }}"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
      gtag('config', '{{ config('services.google_analytics.id') }}');
    </script>
@endif

{{--
    Umami covers everything — signed-in staff included — because it is product
    analytics, not just acquisition. That is the deliberate difference from GA
    above, which excludes logged-in users to keep the funnel numbers clean.

    The script host is allowed in SecurityHeaders on both script-src (to load)
    and connect-src (Umami POSTs each event back), or the CSP would block it
    silently.
--}}
@if(config('services.umami.website_id') && app()->environment('production'))
    <script defer src="{{ config('services.umami.src') }}"
            data-website-id="{{ config('services.umami.website_id') }}"></script>
@endif