GA4 configuration tags are the instructions that determine how Google Analytics 4 collects, processes and organizes data for a digital property. Unlike Universal Analytics’ session-based model, GA4 is built on an event-based model: every interaction is recorded as an event, and configuration tags establish which information associated with those events must be sent to the platform. These instructions are placed on the site’s pages or in the app through a tag management system or directly in the code, and they are the starting point of any measurement implementation.
A correct configuration is crucial because it determines the quality of the data available in reports. Wrong or incomplete parameters can compromise conversion collection, traffic attribution and audience building. For this reason, GA4 configuration tags must be designed carefully, documented and checked regularly, especially on complex sites with multiple domains or mobile apps.
What a GA4 configuration tag is for
A GA4 configuration tag is a set of parameters that identifies the destination property and defines the basic collection settings. The main parameter is the measurement ID, a string that starts with the prefix “G-” and links the data sent by the site or app to the correct property within Google Analytics 4. Without this ID, no data can be attributed to the desired property.
In addition to the ID, the configuration tag can include settings for cookies, how long information is stored on the user’s device, consent and the automatic collection of certain events. These options affect how the platform handles data even before specific events are sent.
What changes compared to Universal Analytics
In Universal Analytics, measurement was based on a session model and a limited number of hit types, such as page views, events and transactions. In GA4, the model is entirely event-based: even a page view is an event. This difference profoundly changes the role of configuration tags, which no longer just set the property but define the context in which all events are interpreted.
From the session model to the event model
In the event model, every interaction is autonomous and can be enriched with custom parameters. Configuration tags establish which context information accompanies events, such as approximate geographic location, device type and traffic source. This setting enables more flexible analysis and more granular segmentation than in the past.
Privacy and consent in configuration
GA4 configuration tags include options designed to comply with data protection regulations, such as consent mode and IP address anonymization. These features let you modulate collection based on the user’s choices and are particularly relevant for sites operating in jurisdictions with strict rules.
The most used parameters and what they control
The most common parameters of a GA4 configuration tag concern the measurement ID, the data stream name, cookie settings and consent management. Some parameters are required, others optional and are used to fine-tune collection behavior. The following table compares the main characteristics of the most widespread parameters.
| Parameter | Required | Function | Impact on collection |
|---|---|---|---|
| Measurement ID | Yes | Links data to the property | Decisive: without it no data is recorded |
| Data stream name | Yes | Identifies the data source | Useful for distinguishing sites and apps |
| Cookie settings | No | Defines cookie duration and domain | Affects recognition of returning users |
| Consent mode | No | Modulates collection based on consent | Relevant for regulatory compliance |
| Automatic event collection | No | Activates predefined events | Expands the set of data collected without manual configuration |
Configuring tags via GTM or in code
Configuration can be done through a tag management system or by inserting the instructions directly into the site’s code. The choice depends on the technical skills available and the complexity of the infrastructure. In both cases, it is good practice to proceed in orderly steps and verify each phase before moving to the next.
- Create a GA4 property in the admin interface and generate the data stream for the site or app.
- Copy the measurement ID associated with the data stream.
- Choose the implementation tool, for example a tag management system or direct insertion in the code.
- Insert the configuration tag with the correct ID and the desired parameters.
- Define cookie and consent settings based on the applicable regulatory requirements.
- Publish the configuration and verify that events are received in the real-time section.
- Check reports after a few days to confirm the consistency of the collected data.
- Document the configuration adopted and plan periodic checks.
The most frequent mistakes and how to avoid them
Common mistakes include using a wrong measurement ID, duplicating tags on the same page and failing to manage consent. These problems can artificially inflate data or prevent collection entirely. It is also advisable to avoid changing the configuration without first testing it in a controlled environment.
A good practice is to keep an updated inventory of active tags, distinguishing configuration tags from event tags. Documenting changes and their reasons makes maintenance easier and reduces the risk of regressions. Finally, it is useful to periodically compare GA4 data with other sources to spot any anomalies.
Frequently asked questions
What is the difference between a configuration tag and an event tag?
The configuration tag sets the property and the collection context, while the event tag sends a specific interaction. The former must be present before the latter for events to be attributed correctly.
Can I have multiple configuration tags on the same page?
In general, it is preferable to avoid multiple configurations on the same page, because they can generate data duplication. If multiple properties are needed, it is better to manage them carefully and verify the results.
Where is the measurement ID found?
The measurement ID is available in the GA4 admin interface, in the data streams section. It corresponds to the string that starts with the prefix “G-“.
Do GA4 configuration tags also work on mobile apps?
Yes, GA4 supports measurement for both web and mobile apps, with separate data streams. Configuration parameters may vary depending on the platform used.
What happens if the configuration tag is not loaded?
If the tag is not loaded, no event associated with the property is recorded. It is therefore essential to verify correct operation after every change.
Does tag configuration affect regulatory compliance?
Yes, consent and cookie settings affect compliance with data protection regulations. An accurate configuration helps collect only the data that is allowed.
Facing this issue?Have you set up the GA4 configuration tag but Google Ads conversions are not being recorded correctly?A missing or misconfigured GA4 configuration tag prevents conversion tracking and makes your advertising efforts pointless. With my Google Ads Conversion Tracking: GA4, GTM and Enhanced Conversions service, I set up the GA4 configuration tag and the entire tracking flow to maximize ROI.Discover the Conversion Tracking service