# Laravel > Add cookieless product analytics to your Laravel application import { Steps, Step } from "@/components/docs"; import { Callout } from "@/components/docs"; import { CodeBlock } from "@/components/docs"; import { Card, Cards } from "@/components/docs"; Add Databuddy's cookieless product analytics to your Laravel application by adding the tracking script to your main Blade layout file. ## How to Add Databuddy to Laravel Get your Databuddy tracking script from your [Databuddy dashboard](https://app.databuddy.cc). It will look like this: `} /> Replace `YOUR_CLIENT_ID` with your actual Client ID from your Databuddy dashboard. In a standard Laravel application, you'll have a main layout file that other Blade views extend. This file is often located at: - `resources/views/layouts/app.blade.php` (common for applications using Laravel's authentication scaffolding) - Or `resources/views/layouts/main.blade.php` or a similar custom name - If you're using Laravel Jetstream or Breeze, the main layout file might be in a slightly different location within `resources/views/` Identify the primary layout file that wraps most or all of your site's pages. Open your main Blade layout file. Paste the Databuddy tracking script just before the closing `` tag. {{ config('app.name', 'Laravel') }} {{-- Stylesheets, etc. --}} @vite(['resources/css/app.css', 'resources/js/app.js']) {{-- Your page content --}} @yield('content') {{-- Other scripts --}} {{-- Databuddy Analytics Script --}} @if(app()->environment('production')) @endif `} /> **Explanation:** - `@if(app()->environment('production'))`: This Blade directive ensures the script is only included when your Laravel application is running in the `production` environment. This prevents tracking during local development. - `{{ config('services.databuddy.client_id') }}`: This accesses your Databuddy Client ID from Laravel's configuration system. See step 4 for `.env` configuration. If you prefer not to use the config helper immediately, you can hardcode the value: environment('production')) @endif`} /> Remember to replace `YOUR_CLIENT_ID` with your actual Client ID. It's best practice to store your Databuddy Client ID and server API key in your `.env` file and access them via Laravel's configuration. **a. Add to `.env` file:** Open your `.env` file and add: **b. Add to `config/services.php`:** Open (or create if it doesn't exist) `config/services.php` and add a configuration for Databuddy: [ 'client_id' => env('DATABUDDY_CLIENT_ID'), 'api_key' => env('DATABUDDY_API_KEY'), 'website_id' => env('DATABUDDY_WEBSITE_ID', env('DATABUDDY_CLIENT_ID')), ], ];`} /> Now, the Blade template code from Step 3 using `config('services.databuddy.client_id')` will work correctly. Make sure to run `php artisan config:clear` if you've cached your configuration. - Deploy your Laravel application to your production environment (or set `APP_ENV=production` locally for testing, but be mindful of tracking local data) - Open your live Laravel website in a browser - Navigate through a few pages - Check your [Databuddy dashboard](https://app.databuddy.cc) for incoming data. It might take a few minutes for the first events to appear ## Configuration Options Enable additional tracking features by adding data attributes to your script tag: environment('production')) @endif`} /> ## Custom Event Tracking Track custom events from your Laravel Blade templates or JavaScript: ### In Blade Templates Click Me `} /> ### Using Data Attributes Enable automatic tracking with data attributes: {{-- Then use in your templates --}} View Pricing `} /> ### In JavaScript Files If you're using Vite or Laravel Mix, you can track events from your JavaScript: ## Server-Side Tracking For server-side tracking in Laravel, use the Databuddy Node SDK or make HTTP requests directly: apiKey = config('services.databuddy.api_key'); $this->websiteId = config('services.databuddy.website_id'); $this->apiUrl = 'https://basket.databuddy.cc'; } public function track(string $name, array $properties = []): void { Http::withToken($this->apiKey)->post("{$this->apiUrl}/track", [ 'name' => $name, 'properties' => $properties, 'websiteId' => $this->websiteId, 'timestamp' => now()->toISOString(), 'source' => 'server', ]); } }`} /> Then use it in your controllers: track('order_placed', [ 'order_id' => $order->id, 'total' => $order->total, 'currency' => 'USD', ]); return redirect()->route('orders.show', $order); } }`} /> ## Common Use Cases ### E-commerce Tracking Track product views and purchases: if (window.databuddy) { window.databuddy.track('product_view', { product_id: '{{ $product->id }}', product_name: '{{ $product->name }}', price: {{ $product->price }}, category: '{{ $product->category }}' }); } @endpush`} /> ### Form Submissions Mark the form with `data-form-type` so the submit handler from `resources/js/app.js` (shown above) tracks it. Avoid adding `data-track` to the form itself: that attribute fires a click event for every click inside the form and would duplicate the submit handler. @csrf `} /> ## Troubleshooting ### Script Not Loading - Verify the script is in the correct Blade layout file - Check that `APP_ENV=production` in your `.env` file (or remove the `@if` condition for testing) - Check browser console for errors - Ensure your Client ID is correct in the config - Run `php artisan config:clear` if you've updated configuration ### Events Not Tracking - Confirm `window.databuddy` exists before calling tracking methods - Check browser console for any errors - Verify events appear in your Databuddy dashboard after 2-3 minutes - Use browser dev tools Network tab to confirm requests are being sent ### Environment-Specific Issues - The script only loads in production by default (due to `@if(app()->environment('production'))`) - For local testing, temporarily remove the environment check or set `APP_ENV=production` in your `.env` - Remember to restore the environment check before deploying ## Related Integrations TypeScript support with React hooks and components. App Router and Pages Router support with SSR. Plugin or manual setup for WordPress sites. Need help with your Laravel integration? Contact us at [support@databuddy.cc](mailto:support@databuddy.cc).