How Long Do UTM Parameters Last in Google Analytics? Shorter Than You Think
How long do UTM parameters last in Google Analytics? The honest answer is that the click itself lasts only for that session, while the memory of it survives in different places for different lengths of time, and the version that matters for your reports is the shortest one.
I learned this the embarrassing way, by celebrating a campaign that had already ended. A newsletter link drove a strong week, and for a month afterward the conversions kept showing up under that campaign in one report and nowhere in another. Both reports were reading real data. They were reading different definitions of "last." The campaign had not lasted a month. My understanding of attribution had lasted about a week longer than the data did.
Here is the map, because there are three clocks running at once and they get confused constantly.
Clock one: the session, which is where the click lives
A UTM parameter is a label on a single arrival. When someone clicks your tagged link, Google Analytics 4 records that session with the source, medium, and campaign from the link. That session attribution is immediate and narrow. If the same person returns tomorrow by typing your address directly, that return visit is a new session, and it does not automatically carry the old UTM values with it. The click did its job in the moment. It does not follow the person around.
This is why the "session campaign" report and the "first user campaign" report disagree, and why both can be right. The session report answers "which campaign brought this visit." The first user report answers "which campaign brought this person the first time we ever saw them." A newsletter click in January can still be someone first user source in June, because first user attribution is a property of the user, not of the visit. It persists as long as the user identity persists, which on the web means as long as the cookie and the device survive, and consent allows it.
Clock two: the cookie, which used to be six months
If you have read older guides, you will remember the six month number. That came from Universal Analytics, the previous version of Google Analytics, where the campaign cookie lived for six months. A visitor who returned within six months without a new campaign link kept the old campaign attached. That cookie is gone now. GA4 does not use it, and repeating the six month figure as a GA4 fact is one of those zombie numbers that survives because it sounds specific.
In GA4, the practical limits are different. First user source sticks to the user record until the cookie is cleared, the device changes, or the browser privacy rules intervene. Safari Intelligent Tracking Prevention can expire client side identifiers in as little as seven days in some cases, which means a visitor who returns after a week may arrive as a stranger with no campaign memory at all. Your own CRM can do better than this, but only if you capture the UTM values on the landing page and store them yourself, with first touch and last touch fields and an expiration you choose, commonly 90 days. The platform will not do that storage for you.
Then there is the reporting window, which is a third clock people mistake for a UTM lifetime. GA4 attribution reports let you set a lookback window for conversion credit, and modeled key event credit can keep updating for up to about 12 days after the event as more data arrives. That is not the UTM lasting 12 days. That is the report settling. If you check a campaign report the day after a launch and again two weeks later, the numbers will move, and the movement is the model finishing, not the campaign returning from the dead.
What to actually do with this
Stop asking how long a UTM lasts, and start capturing it at the moment it arrives. On your landing pages, read the UTM values into hidden form fields or your CRM on first visit, and store both the first touch that brought the person and the last touch before conversion. Set your own expiration, 90 days is a sane default, and overwrite last touch when a new tagged link arrives while keeping first touch intact. That gives you a record that survives cookie deletion, device changes at the level of the form fill, and GA4 report quirks.
In GA4 itself, read the two reports for what they are. Use session campaign to judge whether a campaign is driving visits right now. Use first user campaign to judge which channels introduce new people over time. And when a campaign looks like it is still converting weeks after it ended, check whether you are looking at first user credit before you celebrate, or before you renew a budget on a ghost.
One loose end I am not going to tidy up: cross device journeys break all of this, and there is no honest way to stitch a phone click to a laptop purchase without a login in between. If your customers research on one device and buy on another, some of your campaigns will always look worse than they are. That is a measurement limit, not a tagging mistake, and no parameter length fixes it.
Frequently asked questions
How long do UTM parameters last in Google Analytics?
The click attributes one session. First user source persists on the user record until the cookie is cleared or the device changes, which browser privacy rules can shorten to days. The old six month figure was a Universal Analytics cookie, not a GA4 rule.
Why do session campaign and first user campaign reports disagree?
Session campaign credits the visit, while first user campaign credits the channel that first brought the person. A returning visitor can show a new session source while keeping an old first user source, and both reports are correct under their own definitions.
Does Safari tracking prevention affect UTM attribution?
Yes. Safari Intelligent Tracking Prevention can expire client side identifiers within about seven days in some cases, so a visitor returning after a week may lose the original campaign attribution entirely.
Should I store UTM values in my CRM?
Yes. Capture UTM values on the landing page into first touch and last touch fields with an expiration you choose, commonly 90 days. That record survives cookie deletion and GA4 report quirks in a way platform attribution alone does not.
Why do GA4 campaign numbers change days after a launch?
Modeled key event credit can keep updating for up to about 12 days as more data arrives. The movement is the report settling, not the campaign returning.
Related reading: Why Your UTM Parameters Are Not Showing in GA4 · UTM Parameters vs GCLID Auto Tagging · How to Test UTM Parameters Before Launch · Are UTM Parameters Case Sensitive?