Importing User Profiles that Do Not Have an Email Attribute
Last Updated:
Overview
An email address is required when importing users using a custom database or a bulk user import. This article will explain how to work around this requirement when users do not have an email address.
Applies To
- Imports
- Email Attribute
Solution
The recommendation for these username users who do not have an email is to assign them a fake email to be imported.
- A common pattern for this is to use progressive profiling after importing to eventually collect the user’s emails for the flows that require an actual email address to work (such as password resets).