Short answers to the questions that show up when Google Ads URL options, UTMs and click trackers collide. Deep dives live in Guides and Docs.
Template debugger · Builder · Recipes · Certified trackers
Final URL suffix. They survive redirects and parallel tracking. Reserve the template for redirect structure. Full comparison.
No. Leave it as {lpurl} or empty; put parameters in the suffix.
No. {lpurl} belongs only in the tracking template.
No. The most specific level replaces the higher one entirely. Restate every parameter when you override.
Account / campaign / ad group changes do not send ads for review. Ad-level URL edits can.
Not always. {escapedlpurl} is always encoded. {lpurl} is raw at the start of the template and encoded after ? or =. Encoding guide.
When a hop re-encodes the destination before the last redirect. Match encode layers to the chain — do not “+2 just to be safe.”
Over-encoding. Drop one level (+3 → +2, or +2 → {lpurl}).
Almost never. Raw ?/& break the outer tracker URL. Use an encoded variant.
Yes for modern Search, Shopping, Display and Video. What breaks and what works.
The browser no longer visits the tracker page. You need a server-side HTTPS 301/302, or move to suffix-only measurement.
DevTools Network: 301/302 + Location = server-side. 200 HTML that then navigates = client-side.
Not directly — they fire on the landing page. Pre-landing browser hops are what break.
Yes — and you should. Auto-tagging feeds Google Ads; UTMs feed GA4 and other tools. Keep utm_source=google and utm_medium=cpc lowercase.
Often UTMs only in the template (never on the page), or the site/CDN stripping query params. Move UTMs to the suffix and check canonical/redirect rules.
utm_source without utm_medium, or the suffix missing for that slice of traffic (orphaned level override).
Use the template debugger, then Ads Test + a real click.
Browse certified trackers by redirect vs Final URL suffix, and confirm parallel-tracking support with the vendor.
Ideal tracking template configuration (scheduled/live via docs).