Download the PHP package petercoles/laravel-google-analytics-tracking without Composer
On this page you can find all versions of the php package petercoles/laravel-google-analytics-tracking. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download petercoles/laravel-google-analytics-tracking
More information about petercoles/laravel-google-analytics-tracking
Files in petercoles/laravel-google-analytics-tracking
Package laravel-google-analytics-tracking
Short Description Inject your Google Analytics tracking ID into a Laravel project
License MIT
Homepage https://github.com/petercoles/laravel-google-analytics-tracking
Informations about the package laravel-google-analytics-tracking
Google Analytics Tracking for Laravel
Introduction
Other Google Analytics packages for Laravel are designed to consume analytics data via the Google API and allow you to process it on your Laravel site. Not this one.
Instead this does the ridiculously straightforward task of extracting your Google Analytics tracking ID from your Laravel .env file and injecting it into the a Blade view intended for inclusion in your base layout.
The only wrinkle is that if you don't set the tracking ID in your .env file the Google script won't be included in your site. This is deliberate as it can be marginally useful for development and staging environments.
Installation
Add the package to your project
Add the service provider to the providers list in your config/app.php file
Include the Blade view in your base layout
Traditionally this was placed near the closing body tag. However as the script is now loaded asynchronously, it can be added anywhere where a script tag is legitimate.
On your production server, set your tracking code in the .env file
License
This package is licensed under the MIT license.
Final Note
If you've got this far, you're probably thinking "Couldn't I just cut and paste the Google script into my base layout?", to which the answer is "Absolutely!". I built this package only because I was doing this so often that it had begun to feel like a code smell and I wanted to DRY up this piece of my applications. I also wanted the additional benefit of separating the tracking ID from the script to reduce the risk of accidentally reusing another site's tracking ID.