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.

Sign up for GitHub

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

Update naming and terminology according to the layering effort with Google's Conversion Measurement API #75

Merged
merged 3 commits into from
Mar 18, 2021
Merged

Update naming and terminology according to the layering effort with Google's Conversion Measurement API #75

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c772ed9
For review.
johnwilander Mar 9, 2021
72e460a
Fixed Tess's comments.
johnwilander Mar 9, 2021
8623b5d
Changed attributeOn to attributionDestination and attributionSourceId…
johnwilander Mar 15, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,13 +15,13 @@ the [Privacy Community Group](https://privacycg.github.io/).

## Introduction

A popular business model for the web is to get attribution and payment for conversions, for instance purchases or sign-ups, which result from the click on an ad. Traditionally, such attribution has been facilitated by user identifying cookies sent in third-party HTTP requests to the click source. However, the same technology can be and has been used for privacy invasive cross-site tracking of users.
A popular business model for the web is to get attribution and payment for clicks, for instance ad clicks that result in purchases or sign-ups. Traditionally, such attribution has been facilitated by user or device identifying cookies sent in cross-site HTTP requests. However, the same technology can be and has been used for privacy invasive cross-site tracking of users.

The technology described [in this draft specification](https://privacycg.github.io/private-click-measurement/) is intended to allow for ad click attribution while disallowing arbitrary cross-site tracking.
The technology described [in this draft specification](https://privacycg.github.io/private-click-measurement/) is intended to allow for click attribution, such as ad click attribution, while disallowing arbitrary cross-site tracking.

## Goals

* Support ad click attribution.
* Support click attribution across websites.

* Preserve user privacy, specifically prevent cross-site tracking of users.

Expand All @@ -31,4 +31,6 @@ Repository: https://github.com/privacycg/private-click-measurement

Link to spec: https://privacycg.github.io/private-click-measurement/

Blog post with more background info: https://webkit.org/blog/8943/privacy-preserving-ad-click-attribution-for-the-web/
Blog post with more background info: https://webkit.org/blog/11529/introducing-private-click-measurement-pcm/

Original blog post with further info: https://webkit.org/blog/8943/privacy-preserving-ad-click-attribution-for-the-web/
Loading