If the email address you’re wanting to add already exists you will first need them to free up the email before it can be added. To free up the email address, you (or the account owner) will need to log into the Moz account associated with that email and change it to another email address in order to free it up to be used on your account. To free up an email address that already exists:
You can then move forward with updating your account email by following the steps in our guide for updating your email address. I have a customer who typed their wrong email address. When I go to correct it, I get the error message This email address already exists in your account. However, when I search my contacts that email doesn't exist even if I search all contacts. Any clues?
2 REPLIES 2 05-30-2023 11:39 AM Hello @JoanR81 , There's likely a permissions or compliance-hold on that particular contact. You can do one of the following:
Or, if you're wishing to keep engagement history:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ William A Community & Social Media Support 06-16-2023 03:42 PM William - I have the same problem. While your solution seems to fix this, it would be nice to know why there would be a permissions or compliance-hold preventing a simple email change. Support Tips
Support Tips Welcome Your Audience"Greet new contacts with one or more automated Welcome Emails depending on their interests or your business goals." - Nick I'm experiencing a very weird issue with the Firebase Auth using Facebook. A month ago I've created a test user in Facebook to log in with like I always do, when I try to use it now, I get this error:
I've seen this error before when people move from Facebook to Google with the same email. HOWEVER, this is not the case. This dummy Facebook user is totally not linked to a Google account. I can also find it's email address back in the Firebase console where it is still marked as Facebook: This issue first appeared in the same timeframe as an upgrade of the Facebook plugin and SDK. I've however retested this account now on the old plugin and SDK versions and the issue remains, so this seems to be a coincidence. Other accounts seem to work but we had a similar issue in our production environment which we now think could have been the same. This gives us the opportunity to fully debug this one. Extra information: The (web)app runs on Angular (Ionic cordova). We are using the firebase.auth.FacebookAuthProvider, the error appears on both the Cordova (firebase.auth().signInWithCredential) as web (afAuth.auth.signInWithPopup) version. The network calls to Facebook and Googleapis seem to be ok and return the correct identity (see screenshot 2), it seems as if the Firebase package is incorrectly giving this error. |