Configure your Google tag settings

To access your Google tag settings from your Google Ads account:

1. In your Google Ads account, click the Tools icon .
2. Click Data Manager.
3. Under “Google tag”, click Manage.

1. In your Google Analytics account, go to the Admin screen.
2. In Data Streams, click on a stream to see details.
   Result: Your screen should show you the Google Analytics settings and the Google tag settings.
   

Note: To see Google tag IDs in Google Tag Manager, you need to manage a Google Ads, Analytics or Google tag in a container.

1. In your Google Tag Manager account, click on the Google tags tab to see Google tags you've previously set up.
   
2. Click on the tag name to edit the Google tag settings.

Select which types of events your Google tag should automatically detect for measurement in associated destinations. By default, all event types are turned on.

If you turn off automatic event detection, no products or accounts that use this Google tag will receive associated data. You may want to consider turning off collection of these events in your destination instead.

By default, all event types are turned on. Click the switch to turn the following event types off:

• Page views: Detect a page view event each time a page loads. You can't disable this event type.
• Page views on browser history change: Detect a page view event each time the website changes the browser history state. This setting is useful for detecting page views in single-page applications.
• Scrolls: Detect scroll events each time a visitor gets to the bottom of the page.
• Outbound clicks: Detect an outbound click event each time a visitor clicks a link that leads them away from your domain(s). By default, outbound click events will occur for all links leading away from the current domain. Links to domains configured for cross-domain measurement (in the “Configure your domains” setting) won't trigger outbound click events.
• Form interactions: Detect a form interaction or form submission event each time a visitor interacts with a form on your site.
• Video engagement: Detect video play, video progress, and video complete events as visitors view embedded videos on your site. By default, video events will be automatically detected for YouTube videos embedded in your site with JS API support enabled.
• File downloads: Detect a file download event each time a link is clicked with a common document, compressed file, application, video, or audio extension.

Specify all of your domains that use this tag. This list enables cross-domain measurement and further defines which links on your site don't trigger outbound click events when using automatic event detection.

1. If you use the same Google tag across domains, they're automatically detected and show up in the "Recommendations" section. To accept a recommendation, click Add.
   To manually add a domain, click Add condition under "Include domains that match the following conditions":
   • Choose a match type.
   • Under "Domain", enter the identifier for the domain you want to match (for example, example.com).
   • Add each domain you want to include in cross-domain measurement.
2. When you’ve specified all the domains that use this tag, click Save.

The changes you make here could affect other Google tags loaded on the same page.

Verify that cross-domain measurement is working properly

Cross-domain measurement works by appending parameters to the URLs on your website. In rare cases, your web server might run into an error, such as returning a 5xx error response code or failing to start a download.

To verify cross-domain measurement works:

1. Open a page of your site that contains a link or a form that points to a domain you configured for cross-domain measurement.
2. Click the link or submit the form to navigate to the destination domain.
3. Verify that the page loads correctly.
4. Verify that the URL in the destination domain contains the linker parameter _gl. For example: https://www.example.com/?_gl=1*abcde5*.
5. If your website provides any downloads, navigate to a page with the linking parameter in the URL and start a download. Verify that the download starts successfully.

If you encounter an error, try Troubleshooting cross-domain measurement.

User-provided data helps improve measurement and give you more insights with data that people provide to your website. Google will only use the data you share to provide you services, including technical support. Google won't share your data with others.

Destination product terms

No data will be collected by destination products if that data is disallowed by that product’s Terms of Service or if the terms required for collecting data from this feature aren’t accepted.

• Google Ads: Google Ads Data Processing Terms
• Google Analytics: Google Analytics Data Processing Terms
• Campaign Manager 360: How Google uses Google Marketing Platform advertising product data

Configuration

Define IP addresses whose traffic should be marked with a custom traffic type identifier. Incoming traffic from matching IP addresses will have a traffic_type parameter appended with the selected value.

1. Click Create.
2. In the top right corner, select the pencil icon to edit the configuration.
3. In the “Rule name” section, give your rule a descriptive name.
4. In the “traffic_type” section, choose the name of the traffic_type parameter. The default value is ’internal’.
5. In the “IP address” section, select your match type and enter a value. If you don’t know your IP address, click What’s my IP address?. Matching can be done on either IPv4 or IPv6 addresses. Ranges of IP addresses can be specified using CIDR notation, such as 192.0.2.0/24 or 2001:db8::/32. Learn more about CIDR notation.
6. Use distinct values to help you differentiate and filter different sets of traffic.
7. Click Add conditions.
8. Click Create.

Specify domains whose traffic shouldn't be considered to be referrals. This feature will append the ignore_referrer parameter to events on pages where the traffic source matches the specified domains.

1. Select to ignore referrals that match any of the following conditions as traffic sources. You can select a match type that:
   1. Contains
   2. Begins with
   3. Ends with
   4. Exactly matches
   5. Matches RegEx
2. Click Add conditions.
3. Click Create.

Products like Google Analytics 4 that receive data from the Google tag use sessions to measure periods of user activity on websites where the tag is installed. Use this feature to change how long sessions should last by adjusting how long it takes before sessions expire due to inactivity or become engaged sessions.

1. Adjust session timeout by selecting the hours and minutes. A session is initiated when a webpage is opened. A session ends after a period of inactivity on the part of the user. The default timeout is 30 minutes but can be adjusted here.
2. Adjust timer for engaged sessions by selecting the number of seconds. A session becomes an “engaged session“ if it lasts longer than a certain amount of time. The default threshold for engagement time is 10 seconds but can be adjusted here. Learn more About Analytics sessions.
3. Click Save.

Change how long cookies last and how they're updated. You can override your Google first-party cookie settings. Learn more about cookies and user identification.

Google tags use first-party cookies for various purposes. These cookies have default expiration and update settings, but you can customize these settings by overriding them.

1. Click the checkbox to override the default expiration and update settings of cookies used for analytics purposes.
2. Set how long before analytics cookies expire. Cookie expiration time will be the current time when the cookie is set or updated plus the value of this field. Learn more about cookie expiration.
3. Under “Cookie update” choose:
   1. Set cookie expiration time relative to the most recent visit: By default, each time a user visits your site, your Google tags update the expiration date of associated cookies, extending the cookie lifetime relative to the user's most recent visit.
   2. Set cookie expiration time relative to first visit: You can optionally set your cookie expiration time relative to your users’ first visit, in which case the expiration is set once and never updated. Learn more about cookie update.
4. Click Save.

The 'Set consent mode override' setting overrides any default consent settings in your website code and instead sets the default to 'denied' for all the regions you choose. After a consent signal is received, the consent setting is updated to the end user's consent choice.

For example, assume you set the default consent to 'denied' in your website code only for France, and then set the consent mode override to 'denied' only for Germany. The setting will override all the default commands set in your website code and only set the default command to 'denied' for Germany.

The setting is useful when setting up consent mode via one of Google’s integrated CMP partners to ensure consent is defaulted to denied in regions where you need this behavior. It can also help if you're having difficulty getting your existing default consent commands to take effect before your Google tags load, such as in cases where your website builder or content management platform don't allow you to specify the order in which plugins are loaded relative to one another. In this case, this setting can be used to provide certainty about the default settings that apply to the tag you're configuring.

To use the setting, you must set Manage default consent settings to "No. Do not automatically mark this data as consented."

Asking users for their consent to collect data is an integral part of measurement. Learn more about user consent management.

You can decide which Google services can receive consented end-user data. For optimal measurement, ensure that all Google services receive consented end-user data. You can review which Google services are receiving data from the EEA within this section.

If your business requires you to restrict data sharing across Google services, choose Select Google services. Select all Google services that are allowed to receive user-consented data for measurement and personalization.

Ensure that you declare in your consent banner which Google services receive user-consented data.