Google Ads URL options guide
Google Ads tracking template
Use tracking template, Final URL suffix, and ValueTrack without breaking landing pages, duplicating UTMs, or muddying a governed measurement workflow.
These fields do different jobs. The Final URL owns destination. The Final URL suffix appends landing-page parameters. Tracking templates and ValueTrack handle click-measurement logic. The safest setup is the simplest one that still solves the reporting job.
Most advertisers do not need a tracking template everywhere.
Use one when a click-measurement layer or third-party tracker genuinely needs it, not because every Google Ads URL feels incomplete without one.
If a higher-level template exists, it must insert the Final URL.
At account, campaign, or ad group level, a template needs a URL insertion parameter such as {lpurl} or the landing page breaks.
Keep ownership boring and deliberate.
One layer should own destination, one layer should own appended parameters, and one layer should own QA. That is how you stop Google Ads URL options turning into silent link debt.
Quick answer
Tracking template vs Final URL suffix vs ValueTrack
These terms get lumped together, but they solve different parts of the same click path.
Final URL suffix
Use this when you want parameters appended to the landing-page URL itself.
- Best for stable, governed UTM values that belong on the final landing page.
- Can be applied at multiple Google Ads levels, including account, campaign, ad, ad group, dynamic ads target, keyword, and sitelink.
- Usually the cleanest default when you are not using a third-party click tracker.
Tracking template
Use this when the tracking layer needs its own logic, redirect path, or click-measurement parameters.
- Useful for third-party click trackers or measurement patterns that should sit outside the landing-page destination itself.
- At account, campaign, or ad group level it must include a URL insertion parameter such as
{lpurl}.
- Keep it as simple as possible and use HTTPS-compatible redirect paths.
ValueTrack parameters
Use these when you need Google Ads click-context values such as campaign ID, ad group ID, device, or keyword.
- Google suggests using ValueTrack in the tracking template.
- You can also use ValueTrack in final URLs and custom parameters when that is the right technical fit.
- Do not confuse click-context values with your human-readable campaign taxonomy.
Field ownership
What each field should actually control
Most breakage starts when the same parameter job is spread across too many layers.
Final URL
Owns destination. With upgraded URLs, Google Ads separates the landing page from the tracking portion, so the Final URL should usually stay clean unless the page genuinely needs parameters to render content.
Final URL suffix
Owns parameters that should be appended to the landing page after the click. This is the safest place for stable manual UTMs when they are part of your governed naming system.
Tracking template
Owns click-measurement routing. Use it when a tracker or measurement layer needs its own format, or when ValueTrack belongs in the measurement path instead of the landing-page URL.
Custom parameters
Own reusable advertiser-defined values. They work well when one template needs to read values that change by campaign, ad group, ad, or keyword without hard-coding everything into the template itself.
Default setup
The safest default setup for most teams
Keep ownership simple until a real measurement requirement forces you to add another layer.
If your paid-search workflow also runs in Microsoft Advertising, standardise the parallel build with Microsoft Ads tracking template and UET rather than copying Google logic blindly.
| Scenario |
Best default |
Why |
Main failure risk |
| Standard Google Ads campaign with no third-party click tracker |
Clean Final URL + governed Final URL suffix |
Keeps destination clean and puts stable UTM ownership in one append layer. |
Teams still hard-code duplicate UTMs into the Final URL or builder output. |
| Google Ads campaign using a third-party click tracker or approved redirect measurement path |
Tracking template + {lpurl} + minimal suffix if needed |
Lets the tracker own the measurement route while the landing page still resolves correctly. |
The template omits a URL insertion parameter or points to an incompatible redirect chain. |
| Account with reusable IDs or labels that differ by campaign or ad group |
Custom parameters + one controlled template |
Prevents hard-coded sprawl and lets the most specific value win where needed. |
Conflicting custom parameters across too many levels create silent overrides. |
| Team wants readable manual campaign labels plus Google click context |
Suffix for manual UTMs, ValueTrack in template only if justified |
Separates human-readable taxonomy from Google click-context values. |
People try to make ValueTrack do the same job as UTM naming. |
Breakage rules
The rules that stop Google Ads URL options from breaking attribution
The most expensive problems are usually structural, not analytical.
Do not use a higher-level tracking template without a URL insertion parameter.
At account, campaign, or ad group level, a template needs {lpurl} or another supported URL insertion parameter. Without it, Google Ads cannot build the landing page correctly.
Do not let the same UTM keys appear in multiple ownership layers.
If the Final URL, Final URL suffix, builder, or tracker all try to append utm_source or utm_campaign, the output turns ambiguous fast.
Keep tracker URLs HTTPS-compatible and parallel-tracking-safe.
Google recommends HTTPS in the tracking template, and with parallel tracking the user goes to the final destination while click measurement runs in the background.
Use custom parameters only with a clear ownership rule.
Google Ads allows up to eight custom parameters at each non-account level, and the most specific value wins. That is useful only if people know who is allowed to override what.
Keep the Final URL boring. Destination first. Measurement logic should not turn the landing page field into a dumping ground.
Use Final URL suffix for stable landing-page parameters. This is usually the cleanest home for governed UTMs.
Use tracking templates for measurement logic. Reach for them when the measurement path actually needs them, not by habit.
Test before release. Google Ads has a template test step, but you still need your own QA and live redirect check afterwards.
Build sequence
A practical build pattern for Google Ads URL options
This sequence keeps naming, destination, measurement, and QA in the right order.
1
Set the Final URL as the real destination
Choose the actual landing page first. If the page does not need parameters to render different content, keep the Final URL clean.
2
Decide whether stable manual UTMs belong in Final URL suffix
If you need readable campaign values for reporting, append them in one governed place. This is usually the suffix, not the destination field itself.
3
Add a tracking template only if the measurement layer needs it
If a third-party click tracker or Google click-context setup justifies a template, begin with {lpurl} where the template level requires it and keep the rest of the logic minimal.
4
Use custom parameters for reusable values, not for chaos
If values change by campaign, ad group, or ad, custom parameters can reduce hard-coding. Keep in mind that Google Ads does not allow custom parameters at account level.
5
Test the template in Google Ads, then QA the output yourself
Use Google Ads' built-in test step for the template, then run the final output through the UTM QA Checker so duplicates, malformed URLs, and structural conflicts get caught before launch.
Setups compared
Bad, better, and safest setups
The problem is rarely one field. It is usually unclear ownership across several fields.
Weak
The Final URL already contains manual UTMs, the suffix appends more values, and a tracker template wraps another redirect layer. Nobody can say which field is authoritative.
Better
The Final URL stays clean, the suffix appends stable governed UTMs, and there is no tracking template because the campaign does not need a separate measurement layer.
Safest
The Final URL owns destination, the suffix owns stable landing-page parameters, the tracking template exists only when justified, {lpurl} is present where required, and the team tests, QA-checks, and logs the live output.
FAQ
Questions teams ask about Google Ads URL options
Short answers to the mistakes that cause most of the confusion.
Do we need a tracking template if we already use Final URL suffix?
No. Most advertisers do not need a tracking template by default. Use one when a click-measurement layer, redirect tracker, or specific ValueTrack requirement justifies it.
What breaks if the template forgets {lpurl}?
At account, campaign, or ad group level, the landing page URL breaks because Google Ads has no inserted Final URL to work from.
Should manual UTMs live in the Final URL or the Final URL suffix?
Usually the Final URL suffix, provided those values are just tracking parameters and do not change page content. Keep the Final URL as the destination and keep append ownership in one place.
When should we use custom parameters?
Use them when one template needs reusable values that vary by campaign, ad group, ad, or keyword. Google Ads allows up to eight custom parameters at non-account levels, and the most specific one wins.
Can auto-tagging still stay on?
Yes. That is a different decision. If Google Ads and GA4 reconciliation matters, keep auto-tagging on and make sure your manual UTM and URL-option decisions do not fight the click-measurement layer. See UTMs vs auto-tagging for that boundary.
Sources and next steps
Primary docs, validation pages, and next steps
This page is based on current Google Ads Help documentation and tied into the rest of the Shortlinkfix workflow.