Verifying Microsoft Edge

Testing in Microsoft EDGE

1. Open a page that is thought to be tagged with the Webtrends SharePoint Tag, such as the Home page of a site collection.

2. Open the Developer Tools. This can be done by:
   a. Pressing F12 on the keyboard
   b. Clicking the ... icon in the upper right of the browser, then clicking Developer Tools from the menu.
   

   Note

   You can pop the Developer Tools window into its own window by clicking the Unpin icon in the upper right of the window
   

3. Click on the Debugger tab near the middle of the list of tabs the top.
   

4. Click the small grey folder icon on the upper left of the screen and search for webtrends to display the list of loaded Webtrends files, or scroll down to the w’s in the list that appears.
   

5. Verify you see the Webtrends JavaScript files as noted in the Webtrends JavaScript Files section.

6. Click on the Network tab near the middle of the list of tabs the top.
   

7. Click on the green Play button to Enable network traffic capturing, or by pressing F5 on the keyboard.

8. Return to the browser window.

9. Refresh the page or press F5 on the keyboard.

10. Scroll down through the list of entries and search for a row heading to statse.webtrendslive.com that also has dcs.gif in the URL.
    

    Note:

    If you see a row with sdc.yourdomain.com and wtid.js in the URL, but do not see a row with dcs.gif, you may have the DCSID value set incorrectly. This causes the SDC server to reject the request, and the tag will not continue.

    The DCSID should appear in the URL similar to below, starting with dcs and consisting of randomized alpha-numeric characters, followed by an underscore, and four additional alpha-numeric characters.

    sdc.yourdomain.com/dcsxxxxxxxxxxxxxxxxxxxxxx_xxxx/dcs.gif

    There should be no leading or trailing text or whitespace in the value.

11. Select the dcs.gif row.

12. Click the Parameters in the right side panel.

13. Review the list of parameters and their data on interactions to verify the data sent to Webtrends.
    

14. To verify link tracking, return to the Developer Tools > Network window.

15. Click the X icon to clear all entries
    

16. Return to the browser window.

17. Find a link you wish to test.
    a. If Collect all links clicks? (app method), or the allClick option in the webtrends.load.js file (manual or WSP method) are true, clicks to any <a> link on the page should trigger a hit.
    b. If these options are not enabled, only some links will be expected to pass data. Navigate to a document library and use adocument link orHover Card orRibbon link to test.

18. Left click on the desired link, but do not let go of the mouse button. Drag the mouse slightly, then let go of the mouse button.
    a. This should cause the link click hit to be sent, but the browser will not move to the next page. This allows you to review the data while still staying on the same page. Multiple links can be quickly tested using this technique.

    Note:

    There is also a Clear entries on navigate button in the top of the Network tab that will keep or discard all the traffic when moving to another page.

    Turn it off, so that if you fully click on a link and move to the next page the link click hit will not be lost in the process and it should appear as the next line in the list.

    

19. Review the data in the link click hit by repeating the last few steps.