You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #8 was merged, we had some new situation introduced where ad's are requesting other ads. See lax1-ib.adnxs.com below, where the content is Website Origin, Requested Ad Host, and Response Time (in that order, from left to right):
Above, you can see that cnn.com is requesting an ad from lax1-ib.adnxs.com. That ad presumably proceeds to call js.moatads.com (note that the above picture is in reverse chronological order, so the last item was requested first and vice versa).
In order to mitigate this, we'd need to group all requests from a page to the original host. We can do this by grabbing the URL of the requested ad's tab (using details.tabId). This also allows us to map data in the same way lightbeam does, which could be interesting.
The text was updated successfully, but these errors were encountered:
After #8 was merged, we had some new situation introduced where ad's are requesting other ads. See
lax1-ib.adnxs.com
below, where the content is Website Origin, Requested Ad Host, and Response Time (in that order, from left to right):Above, you can see that
cnn.com
is requesting an ad fromlax1-ib.adnxs.com
. That ad presumably proceeds to calljs.moatads.com
(note that the above picture is in reverse chronological order, so the last item was requested first and vice versa).In order to mitigate this, we'd need to group all requests from a page to the original host. We can do this by grabbing the URL of the requested ad's tab (using
details.tabId
). This also allows us to map data in the same way lightbeam does, which could be interesting.The text was updated successfully, but these errors were encountered: