Testing and Troubleshooting User Profiles

# In this article

# Viewing a user profile

To verify that a user profile has been generated and contains the right data, go to Audience > Contact Lookup and search by the user's email address or user ID. This will return a matching user profile if the user exists.

# Troubleshooting common issues

# User profile not found

There are a couple of possible reasons for this error:

• Make sure you're signed in to the right project. (User profiles created and updated in your sandbox project won't appear in production, and vice versa).

• Make sure you're creating users after initiating the Iterable SDK.

# User profile update failed

This error may be caused by a record conflict. To troubleshoot, first find out which unique identifier your project uses.

For email-based projects, we recommend using email as the primary key when updating a user's profile. If you use userId, you may run into a duplicate record error, as this field is non-unique in this project type.

# Error: dataTypeMismatch

This error occurs when you pass the wrong data format for an existing field. Make sure all your data formats match when making an update user profile call.

# Invalid API key

Verify that your API key is valid. For more information about API keys, read API Keys.

# Error 4XX: Email already exists

You'll see this error when you make a POST /api/users/updateEmail call and propose a new email address that already exists on another user profile in your Iterable project.

# Duplicate users

This can happen when your web and mobile apps don't sync properly. If a user changes their email address in your web app, their Iterable user profile is updated with their new email address. If your mobile app isn't synced to fetch new data from an updated user profile, when the user acesses your mobile app later, the registerDeviceToken method creates a new user with their old email address.

Make sure you're not calling the registerDeviceToken method with a user's old email address.