Request:

In the current spec, Trusted Bidding Signals fetching includes the hostname of the top-level webpage where the ad will appear. It would be helpful for brand safety to include the full path of the webpage where the ad will appear rather than only the top level hostname.

###Use Case:
Many advertisers will define domain-level allow-lists or block-lists to define what websites they are willing to show their ads. Advertisers may wish to block specific paths of a domain, for example an advertiser may wish to show their ads generally on https://news-site.com/ but do not want to show their ads near political articles and therefore block https://news-site.com/politics.

In this scenario the trustedBiddingSignals request would only contain hostname=news-site.com and therefore evaluating the domain's full path against the the advertiser's defined domain targeting.

Advertisers often define very large lists of domains they wish to Block or Allow (this could be in the millions of domains), and therefore it is not feasible to send the full list of blocked or allowed domains to the client to be evaluated, and instead can be evaluated within the Trusted Bidding Signals server.

Would it be possible to update the trustedBiddingSignals fetch call to include the full path?