Web Companion shows OK status but does not show in Network Call

[jmm42837]

I created a Tag before a week and everything was fine on Dev and QA. Then swithed off the tag. Now after a week, when I turned back on so that I can push it to prod, I see OK status in Web Companion but do not see in the network call. (Before a week, web companion showed ok status and even netowork call showed the tag firing)

Any insight?

[mitchellt]

Personally, I hate it when this happens, @jmm42837!  Be sure you have the tag enabled for the environment you are testing. Use the scan tool to make sure tag templates are up to date. And perhaps try publishing again.

[davidcreason]

@jmm42837 When you say there was a network call, are you referring to the actual pixel showing as loaded or the utag.x.js file has loaded? Web Companion can only check that the utag.x.js file has successfully loaded, but does not verify the pixel request was made. 

[mvenkatesan]

Its a basics, @jmm42837, but still make sure that you have not used any filter in the network tab.

[adrian_browning · Accepted solution]

@jmm42837

There is a known scenario that will cause the Web Companion to show this value incorrectly, make sure you are on the latest version and revision, to avoid this.

If you wanted to be 100% sure, I would do a Save As, and then query that. Also, as @davidcreason commented, OK means that from utags perspective the tag was loaded and the send command was executed without error.

Adrian

[jmm42837]

Yes, I was not on the latest version of the Tag. Thank You all for the help.