What is a Query String in Google Analytics 4?

Ever look at your Google Analytics 4 reports and see the same page listed ten different times with strange bits of text tagged on the end of the URL? Those are query strings, and they can make your reports messy and difficult to understand. This guide will walk you through what query strings are, why they cause reporting headaches in GA4, and how to tame them for cleaner, more accurate data.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

What is a URL Query String?

A query string is the part of a URL that comes after a question mark (?). Its job is to pass small pieces of information to a web server or a browser-side script. This information is structured as one or more "key-value pairs," also known as parameters and values.

Let’s break down the anatomy of a URL with a query string:

https://www.yourwebsite.com/products/shoes?utm_source=facebook&utm_medium=cpc

• Protocol: https://
• Domain: www.yourwebsite.com
• Path: /products/shoes
• Query String Separator: ? (This is where the query string begins)
• Parameter 1 (Key-Value Pair): utm_source=facebook
• Parameter Separator: & (Used to separate multiple key-value pairs)
• Parameter 2 (Key-Value Pair): utm_medium=cpc

In this example, the query string is ?utm_source=facebook&utm_medium=cpc. It tells us that the visitor who landed on the shoes page came from a paid ad (cpc) on facebook. This is the most common use of query strings for marketers: campaign tracking.

Why Do Query Strings Matter in GA4?

By default, Google Analytics 4 treats every unique URL as a separate page. This means that from GA4’s perspective, the following URLs are three completely different pages:

• /blog/top-10-marketing-tips
• /blog/top-10-marketing-tips?utm_source=newsletter
• /blog/top-10-marketing-tips?fbclid=IwAR2... (from a Facebook link)

While technically true, this isn’t helpful for analysis. You want to see the total traffic for your blog post, not how many people came from the newsletter, how many from Facebook, and how many came directly, all listed on separate rows. This default behavior leads to several very specific problems.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

1. Fragmented Page Reports

The most immediate issue is messy reporting. Instead of a single clean row showing the total performance of your page, you get dozens of rows for the same underlying piece of content. This fragments a page's metrics and makes it nearly impossible to quickly gauge performance.

Imagine your 'Pages and Screens' report looking like this:

• /contact: 1,500 views
• /contact?ref=footer: 340 views
• /contact?from_quick_link=true: 210 views
• /contact?utm_source=google: 115 views

Suddenly, answering "How many views did our contact page get?" requires you to manually export the data to a spreadsheet and sum up all the variations. It turns a 10-second check into a 10-minute task.

2. Diluted Engagement Metrics

This fragmentation doesn't just impact pageviews. It also dilutes every other metric associated with the page, like Average engagement time, Conversions, and Users. If a page's performance is split across ten different URLs, the data for each URL variant will naturally be smaller and potentially misleading on its own.

Your most valuable page might look like an average performer at first glance because its success is spread thinly across many query parameter variations.

3. Trouble Analyzing Campaign Performance

While GA4 automatically handles standard UTM parameters (utm_source, utm_medium, etc.) and doesn’t typically fragment reports based on those, other parameters often slip through. Click identifiers from ad platforms, internal navigation parameters, or third-party tool parameters can clutter your reports and make it hard to isolate the impact of your marketing efforts.

Common Types of Query Parameters

Not all query strings are created equal. Understanding the different types can help you decide which ones are valuable and which ones are just noise. Here are the most common categories you'll see in your GA4 data:

• Marketing Campaign Parameters: These are the good ones. They track where your traffic is coming from. Examples include utm_campaign, utm_term, utm_content, gclid (Google Ads), and fbclid (Facebook/Meta Ads). GA4 is built to recognize and process these into the right traffic acquisition reports.
• Site Search Parameters: When a user searches on your website, their query is often passed as a parameter, like ?q=running+shoes or ?s=customer+support. These are valuable because they give you direct insight into what your users are looking for.
• Session and User ID Parameters: Some systems might add parameters like ?sessionid=xyz123... to track a user's journey through a session. These are often redundant and create massive report fragmentation.
• Filtering and Sorting Parameters: E-commerce and catalog websites use these heavily. When a user sorts a product page by price or filters by color, it can generate URLs like ?sort=price_low_to_high or ?filter_color=blue.
• Pagination Parameters: Used to navigate through lists of content, such as blog archives or product categories (e.g., ?page=2, ?p=3).

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

How to Handle Query Strings in GA4 Reports

Unlike Universal Analytics, which had a simple "Exclude URL Query Parameters" setting, GA4 doesn't offer a single text box to solve this. Instead, handling query parameters relies on using the right reporting dimensions and, for more advanced cases, configuring things outside of the GA4 interface. Here’s the practical way to get clean reports.

The Easy Solution: Use the 'Page path' Dimension

For 95% of users, this is the only step you need to take. The solution lies in choosing the correct dimension within your GA4 reports.

By default, many GA4 reports use the Page location dimension, which is the full URL, including the domain and any query strings. However, GA4 provides a much cleaner dimension: Page path and screen class (often shortened to "Page path").

The "Page path" dimension shows you the part of the URL that comes after the domain and before any query string.

• Page location: https://www.yourwebsite.com/blog/article-1?utm_medium=cpc
• Page path: /blog/article-1

When you customize your reports (like the 'Pages and screens' report) to use "Page path" as the primary dimension, all the fragmented views for a single page will automatically be aggregated into one clean row.

How to Change the Dimension in a Report:

1. In GA4, go to Reports > Engagement > Pages and screens.
2. Click the small pencil icon in the top right corner of the report to Customize report.
3. In the 'Report Data' panel on the right, click on Dimensions.
4. Click Set as default next to 'Page path and screen class'. If it's already the default, great! If not, make it the default and/or add it to your report. You can remove 'Page title' if you want a cleaner view focused only on the URL path.
5. Click Save > Save changes to current report.

Now, your report will group all traffic by the core page path, effectively ignoring any messy query parameters.

The Advanced Solution: Use Google Tag Manager (GTM)

Sometimes, you may have rogue, useless parameters generated by your CMS or a plugin that you want to remove from your data collection entirely. Using the "Page path" dimension cleans up reports, but the full URL (with query strings) is still collected in GA4. If you want to prevent that data from ever being sent, Google Tag Manager is the tool for the job.

This method involves creating a custom variable in GTM that strips the query string from the URL, and then telling your GA4 tag to use this cleansed URL for the page_location field.

Warning: This permanently alters the data you collect. Do not use this method to strip out useful parameters like affiliate IDs, campaign identifiers, or site search queries. It should only be used for removing "noise" parameters with no analytical value.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Steps in Google Tag Manager:

1. Create a Custom JavaScript Variable:

function() {
  // Uses the built-in Page URL variable
  var a = document.createElement('a'),
  a.href = {{Page URL}},
  // Combines the origin (https://domain.com) and the pathname (/path/to/page)
  // This effectively removes search (query strings) and hash (#anchors)
  return a.origin + a.pathname,
}

1. Modify Your Google Tag:
2. Save and Publish: Save your tag, preview your changes to ensure pageviews are still being sent correctly, and then publish your GTM container.

After this, all data sent to GA4 will have the query strings scrubbed from the page_location field.

Final Thoughts

Mastering query strings is about turning noisy data into clean insights. For most situations in GA4, simply switching your reports to use the "Page path" dimension is enough to consolidate your pageview data effectively. For truly persistent and worthless parameters, a quick trip to Google Tag Manager can remove them for good, ensuring the data you collect is as clean as possible from the start.

While these fixes work wonders, the underlying challenge is that business data is scattered everywhere – not just inside GA4, but in your CRM, ad platforms, and e-commerce dashboards. Stitching it all together is often tedious and manual. We built Graphed because we believe getting answers from your data shouldn't be that hard. Instead of spending hours hunting through reports and changing dimensions, you can connect all your sources once and just ask in plain language an AI analyst who can create real-time reports instantly, giving you back the time to focus on strategy instead of report-building.