Google Ads server-side tracking guide

Server-side tracking for Google Ads is an advanced method for measuring ad campaign performance. Instead of sending data directly from the user's browser, you send it from your own server. This approach uses Google Tag Manager's server container to manage measurement data and offers several advantages over traditional client-side tracking. By shifting data collection to a server you control, server-side tracking helps you get around ad blockers, privacy settings like Intelligent Tracking Prevention (ITP), and third-party cookie limitations. The result is more accurate and secure conversion data.

Server-side tracking provides greater flexibility in routing data to multiple destinations, including Google Ads and other platforms. For those looking to upgrade from, for example, a standard Google Tag Gateway implementation, a full server container ensures your data remains intact even as privacy measures become stricter across browsers. Setting up server-side tracking involves creating a server container in Google Tag Manager, configuring Google Ads conversion tags, and integrating with other platforms to centralize and secure your data flow. This setup preserves the integrity of your tracking data and makes your business resilient to upcoming changes in advertising

Google Ads conversion tracking measures what happens after a user interacts with your ad, such as completing a purchase, submitting a form, or adding a product to their cart. This data helps you assess ad performance and powers Smart Bidding, enabling Google to target users more likely to convert based on your specified business goals.

By tracking both primary and micro-conversions, you gain insights into which campaigns, keywords, and ads drive results. It also helps optimize ROAS, lower the cost per conversion, and adjust values post-conversion if needed (e.g., for returns), making your ad strategy more effective and data-driven.

In addition to online conversions, many businesses also track sales that happen offline, such as phone orders, in-store purchases, or upsells. The Google Ads Offline Conversion tag lets you send this data directly from your server GTM container to Google Ads, so you don't have to upload files manually.

If you don't already use a CRM, our guide on Google Ads offline conversion tracking without a paid CRM walks through building this with just GTM, Stape, and a Google Sheet. This improves attribution across online and offline touchpoints and ensures Google's bidding algorithms can optimize for customers most likely to convert.

Here is the official documentation on Google Ads and server-side tracking: Google Ads conversions (Google).

While moving to the server provides a significant boost in data accuracy, it doesn't replace the need for a solid client-side foundation. Understanding what is an ad tag and how a click tag communicates with the server is essential for any marketing specialist auditing their setup.

In July 2021, Google released Google Ads conversion tracking and conversion linker tags for the Google Tag Manager server container. This update to GTM server-side tracking allows you to derive more value from your Ads account by providing more reliable server tracking and ensuring more accurate conversion data.

Google Ads conversion tracking works exclusively with the Google Analytics 4 (GA4) tag, meaning that if you want to set up Google Ads tracking yourself, you should configure the server-side GA4 tag. Unlike Facebook, Google Ads does not support deduplication, so you should use either web or server-side conversion tracking.

Follow the steps below to set up Google Ads server-side tracking.

This guide explains how to set up and host a server container. We also have an article that covers the steps for sending data from the web to the server container.

The next step is to configure the server-side Google Analytics 4.

We have a detailed user manual on how to set up server-side Google Analytics 4 in our blog post.

In the Server container, set up the Conversion Linker tag. This tag should trigger on all pageviews. 

Create a new Google Ads Conversion Tracking tag in the Server container → add Conversion ID and Conversion Label similar to the web Ads tag setup.

Then, you can add Product and User Data (it looks very similar to how Facebook's Conversions API works). If you send user and product data from the web to the server, you can enable these checkboxes and select event data as a data source. Our Ads server conversion triggers on the purchase event. 

That's it for the server container. But Google also added a bonus to the web Google Ads tag. 

You can set up Enhanced Conversions in Google Ads to send user data. 

Why set Enhanced Conversions up?

• Improves the accuracy of conversion tracking and bidding.
• Ensures data security using Google’s SHA-256 algorithm.
• Collects first-party data (such as name, email address, home address, phone number, etc.).

Log in to your Google Ads account → Tools & Settings → Conversions → check Turn on Enhanced Conversions.

In web GTM, go to Variables → in the section User-Defined Variables → click New → add the following settings:

• Variable Type - User-Provided Data
• Type - click on Manual Configuration
• Add to the parameters variables as shown in the screenshot below

Go to the Tags section and find the GA4 tag or create it (click New → Tag Type: Google Analytics: GA4 Event).

Add the user-provided data using the user_data parameter, as shown in the screenshot below. Select the variable you created in Step 2 in the User Data section.

In the server GTM container, go to Tags → New → Tag configuration Google Ads Conversion Tracking.

Add triggers based on the needed conversion events. The tag will automatically process user data from GA4 requests.

The server Google Ads product remarketing tag works based on the Google Analytics 4 product data.

Open the Google Ads Remarketing tag inside the server Google Tag Manager container and enable Send dynamic remarketing event data.

To make dynamic product remarketing work, ensure that in the Google Tag Manager web interface, you've configured product data inside the Google Analytics 4 tags. 

First, test that the Google Ads Conversion tag was triggered in the server container and that the request it sent was correct.

Check that the FPGCLAW cookie was added. It will work if you add the gclid parameter to the URL.

1. A user wanted to send Enhanced Conversions server-side for Google Ads, as no data was coming from the web. In the full thread, the solution was to create a transformation that structures a user data object like the web’s user-provided-data, or to use the dedicated User-Provided Data Event tag in the server container to send the enhanced data correctly.

2. A user implementing Google Ads server-side tracking couldn’t send Enhanced Conversions because user_data from the GA4 SS Configuration tag wasn’t available on the GA4 purchase event. In the full thread, the solution was to use tag sequencing so the GA4 purchase tag fires after the GA4 SS Configuration tag, or to explicitly add the user-collected variables under the user_data key in the GA4 purchase tag. This ensures Enhanced Conversions are sent correctly.

3. A user noticed that view-through conversions were not being recorded in Google Ads when using server-side tracking with Stape, even though GA4 and standard clicks were tracked. In the full thread, the solution was to ensure user data is sent along with conversions for Enhanced Conversions. With proper user data, server-side tracking can attribute view-through conversions correctly, improving accuracy for YouTube and display ad campaigns.

4. A user noticed a spike in unassigned traffic after implementing Google Ads server-side tracking via Google Tag Manager. In the full thread, the main causes were identified as misconfigured UTM tags in ad campaigns and potential double redirects that strip UTM parameters before GA4 can register them. The solution is to verify UTM tagging in ads and check for redirects, ensuring server-side tracking accurately attributes traffic.

Setting up server-side tracking in Google Ads isn't difficult, but it does require some time and careful configuration. You can implement this type of tracking by using the Google Ads tag for the server container or server-side Google Analytics.

If you need help setting up either option, don't hesitate to submit a help request. We have experience with both methods and would be happy to provide a cost estimate for our services.

Do any of these solutions sound right for you? Reach out and let us know which approach fits your needs, or share your challenges so we can help you find the best path forward.