Quantcast cause CORS error

  • arthuroadam

    (@arthuroadam)


    5 years, 8 months ago

    Hi!

    We experience other problem with Quantcast choice. After the user accept the consent, no ads loading and we got this error:

    Access to XMLHttpRequest at ‘https://securepubads.g.doubleclick.net/gampad/ads?…’ from origin ‘siteurl’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.

    You could check this page: https://minimatine.hu/top-10-kirandulas-gyerekekkel-a-legjobb-valogatasok-a-minimatinetol/

    If we delete the quantcast choice from the site, the ads are appearing.
    What could cause this problem?

    Thanks.
    Best regards,
    Adam

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Ryan

    (@rbaronqc)

    5 years, 8 months ago

    @arthuroadam I dont know the issue off hand, but flagged it with a few people and will let you know once I have more information.

    Thread Starter arthuroadam

    (@arthuroadam)

    5 years, 8 months ago

    Thanks, we are waiting for it!

    Plugin Contributor Ryan

    (@rbaronqc)

    5 years, 8 months ago

    @arthuroadam I may have found the issue here. There are certain consent configurations that Google does NOT allow. I believe you currently have consent configuration that violates what Google allows, hence no ads.

    I believe you have special feature 2 enabled (which google does not allow). That is why when you enable the CMP, your ads do not work, but when you disable the ads work. “Special Feature 2 refers to actively scanning device characteristics for identification.”

    If you set the CMP to the default configuration (or disable special purpose 2) and deploy that CMP do you then see ads on the site?

    Please see the article here for more details about allowed google configurations.
    See the article here http://www.quantcast.com/blog/quantcast-supports-google-tcf-v2-integration/.

    From Article:
    Active Fingerprinting is Not Allowed
    Google will not work with vendors who register for Special Feature 2 and have an opt-in for it. Special Feature 2 refers to actively scanning device characteristics for identification.

    • This reply was modified 5 years, 8 months ago by Ryan.
    Plugin Contributor Ryan

    (@rbaronqc)

    5 years, 8 months ago

    @arthuroadam In the requested config file here https://quantcast.mgr.consensu.org/choice/E6msG-gSKtB9C/minimatine.hu/choice.js I can see vendorSpecialFeaturesIds and publisherSpecialFeaturesIds both have ‘2’ enabled. It is my understanding that google is only looking at ‘vendorSpecialFeaturesIds’ and not ‘publisherSpecialFeaturesIds’ so you would be ok to have ‘publisherSpecialFeaturesIds’ [1,2] but this should be tested to verify. If you disable special purpose 2 at the vendor level and you still don’t see ads try disabling it at the publisher level as well. If that still doesnt work check out the other configuration options required by google here http://www.quantcast.com/blog/quantcast-supports-google-tcf-v2-integration/ and here https://help.quantcast.com/hc/en-us/articles/360052427553

    Thread Starter arthuroadam

    (@arthuroadam)

    5 years, 7 months ago

    @rbaronqc Thanks for the help. I did an other registration for minimatine and now it’s working, however special purposes are on. But something with consent options cause the problem
    One more question about consent configuration: in your help section, there is a recommended stack for consents, but if I register a new site, I don’t have that option.
    Why it isn’t available?

    Thanks.

    Thread Starter arthuroadam

    (@arthuroadam)

    5 years, 7 months ago

    @rbaronqc
    Hi!

    Now, everything working fine, if I give the consent, but if I don’t give it, the cors problem is back. Why I don’t get non-personalized ads?
    What purposes cause the problem?

    “Customised purposes configuration:

    Purpose 1: Store and/or access information on a device
    Purpose 2: Select basic ads
    Purpose 3: Create a personalised ads profile
    Purpose 4: Select personalised ads
    Purpose 5: Create a personalised content profile
    Purpose 6: Select personalised content
    Purpose 7: Measure ad performance
    Purpose 8: Measure content performance
    Purpose 9: Apply market research to generate audience insights
    Purpose 10: Develop and improve products”

    Thanks.
    Best regards,
    Adam

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

The topic ‘Quantcast cause CORS error’ is closed to new replies.