ghostery
[Unidentified Tracker]: tally-1.qubitproducts.com
We have already QuBit OpenTag. There is also a potentially tracker operating on tally-1.qubitproducts.com, but it needs more investigation where to put it (merge into QuBit OpenTag or is it something independent?).
Example page: https://us.myprotein.com/sports-nutrition/impact-whey-protein/10852500.html
During checkout, there should be a request like that:
POST https://tally-1.qubitproducts.com/tally/myprotein_us/ecount/atom-views-1440min/10852500/1440
Perhaps we could create an entry called "QuBit API" for it? For instance, the call to tally-1.qubitproducts.com is documented here:
https://docs.coveo.com/en/qbb1t322/coveo-experimentation-hub/increment-and-decrement-counters
POST tally-1.qubitproducts.com/tally/<tracking_id>/<op_type>/
/ /<window_size>
Background: these are the entries that we already have:
- QuBit OpenTag (pattern): https://github.com/ghostery/trackerdb/blob/084068a0076298ed382a9229e3bb9f56a5cf4875/db/patterns/qubit.eno#L4
- Qubit (company): https://github.com/ghostery/trackerdb/blob/084068a0076298ed382a9229e3bb9f56a5cf4875/db/organizations/qubit.eno
One question is to do research to decide whether tally-1.qubitproducts.com should be a new entry (e.g. QuBit API) or whether it should be merged into the existing QuBit OpenTag.
(When I last looked into it, my impression was that it is different from QuBit OpenTag and deserves its own entry. My summary would have been QuBit API, but maybe there is something more fitting)
Candidates of test pages (unverified):
www.menards.com
www.riverisland.com
www.very.co.uk
www.tkmaxx.com
www.glassesdirect.co.uk
www.matalan.co.uk
www.myprotein.com
fr.myprotein.com
nl.myprotein.com
www.dermstore.com
www.chanel.com
www.halfords.com
www.myprotein.it
www.lookfantastic.com
www.lookfantastic.fr
www.g-star.com
www.menswearhouse.com
de.myprotein.com
www.cultbeauty.co.uk
Sorted with the most events (on top) to the fewest events (on bottom).