Google Ads tracking templates
Google Ads is where most tracking-template pain shows up: Tracking template vs Final URL suffix, {lpurl} encoding, parallel tracking, and HubSpot hsa_* colliding with click-fraud redirects.
Use this hub for paste-ready stacks. For the macro cheat sheet see Google Ads parameters. Field ownership is covered in template vs suffix.
How Google Ads tracking is split
- Tracking template — redirect structure /
{lpurl}(or a tracker URL wrapping it). - Final URL suffix — query params that should reach the landing page (UTMs,
nbt=, call-tracking keys). - Auto-tagging — keep on for
gclid; UTMs do not replace it.
Inheritance trap
Most specific level wins and replaces entirely (account → campaign → ad group → ad / keyword / sitelink). Orphaned sitelink or keyword overrides are why “half our clicks have no UTMs.” Prefer account-level template + suffix. FAQ: level precedence.
Mobile measurement (MMP)
App campaigns usually need an MMP redirect in Tracking template — see AppsFlyer and Adjust. Web landings measured in AppsFlyer can use a Final URL suffix instead.
Related guides
- ValueTrack cheat sheet (print / download)
- {lpurl} encoding
- Parallel tracking and redirects
- Ideal tracking template setup
- Template auditor · Template debugger
Featured Google Ads recipes
See all 165 Google Ads recipes →
FAQ
Should UTMs go in the Google Ads tracking template?
No — Final URL suffix under parallel tracking. Reserve Tracking template for redirects. Comparison.
Can HubSpot and ClickCease both use Tracking template?
Not as two redirects. One Tracking template per level. Typical pattern: HubSpot in template (or suffix) and ClickCease keys in suffix — see HubSpot + ClickCease.