We are looking for a way to update users email addresses so that we do not have two profiles in the system.
If a user updates their email address currently it creates a new account in Iterable and we could end up emailing two account.
Page 1 / 1
Hello Andrian,
Can you please let me the process you are using when a user update's their email address? Are you using the Update User API call, if so this will create a new user instead of updating the email address.
If you would like to update the email address the best API call to use would be the Update user email endpoint (https://api.iterable.com/api/docs#users_updateEmail).
Please let me know if that helps to answer your question.
Regards,
Andre Linde
Can you please let me the process you are using when a user update's their email address? Are you using the Update User API call, if so this will create a new user instead of updating the email address.
If you would like to update the email address the best API call to use would be the Update user email endpoint (https://api.iterable.com/api/docs#users_updateEmail).
Please let me know if that helps to answer your question.
Regards,
Andre Linde
We looked at using this but both the emails are already in Iterable, we tried exporting users from the suggested endpoint but it's way too slow.
We tried to fetch the latest users but I gave up after the response took over 5 minutes. The time ranges seem to be the profile update timestamp which for us is the same for large groups of users. Even querying a minute at a time results in the response taking very long and I assume it's because it's matching too many users.
So we have implemented a workaround for this until we can start to use something other than email as a unique identifier
We tried to fetch the latest users but I gave up after the response took over 5 minutes. The time ranges seem to be the profile update timestamp which for us is the same for large groups of users. Even querying a minute at a time results in the response taking very long and I assume it's because it's matching too many users.
So we have implemented a workaround for this until we can start to use something other than email as a unique identifier
Reply
Create a new Iterable Plaza community account
Already have an account? Login
Login to the Iterable Plaza Community
Not a customer? Create an account
Log in to Iterable (SSO)
Iterable customers and employees login/create an accountor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.