Labeling Examples
- Topics:
- Data Governance
CREATED FOR:
- Admin
Sample hit data
Suppose you have the following hit data:
- The first row contains the labels for each variable.
- The second row is the name of the variable. If it has an ID label, it contains the assigned namespace in parentheses.
- Hit data starts in the third row.
| Labels | I2 ID-PERSON DEL-PERSON ACC-PERSON | I2 ID-DEVICE DEL-DEVICE ACC-ALL | I2 DEL-PERSON ACC-PERSON | I2 DEL-DEVICE DEL-PERSON ACC-ALL | I2 ID-DEVICE DEL-DEVICE ACC-ALL |
|---|---|---|---|---|---|
| Variable Name (Namespace) | MyProp1 (user) | Visitor ID (AAID) | MyEvar1 | MyEvar2 | MyEvar3 (xyz) |
| Hit Data | Mary | 77 | A | M | X |
| Mary | 88 | B | N | Y | |
| Mary | 99 | C | O | Z | |
| John | 77 | D | P | W | |
| John | 88 | E | N | U | |
| John | 44 | F | Q | V | |
| John | 55 | G | R | X | |
| Alice | 66 | A | N | Z |
Sample Access request
If you submit an access request, you will receive two files that you can return to the data subject. One file is a CSV file containing one row for each hit received for the data subject and a column for each variable with the appropriate access label. The other file is a summary HTML file that lists each variable, followed by all unique values seen for that variable for the data subject and the number of times each unique value was seen.
For our example, the summary file contains the values indicated in the table below. A request may return only a device file, only a person file or one of each. Two summary files are returned only if a person ID is used and expandIds is true.
| API Values | Summary file type returned | Data in Summary Access File | |||||
|---|---|---|---|---|---|---|---|
| Namespace/ID | expandIDs | MyProp1 | Visitor ID | MyEvar1 | MyEvar2 | MyEvar3 | |
| AAID=77 | false | device | not present | 77 | not present | M, P | X, W |
| AAID=77 | true | device | not present | 77 | not present | M, P | X, W |
| user=Mary | false | person | Mary | 77, 88, 99 | A, B, C | M, N, O | X, Y, Z |
| user=Mary | true | person | Mary | 77, 88, 99 | A, B, C | M, N, O | X, Y, Z |
| device | not present | 77, 88 | A, B, C | N, P | U, W | ||
| user=Mary AAID=66 | true | person | Mary | 77, 88, 99 | A, B, C | M, N, O | X, Y, Z |
| device | not present | 66, 77, 88 | A, B, C | N, P | U, W, Z | ||
| xyz=X | false | device | not present | 55, 77 | not present | M, R | X |
| xyz=X | true | device | not present | 55, 77 | not present | M, P, R | W, X |
Notice that the setting for expandIDs does not make any difference to the output when a cookie ID is used.
Sample Delete requests
With a delete request using the API values in the first row of the table, the hit table will be updated to look something like this:
| AAID=77 (expandIDs value does not matter) | ||||
|---|---|---|---|---|
| MyProp1 | AAID | MyEvar1 | MyEvar2 | MyEvar3 |
| Mary | 42 | A | Privacy-7398 | Privacy-9152 |
| Mary | 88 | B | N | Y |
| Mary | 99 | C | O | Z |
| John | 42 | D | Privacy-1866 | Privacy-8216 |
| John | 88 | E | N | U |
| John | 44 | F | Q | V |
| John | 55 | G | R | X |
| Alice | 66 | A | N | Z |
NOTEAAID=77 and a DEL-DEVICE label are impacted.expandIDs=false
NOTEuser=Mary and a DEL-PERSON label are impacted. Also, in practice, the variable containing A_ID would probably be a prop or an eVar. Its replacement value would be a string starting with Privacy-, followed by a random number (GUID), rather than replacing the numeric value with a different, random numeric value.expandIDs=true
Note the following:
- Cells on rows containing
user=Maryand aDEL-PERSONlabel are impacted.