Download the PHP package alexwestergaard/php-ga4 without Composer
On this page you can find all versions of the php package alexwestergaard/php-ga4. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download alexwestergaard/php-ga4
More information about alexwestergaard/php-ga4
Files in alexwestergaard/php-ga4
Package php-ga4
Short Description PHP Wrapper for Google Analytics 4 with Server Side Tracking
License MIT
Homepage https://github.com/aawnu/php-ga4
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package php-ga4
Package
Development
- GDPR Notice
- Getting started
- Data flow
- Layers
- Events
- Default
- E-commerce
- Engagement / Gaming
- Frontend \& Backend Communication
- Logging / Queue
- Frontend => Backend
- Frontend
- Backend
- Custom Events
- Debug
- Additional information
- Documentation
GDPR Notice
European Union have noticed that default setup of Google Analytics does not comply with GDPR as data is sent unrestricted to an american service possibly outside of Europe.
This includes the use of gtag.js as JavaScript pushes the request from visitors device including their IP-Address.
Server Side Tracking, however, does only send information specified inside the body and about your server.
Relying solely on Google Analytics 4 Events - that is not pushed through the gtag.js script - can be scraped of GDPR-related information.
- Source: Europe, GDPR, Schrems II
- https://support.google.com/analytics/answer/9019185?hl=en
Getting started
To setup Analytics you need a Measurement ID and API Secret.
Go to Administrator (bottom left) and then select your Account -> Data Streams -> your stream.
Here you will find Measurement-ID at top from and further down Api Secrets for Measurement Protocol, in there you can create yourself an API Secret.
PLEASE note that Google Analytics will look out from traffic gathered by the gtag.js library, as Server Side Events are supposed to supplement the frontend through its _ga/_gid cookie sessions.
Data flow
session_id > Google Analytics does not specify a required type of session or user id. You are free to use any kind of unique identifier you want; the catch, however, is that Google Analytics populates some internal data with gtag.js, that is then referenced to their _ga cookie session id. Just be aware that gtag.js is using client-side Javascript and can therefore have some GDPR complications as requests back to Google Analytics contains client information; such as their IP Address.
- Acquire proper GDPR Consent
- Client/GTAG.js sends session_start and first_visit to GA4
- GA4 sends
_gaand_gidcookies back to Client/GTAG.js - Server uses
_ga(or_gid; or your unique session_id) to populate events
Note: It is entirely possible to push events to backend without acquiring the session cookies from Google Analytics; you will however lose information bundled inside the GTAG.js request if you do not figure out how to push that via backend too.
Layers
The code is following 3 layers that should be considered; 5 layers at max.
Events
This is a list of prebuilt events as shown in the documentation. All events have the following parameters to locate trigger location of each event.
Default
E-commerce
Engagement / Gaming
Frontend & Backend Communication
This library is built for backend server side tracking, but you will probably trigger most events through frontend with Javascript or Websockets. There will be 2 examples, one as pure backend for logged/queued events and one for frontend to backend communication.
Logging / Queue
Frontend => Backend
Frontend
Backend
Custom Events
You can build your own custom events. All you need is to implement and fullfill the AlexWestergaard\PhpGa4\Facade\Type\EventType facade/interface.
If you want ease of life features, then you can extend your event from AlexWestergaard\PhpGa4\Helper\EventHelper and overwrite as you see fit.
Debug
Measurement protocol for GA4 has debug functionality that can be enabled with the debug parameter in the Analytics constructor.
When Debug is enabled then events are sent to https://www.google-analytics.com/debug/mp/collect where issues will be caught with
GA4Exception (Be aware of $exception->getPrevious() stacks);
such response will look as follows:
Notice: This library already validates that events are properly formatted when added to analytics ($analytics->addEvent(...)).
Two important points:
- Events sent to the Validation Server will not show up in reports.
- There is no way for events sent through measurement protocol (Server Side) to show up in the
debugViewin Google Analytics Admin.
Additional information
- Geographic information is only available via automatic collection from gtag, Google Tag Manager, or Google Analytics for Firebase.
- The
page_viewevent works, however it's not documented in the official documentation, so do not rely on it.
