Template debugger

Paste a Final URL, tracking template and optional Final URL suffix. See the resolved click URL, how {lpurl} is encoded, and common parallel-tracking mistakes — including %253F over-encoding.

Which tool? Debugger = inspect one setup. Template auditor = is this stack correct? Template builder = merge stacks. {lpurl} encoding · Parallel tracking · Template vs suffix.

Examples:

Sample ValueTrack fills use fixed demo IDs (campaignid, keyword, Microsoft CampaignId, …). Encoding follows Google’s position rules and +2/+3 variants — still verify with Ads Test and a real click. The address bar updates with ?f=&t=&s= so you can share a setup.

FAQ

Does this replace Google Ads Test?

No. It explains encoding and parallel-tracking footguns before you publish. Still use Ads Test and a real click.

Why is my resolved URL still encoded?

Redirect trackers receive an encoded destination on purpose. The tracker decodes, then redirects. If the landing address bar shows %253F / %25, you likely over-encoded — the debugger flags that. See {lpurl} encoding.

Where should UTMs go?

Final URL suffix under parallel tracking. Details: template vs suffix and parallel tracking.

Can I share a debug setup?

Yes. Use Copy share link — the URL keeps Final URL, template and suffix in ?f=&t=&s= query params (client-side only).