What is a configuration settings variable?
You can reuse configuration settings across several Google tags using a Google tag: Configuration settingsvariable. For example, let's say you publish your website in multiple languages, and want to segment your audience according to the language they read in. You can create a configuration variable with a language
parameter and use it across your Google tags, instead of manually updating each tag.
How to set up a configuration settings variable
To create a new configuration settings variable:
- Open Google Tag Manager
- In your workspace, open the Variablesmenu on the left.
- Create a Newuser-defined variable.
- In Variable Configuration,select the Google tag: Configuration settingsvariable.
- Add the parameters you want to reuse. You can find a table of pre-defined parameters below. If none of these fit your needs, you can always create a custom parameter. Just type a name of your choice in the Namefield.
- Name your variable and Save.
Reuse settings in a Google tag
- In your workspace, open the Tagsmenu on the left.
- Select a Google tagyou want to apply a settings variable to.
- Reuse settings:
- To reuse Configuration settings, select a Google tag: Configuration settingsvariable from the dropdown list.
- To reuse Shared event settings, select a Google tag: Event settingsvariable from the dropdown list.
- To see what parameters were inherited from the settings variable, click Show inherited settings.
- To edit an inherited parameter for the Google tag only, click on Edit.
- To revert an edited inherited parameter, click Reset.
- Savethe tag and Publishthe container.
Valid parameters for configurations settings
The following table lists pre-defined parameters and which products you can use them with (marked by an x).
false
&gclid
, &dclid
, &wbraid
, etc.) from all requests when consent is denied.true
false
to disable advertising personalization features.true
true
. To disable all advertising features, set allow_google_signals
to false
.true
campaign_content
to differentiate ads or links that point to the same URL.Note:Setting this value will override the
utm_content
query parameter.campaign_id
to identify a specific campaign.Note:Setting this value will override the
utm_id
query parameter.campaign_medium
to identify a medium such as email or cost-per-click.Note:Setting this value will override the
utm_medium
query parameter.campaign_name
to identify a specific product promotion or strategic campaign.Note:Setting this value will override the
utm_name
query parameter.campaign_source
to identify a search engine, newsletter name, or other source.Note:Setting this value will override the
utm_source
query parameter.campaign_term
to note the keywords for this ad.Note:Setting this value will override the
utm_term
query parameter.true
false
, you can opt-out of conversion linking.'auto'
To set the cookie without specifying a domain, set to
'none'
.Set to
'auto'
(the default value) to set the cookie to the top level domain plus one subdomain (eTLD +1). For example if cookie_domain
is set to 'auto'
https://example.com
would use example.com
for the domain, and https://subdomain.example.com
would also use example.com
for the domain.63072000
cookie_expires
field. This means that if you use the default value time of two years ( 63072000
seconds), and a user visits your site every month, their cookie will never expire. If you set the cookie_expires
time to 0 (zero) seconds, the cookie turns into a session based cookie and expires once the current browser session ends. Caution:If you set the cookie to expire too quickly, you will inflate your user count and decrease the quality of your measurement.'/'
_gcl_aw
to <your-prefix>_aw.
true
cookie_update
is set to true
: - GA4 and Merchant Center update cookies on each page load. This will update the cookie expiration to be set relative to the most recent visit to the site. For example, if cookie expiration is set to one week, and a user visits using the same browser every five days, the cookie expiration will be updated on each visit and will effectively never expire.
- Ads and Floodlight update cookies with the original expiration date, so it is still relevant to the first visit.
false
, cookies are not updated on each page load. This has the effect of cookie expiration being relative to the first time a user visited the site. send_to
parameter in an event tag.false
true
to indicate to Analytics that the referrer shouldn't be displayed as a traffic source. Learn when to use this field
./
).This parameter allows you to override the automatic value.true
Set to false
to prevent the default snippet from sending a page_view
event.
Note:This won’t affect enhanced measurement
from sending page_view
events based on the page’s history changes.
window.screen
value.