Trigger the event you are tracking via ga event tracking and then look at the real time events report to check whether the event data (category,action,label) is being passed to google analytics. #2 the second way to see the real time firing of events is through ‘ google developers console ’.. Since most of the time you don't have a reference to the tracker object, using the ga() command queue is the recommended way to send tracker data to google analytics. using the ga() command queue the signature for adding a send command to the ga() command queue is as follows:. Google analytics is one of the best data-driven marketing tools available today. managed by the world s largest search engine, it provides you with detailed, day-by-day analysis of how users are interacting with your website..
Ga.js is a legacy library. if you are starting a new implementation, we recommend you use the latest version of this library, analytics.js.for existing implementations, learn how to migrate from ga.js to analytics.js. this document assumes familiarity with google analytics tracking code (gatc) configuration.. When the send command is executed, the title and location fields stored on the tracker get sent, and google analytics uses those values to show you which pages your users visited. the default tracker does not set the page field, but if you set it manually, that value gets used as the page path in reports, overriding the location field's value.. The ga command queue reference the ga() command queue provides an interface for doing almost everything you need to do with the analytics.js library. the javascript tracking snippet defines the initial ga() command queue function, so it can be used even before the analytics.js library is fully loaded..