For deletion requests, ODP does the following for the next 30 days after the deletion request:

• ODP finds all identifiers associated with the profile requested for deletion and does not rediscover customers using those identifiers.
• You cannot move or associate identifiers that are linked to a profile requested for deletion to other profiles. Also, you can not add new identifiers to the profile.
• ODP ignores and drops events tied solely to the identifiers of the profile under deletion.
• If an event includes identifiers from both a profile under deletion and a high-confidence identifier from an active profile, ODP processes the event using the high-confidence identifier and attributes it only to the active profile. ODP ignores identifiers from the profile under deletion.
• If an event includes identifiers from a profile under deletion along with a new low-confidence identifier, the event is dropped. The low-confidence identifier is neither linked to the deleted profile nor used to create a new one.

❗️

Warning

Use the Compliance endpoints for compliance-based changes only.

If you are trying to remove users from a list or a specific channel, or globally revoke marketing consent, do not use the Compliance endpoints.

• Use the Consent API for managing typical marketing-based opt outs.
• Use the Lists API to manage list subscriptions.