After including your tag, you should see (in the Network tab of Developer Tools in Chrome) a fetch to
https://secure.quantserve.com/quant.js
followed by one or more requests to the quantserve pixel which will be URLs starting with
https://pixel.quantserve.com/pixel
If no pixel requests are being made, one reason may be an improperly configured Consent Management Provider (CMP) that isn't making the callbacks in response to the "getVendorConsents" command.
To diagnose this issue, run the following command in the Developer Tools Console (which can be entered by pressing F12 in the webpage):
__cmp('getVendorConsents',[11],function(){console.log('arguments=',arguments)})
You should immediately see the "> undefined" return value, which can be ignored. If you instead see "__cmp is not defined" it means there is no CMP installed on the page and so is unlikely the cause. Otherwise, if you don't see a line like:
arguments= ▶Arguments(2) [{…}, true, callee: ƒ, Symbol(Symbol.iterator): ƒ]
it means the CMP is not invoking the callback for the getVendorConsents command which will prevent quant.js from making the pixel request (as it is unable to retrieve the user's consent choices). If the CMP is visible, you'll need to make a consent selection in the web page and close/save before the above line will appear.
Another confirmation step is to run the following "ping" command in the Console:
__cmp('ping',null,function(){console.log('arguments=',arguments)})
and click on the ▶ next to "Arguments(2)" in the result. If you see on the "0:" line that "cmpLoaded: false" this is indicative of a frequently-encountered CMP failure.
If you have determined that it is the CMP causing the pixel request to not be made, consult your CMP documentation to properly initialize and configure your CMP, or contact your CMP provider for a solution to the problem. Quantcast Choice is available as a TCF-compliant consent manager as well that is easy-to-integrate with and is tested to work properly with our tag.