3rd Party Badge Request: mParticle.com
Reported by
toml...@gmail.com,
Aug 29 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1. Enable 3rd party badging 2. Go to mparticle.com 3. Note that the request to jssdkcdns.mparticle.com and jssdks.mparticle.com are not badged What is the expected behavior? 3. Requests to jssdkcdns.mparticle.com and jssdks.mparticle.com should be badged with "mParticle" What went wrong? Entry for mparticle does not yet exist. Did this work before? No Chrome version: 60.0.3112.113 Channel: stable OS Version: 10.0 Flash Version: Chrome dev tools rock! From one web developer to another - THANK YOU
,
Sep 29 2017
We are a consumer of Google's 3PAS data set. You need to register through them and eventually the updates will get merged in. I believe the link is (if this isn't it, I can dig deeper): https://support.google.com/adwords/troubleshooter/6162023 Marking WontFix to get it off our stack. Thanks!
,
Sep 29 2017
I can look into that, but just to make sure, we're both talking about Devtools badging in the network panel, correct? I followed the instructions here: https://stackoverflow.com/questions/45720950/how-do-chrome-devtools-3rd-party-badges-get-added Thanks, Tom Longson
,
Sep 29 2017
#5 Yes I am referring to the 3rd party badges feature in devtools network panel. |
||
►
Sign in to add a comment |
||
Comment 1 by pfeldman@chromium.org
, Aug 30 2017Status: Assigned (was: Unconfirmed)