Google Ads Tracking Template vs Final URL Suffix: Which to Use

You want UTM tags or keyword data on your Google Ads clicks, and Google Ads offers two places to put them: the tracking template and the final URL suffix. Put them in the wrong one and GA4 shows “(not set)” campaigns, a CRM loses the keyword, or a click tracker stops counting.

The short answer

• Use the final URL suffix for anything your landing page or analytics needs to see: UTM tags, and ValueTrack tags like {matchtype} or {device} that you want stored with the lead.
• Use the tracking template only when a third-party click tracker must record the click, such as a call-tracking or affiliate tool that gave you a URL to use.
• Most small businesses need only the suffix, set once at account level, with Google’s auto-tagging left on.

The rest of this guide explains why, so you can tell which setup fits your account.

The URL fields in Google Ads

Google Ads has three fields that together build the address a person lands on. Google describes them on its types of URLs page.

Field	What it holds	Example
Final URL	The page you want people to land on	https://example.com/boots
Final URL suffix	Parameters added to the end of that page’s address	utm_source=google&utm_medium=cpc
Tracking template	A URL pattern used to measure the click	{lpurl}?matchtype={matchtype}

Two more terms come up a lot:

• ValueTrack parameters are Google’s placeholders in curly braces, such as {campaignid}, {keyword} or {device}. Google swaps them for the real value at click time. The full list is on Google’s ValueTrack page.
• Auto-tagging adds a click ID called gclid to every click. It is separate from both fields and should stay on. Google says GA4 uses the auto-tagged values for source and medium when both are present.

What the final URL suffix does

The final URL suffix is the simpler field. Google says it lets you enter parameters that will be attached to the end of your landing page URL. You type only the parameters, joined with &:

utm_source=google&utm_medium=cpc&utm_campaign={_campaign}&utm_id={campaignid}

If your final URL is https://example.com/boots, a click lands on:

https://example.com/boots?utm_source=google&utm_medium=cpc&utm_campaign=fall-boots&utm_id=1234567890

A few things make the suffix easy to live with:

• ValueTrack tags work in it. Google’s rules for building the clicked URL add the suffix to the final URL first, then fill in custom parameters, then ValueTrack tags.
• It can’t break the landing page by forgetting {lpurl}. In fact, Google’s error list says the suffix can’t contain {lpurl} or {ignore} tags.
• Google handles the ?. You never type it. The same error list says the suffix cannot begin with ? or &.

What about the campaign name? Google’s ValueTrack list has {campaignid} but no tag for the campaign’s name. The usual workaround is a custom parameter: a placeholder you define yourself, like {_campaign}, with a value you set for each campaign. Google’s custom parameter page allows up to 8 per level, names of up to 16 letters and numbers, and no custom parameters at account level. So the suffix can live at account level, but each campaign needs its own _campaign value. If a campaign has none, Google’s URL rules fill in an empty string, and utm_campaign arrives blank.

What the tracking template does

The tracking template is a full URL pattern. Google calls it the field where you will put tracking information. It comes in two shapes.

1. A template that starts with {lpurl}. The {lpurl} tag means “your final URL goes here”. Google’s example is {lpurl}?matchtype={matchtype}. With a final URL of http://example.com, Google shows the landing page as http://example.com?matchtype={matchtype} with the match type filled in (ValueTrack setup page). Google’s help still shows this example. But its developer docs say that with parallel tracking, landing page parameters belong in the suffix (more on that below). Treat this shape as something to move, not something to copy.

2. A template that points to a third-party tracker. For example, Google’s developer docs show:

https://www.tracker.com/?u={lpurl}&alloc={_promoCode}

Here the tracker’s address comes first, and {lpurl} sits inside it. The tracker records the click and knows where the visitor was going.

Three rules from Google for templates:

• Account, campaign and ad group templates must include a tag that inserts the final URL, like {lpurl}. Google warns that without one, your landing page URL will break.
• When {lpurl} is not at the start, Google escapes it. Escaping means special characters such as ? and = are turned into codes. So the next question mark must be written %3F, not ?.
• The template and every redirect in it need to be HTTPS.

Why parallel tracking matters

Parallel tracking is the reason this choice matters. Google says it is mandatory for Search, Shopping, Display, Video and Performance Max campaigns. With it, the visitor goes straight to your final URL. The Google Ads click tracker and your tracking template URL load in the background.

That has one big result. Google’s developer docs say that with parallel tracking, any parameters that the landing page needs must be in the final URL suffix or the final URL, not in the tracking template. If you used to put UTM tags at the end of a tracker URL, the landing page may no longer see them.

The example on Google’s final URL suffix page shows both fields working together: a template of tracker.com/redirect={lpurl} and a suffix of x=y. With parallel tracking, people go straight to https://example.com/?x=y while the tracker runs in the background.

If you use a click tracker, Google also asks you to check with the provider that it supports parallel tracking. If it doesn’t, your click counts in that tool could stop working.

Which to use: four common setups

Your situation	Final URL suffix	Tracking template
Google Ads and GA4 only, and you want UTM tags	UTM tags, at account level	Leave empty
You want keyword, match type or device stored with each lead	UTM tags plus {keyword}, {matchtype}, {device}	Leave empty
A call-tracking or affiliate tool gave you a tracking URL	UTM tags and anything else the page needs	The tool’s URL, with {lpurl} where it says
Your account already has {lpurl}?utm_source=… in the template	Move the tags here now	Clear it once the suffix is live

Don’t leave the last row for later. Google’s ValueTrack help still shows a {lpurl}? template adding parameters to the landing page, but its developer docs say that with parallel tracking those parameters must go in the final URL suffix or the final URL. Moving them settles the question. It also keeps every landing page tag in one field, so the same tag can’t show up twice when someone adds a suffix later.

The tracking template generator for Google Ads asks which of these setups you have. If you have no click tracker, it puts everything in a final URL suffix and tells you no template is needed. If you do, it builds the template with the right {lpurl} escaping and checks it against Google’s rules.

Whatever you choose, keep utm_medium=cpc. Google’s GA4 page on how traffic source dimensions are updated recommends utm_source=google and utm_medium=cpc for Google Ads. When the gclid can’t be used, for example after a visitor denies ad_user_data consent, GA4 can fall back to your UTM values. A different medium would then put the same ads in two channels. For naming the rest, see our UTM best practices.

Account, campaign or ad group level

You can set both fields at several levels. For the tracking template, Google says the most specific one wins: keyword, then ad, then ad group, then campaign, then account.

The part people miss: the fields don’t merge across levels. Google’s URL rules pick the template, the suffix and each custom parameter separately, each from the most specific level that has one (a keyword or ad before its ad group, an ad group before its campaign, a campaign before the account). So if your account-level suffix has five UTM tags and someone adds a campaign-level suffix with just promo=fall, that campaign loses all five UTM tags.

A simple pattern for small accounts:

• Account level: one final URL suffix with all your UTM tags, using {_campaign} for the name.
• Campaign level: only the _campaign custom parameter value, in every campaign. A campaign without one sends a blank utm_campaign. No suffix, unless the campaign truly needs different tags. If it does, copy the whole account suffix and change it.
• Ad group, ad and keyword levels: leave empty unless you have a clear reason.

Mistakes that break tracking

Most of these come from the rules above. A quick list to check against:

• A suffix that starts with ? or &. Google rejects it. Start with utm_source=google.
• A template without {lpurl}, or a plain ? after an {lpurl} that isn’t at the start. Both break the landing page URL. Use %3F after an escaped {lpurl}.
• A campaign without a _campaign value. The tag arrives blank in GA4.

Tags Google doesn’t know

Google Ads only fills in tags from its ValueTrack list and your own custom parameters. {campaign}, {campaign_name} and Meta-style double-brace tags are not on that list, so they will never turn into your campaign name. Use {campaignid} or a custom parameter such as {_campaign}.

A campaign suffix that wipes the account suffix

If one campaign suddenly shows “(not set)” in GA4 while the others look fine, check whether someone gave it its own suffix. As the levels section explains, a campaign suffix replaces the account suffix instead of adding to it.

Judging the change too soon

Google says changes to tracking templates take 24–48 hours to reach your ads. Wait a day before you decide it didn’t work.

How to set it up and test it

These steps follow Google’s final URL suffix page. Menu names can shift a little as Google updates its interface.

1. Build the values. Write your suffix and, only if you need one, your template. The tracking template generator above checks both before you paste anything into Google Ads.
2. Account level. In Google Ads, open Admin, then Account settings, and go to the Tracking template section. Paste the suffix into the final URL suffix field (and the template into its field, if you have one). Save.
3. Campaign values. For each campaign, open Campaigns, select the campaign’s Settings, find the Campaign URL options, and add the custom parameter _campaign with a value such as fall-boots. Google’s custom parameter page has the exact steps.
4. Test. If you have a tracking template, select Test next to it, and Google checks that the landing page loads through it. For the suffix, paste your final URL with the suffix added into a browser. The page should load and keep the tags in the address bar. If a redirect on your site drops them, fix that first.
5. Check GA4 a day later. In Reports, open Acquisition, then Traffic acquisition. Google Ads clicks should show as google / cpc, with real campaign names, not “(not set)”.

Once it works, write the suffix into your team’s naming rules so nobody adds a second one at campaign level by accident. One field, one place, one set of rules.