Skip to main content
Does anyone use a user ID instead of an email address as a key identifier for users? In our platform, a single user might have multiple venues under one email address. I would be extremely grateful for any best practices, pros&cons, and tips around the id as a key identifier. Thanks!
That is something we'll be pivoting to later this year and then I may be asking the same question.
We have this exact same problem. We have been advised that this is on the roadmap.
But defiantly something we need as we have merchants with multiple venues and sometimes venues with multiple devices 😀
@"Adrian Gray" what do you mean this is on the roadmap? It's perfectly doable with Iterable at the moment according to the documentation.
@Antti Tuomola we have been advised that this would not work the way that we would need it, as we want to create them without email addresses as we do not always have this information for all our devices.
Ah, I see - in our cases there are multiple devices in use for a single venue, but they all use a shared account with the same email. Our issue is that many entrepreneurs have multiple venus (or locations) which all need a unique account, but often share the same email.
Hi all! This is something that is top of mind for us and in progress. We'll provide more updates as we have them. Thank you for your feedback!
Thanks @Sarah Lubecki, great to hear! Our company will gladly participate in a possible beta program for this!

Sarah Lubecki any update on this? We're about to do our internal changes to tackle this issue, but our solution is not perfect, so I was wondering if there's a timeline for this?


Reply