{"_id":"5e3202e1cbd2420045c2dc73","project":"55de06fa57f7b20d0097636b","version":{"_id":"5dd81acdb8c91603c41dff08","project":"55de06fa57f7b20d0097636b","__v":0,"forked_from":"55de06fa57f7b20d0097636e","createdAt":"2015-08-26T18:35:38.642Z","releaseDate":"2015-08-26T18:35:38.642Z","categories":["5dd81acdb8c91603c41dfeba","5dd81acdb8c91603c41dfebb","5dd81acdb8c91603c41dfebc","5dd81acdb8c91603c41dfebd","5dd81acdb8c91603c41dfebe","5dd81acdb8c91603c41dfebf","563cbfe4260dde0d00c5e9d4","5dd81acdb8c91603c41dfec0","5dd81acdb8c91603c41dfec1","5dd81acdb8c91603c41dfec2","5dd81acdb8c91603c41dfec3","5dd81acdb8c91603c41dfec4","5dd81acdb8c91603c41dfec5","5dd81acdb8c91603c41dfec6"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"PostSDK","version_clean":"2.0.0","version":"2.0"},"category":{"_id":"5dd81acdb8c91603c41dfec3","__v":0,"project":"55de06fa57f7b20d0097636b","version":"5dd81acdb8c91603c41dff08","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-04-11T18:09:32.839Z","from_sync":false,"order":11,"slug":"data-transfer-and-integration","title":"Data Transfer and Integration"},"user":"55de06e19db51a0d0064947d","__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2020-01-29T22:10:41.408Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":999,"body":"Under CCPA regulations, companies who receive consumer requests to delete or opt-out are required to implement the requests and also pass the requests along to any other companies that they've distributed that consumer’s data to.  PushSpring will drop lists of mobile advertising IDs who have requested to delete or opt-out for pickup by our distribution partners to implement in their systems. This documentation describes how to access these lists and what’s in them.\n[block:api-header]\n{\n  \"title\": \"Consumer Opt-Out Ledger\"\n}\n[/block]\nThe consumer opt-out ledger consists of one or more gzipped CSV files located within s3://partners.pushspring.com/optouts/. These files are updated weekly and can be retrieved at any time. Partners can access these files using the same S3 credentials used to retrieve other data from this bucket.\n\nEach file consists of one or more rows containing the ID and ID type of the device that has elected to be left out of the PushSpring data set. ID types consist of the following:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"ID TYPES\\nIDFA (iOS) = 1,\\nAndroid Advertising ID (Android) = 3\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"pushspring-opt-outs-and-deletions","type":"basic","title":"PushSpring Opt Outs and Deletions"}

PushSpring Opt Outs and Deletions


Under CCPA regulations, companies who receive consumer requests to delete or opt-out are required to implement the requests and also pass the requests along to any other companies that they've distributed that consumer’s data to. PushSpring will drop lists of mobile advertising IDs who have requested to delete or opt-out for pickup by our distribution partners to implement in their systems. This documentation describes how to access these lists and what’s in them. [block:api-header] { "title": "Consumer Opt-Out Ledger" } [/block] The consumer opt-out ledger consists of one or more gzipped CSV files located within s3://partners.pushspring.com/optouts/. These files are updated weekly and can be retrieved at any time. Partners can access these files using the same S3 credentials used to retrieve other data from this bucket. Each file consists of one or more rows containing the ID and ID type of the device that has elected to be left out of the PushSpring data set. ID types consist of the following: [block:code] { "codes": [ { "code": "ID TYPES\nIDFA (iOS) = 1,\nAndroid Advertising ID (Android) = 3", "language": "text" } ] } [/block]