I had to find out the hard way that you restrict the min length for user_id
This is a loom video of my experience navigating your forum.
This is a horrible horrible experience
Hi kimsia Thank you for taking the time to create this video and for this important feedback. Such a frustrating situation! I’ll make sure to relay the message to the team and see if I can gather any additional guidance so that you can succeed with Amplitude. We’re here to help!
Hi kimsia I have an update. Here’s where you can find more information about min id length configuration in our developer center.
The default setting is still to have user_id or device_id be >5 char length but in Segment there's an option to change that setting. Take a look:
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).
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…
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.
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 !!
