One of the advantages of this method is the use of the Call Stack, reported through the Developer Tools in the Sources tab, to inspect the origin of the tracking call. Learn more about setting breakpoints in Chrome Developer Tools.
This is the data that you have to work with in extensions, load rules and mappings. Type a and click Enter to add a watch expression for this variable.Įxpand the object that is contained in parameter a to show the data was passed to the tracking call. Click the + sign to add a watch expression. In the right-hand side of the developer tool there is a section called ”Watch Expression”. When a tracking call is made, one of the breakpoints stops the action in order to inspect the code. Return to the main window and perform an action to invoke one of the tracking calls.
ISWIFT VIEW ENTIRE STACK TRACE CODE
Unminify (pretty print) the code by clicking the curly braces at the bottom left of the window.įind the line with return ack( and click the line number to set a breakpoint: In Chrome Developer Tools, go to Sources and open utag.js. To use Chrome developer tools to set a breakpoint: Breakpointsįor more in-depth debugging, it is useful to set breakpoints in utag.js to pause the code when calls tracking calls are made. This allows you to review the data being passed as well as examine the stack trace to see where the call originated. The following example demonstrates how this looks in the console after an event is tracked:Ĭlick the line under trigger:view or trigger:link to expand and collapse the event data object. Inspect the console output for: trigger: view or trigger: link Once debug mode is enabled, when you trigger actions on the page that are tracked, debug logs appear in the console. This cookie turns on debug mode within utag.js, which generates useful output to the console.
0 kommentar(er)
