Troubleshoot with Tag Assistant - Tag Assistant Help (original) (raw)

If you use Google Tag Manager (GTM) to manage your conversion tags, you need to implement the Google tag in GTM for all ads products. The Google tag simplifies tag management and improves data accuracy. This is in addition to the Conversion Linker tag and Floodlight or Google Ads Conversion measurement tags. Learn more about using GTM to deploy Google Ads conversion tags.

Note: Google Tag Assistant and Tag Diagnostics will continue to show implementation warnings when an event is sent to any Google product without first firing the corresponding Google tag.

Tag Assistant is a troubleshooting tool that helps you verify the implementation and functionality of tags on your website. It lets you review the tags, events, and data on your website, export and import debug sessions, and share a debugging URL so others can debug for you.

When your website contains the Google tag, Tag Assistant adds tagged and untagged pages to the Tag coverage summary, so you have an overview of the overall tagging status of your site.

Before you begin

We recommend you install the Tag Assistant Chrome extension to enable these features:

• Detection of the Google tag inside an iframe.
• Debugging of pop-up windows or new tabs opened from the current window.
• The debug window opens in a new browser tab instead of a pop-up. This allows the user to manipulate the browser URL bar and can help facilitate debugging of referrer-based actions.
• Multiple windows can be debugged in the same debug session. Each window is marked with a symbol in the event tree so that they can be easily identified.

Note: The Tag Assistant Legacy and Tag Assistant Companion Chrome extensions are now combined into a unified extension that supports both sets of features.

If you’re using Tag Assistant Legacy, there’s no need to uninstall anything, as it will be updated to Tag Assistant. Tag Assistant Companion will be uninstalled automatically once the Tag Assistant extension is updated. The Tag Assistant Companion extension will still work, but will be deprecated in the coming months.

Connect Tag Assistant to your website

1. Go to Google Tag Assistant.
2. Click Add domain.
3. Enter the URL of the website you want to debug, starting with "https://" or "http://".
4. Click Connect.

When you connect Tag Assistant to your website, we add a debug parameter (_dbg) to the end of your URL. The parameter helps you view events in other debugging surfaces, such as Google Analytics' DebugView.

Disconnect Tag Assistant

1. Open the web browser tab that is active for debug mode.
2. In the debug window, click Stop Debugging or the X in the upper left corner.

Tag Assistant Chrome extension

The Tag Assistant browser extension helps you analyze the tags on your domain. It allows you to see a list of all the tags that have been implemented on that specific page.

Troubleshoot Tag

You can troubleshoot the tags on your site to verify their implementation and functionality. Troubleshooting can be used to view the hits sent, updates to the data layer, and any other errors.

1. Click on the Tag Assistant Chrome extension.
2. Click Troubleshoot tag, and it will navigate to tagassistant.google.com in a new tab and initiate a debug session.

What's next?

To resume an active or closed debug session, click the domain name from the Active Domains or History on the Tag Assistant homepage.

Debug information is not visible to your regular website visitors. The debug window will stay open and display debug information while you navigate within the same domain and as long as there is the Google tag on the page.

As you click through your website, we'll update Tag Assistant with information about your tags.

Fix connection issues

If the debug window does not connect to your page successfully, try some of these solutions:

• The URL you entered might not have the Google tag on the page. Try a different URL on your website where you expect to have the Google tag installed.
• The debug parameter added to the page URL may interfere with page behavior. To solve this, edit the domain that you enter for debug mode, and deselect Include debug signal in the URL.
• The Google tag script is loaded after the point when Tag Assistant tries to connect to the page. Click Retry to connect again.
• Your page is an AMP page. AMP is not currently supported by Tag Assistant.
• The page loads the Google tag in an iframe. iframe-loaded tag configurations can only be debugged when the Tag Assistant Chrome extension is also installed.
• Multiple browser redirects can prevent the debug window from loading.
• Ad blockers installed in your web browser may prevent the Google tag from running. Disable ad blockers for the pages you need to test.
• If you have the Tag Assistant Chrome extension installed, make sure the extension has permission to read and change site data for the pages you need to test.
• Consent management tools may block Google tags. Configure any consent management tools that you use to allow interaction with Google's consent API.

Troubleshooting steps

If the issue is still not resolved, you can also try some of these troubleshooting steps:

• The Google tag may be blocked by a browser extension. Try disabling browser extensions and retrying the connection.
• Check if the Google tag is loaded on the page. Make sure the Google tag is present on the page before you attempt to connect.
• Check if the Google tag is loading correctly. You can use the browser's developer tools to see if the Google tag is loaded correctly.
• Check if the Google tag is firing. You can use the browser's developer tools to see if the Google tag is firing.
• Make sure you're using the correct domain name. Double-check the domain name you're using to connect to the website.
• Make sure you're using the correct website URL. Double-check the website URL you're using to connect to the website.
• Check for any errors in the Google tag code. Make sure the Google tag code is correctly implemented.
• Check if the Google tag is being blocked by a firewall or proxy server. Make sure the Google tag is not being blocked by a firewall or proxy server.
• Check if the Google tag is being blocked by a content security policy (CSP). Make sure the Google tag is not being blocked by a CSP.