URL Query Parameters: What They Are and How Marketing Teams Use Them
What query parameters are, how they're structured, and the nine ways marketing teams use them — from campaign tracking to personalization.
A URL query parameter is a key-value pair added after a ? that passes extra information to the page — most often about where the visitor came from. In example.com/pricing?utm_source=newsletter&plan=pro, there are two parameters: utm_source=newsletter and plan=pro, separated by &.
Developers use them to filter, sort and paginate. Marketing teams use them for something else: to carry campaign context that analytics tools read on arrival. That second use is where they either make attribution work or quietly break it. A parameter that is spelled inconsistently, stripped by a redirect, or missing entirely produces traffic your reports cannot explain.
What is a query parameter?
A query parameter is a key-value pair appended to a URL after a ? to pass information to the receiving page.
Everything before the ? tells the browser what page to load. Everything after it tells that page how to behave: which filter to apply, which variant to show, or which campaign sent the visitor. The page loads either way; the parameters change what it does.
That is the whole concept. What makes it worth 2,000 words is that marketing and engineering use the same mechanism for almost unrelated purposes, and the marketing use is the one nobody documents.
How a query string is structured
A query string begins at the first ?, pairs keys to values with =, and separates pairs with &.
https://example.com/shoes?color=black&size=10&utm_source=newsletter
└────── base URL ──────┘└──────────── query string ────────────┘Three pairs, one string. The rules that govern it are short (Wikipedia, “Query string”, accessed 2026-09-10):
- The first
?starts the query string. Any later?is just a character. &separates pairs. Some older systems accept;; almost nothing produces it now.- Order does not matter to the receiving page.
?a=1&b=2and?b=2&a=1are equivalent. - Case does matter to the values.
utm_medium=Emailandutm_medium=emailare two different values, and analytics tools will report them as two different channels. - Spaces and reserved characters must be encoded. A space becomes
%20or+; an&inside a value becomes%26, or it will be read as a separator.
The last two rules cause nearly all of the damage. The syntax is forgiving. The values are not.
Query string or query parameter? The terms get used interchangeably, and the difference is one of scope: a URL carries a single query string containing any number of parameters inside it. That rarely matters in conversation and matters a great deal in a bug report.
“The query string was stripped” means every parameter was lost and the visit is unattributable. “A query parameter is missing” means one field did not populate and the rest of the record is intact. Those are different failures with different causes, and a team that uses the words loosely will spend the first hour of an incident working out which one it is looking at.
Query parameters vs path parameters
A path parameter identifies which resource you want; a query parameter modifies how it behaves.
| Path parameter | Query parameter | |
|---|---|---|
| Position | Inside the path, before any ? | After the ? |
| Example | example.com/products/running-shoes | example.com/products?category=running-shoes |
| Identifies | A specific resource | A modification to a resource |
| Optional? | Usually required — remove it and the URL breaks | Usually optional — remove it and the page still loads |
| Order | Meaningful | Irrelevant |
| Typical marketing use | Rare; it is a site-structure decision | Constant; tracking, personalization, filtering |
The practical test: if deleting the segment gives you a broken link, it is a path parameter. If deleting it gives you the same page in a default state, it is a query parameter. Campaign tracking always uses the second kind, which is why you can strip every utm_ value off a URL and still land on the page.
Nine ways marketing teams use query parameters
Marketing teams use query parameters for nine distinct jobs, and campaign tracking is only one of them.
This is the part the developer-oriented references skip entirely, and it is where most of the value sits.
1. Web page navigation. Parameters drive filtering, sorting, pagination, search, and language on almost every ecommerce site. Filtering looks like prefn1=brand&prefv1=adidas or pmin=20.00&pmax=50.00; sorting like srule=priceLow-High; pagination like page=3&pageSize=30; on-site search like ?q=baby+shoes; translation like lang=fr. Each one is a state the user chose, encoded in a link you can share.
2. Landing page personalization. The same landing page can greet visitors differently depending on the parameter that brought them. Run three ads (SEO auditing, A/B testing, content creation) and a single ?service=seo-audit lets one page headline each of them correctly. One page, three experiences, no extra builds.
3. Cross-domain tracking. When a journey spans related domains, parameters carry the session identifier across the boundary so analytics treats it as one visit rather than two strangers. Without it, the second domain sees a referral from the first and the original source is lost.
4. Campaign tracking. The best-known use. UTM parameters carry utm_source (where it came from), utm_medium (the channel type), utm_campaign (which campaign), utm_term (the paid keyword) and utm_content (which creative). Together they let you say which channel and which creative produced a result, which is the precondition for allocating budget on anything other than instinct. The tracking-parameter deep dive covers the five in detail.
5. Form population. Parameters can prefill known fields so a returning customer is not retyping an address at checkout. Fewer fields to complete means fewer abandoned carts, which is why retail checkout flows lean on this heavily.
6. Email marketing. Personalization beyond a first name: parameters passed dynamically into links let each subscriber’s URL carry their own context, so the page they land on already knows which offer they were sent.
7. Affiliate and referral support. A custom link per partner (example.com/signup?affiliate=johnsmith2) makes it possible to attribute a signup to the person who sent it, and therefore to pay them correctly.
8. Discount codes. A parameter can apply an offer automatically at the cart rather than asking the customer to remember a code: ?addcpn=freeship. The friction removed is small and the conversion effect is not.
9. Lead qualification. Which pages a visitor touched (pricing, knowledge base, tech specs) can be passed downstream as parameters, giving sales a behavioral signal rather than a form fill alone.
The tracking-parameter deep dive: Read: UTM parameters — the five UTM parameters and how to govern them.
How query parameters break attribution
Query parameters break attribution in three ways: inconsistent values, redirect stripping, and parameters that never get applied.
“Most attribution gaps we’re asked to diagnose aren’t analytics problems at all — the parameter was wrong, missing, or stripped before the data ever reached the report.” — Kaden Carroll, Lead Solutions Architect, Claravine Inconsistent values. The mechanism is a string match, so
Redirect stripping. A link that passes through a shortener, a consent gate, or a marketing-automation redirect can arrive with its query string trimmed. The visit is recorded; its origin is not. This one is invisible until someone compares click counts against session counts and finds a gap nobody can account for.
Parameters that were never applied. A campaign launched without tags produces traffic that lands in Direct, which is the bucket that quietly absorbs every measurement failure. Direct traffic rising is rarely good news.
Enabling cross-channel attribution and campaign performance reporting is one of the most common jobs enterprise teams bring us, across 58 accounts — and in nearly all of them the blocker turns out to be upstream of the analytics tool, in how the parameters were created.
How to keep parameter values consistent across teams
Consistency comes from generating parameters against an approved value list, not from documenting a convention.
The difference is where the check happens. A convention in a shared document tells a person what the value should be at the moment they are already typing something else. An approved list applied in the builder will not let the wrong value be created.
A workable setup covers four things:
- Closed lists for the fields that feed reporting.
sourceandmediumabove all, because those two drive channel grouping. Adding a value becomes a request rather than a keystroke. - Format rules by pattern. Case and separator conventions enforced where the value is typed, so
Spring Launch 2026cannot arrive alongsidespring_launch_2026. - One generation point for everyone, including agencies. A large share of tagged links are built by people outside your organization, in tools your team does not administer. A rule they cannot see is a rule they will approximate.
- A check before the link goes live, not after. Correcting a value costs seconds before launch and a quarter of fragmented reporting afterward.
Vanguard’s marketing technology team described what changes when generating a compliant code stops being a bottleneck.
Enforce values at creationApproved values applied where campaign links are built.Explore campaign tracking“Now that you’re able to have more people creating codes, you can move a little faster.” — Kimberly Whitehead, marketing technology manager, Vanguard
How to read query parameters from a URL
In a browser, new URL(location.href).searchParams.get('key') returns a parameter’s value.
The URLSearchParams interface parses a query string into something you can read, iterate and modify without writing string-splitting code (MDN Web Docs, “URLSearchParams”, accessed 2026-09-10).
For marketers the question usually has a simpler answer. To see the parameters on a URL, look at the address bar: everything after the first ? is the query string. To confirm analytics received them, open the real-time or traffic-acquisition report and check that the source and medium match what you set. If the report shows Direct, the parameters did not survive the trip.
Frequently asked questions
How do I get query parameters from a URL?
In JavaScript, new URL(location.href).searchParams.get('utm_source') returns the value. In analytics tools, parameters are parsed automatically on page view.
What are URL parameters?
Key-value pairs after the ? in a URL that pass information to the page, used for filtering, sorting, personalization and campaign tracking.
How do I add query parameters to a URL?
Append ?key=value, then &key=value for each additional pair. Order does not matter; spelling and case do.
How do I find URL parameters?
Everything after the first ? in the address bar is the query string.
Are URL parameters and query strings the same thing?
The query string is the whole segment after ?; a query parameter is one key-value pair inside it.
Do query parameters affect SEO?
They can. Multiple parameterized URLs serving the same content create duplicate-content signals unless canonicalized.
Are parameterized queries the same thing?
No. A parameterized query is a database technique for safely passing values into SQL. It shares the word and nothing else.
Sources
Outbound citations, named and dated:
- Wikipedia, “Query string” (accessed 2026-09-10) — query-string syntax, delimiters and encoding rules.
- MDN Web Docs, “URLSearchParams” (accessed 2026-09-10) — the browser interface for reading and modifying a query string.
