403 Error and Uncaught TypeError

  • I’m trying to resolve a couple of errors that I’m seeing in Chrome DevTools Console while using Quantcast Choice.

    The first is an Uncaught TypeError with the cmp.js file, which returns the following:

    TypeError: n is not a function
    at e.apiCall (cmp2.js:1)
    at new e (cmp2.js:1)
    at Module.<anonymous> (cmp2.js:1)
    at n (cmp2.js:1)
    at Object.<anonymous> (cmp2.js:1)
    at n (cmp2.js:1)
    at cmp2.js:1
    at cmp2.js:1

    The second is a “Failed to load resource: the server responded with a status of 403 ()” error for the the following:
    https://quantcast.mgr.consensu.org/choice/1mk94hmLDvjYg/www.boroguide.co.uk/.well-known/noniab-vendorlist.json?timestamp=1610656531509

    I’ve searched through the forums and the Quantcast Help Centre to find out what I’ve done wrong – but none of the suggestions have so far resolved the issue. What am I missing?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • This problem has now been fixed.

    I am getting a similar error.

    I tested my site in incognito and consent is being shown every single time. I am not ready to show ads anyway, but I want to be compliant.

    You can't use publisher legal basis 
on global consent scope.
e @ cmp2ui-en.js:2
quantcast.mgr.consensu.org/choice/
Q29c-SzLmxusA/
au-ti.com/
.well-known/noniab-vendorlist.json?
timestamp=1611063015203:1 
Failed to load resource: the server 
responded with a status of 403 ()
cmp2.js:1 the cookies was saved successfully

    I had an error with my site that in the QC CMP dashboard my site was displaying as www.au-ti.com when in fact it is au-ti.com. Remove the www. and it is now being directed to the correct site. Same problem would occur if your site is registered with a www. prefix and you had it registered in your QC CMP dashboard as a non-www.

    • This reply was modified 3 years, 10 months ago by autimedia.
    • This reply was modified 3 years, 10 months ago by autimedia.
    • This reply was modified 3 years, 10 months ago by autimedia.
    Thread Starter boroguide

    (@boroguide)

    Yeah, I thought that was part of my issue – but the property in my display is showing www as it should be.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘403 Error and Uncaught TypeError’ is closed to new replies.