You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we have a database of members numbering about 1,000 and we try to do the right thing by keeping our email addresses as up to date as possible and we use the API where possible.
Would it be possible to create a new call of
replaceEmailAddress(old email address {string required},
new email address {string required},
Delete old Address {boolean default True}
)
This would
1. Check if old email address exists and fails if it doesn't exist
2. Check if new email address exists and fails if it does exist <- too many other considerations re lists, history etc.
3. Create the new email address
4. Find all the lists the old contact was in and add new contact to the same lists.
5. Same as above re segmentation
6. No email history is brought over from the old contact but it would be good to show that it was a replacement for the old email address
7. Adds old contact to exclusion list
8. If "Delete old Address" is true then purge the entire old contact details.
Reasoning: I am finding that it takes about 10-15 minutes per replacement email address to update the db, confirm what lists they are on and manually add them. This way it could be do easily and also provided by the MJ website. It would reduce the number of bounced emails and increase rates of delivery.
The text was updated successfully, but these errors were encountered:
Hi, we have a database of members numbering about 1,000 and we try to do the right thing by keeping our email addresses as up to date as possible and we use the API where possible.
Would it be possible to create a new call of replaceEmailAddress(old email address {string required}, new email address {string required}, Delete old Address {boolean default True} )
This would
1. Check if old email address exists and fails if it doesn't exist
2. Check if new email address exists and fails if it does exist <- too many other considerations re lists, history etc.
3. Create the new email address
4. Find all the lists the old contact was in and add new contact to the same lists.
5. Same as above re segmentation
6. No email history is brought over from the old contact but it would be good to show that it was a replacement for the old email address
7. Adds old contact to exclusion list
8. If "Delete old Address" is true then purge the entire old contact details.
Reasoning: I am finding that it takes about 10-15 minutes per replacement email address to update the db, confirm what lists they are on and manually add them. This way it could be do easily and also provided by the MJ website. It would reduce the number of bounced emails and increase rates of delivery.
Hello. Sorry for the delay, but looks like your request is for another wrapper, am I right ?
Hi, we have a database of members numbering about 1,000 and we try to do the right thing by keeping our email addresses as up to date as possible and we use the API where possible.
The scenario is [email protected] has moved jobs to [email protected] and we just want to update his address easily and in both our db and MailJet. Unfortunately you cannot (see mailjet/mailjet-apiv3-nodejs#64)
Would it be possible to create a new call of
replaceEmailAddress(old email address {string required},
new email address {string required},
Delete old Address {boolean default True}
)
Reasoning: I am finding that it takes about 10-15 minutes per replacement email address to update the db, confirm what lists they are on and manually add them. This way it could be do easily and also provided by the MJ website. It would reduce the number of bounced emails and increase rates of delivery.
The text was updated successfully, but these errors were encountered: