It is therefore worth configuring the events that will be sent to GA from scratch, so that they are consistent with the recommend naming and the new data structure. This is a great opportunity to organize data, conventions in naming and eliminate events that we have collect in UA so far, and we did not really ne them The debug_mode parameter Google Analytics offers us the ability to verify the collection of events using the DebugView module. We can enable it: using the Google Analytics Debugger plugin , enabling Google Tag Manager preview mode, by sending the debug_mode parameter along with the event.
In this module you will see a very
If you use the third method and your configuration tag in GTM looks like this: GA configuration Then GA will display all events of each client in DebugView. What will it cause? Large number of devices: GA – DebugView This will make the debugging process much more difficult for you, making it difficult for you to find your device. How to prevent it? You can create a Greece Phone Number List custom GTM variable that returns true or undefin and use it as the value for this parameter. Another solution would be to use the other two methods to enable Debug View.
So Remember not to overdo
Creating events We already know that when we assign parameters to a given event, we must also register them in the GA Configuration section. Some GA users may think that we ne to add events in a similar way. For this, they use the Create an event function , available in the Events section : event creation As a result, they will actually see duplicate events in the reports: report – duplicate items it and configure events only in GTM Too many unique custom definitions When creating events, it is worth giving them additional parameters, thanks to which Bulk Lead we will collect more information about our customers.