-
Notifications
You must be signed in to change notification settings - Fork 73
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
Investigate: should analytics.tiktok.com be detected as a tracker? #262
Comments
From the raw data, the most popular pages in my sample data were https://www.nfl.com/ and https://www.lowes.com/. Both sent 3rd party requests to https://analytics.tiktok.com/i18n/pixel/identify.js with the same cookie:
On a different profile, I got another unique identifier. Not clear why we don't detect it, I'll mark it as a bug. This is clearly cross-site tracking, and the amount of traffic is not too small that can miss it because of that. (The Ghostery extension reports it also as tracker, by the way.) |
We are confident that we tracked it down in our internal processing pipeline (a missing mapping step). Existing trackers are not affected, but new ones will not be detected. In the raw data, everything is there, so once we fixed it, they should show up when the data is recomputed. From what I see in sample data, |
The data from January has been now processed. https://whotracks.me/trackers/tiktok_analytics.html It could be that the stats will change with the next month, as we made the internal changes in the middle of January. That could affect the estimated popularity (increasing its relative ranking). Otherwise, the data looks OK as far as I can tell (e.g. the sites from the samples |
Closing it now. With the March release, the reach increased (0.7% to 1.2%), but the data looks stable. |
Currently, it is not detected as a tracker by WhoTracks.me, but perhaps it should be. In the raw data (
tp_events
), third-party requests do exist. The question is now whether it should have be detected as a third-party tracker. And if so, why are the algorithms missing it?(Context: originally reported here #261)
The text was updated successfully, but these errors were encountered: