Project Settings Overview

This guide describes the settings found on the Settings > Project Settings page, which should be configured when setting up an Iterable project.

# Table of contents

# Settings

The Settings > Project Settings page contains the following settings:

# Unique Identifier

The field used to uniquely identify your users. May be email, userId, or both. To learn more, see Unique Identifiers.

# Project name

Name of the project. The name should be intuitive to other users in your organization (especially to those who have access to multiple projects).

If you plan to use Iterable's auto-appended unsubscribe block, subscribe success page, or unsubscribe successful pages, keep in mind that your project name will be displayed to end users as your company name.

# Project logo

Logo for the project, which will be displayed if using our subscribe or unsubscribe successful pages. Ideal width for the image is 300px.

# Physical mailing address

Address for CAN SPAM laws compliance. Will be auto-filled at the bottom of marketing emails if you choose to use auto-appended unsubscribe blocks.

# First name field

The "first name" field name that you intend to use (for example, firstName or first_name). Used to boost deliverability by customizing the To field.

# Last name field

The "last name" field name that you intend to use (for example, lastName or last_name). Used to boost deliverability by customizing the To field.

# Hosted unsubscribe URL

# Use the hosted unsubscribe URL (above) as the 'List-Unsubscribe' mail header value

Whether or not to use the Iterable-hosted unsubscribe URL.

# Subscribe success redirect URL

The URL to which users should be redirected after a successful signup through an Iterable-generated signup form.

By default, users are taken to a screen similar to the following:

# Custom project sending domain (Amazon SES only)

Your intended sending domain, which will also be used for DKIM, SPF, DMARC, and link rewriting. The DNS records listed in Settings > DNS Setup are dependent on this domain, and all sender email addresses specified in Settings > Senders must be associated with it.

If you are using an ESP other than Amazon SES, reach out to your account manager for assistance with setup.

# Project time zone

The default time zone for the project.

# Use dynamic sender emails

Whether or not to assign a different sender email to each recipient of a given template, rather than using the same sender in all cases. Learn more in the Dynamic Sender Email Addresses guide.

# HMAC secret

Using HMACSHA1 Handlebars to generate authentication tokens allows you to use fields other than email, campaignId and templateId in your hosted unsubscribe page URL.

For example, using this technique to include userId as a hashed merge parameter in your hosted unsubscribe URL makes it possible to navigate users to a custom unsubscribe screen that displays personalized information.

For more information, read Using HMACSHA1 Handlebars to generate authentication tokens.

# Auto-append unsubscribe block

Whether or not to auto-append Iterable's default unsubscribe block to your emails. For example:

When users click on this unsubscribe link, Iterable will unsubscribe them from the entire message channel that delivered the message.

Disable this option if you wish to provide custom unsubscribe blocks in your messages. You will need to add an unsubscribe URL and your company's physical mailing address.

# Manage labels

Manage campaign labels, which can be used to organize and filter campaigns. For more information, read Adding Labels to Your Campaigns.

# Use WYSIWYG template editor

Disable this option to prevent use of the WYSIWYG template editor, and use only the HTML editor.

For more information, read Template Editors.

# Enable user IP to location lookup

With this option enabled, including an ip field (containing an IP address) when importing or updating a user causes Iterable to find their approximate location and save it to their profile as city, region, country and timeZone.

Enabling this setting does not cause Iterable to automatically update these location fields for users who already have ip addresses on their profiles. Location lookups happen as Iterable receives updates that include the ip field.

# Automatically update IP in user profile from inbound events

If you'd like Iterable to update a user's ip field based on their email click events, enable this option.

To update their city, region, country and timeZone fields at the same time, turn on the Enable User IP to Location Lookup option, too.

# Include SMS opt-out instructions

This setting determines how often (if at all) your project will automatically include opt-out instructions with your SMS campaigns. There are three possible values:

• With every SMS campaign - Your project will include opt-out instructions with every SMS campaign it sends to every contact. This is the best option, since it can improve deliverability.
• Only with the first SMS campaign to each contact - Your project will include opt-out instructions with the first SMS campaign it sends to each contact.
• Disabled - Your project will never automatically include opt-out instructions with your SMS campaigns. This can have negative deliverability implications. To use this option, your customer success manager must select it for you.

# SMS opt-out instructions text

The opt-out instructions to use with your SMS messages (as specified above). If you leave this field blank, your project will use the default SMS opt-out instructions: Msg&data rates may apply. Text 'STOP' to quit..

# Group recurring campaigns under the parent campaign

Group recurring campaigns underneath the parent campaign to reduce the number of visible campaigns. When this setting is enabled, view child campaigns by clicking on the parent.

# White-labeled links domain

This will show as links.[YOUR_DOMAIN].com if you have provided a custom sending domain and added the CNAME record for links.[YOUR_DOMAIN].com to your DNS (with a value of links.iterable.com).

# Manage custom events

Dictates how events are handled when passed through to Iterable.

For more information, read Managing custom events.

# Select user fields to hide

User-related fields that Iterable users should not be able to select in segmentation, journey filters, or template editors.

If a hidden field is already being used in a template, it will remain there and continue to insert data into associated sends.

# Select purchase fields to hide

Purchase-related fields that Iterable users should not be able to select in segmentation and journey filters.

# Locales

Iterable's template editor supports different languages, so that campaigns can be sent to users around the world.

When adding locales, use two-letter ISO country codes. For example:

• English: en
• French: fr
• German: de
• Spanish: es

After adding a locale, the template editor will show a Locales control. To edit the template's content for a particular language, select it in the control and edit as you normally would:

After adding localizations, you can set Locale Overrides, which cause Iterable to send the default localization of a template when it (or the project) does not support a recipient's locale.

For more information about multi-language support in Iterable, read Supporting Multiple Languages.

# Use double opt-out for unsubscribes

Enables double opt-out unsubscribes.

More information, read Double opt-out unsubscribe.

# Default unsubscribe pages

When you are not using hosted unsubscribe pages, Iterable generates unsubscribe pages similar to those shown below. To create these pages, Iterable uses your project's name and logo and the name of the relevant message channel or message type.