{"id":4836,"date":"2020-12-22T12:07:22","date_gmt":"2020-12-22T09:07:22","guid":{"rendered":"https:\/\/trackingchef.com\/?p=4836"},"modified":"2020-12-22T13:29:41","modified_gmt":"2020-12-22T10:29:41","slug":"debugging-gtm-with-integromat-google-sheets","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/google-tag-manager\/debugging-gtm-with-integromat-google-sheets\/","title":{"rendered":"Debugging GTM with Integromat & Google Sheets"},"content":{"rendered":"\n
One of the challenges when working with Google Tag Manager (GTM) is the gap between preview mode and actual deployment.<\/p>\n\n\n\n
Plenty of times, you deploy a tag with a certain configuration, and results show up entirely different. Sometimes this is due to the nature of edge cases that you didn’t think about or couldn’t simulate on your machine.<\/p>\n\n\n\n
One tactic I’ve found for tracing back the source of the issue is simply logging the tag fired and its variables. This is done by capturing all these in an HTTP POST webhook that logs these in a Google Sheets spreadsheet.<\/p>\n\n\n\n