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

Does every eTLD+1 visiting website need enrollment/attestation? #324

Closed
relevance-api-topics opened this issue Jul 16, 2024 · 1 comment
Closed

Comments

@relevance-api-topics
Copy link

Hope to ask a question for enrollment/attestation requirement for utilizing Topics API-

Support a browser has visiting history for hostname1.com, hostname2.com, both websites do fetch call to service.com through client JS tool offered by service.com, do hostname1.com and hostname2.com need enrollment/attestation firstly to successfully do fetch call to service.com with Topics?

Please help let us know. Thanks!

@michaelkleber
Copy link
Collaborator

  1. In the situation you describe, it should be service.com that enrolls — they are the one interacting with the API, through HTTP headers on requests going to their server.
  2. For future questions like this I would recommend instead the Privacy Sandbox Developer Support repository, https://github.com/privacysandbox/privacy-sandbox-dev-support

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

No branches or pull requests

2 participants