Daniel
My feedback
1 result found
-
5 votes
An error occurred while saving the comment An error occurred while saving the comment Daniel commentedThis case is fairly common for any site that allows their users to update their email address:
1. User signs up to our website.
2. We sync user's details with AP using their email.
3. User changes email address on our site.
4. We sync user details again with new email (because we can't update via contact_id).
5. AP now has two emails recorded for the one user.Workaround is to delete the old email from AP. This has two negative effects:
1. Old email is now out of any current journey/s.
2. Updated email is now seen as a new user and triggers all of the "new" user journey/s.It would be unreasonable to expect that our system locks email addresses down with each account or for us to try and reattach the new email to the old email's journey/s.
Furthermore your system already supports GET and DELETE requests for a contact via the contact_id.
Daniel supported this idea ·
This case is fairly common for any site that allows their users to update their email address:
1. User signs up to our website.
2. We sync user's details with AP using their email.
3. User changes email address on our site.
4. We sync user details again with new email (because we can't update via contact_id).
5. AP now has two emails recorded for the one user.
Workaround is to delete the old email from AP. This has two negative effects:
1. Old email is now out of any current journey/s.
2. Updated email is now seen as a new user and triggers all of the "new" user journey/s.
It would be unreasonable to expect that our system locks email addresses down with each account or for us to try and reattach the new email to the old email's journey/s.
Furthermore your system already supports GET and DELETE requests for a contact via the contact_id.