“Google Ads says we made $40,000 last month. GA4 says $26,000. Shopify says $31,000.”
If someone brought me those numbers, I’d ask which reports they opened before touching a tracking setting. Different attribution models, purchase values, and reporting dates can produce different totals. A missing tag can create another problem on top of that.
Tracking templates and UTM parameters help you identify the traffic arriving at your store. Set them up consistently, and you have a better starting point for investigating the gap. Here’s how I’d do it.
Key takeaways
- Keep auto-tagging enabled, check the Google Ads–GA4 link, and make sure redirects preserve click information.
- Use a final URL suffix to put UTMs on the landing page. Use a tracking template when your measurement provider needs one.
- Check which ValueTrack parameters your campaign supports before copying a suffix across the account.
- Test the assembled URL and data collection separately. A page loading successfully is only the first check.
What each tracking field does
The final URL is the destination you enter for the ad. The final URL suffix holds parameters Google appends to that destination, such as UTMs.
A tracking template defines a tracking URL, often for a third-party measurement provider. It normally includes a landing-page placeholder such as {lpurl}. With parallel tracking, shoppers go directly to the landing page while the measurement request runs in the background. Google requires parallel tracking for Search, Shopping, Display, Video, and Performance Max.
ValueTrack parameters, such as {campaignid}, insert Google Ads information into the URL. Custom parameters, such as {_season}, insert values you define. A campaign might define the custom value as bfcm, for example.
UTMs are the named URL parameters your reporting tools read. You can use utm_source=google to label the source and utm_medium=cpc to label the medium. The tracking options in Google Ads give you places to add those labels without editing every destination URL.
Start by checking auto-tagging and the GA4 connection
In Google Ads, go to Admin → Account settings → Auto-tagging and check that tagging is enabled. Google enables auto-tagging by default for new accounts. It adds click information, commonly a gclid parameter, that supports Google Ads measurement and integrations.
Then confirm the right Google Ads account is linked to the right GA4 property. Auto-tagging is Google’s recommended way to bring detailed Google Ads data into Analytics, but your Analytics collection still has to work. A redirect that strips parameters or a purchase event that never fires needs its own fix.
What happens if you also use UTMs?
When manual tags and usable auto-tagging information are both present, GA4 prioritizes auto-tagged values for traffic classification. You can still use utm_content and utm_term for the manual ad content and manual term dimensions.
If GA4 cannot use the click identifier as intended and UTMs are present, it derives cross-channel traffic-source values from the UTMs. That’s why I’d use a consistent set of relevant fields rather than adding a campaign label on its own.
UTMs can also help Shopify or another reporting tool recognize the traffic. Check what each tool expects before replacing an agency’s existing tagging convention.
Do you need a tracking template?
I’d leave the template empty if the account only needs UTMs on the landing page. A final URL suffix handles that job.
If you use a click-measurement provider, ask for its documented Google Ads template and confirm parallel-tracking support. The provider may need an escaped landing-page placeholder or other identifiers.
Google requires a final-URL insertion parameter, such as {lpurl}, in account-, campaign-, and ad-group-level tracking templates. Dynamic Search Ads and auto-targets require one at all levels. Follow the provider’s format so the landing page is inserted correctly.
What a third-party tracking template looks like
A provider might give you something shaped like this:
https://tracker.example/click?destination={lpurl}&campaign_id={campaignid}
That’s an illustration using a fictional tracker. The provider defines the endpoint and parameter names. Google supplies the resolved landing page and campaign ID. If the destination contains query parameters of its own, the provider may require an escaped URL placeholder so its system can read the nested URL correctly.
I’d keep shopper-facing UTMs in the final URL suffix unless the provider explicitly documents a different setup. With parallel tracking, parameters attached only to a background tracking request may never reach the shopper’s page. Google’s suffix example shows the destination receiving its suffix while the tracking request runs separately.
Before replacing an existing template, ask who uses the data it sends. An unfamiliar tracker could be feeding an attribution tool the finance team relies on. Save the original configuration, confirm the provider’s requirements, and test the replacement on a small scope.
How I’d set up a final URL suffix
For a Search campaign, I might start with this convention after checking the store’s existing reporting requirements:
utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_id={campaignid}&utm_source_platform=google_ads&utm_content={creative}&utm_term={keyword}
Here, google_ads is a label we’ve chosen for source platform. {campaignid}, {creative}, and {keyword} are placeholders Google fills in. The campaign ID stays stable if someone renames the campaign, but the reporting team needs a way to map it back to a readable name.
Google recommends setting all relevant UTM fields, especially source, medium, campaign, campaign ID, and source platform, when you use manual tagging. Agree on capitalization and labels across the tools reading them.
To add the suffix, go to Admin → Account settings, open the tracking settings, and enter it in Final URL suffix. Google also supports suffixes at campaign and more specific levels. Start without a question mark.
What each UTM field will mean in the report
utm_source identifies the source, such as google. utm_medium identifies the traffic medium, such as cpc. Keep the spelling consistent across paid campaigns so a report doesn’t end up with separate labels for Google, google, and GoogleAds.
utm_campaign is the campaign label a downstream tool can display. Using {campaignid} gives it a stable identifier. If Shopify users need readable labels immediately, agree on a stable campaign label instead and maintain it deliberately. Either approach needs documentation.
utm_id provides a campaign ID field alongside that label. utm_source_platform identifies the platform according to your chosen convention. Check how the receiving tool uses these fields before assuming it reports every one.
utm_content can distinguish ads or asset groups, depending on the campaign. utm_term can carry the matched Search keyword. Neither is automatically a report of the exact headline combination shown or the query the shopper typed.
Add it without overwriting an existing setup
- Copy the current account tracking template and suffix into your change notes.
- Check campaign URL options for existing suffixes and any requirements from third-party tools.
- Choose whether the Search example belongs at account level or only on the relevant Search campaigns.
- Open Admin → Account settings, expand the tracking settings, paste into Final URL suffix, and save.
- For a different campaign suffix, use the campaign’s tracking/URL options and enter the complete intended suffix.
- Test both the ordinary ad destination and a sitelink destination before expanding the change.
If Search and Performance Max need different content identifiers, I’d make the campaign-level exceptions explicit in the notes. A default at account level is easier to maintain when everyone can see where it has exceptions.
What the landing-page URL should look like
Say the final URL is:
https://example.com/collections/hiking-boots
For a hypothetical Search click with campaign ID 123456789, ad ID 987654321, and keyword waterproof boots, the UTM portion would resolve to:
https://example.com/collections/hiking-boots?utm_source=google&utm_medium=cpc&utm_campaign=123456789&utm_id=123456789&utm_source_platform=google_ads&utm_content=987654321&utm_term=waterproof%20boots
Auto-tagging may add click information as well. This example shows the UTM portion so you can see what each placeholder becomes. Google assembles the URL separators for the suffix. If the destination already has query parameters, check the resulting URL rather than manually adding another question mark.
Which ValueTrack parameters work for your campaign?
Use Google’s ValueTrack reference to check support before rolling a template out. These are the distinctions I’d keep in front of the person doing the setup:
- {campaignid} identifies the campaign and is supported in Performance Max.
- {creative} returns the ad ID. Google doesn’t list it in the supported Performance Max parameter set.
- {keyword} returns the account keyword that matched a Search query. It can be blank for keywordless AI Max matches, Dynamic Search Ads, and Performance Max. It doesn’t return the shopper’s actual search.
- {device} returns mobile, tablet, or computer codes and is supported in Performance Max.
- {assetgroupid} identifies the Performance Max asset group.
- {network} returns x for Performance Max traffic. It cannot tell you whether that click came from Search or YouTube.
- {product_id} has limited Performance Max support, depending on the format or channel.
For Performance Max, I’d use campaign and asset-group IDs if those are the identifiers the reporting tool needs:
utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_id={campaignid}&utm_source_platform=google_ads&utm_content={assetgroupid}
Document that utm_content now contains an asset-group ID. Keep the meaning clear for whoever builds the report.
AI Max and Shopping need their own checks
For keyword-based Search matches, {matchtype} can return e, p, or b. Google also documents a for AI Max keywordless matches. Its separate {search_term_matchtype} parameter covers AI Max broad expansions as well as keywordless matches. Use the current parameter definitions when deciding which distinction your reporting actually needs.
If final URL expansion can select different destinations, test the tagging on those destinations too. A successful test of the ad’s original final URL doesn’t cover every page the campaign might choose.
For Shopping traffic, product identifiers can help a tool connect a visit to an item, but check format support and how that tool maps the identifier to your catalog. A product ID in the URL doesn’t establish which products the customer eventually bought. Purchase events and item data need their own validation.
Check for overrides before changing the account
An account-level template may look right while an old keyword-level template is still being used. For Search, Google applies the most specific tracking template, working down through campaign, ad group, ad, and keyword settings. Sitelinks also have URL options, and Performance Max has asset-group URL options.
I’d export the current settings before editing them. Check templates, suffixes, hardcoded UTMs, and any custom parameters at the levels the account uses. Lower-level settings need reviewing before you assume an account-level change will cover every click.
Google lets you define up to eight custom parameters at supported levels other than account level. If you define the same custom parameter name at multiple levels, the more specific value takes precedence. Keep a record of what each label means.
A common override problem
Imagine the account template points to your current measurement provider. One high-spend ad group still has an old provider’s template. Changing the account template leaves that ad group’s more specific setting in place.
I’d add the tracking template columns to the campaign, ad group, ad, and keyword views used in the account, then inspect the populated values. Check sitelink URL options separately. In Performance Max, inspect asset-group URL options as well. Save an export so you can identify the setting responsible if one campaign’s tracking behaves differently after launch.
Keep template selection and custom-parameter values separate in your notes. A campaign can define {_season}=bfcm, while a more specific entity can define a different value under the same name. Google’s custom-parameter hierarchy determines which value is inserted.
How I’d test the setup
- Test a limited change first. Save the existing configuration and use the Google Ads Test option where available. The landing-page test helps identify URL configuration problems.
- Inspect the resolved destination. Check that the right page opens, parameters survive redirects, and the URL contains no duplicate UTM fields or unresolved placeholders.
- Check collection. Use browser inspection, Tag Assistant, or GA4 debugging tools as appropriate. Inspect the full page_location value when checking the arriving URL. Use a clearly labeled test URL for manual checks and keep test activity out of performance analysis.
- Verify purchase measurement. Confirm that a purchase sends the expected transaction ID, value, and currency. Check for duplicate purchase events.
- Review actual traffic after rollout. Check Search, Performance Max, sitelinks, and any expanded destinations separately. Let reporting populate before deciding a missing campaign row means the URL setup failed.
Google documents review requirements for tracking changes, including review for changes at ad, keyword, and sitelink level. Build that into your launch plan. A successful URL test alone doesn’t validate attribution or revenue reporting.
Three checks I’d do in the browser
Follow the redirect chain. Open a clearly labeled test URL carrying harmless test UTMs. Check whether the first page redirects to a different collection, locale, or canonical URL. Confirm the parameters are still available when collection occurs. A redirect from a retired collection to its replacement can load the right products while dropping the tracking labels.
Look for duplicate fields. A destination might already contain utm_source=google, while a new suffix adds utm_source=google again. Another system may append a conflicting campaign label. Choose one maintained location for each field and test the result. I wouldn’t depend on different tools resolving duplicate parameters in the same way.
Distinguish static tests from Google Ads substitution. Pasting {campaignid} into your browser doesn’t make Google replace it. A manual browser test needs sample resolved values. Use Google Ads’ testing tools and subsequent real traffic to inspect the actual substitution. A manually invented click ID also cannot validate Google Ads attribution.
What I’d check in GA4
Use Tag Assistant and the relevant debugging tools to confirm the correct GA4 property receives the visit and purchase event. Inspect page_location for the full arriving URL and compare the purchase event’s transaction ID, value, and currency with the test order.
Then check the dimension used in the report. Session source/medium answers a session acquisition question. First-user dimensions describe how a user was initially acquired. Event-level attribution can answer another question again. Google’s traffic-source dimension guide distinguishes these scopes. Choose matching scopes before comparing totals.
For a live rollout, record the change time and review new traffic after that point. Updated tags identify future arrivals. They don’t rewrite the tags collected on last month’s visits.
How Shopify fits into the picture
Shopify supports standard UTMs for campaign reporting. Its Campaigns auto-match rules can assign sessions based on a specified combination of parameters. Once a rule matches, additional parameters are ignored for that matching process. That statement applies to campaign matching.
Before comparing revenue, open the report’s attribution settings. Shopify’s marketing performance view uses last non-direct click by default, while other report configurations can use different defaults. Its marketing reports let you choose supported attribution models.
Consistent tags make traffic easier to identify. You still need to know which report and model produced the sales total.
A Shopify campaign-matching example
Suppose your Shopify Campaigns rule expects utm_campaign=bfcm, but the Google Ads suffix sends utm_campaign=123456789. Both values can be valid labels, yet they won’t satisfy the same exact rule.
Check the actual arriving value against the campaign’s auto-match conditions. Decide whether to update the rule or your tagging convention after checking what existing reports depend on. Shopify warns that editing an existing rule can change the traffic included in the campaign report, so document the change before making it.
I’d verify the full path from the ad’s URL settings to the arriving session before blaming Shopify for missing a campaign. The fault could be the label, an override, or a redirect upstream.
Why the revenue numbers may still disagree
Go back to that $40,000, $26,000, and $31,000 example. I’d check the selected purchase action and revenue definition, the date range and time zone, and the attribution model and window. I’d also check whether one report uses interaction dates while another uses purchase dates. Google documents that date difference as a source of discrepancies.
Then I’d investigate duplicate or missing purchases, refunds, and differences in the values being sent. Consent affects collection too. Basic and advanced consent mode behave differently, and modeled data depends on the implementation and eligibility.
The question I want to answer is whether the remaining gap comes from known reporting choices or something broken in collection. That gives the team a concrete next step.
How I’d troubleshoot the symptoms
The page loads, but the tracker records nothing
Check whether the provider’s request is being sent, whether the template is associated at the intended level, and whether the provider supports parallel tracking. Confirm required identifiers and escaping against its documentation. A working destination and a working measurement request are two separate checks.
The tracker has clicks, but GA4 is missing visits
Inspect the destination and redirects, then check Analytics collection and consent behavior. A click can happen without a recorded page visit if the page fails to load or the tag never sends data. Multiple visits can also follow one click, so clicks and sessions need investigation when they differ, without assuming a one-to-one relationship.
Google Ads traffic is classified unexpectedly
Check the Google Ads–GA4 link and whether click information survives to the page. If UTMs become the fallback, inspect all of them together, particularly source and medium. Check whether a hardcoded parameter or more specific URL option is supplying a different value.
Revenue is duplicated or the values are wrong
Check transaction IDs, the number of purchase events fired per order, currency, and the value supplied by each integration. Investigate whether two implementations are sending the same purchase. Fixing a campaign tag won’t repair a duplicated purchase event.
The keyword is blank, but the campaign ID is present
Identify the campaign and match source first. Keywordless traffic can legitimately produce a blank keyword value. Compare against the supported ValueTrack parameters before changing the template.
Google Ads tracking template FAQ
Should every ecommerce account have a tracking template?
Use one when your measurement setup requires it. For ordinary UTM tagging on the destination, a final URL suffix is usually sufficient.
Should I turn off auto-tagging if I use UTMs?
Keep auto-tagging on unless a specific, documented implementation requires otherwise. Google recommends it for the Google Ads–Analytics integration.
Will renaming a campaign change a hardcoded UTM?
A campaign rename doesn’t rewrite manually entered UTM text. If you change that text too, future traffic can use a new label. Campaign IDs help keep the identifier consistent.
Why is the keyword field empty?
The click may have come from a keywordless match or a campaign type that doesn’t populate that parameter. Check campaign support and match source before treating the empty field as a fault.
Want your tracking setup checked?
Start by saving the existing URL settings and testing one representative campaign. If you’d like help working through tagging, purchase measurement, or the reporting gap between platforms, talk to Solutions 8 about Google Ads management. Our guide to Google Ads conversion tracking covers the conversion setup alongside the URL checks.



