- From: Aram Zucker-Scharff via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 Jan 2023 15:57:31 +0000
- To: public-patcg@w3.org
I've tried to pull as is from the preexisting document text, but if I've malformed here, let me know. Is this clearer phrasing on those two points @csharrison ? I can change `Scope of Privacy Budget is limited by delegation to another provider.` to `User data is limited by a privacy budget, with the amount of properties about a user further limited if the TLD delegates to a measurement provider outside of the TLD` For the 2nd one, I think it may make more sense to split it. `Can measure interaction events that do not 'convert' (send the user to another domain). This could include general interactions (mouse over, non-converting click, scroll event) or specific defined interactions like 'started a form fill' or 'played the in-ad game'.` -> - `Can connect interaction events (like generated a purchase or a form fill) on a landing site in connection to ad events, associating these ad events with desired outcomes on ad-defined target/landing sites` - `Can track events within the body of an ad beyond converting clicks and views, so long as those events are predefined by the ad's internal code (like a scroll event or video play)` Do these changes make more sense? -- GitHub Notification of comment by AramZS Please view or discuss this issue at https://github.com/patcg/meetings/issues/91#issuecomment-1402184540 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 January 2023 15:57:33 UTC