I added a warning containing the following message:
"It's important to note that the userID required for deletion requests are the user IDs sent through your events according to the Segment Spec. In other words, the IDs under the userId fields specifically, not just any identifier."
I've had a few customers in the past complain that the documentation should be clearer on which userIDs should be submitted for deletion. They've usually written in because they used some sort of internal identifier or an email as the ID for deletion, when it should be the user ID per the Segment Spec. I wanted to add this warning in order to prevent this from happening in the future.
Proposed changes
I added a warning containing the following message: "It's important to note that the userID required for deletion requests are the user IDs sent through your events according to the Segment Spec. In other words, the IDs under the userId fields specifically, not just any identifier."
I've had a few customers in the past complain that the documentation should be clearer on which userIDs should be submitted for deletion. They've usually written in because they used some sort of internal identifier or an email as the ID for deletion, when it should be the user ID per the Segment Spec. I wanted to add this warning in order to prevent this from happening in the future.
Merge timing
Related issues (optional)