I'm running into some issues surrounding the use of aliases, and I haven't been able to get anyone from support on the line, I'm hoping someone here knows: is there any way to delete an alias? Once an alias is created is there any way to send events and/or profile updates to the user profile that existed before the alias was put in place? I found that the profile deletion API endpoint has an $ignore_alias option, do other endpoints have that option, that might not be documented?
I'm looking at something similar currently, where we had a bug that accidentally aliased two real users together, rather than just aliasing the real user to their anonymous ID etc. When I reached out to customer support they said that un-aliasing wasn't something supported, and that one potential workaround is to do an export of the combined user, trigger a delete of that user, and then update the exported data to distinguish what is for which user etc, and import that data back in. I haven't had a chance to test this just yet, and we've got ~2.5k (5k) users impacted by this bug so I'm really interested in knowing if you have any other alternatives, I might look into the profile deletion endpoint, we were currently looking at the GDPR deletion route as that would ensure the alias is deleted presumably etc.
I just heard back from support, they can't delete aliases and they suggested the same thing, export the user activity and profile, trigger a gdpr request and re-upload all the data; in my case they also said they can manually move our project from legacy id merge to original id merge, which would solve our immediate issue (but likely not yours)