Server-side Tag Manager allows you to move your Google Floodlight sales and counter tags from the web page to the server. Moving these tags to the server will reduce the amount of code you have to run in the page, and may help improve page load times.
This article describes how to configure your Tag Manager web container and server container to use Floodlight tags. This article assumes that you already have a server container created.
Send data from the web container to the server container.
All measurement for Ads products in a server container relies on the Google Analytics: GA4 Config tag in your web container to send data.
- Configure a Google Analytics: GA4 Configuration tag
- Set up a trigger for the configuration tag. The built-in All pages trigger is recommended for most cases.
Set up Google Analytics: GA4 client
Follow these instructions to set up your Google Analytics: GA4 client. If you already have a Google Analytics: GA4 client configured in your server container, you can skip this step.
Set up the Conversion Linker server-side tag
If you already have a Conversion Linker tag configured in your server container, you can skip this step.
From your server container workspace, select Tags on the left side of the page.
- Click New
Select the Conversion Linker tag type
Set up the trigger that will cause the Conversion Linker server-side tag to fire.
In most cases, you should use the built-in All pages trigger for this tag.
Set up the Floodlight Counter tag in the server container
From your server container workspace, select Tags on the left side of the page
- Click New
- Select the Floodlight Counter tag type
- To gather the values required for tag configuration, open another browser
window and sign in to
Campaign Manager 360.
Click Advertisers, and then click the name of the advertiser. Enter
these values in your new Tag Manager Floodlight Counter tag:
- Advertiser ID: The Advertiser ID will appear on the advertiser details
page just below the advertiser's name. This value is also found as the
src=in a generated Floodlight tag snippet.
- Group Tag String: In the Activity table, identify the activity you
want to work with and find the group tag string listed in a column to
the right. This is also found as the value of
type=in a generated Floodlight tag snippet.
- Activity Tag String: In the Activity table, identify the activity you
want to work with and find the activity tag string listed in a column
to the right. This is also found as the value of
cat=in a generated Floodlight tag snippet.
- Advertiser ID: The Advertiser ID will appear on the advertiser details page just below the advertiser's name. This value is also found as the value of
- Set the desired Counting Method:
- Standard: Counts every conversion.
- Unique: Counts the first conversion for each unique user during each 24-hour day, from midnight to midnight, Eastern Time (US).
- Per session: Counts one conversion per user per session. Session length is set by the site where the Floodlight tag is deployed.
- Open the Choose a trigger window.
- Select a desired trigger, such as All Pages.
- Enter a tag name and click Save.
Set up the Floodlight Sales tag in the server container
Setup steps for the Sales tag are the same as the steps for the Floodlight Counter tag apart from the step 2:
- Select the Floodlight Sales tag type
Order ID (Transaction ID), Revenue (Value) are automatically read from the corresponding ecommerce field.
Validate your implementation
Once you start sending data with the server container, you can check to see if it’s working properly by following these steps:
- Select Preview from the server container homepage.
- Click Tags. This will show the tags that have fired and can be used to validate whether the Ads Conversion Remarketing tag has fired.
- Click Errors. It is important to check the Errors section as well, since this will surface any errors that occurred during the transmission of data to the server container.