Device: Mac 10.12.3
Browser: Chrome 73.0.3683.103
Target: at.js 1.7.1
Target Activity: uses Conversion goal measured by Click of Element (set within Goals & Settings)
Problem: With active test on click of selected element, Chrome blocks response (CORB)
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://mboxedge17.tt.omtrdc.net/m2/crocs/mbox/json?mbox=clicked-btn-x&mboxSession=b1268b31051b407ea... with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.
NOTE: I see the same issue when using getOffer/applyOffer.
joelc13866394 I did some trouble shooting and was able to confirm that engineering are aware of the CORB issue that is affecting chrome v73 and above. This issue affects both at.js 1.x click-tracking requests, as well as at.js 2.x display and click-tracking notifications.
I am checking with them on the ETA for the fix. Will post the same here once I get an update on the same.
That is correct this will not affect target metrics. Additionally since it's yellow that tells us it is a warning not a red error (show stopper)
If I did a good job please like, mark as helpful and mark as answer. Hope you have a wonderful day.
Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335
I think there is no issue with target.
Cross-Origin Read Blocking (CORB) is a web platform security feature that helps mitigate the threat of side-channel attacks (including Spectre). It is designed to prevent the browser from delivering certain cross-origin network responses to a web page, when they might contain sensitive information and are not needed for existing web features. For example, it will block a cross-origin text/html response requested from a <script> or <img> tag, replacing it with an empty response instead. This is an important part of the protections included with Site Isolation.
This may help you to understand about it more,
Is there an update for fix? I'm still having this issue...
I have got an update that the fix for this issue is tentatively stated for the next target release. Will keep you posted on the same .
Chrome's CORB algorithm seems to be fickle. For some reason it doesn't block a JSON response when I use the getOffer method, which is practically the same thing as the JSON response when using the Measure by click element.
Chrome definitely blocks the response from a Measure by click (yet to test getOffer/applyOffer), whether that affects the Target test analytics I'll be testing.
Chrome, no response from the click request:
FireFox (and Safari) don't block the JSON response: