🎯 Idea: Use Multiple User Properties for ID Resolution

Hello there,

I’m looking into options to use Amplitude more as a CDP and am a little stuck with the concept of ‘ID Resolution’.

We can do some basic ID resolution in a Data Warehouse for certain data sources (though this is still not very satisfactory) but we’d like to ‘resolve’ IDs with those captures in the client-side tracking.

For example, sometimes in client side we get only Email, sometimes we get Email AND Phone, sometimes we just get Phone… and other times we get Unique User ID. Same thing goes in the Data Warehouse.

It would be very cool if we could sync user properties then ‘flag’ them as ‘to be used for ID resolution’… I think this would be amazing.

Find more posts tagged with

User IDs

Active

Status: Active

Comments

There are no comments yet

Quick Links

Give your vote

Linking AI Feedback to Specific Surveys in Amplitude
It would be really helpful if Amplitude showed which survey a piece of feedback belongs to. Right now, it’s hard to tell where comments originate when multiple surveys are active. As a bonus, it would also be great if the feedback text matched the UI language (currently, mine shows in German).
playback video in 9:16 in guides on phones
It would be great to have the option of playing back video (and having the video preview) in a 9:16 (vertical) orientation so that an end user of a video in a guide didn't have to full-screen the video in order to have it play in the correct orientation. It would also be great to have support for Wistia as more and more…
Grouping reordering
Hi, I’d like to request a feature: it would be really helpful to have the ability to shuffle or reorder properties within an event, especially when grouping. Right now, adjusting the order of grouped outputs is quite cumbersome.
Fix the search when filtering
When changing a property value, because we often have complex and long values, we paste the exact value in the search bar. However the matching value will appear at the very top but all other values will remain, which makes the search complex and we lose a few seconds each time Here is a loom to show my point Thanks !!

View All