The GA4 client is responsible for intercepting incoming GA4 HTTP requests and parsing them into event data objects for further processing.
The GA4 tag will receive event data from the GA4 client and forward it to your GA4 property.
1. In the tag settings, click Triggers.
2. Select New.
3. Click on the pencil at Trigger Configuration and choose Custom as the trigger type.
4. Select Some events under This Triggers fires on. Then enter: Client name – equals – GA4.
5. Name the trigger and click Save.
server_container_url points to your TAGGRS subdomain.{{Event}} not capturing event nameevent (lowercase). Check that your data layer pushes include an event key.The GA4 configuration tag initializes Google Analytics 4 on the page and establishes the connection between your website and your GA4 property (optionally through a server-side GTM endpoint). It typically fires once per page load.
A GA4 event tag sends specific interaction data (e.g. clicks, form submissions, or purchases) to GA4. These tags fire only when the defined interaction occurs.
You usually need both: the configuration tag as the foundation, and one or more event tags to send specific interaction data.
Yes, many setups use a single GA4 event tag with the dynamic {{Event}} variable as the event name, triggered by relevant data layer pushes. This approach is efficient and scalable, but it relies on a consistent and well-structured data layer.
For events that require unique parameters or custom logic (e.g. purchase events) dedicated event tags often provide better control and easier debugging which most of the times is the preferred method.
