Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore URL Mapping/ Grouping #17

Open
FrancescoSTL opened this issue Aug 2, 2016 · 2 comments
Open

Explore URL Mapping/ Grouping #17

FrancescoSTL opened this issue Aug 2, 2016 · 2 comments
Assignees
Labels

Comments

@FrancescoSTL
Copy link
Owner

FrancescoSTL commented Aug 2, 2016

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):
screen shot 2016-08-02 at 1 43 01 pm

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.

@FrancescoSTL FrancescoSTL self-assigned this Aug 2, 2016
@FrancescoSTL FrancescoSTL added this to the V1.0 milestone Aug 2, 2016
@FrancescoSTL
Copy link
Owner Author

FrancescoSTL commented Aug 2, 2016

An example of how Lightbeam uses the data to map entity's across multiple page visits:
screen shot 2016-08-02 at 1 43 01 pm

@FrancescoSTL FrancescoSTL removed this from the V1.0 milestone Aug 5, 2016
@FrancescoSTL
Copy link
Owner Author

This won't happen in v1. We might tackle this as a v2 issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant