Syncing User Email Address Changes with Smart Ingest

Sync user email address changes from your data source to Iterable with Smart Ingest.

Use this sync mode to update existing users' email addresses in email-based projects.

When you are planning to sync email address changes, there are a few decisions to make for sync setup. For example, you need to decide how you want to match users in Iterable.

Settings available for for the updated email addresses sync include:

• User matching
  • By user ID
  • By email address
• Field mapping for the new email address field

You must also have a data model ready that meets the requirements for this sync.

Continue reading for more information on the settings available for this sync.

# In this article

# Data model requirements

To run this sync, your data needs to contain the following columns of data:

• The user identifier to locate the user in Iterable, either:
  • Each user’s current email address of record (matching by email in Iterable)
  • A user ID field (matching by userId in Iterable)
• The user’s new email address as a separate column

# User matching

You can use either email or user ID to match rows from your model to users in Iterable.

Select the user identifier to look up users in Iterable, and then map the user identifier between your data source and Iterable.

For more information on selecting an identifier to match users, read Users sync type > User matching.

# Match by user ID

Matching by user ID updates the email:

• The first time the record appears in your query results.
• Every time changes are detected.

# Match by email address

If you match by email, the update call is only made the first time the record appears in your query results.

# Field mapping

The only field you can include in field mapping is the new email address. If you want to update other user data fields, use the user sync type.