Google Ads Tracking Templates: Examples, Overrides and an AI Audit

Choose between a tracking template and a final URL suffix

Start with what the destination needs to receive. If you need UTM parameters on the landing page, the final URL suffix is the place to examine. A third-party measurement provider can require a tracking template with its own redirect URL and an inserted destination.

Google explains the roles of these fields in its URL tracking documentation. Check your measurement provider’s instructions before replacing an existing template. Its URL can be responsible for reporting that your team already relies on.

Use a ValueTrack example you can inspect

For an illustrative Search campaign with an otherwise untagged destination, a final URL suffix could be:

utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}

Enter a suffix without a leading question mark. Google supplies the connection to the destination URL. Campaign and creative IDs are identifiers, so keep a lookup to the corresponding account names when another reporting tool needs readable labels.

The {keyword} parameter refers to the keyword associated with the click. It does not recover every search phrase a person typed. Use the account’s search-term reports for that investigation, subject to their reporting limits.

A simple tracking-template example is shown below to explain the syntax. For parameters intended for the landing page, review whether a suffix better fits your setup.

{lpurl}?utm_source=google&utm_medium=cpc&utm_campaign={campaignid}

{lpurl} inserts the destination. Google’s ValueTrack setup guide explains URL insertion and parameter substitution. These examples require testing against your own destination, especially if it already contains parameters or passes through a measurement provider.

Check which level overrides the account template

Tracking templates can be set at several levels. Google uses the most specific applicable value: keyword, ad, ad group, campaign, then account. An account setting by itself cannot prove which template a particular click uses.

For example, suppose the account template uses utm_source=google, but one ad has an older template using utm_source=paid-search. Changing the account template leaves that ad’s override in place. Record the effective setting for the affected ad before editing a broader level.

SourcetoMCP’s account-settings read returns the account template, suffix and auto-tagging state. For more detailed reads, the assistant can discover available Google Ads fields and query supported resources. When a field or combination is refused, inspect the level in Google Ads or supply an export. An unread level should remain marked as unchecked.

Keep auto-tagging under separate review. Removing Google click identifiers or disabling auto-tagging can affect linked reporting even when your manual UTMs still look correct.

Run a read-only tracking audit with AI

Connect the correct account, then give your assistant a destination and an affected campaign. Ask for evidence at each level rather than a blanket account change.

Audit URL tracking for [Google Ads account] and [campaign]. Make no changes. Read account-level auto-tagging, final URL suffix and tracking template. Identify available fields for campaign, ad group, ad and keyword overrides before querying them. Show the level and resource ID for each value. Mark any level you cannot inspect. Compare the settings with this intended destination and measurement-provider setup: [details]. Propose the smallest change for review, with a manual URL test.

The audit should return current values, checked resources, unresolved levels and a proposed edit. It cannot establish that a website redirect preserves parameters without testing the destination in a browser.

For a broader tracking review, add the findings to your Google Ads audit checklist. Use the GA4 audit checklist to check how the linked property collects and reports visits after the click.

Test the destination before applying a change

Use the Test control beside the tracking template in Google Ads. Then open the resolved landing page and inspect the parameters after redirects. A successful URL test checks the destination path, but you still need to verify that your analytics and measurement tools receive the intended data.

Google’s parallel tracking guidance explains that the landing page can load while measurement runs in the background. A tracking URL working in isolation does not validate every third-party integration.

Use a hypothetical audit of ten ads to keep the scope concrete. If eight inherit the account template and two have their own template, an account edit addresses only the inherited group. Save the two exceptions with their IDs and decide whether each override is intentional.

Approve the exact edit and read the saved settings

SourcetoMCP can update account-level auto-tagging, final URL suffix and tracking template. Those are account-wide changes. Give the assistant the precise account and field values you approve after you have tested the proposed URL.

For account [ID], propose setting only the final URL suffix to [approved value]. Preserve the existing tracking template and auto-tagging state. Show the before and after values and wait for approval. After the approved change, read the account settings again and report the saved value. Leave all campaign, ad group, ad and keyword settings unchanged.

Keep the previous value, change time and test result in your reporting notes. Recheck an affected campaign’s attribution after fresh visits have been processed, using the same definitions and reporting periods as your baseline.