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.
- You can store a soft limit of 1,000 fields on a user profile.
- In email-based projects, if you create a new user by setting the
IterableAPI.userIdSDK property, Iterable automatically assigns that user an
@placeholder.emailemail address (this is a user identifier — not a valid email address). To learn more, see Handling Anonymous Users.
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
userId, you may run into a duplicate
record error, as this field is non-unique in this project type.
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
call and propose a new email address that already exists on another user profile
in your Iterable project.
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
registerDeviceToken method creates a new user with their old email
Make sure you're not calling the
registerDeviceToken method with a user's old