To check the Google tags implemented on a webpage, you can follow these steps:
Dev Tool > Network > Payload > "collect"
Please note that some tags may load asynchronously or be triggered by specific events, so you may need to interact with the page (e.g., click a button, submit a form) to trigger the loading of certain tags.
Inspecting the network requests in the browser's developer tools allows you to see the requests made by the webpage, including those related to Google tags. By examining the request parameters, you can gain insights into the tags implemented on the page and their configurations.
Keep in mind that this method assumes that the tags are implemented directly on the webpage and not loaded dynamically or via an iframe from another source. In some cases, the tags may be managed through Google Tag Manager, in which case you might not see the tag requests directly in the network tab but rather within the Tag Manager container.
+ How to Decipher Payload in Network (w/ e.g.)
++Another e.g.
v: 1: This indicates the version of the Google Analytics Measurement Protocol being used.
· a: 2123071514: This is the anonymized ID of the user or client.
· t: pageview: This indicates that it's a pageview hit type, representing a view of a particular page.
· ni: 0: This specifies whether the hit is non-interactive (0) or interactive (1). Non-interactive hits don't affect bounce rate calculations.
· dl: https%3A%2F%2Fwww.******.com%************%2F: This is the URL of the page that was viewed. It's URL-encoded, and the actual decoded URL is "*****".
· dp: %2************%2F: This is the document path or page path of the viewed page. It's URL-encoded, and the actual decoded path is "/************/".
· ul: ko-kr: This indicates the user's language preference, which is set to Korean (Korea).
· de: UTF-8: This specifies the character encoding used for the page.
· dt: %E3%83%9B**************%E3%80%91: This is the document title of the page. It's URL-encoded, and the actual decoded title is "********".
· sd: 24-bit: This indicates the color depth of the user's screen.
· sr: 1055x882: This specifies the screen resolution of the user's device.
· vp: 1055x882: This indicates the viewport size or the visible area of the page.
· je: 0: This specifies whether JavaScript is enabled (0 for disabled, 1 for enabled).
· _u: SCCACUALBAAAACANK~: This could be a unique user identifier or session identifier.
· jid, gjid: These seem to be placeholders or empty values for job ID and group job ID.
· cid: 884654338.1687232195: This is the client ID, a unique identifier for the user.
· tid: UA-162****-**: This is the Google Analytics tracking ID associated with the website or application.
· gtm: 45He36e2n71T*****: This indicates the Google Tag Manager ID or container ID used for managing tags and analytics on the website.
· pa: detail: This indicates the type of page or the specific page category, in this case, "detail."
· pr1br: Aa: This represents a product-related variable or parameter, indicating the brand of the product as " Aa."
· pr1id: 8400: This represents a product-related variable or parameter, indicating the ID of the product as "8400."
· pr1nm: 8400: This represents a product-related variable or parameter, indicating the name of the product as "8400."
· pr1cd11, pr1cd12, pr1cd13, pr1cd14, pr1cd15, pr1cd16, pr1cd17, pr1cd20: These represent product-related custom dimensions or variables capturing specific values related to the product.
· pr1cm1, pr1cm2, pr1cm3, pr1cm4: These represent product-related custom metrics capturing specific values related to the product.
Note: without additional context or documentation specific to the implementation of the tracking system or analytics tool, it can be challenging to decipher the exact meaning or purpose of each custom dimension or variable in the payload.
Task 2. Create a "like" button event for my website (0) | 2023.06.16 |
---|---|
[dataLayer] How to Configure a dataLayer (e.g.) (1) | 2023.06.13 |