Tracker config doesn't account for shared origins

The current tracker config uses origins, such as google.com, to make its lookups more efficient. This is fine, but it causes issues in the rare case of a shared origin, such as DoubleClick servers. Google uses some DoubleClick origins for its other Ad services, causing these calls to be incorrectly attributed to DC.

To get around this, the config will need to be altered. In the interest of keeping optimizations in place, the origin can still provide the constant-time lookups, but endpoints can be replaced with full URL patterns.

MightyHive / chrome-extension

Tracker config doesn't account for shared origins #2