Using guest delete
The Guest Delete endpoint in the Sitecore CDP Batch API enables you to delete a guest record and all entities associated with the guest including orders, sessions, and events. This is an irreversible operation. After you delete a guest record, you cannot retrieve the guest record or any related entities.
The following steps provide an overview of how a guest is deleted:
-
Upload a batch file containing guest records. If you are deleting the guest records in order to meet GDPR compliance, use
gdpr_deletemode. If you are deleting the guest records for any other reason, usedeletemode. -
If there is enough identifying information, proceed to the next step. If there is not enough identifying information, the Guest Delete endpoint returns a 400 Response
Not Enough Identifying Infofor the guest record. -
If the guest record is found, proceed to the next step. If the guest record is not found, the Guest Delete endpoint returns a 404 Response
Guest not found. -
The Guest Delete endpoint attempts to find any and all Guests with matching identity:
-
The Guest Delete endpoint only finds one guest with matching identities. the Guest Delete endpoint returns a 200 Response
Guest and associated entities deleted. The guest record is permanently deleted along with their sessions and events. Orders and order items are deleted only if you use thegdpr_deletemode, not if you use thedeletemode. For more information, see how to delete order data indeletemode. -
Alternatively, if the Guest Delete endpoint finds more than one guest with matching identities, the Guest Delete endpoint returns a 200 Response
n matches found for this guest, 1st match deleted. In this 200 Response, n represents the number of guests with matching identities. Only the first guest with matching identities is deleted. You must perform this procedure again to delete any remaining guest records with matching identity.
-
Ensuring GDPR Compliance
If you are deleting a guest due to maintaining GDPR compliance, you must perform the above procedure for each matching identity. As the data controller, it is your responsibility to ensure that none of your systems send any of the deleted guest's PII to Sitecore CDP.
The Guest Delete endpoint in the Sitecore CDP Batch API enables you to delete a guest record and all entities associated with the guest including orders, sessions, and events. This is an irreversible operation. After you delete a guest record, you cannot retrieve the guest record or any related entities.
The following terms help you understand how Sitecore CDP deletes guests:
-
Contact - the contact on the order is the owner of the order. For example, the person who purchased a flight on behalf of the consumer.
-
Consumer - the consumer of an order is someone who is listed as traveling or consuming a product or service. They might or might not be the contact on the order.
The following steps provide an overview of how a guest is deleted:
-
Upload a batch file containing guest records. If you are deleting the guest records in order to meet GDPR compliance, use
gdpr_deletemode. If you are deleting the guest records for any other reason, usedeletemode. -
If there is enough identifying information, proceed to the next step. If there is not enough identifying information, the Guest Delete endpoint returns a 400 Response
Not Enough Identifying Infofor the guest record. -
If the guest record is found, proceed to the next step. If the guest record is not found, the Guest Delete endpoint returns a 404 Response
Guest not found. -
The Guest Delete endpoint attempts to find any and all Guests with matching identity:
-
The Guest Delete endpoint only finds one guest with matching identities. the Guest Delete endpoint returns a 200 Response
Guest and associated entities deleted. The guest record is permanently deleted along with their sessions and events. Orders and order items are deleted only if you use thegdpr_deletemode, not if you use thedeletemode. For more information, see how to delete order data indeletemode. -
Alternatively, if the Guest Delete endpoint finds more than one guest with matching identities, the Guest Delete endpoint returns a 200 Response
n matches found for this guest, 1st match deleted. In this 200 Response, n represents the number of guests with matching identities. Only the first guest with matching identities is deleted. You must perform this procedure again to delete any remaining guest records with matching identity.
-
-
If the guest is a consumer on an order but not also the contact, the following occurs:
-
Sitecore CDP creates a new guest record to replace the original guest record. The new guest record has a
guestTypeof traveller. -
If you performed the guest delete operation using the
gdpr_deletemode, the guest profile in the UI has a first name of GDPR_Delete and a last name of GDPR_Delete, and does not contain any Personally Identifiable Information (PII). -
If you performed the Guest Delete operation using the
deletemode, the new Guest Profile has a first name of Deleted and a last name of Deleted, and does not contain any PII. -
The purpose of creating the new Guest Profile is to maintain the referential integrity of Sitecore CDP. This means that if
gdpr_deletemode was used, a user looking at orders in the contact's guest profile can see that there is a consumer on an order with a first name ofgdpr_deleteand a last name ofgdpr_deletebut with no PII. Likewise, ifdeletemode was used, a user looking at orders in the contact's guest profile can see that there is a consumer on an order with a first name of deleted and a last name of deleted but with no PII. -
Similar to any other guest profile, you can search for the deleted guest profile, but it does not contain any PII.
-
Ensuring GDPR Compliance
If you are deleting a guest due to maintaining GDPR compliance, you must perform the above procedure for each matching identity. As the data controller, it is your responsibility to ensure that none of your systems send any of the deleted guest's PII to Sitecore CDP.