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)
MyProp1AAIDMyEvar1MyEvar2MyEvar3
Mary42APrivacy-7398Privacy-9152
Mary88BNY
Mary99COZ
John42DPrivacy-1866Privacy-8216
John88ENU
John44FQV
John55GRX
Alice66ANZ
NOTE
Only columns on rows containing AAID=77 and a DEL-DEVICE label are impacted.
user=Mary
expandIDs=false
MyProp1AAIDMyEvar1MyEvar2MyEvar3
Privacy-052377Privacy-1866Privacy-3681X
Privacy-052388Privacy-2178Privacy-1975Y
Privacy-052399Privacy-9045Privacy-2864Z
John77DPW
John88ENU
John44FQV
John55GRX
Alice66ANZ
NOTE
Only celcolumnsls on rows containing user=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.
user=Mary
expandIDs=true
MyProp1AAIDMyEvar1MyEvar2MyEvar3
Privacy-578209Privacy-0859Privacy-8183Privacy-9152
Privacy-578216Privacy-6104Privacy-2911Privacy-6821
Privacy-578283Privacy-2714Privacy-0219Privacy-4395
John09DPrivacy-8454Privacy-8216
John16EPrivacy-2911Privacy-2930
John44FQV
John55GRX
Alice66ANZ

Note the following:

  • Cells on rows containing user=Mary and a DEL-PERSON label are impacted.
  • Because of ID expansion, cells on rows containing AAID=77, AAID=88 or AAID=99 (which are the AAID values on rows containing user=Mary) and a DEL-DEVICE label are impacted. This includes cells with a DEL-DEVICE label on rows where user=Mary. This causes cells in rows 4 and 5 (as well as rows 1-3) with DEL-DEVICE labels (AAID, MyEvar2 and MyEvar3) to be obfuscated.
  • The expandIDs setting does not expand to the call to include values present in MyEvar3 (X, Y and Z), which has an ID-DEVICE label, when user=Mary. ExpandIDs only expands to include Visitor IDs (AAIDs in this example, but also the ECID) on rows where user=Mary. Thus the last two rows, which contain MyEvar3 values of X and Z are not impacted.
  • MyEvar2 in the fourth and fifth rows are updated because these rows contain the same Visitor ID values (77 and 88) as those on the first and second rows. As a result, ID expansion includes them for device-level deletes.
  • The values of MyEvar2 in rows two and five match both before and after the delete. However, after the delete they no longer match the value N that occurs in the last row, because that row was not updated as part of the delete request.
  • MyEvar3 behaves very differently than it did without ID expansion, because without ID expansion, no ID-DEVICES matched. Now, AAID matches on the first five rows.

Analytics