cworeo.blogg.se - Network inspector not showing google analytics events

NETWORK INSPECTOR NOT SHOWING GOOGLE ANALYTICS EVENTS UPDATE
NETWORK INSPECTOR NOT SHOWING GOOGLE ANALYTICS EVENTS CODE

You can use RegEx to filter by account or by a specific property e.g. When you want to focus on one, it’s sometimes difficult to narrow down the activity. Sometimes sites have multiple properties receiving hits.

To exclude hits with the category “click”, use “ec:click”.

To exclude all “gtm” events, use “^gtm”.

For pushes, the key “event” is evaluated and for hits, the event category “ec” is evaluated. Use RegEx to filter events pushed to the dataLayer and hits. In addition, we have a couple of filters that use RegEx to exclude the noise. Hiding timing and internal directs are simple ways to reduce the data. Reducing the firehose of data can help focus on the important information.

NETWORK INSPECTOR NOT SHOWING GOOGLE ANALYTICS EVENTS CODE

This can be very helpful in debugging code on sites with code-related issues and you need to be there before GTM is loaded. This option allows you to add code to the page before any other code runs. Clicking on the badge will show or hide the badge: You will be able to tell if the container is inserted if the badge is visible in the top left-hand corner of the page.

The RegEx option can help ensure you only insert the container into the right pages or it can help you use the same container across multiple domains. Selecting this option will add the specified GTM container to any pages that match the Host.

This option will push an object into the dataLayer immediately upon loading the Inspector, usually within a couple of milliseconds of the page starting to load. When selected, these actions will happen very early in the page load process. Sometimes we need to add data, a container, or code to a page.

Is the hit successfully delivered to Google Analytics?.

Is the dataLayer initialized correctly?.

Since we all want a properly initialized dataLayer and well-formed dataLayer pushes, (who doesn’t?), the dataLayer Inspector+ evaluates multiple aspects of the process: You can expand the network hit to see all the data sent to GA by clicking on the arrow icon ►. The output will include the target property, the GTM container (if sent by GTM), timing, and the details of the network hit. Typically a pageview, followed by events. BTW, you can hide the timing with advanced options. Included in the group are the pushed object, errors and warnings (if applicable), and timing information. Click on the arrow icon ► to expand the details and the Object key/value pairs. Events are the most common and are labeled with event. Monitor dataLayer pushes and hits Inspecting the dataĮach dataLayer push is logged as a collapsed group to the console. Expanding the Advance Options will give you the ability to turn back time, and perform other magic. Once added, you will be able to start inspecting the dataLayer by clicking on the extension icon in your address bar. Using the Analytics Pros dataLayer Inspector+įirst, add the extension to Chrome.

Or turn the clock back to simpler times (i.e.

Add code to the page before anything else happens.

Work with GTM containers not deployed on a site.

In addition to the diagnostics we added a set of features to help you significantly speed up implementations.

What is pushed to the Google Tag Manager dataLayer?.

Our add-on makes it significantly easier to debug, monitor and see detailed information without having to constantly rotate from the page to the page code and finally the developer console.

NETWORK INSPECTOR NOT SHOWING GOOGLE ANALYTICS EVENTS UPDATE

We just released a major update to our dataLayer inspector for Google Tag Manager and Google Analytics.