---
schema_version: "1"
id: c6a21f7d550bd3e828b6bf5b3e404979a5628fe54ab458865d75e2c26dd4471e
title: Delete Ingested Records in Data 360
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_delete_data_stream_records.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_delete_data_stream_records.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a3f6405df5f525ed7fbe9d9d8291dedf6e7cee08f95ef1229e7ca428ef86ffa6
description: You can delete data ingested into Data 360. Your data stream must have an upsert refresh mode. The deletion process depends on the type of connector that you’re using.
products:
  - Data 360
release: "264"
---
# Delete Ingested Records in Data 360

You can delete data ingested into Data 360. Your data stream must have an upsert refresh mode. The deletion process depends on the type of connector that you’re using.

Amazon S3, Google Cloud Storage, and Microsoft Azure Storage connectors—The records that you’re deleting must be read from the same source directory that the corresponding data stream is ingesting from. When a data stream has multiple upsert and deletion files, the files are processed in the order of their last modified time. Row versioning isn’t supported for deletes.

Ingestion API connector—The API provides a delete operation for both streaming and bulk interaction patterns. To delete up to 200 records, refer to [Delete Records](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_delete_records.htm). To delete more than 200 records in a request, use bulk ingestion operations. For more information, see [Upload Job Data](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_upload_job_data.htm) and [Delete a Job](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_delete_a_job.htm). After the delete requests are received programmatically, they're processed asynchronously.

SFTP connector—The records that you’re deleting must be read from the same source parent directory that the corresponding data stream is ingesting from. When a data stream has multiple upsert and deletion files, the order of processing isn't guaranteed. Row versioning isn’t supported for deletes.

Salesforce CRM connector—The connector manages the deletion requests. After data is deleted on the source org, it’s removed from Data 360 with the next incremental refresh. You can store deleted records that have been in the Salesforce Recycle Bin for up to 15 days by creating a Deleted Record Data Lake Object, see [https://developer.salesforce.com/docs/atlas.en-us.c360a\_api.meta/c360a\_api/c360a\_api\_upload\_job\_data.htm](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_upload_job_data.htm).

Data 360 doesn’t support cascading deletes. If you delete a profile record, its related engagement or other profile records aren’t deleted. Delete these records manually from each table.

- **[Delete Records by Using a Delete File](https://help.salesforce.com/s/articleView?id=data.c360_a_delete_data_stream_records_deletion_file.htm&release=264.0.0&type=5)**  
    To delete data records ingested by using the Amazon Simple Storage Service (Amazon S3), Google Cloud Storage (GCS), Microsoft Azure, Ingestion API, or Secure File Transfer Protocol (SFTP) connector, create a delete file. Create the file in CSV or Parquet file format. S3, GCS, and Azure data streams support Parquet file ingestion.

#### See Also

- [_Salesforce Developer_: Data 360 Reference- Delete Records](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_delete_records.htm)
- [_Salesforce Developer_: Data 360 Reference- Delete a Job](https://developer.salesforce.com/docs/atlas.en-us.c360a_api.meta/c360a_api/c360a_api_delete_a_job.htm)