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

Create google_play_services #585

Merged
merged 2 commits into from
Dec 5, 2024
Merged

Conversation

BrianClifton
Copy link
Contributor

This is a VERY difficult one to pin down as the same domain/URL is used in different context: play.google.com/log?format=json

On Volvo with embedded YouTue video: https://www.volvoce.com/france/fr-fr/products/electric-machines/ew240-electric-mh/

On Booking.com where is loads a Google login dialogue.

The URL is doing some kind of logging, but on reflection I have opted for category=hosting as it "feels" a better match than site_analytics.

This is a VERY difficult one to pin down as the same domain/URL is used in different context: play.google.com/log?format=json

On Volvo with embedded YouTue video: https://www.volvoce.com/france/fr-fr/products/electric-machines/ew240-electric-mh/

On Booking.com where is loads a Google login dialogue.

The URL is doing some kind of logging, but on reflection I have opted for category=hosting as it "feels" a better match than site_analytics.
@philipp-classen
Copy link
Member

Makes sense. I'm thinking of handling the logging with a separate pattern (aliasing to this one, but having only filters rules). Like we did for Google Tags.

But starting with hosting, which is more neutral than site_analytics, sounds like a good first step.

@philipp-classen philipp-classen merged commit 6f50daf into ghostery:main Dec 5, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants