Testing Your New Tag

Quick overview of how to test the newly created Tag

Testing before submitting

It is highly recommend that before you submit your changes, it’s probably a good idea to test what you’ve created and make sure that everything is behaving as expected.

Enter Preview Mode - Google Tag Manager provides you the ability to test your tags, triggers and variables by loading your unpublished container, locally, within your browser. 

Once we do, Tag Manager will ask us to provide a URL when our container is installed and load an instance of that page with our current Tag Manager setup injected into the page.

Once we do this, Tag assistant will open - now we will see a summary on the left hand side that tracks all the interactions as they take place, and in the main window you will see a list of all your tags. On top, those that have fired, and below those that have yet to be triggered.

If we navigate to our page that GTM opened up for us and begin to scroll down the page, we should start to see Scroll Depth Events appearing in the Summary as we hit the thresholds we defined (10%, 25%, 50%, 75%, 90%).

Note: If you click on one of those Scroll Depth Events you will be able to examine that particular interaction more closely. By default, the “Tags” tab will display all the tags that fired when that interaction occurred



Test if data is being ingested by Funnelytics


In order to check and see that the Tag is sending data to Funnelytics, we need to go to the instance of your site that Tag Manager opened for you and open up the dev tools in your browser.
Once the dev tools are open, select the Network tabs and in the filters text box, enter the work “trigger”


Now as you scroll through the page, you should see a list of trigger event appearing in the network activity pane, each with a status of 200

200 is optimal - If you do see something other than 200, or you want to investigate what data is being sent to Funnelytics, click on one of the triggers and select the “payload” tab.

Important: If you do see that your trigger has failed, this is the first place your going to want to look to check for any unusual characters in the name or attributes.



Something missing?

if something is missing in the documentation or if you found some part confusing, please reach out to support team, with your suggestions for improvement.

We love hearing from you!