Articles in this section

See more

BriteVerify + Iterable Integration

The BriteVerify + Iterable integration lets you seamlessly verify your Iterable users' email addresses to reduce hard bounces and protect your sender reputation.

Setup instructions

In Iterable

  1. Go to Integrations > API Keys.
  2. Click New API Key.
  3. Give your API key a name (for example, "BriteVerify Integration") and select Server-side.
  4. Click Create.
  5. Copy the API key to your clipboard.

NOTE

Store this API key in a secure location. After you close the setup menu, Iterable can only display the key’s last 8 characters. If you lose the full API key, you’ll have to create a new one.

In BriteVerify

  1. Sign in to your BriteVerify account.
  2. Select Settings > Integrations > Create New.
  3. For Where Is Your List?, select Iterable.
  4. Enter the Iterable API key you created earlier, and click Submit to authenticate.

Verifying an Iterable list in BriteVerify

  1. Sign in to your BriteVerify account.
  2. For My Lists, select Verify New List.
  3. In the Where Is Your List? menu, select Iterable.
  4. Choose the list you want to import. BriteVerify will confirm the number of rows in your list and the number of credits the verification will use.
  5. Under Export To, select Iterable.
  6. Click Verify List.
  7. You can close the menu. When the verification is finished, you'll receive an email, and your data will automatically be exported to Iterable.
  8. Click View Details to see a detailed breakdown of your file verification. (Deleting this verification in BriteVerify will not delete your list from Iterable.)

Using BriteVerify to check email addresses in an Iterable journey

Querying BriteVerify as a step in an Iterable journey lets you check whether each user's email address is valid and make decisions based on this information.

For example, after the verification step, you could use a Yes/No Split tile to either email the user if their email address is valid or remove them from your mailing list if their email address is invalid.

Iterable Journey Validity

In BriteVerify

To connect to BriteVerify in an Iterable journey tile, create a BriteVerify API key.

  1. Select API Keys > Generate New Key.
  2. Give your key a name and choose Server-side for the key type.
  3. For Site, select Iterable.
  4. Click Create.
  5. The key you created will appear at the top of the Active Keys table. Click the clipboard icon to copy your API key.

In Iterable

To query BriteVerify in an Iterable journey tile, set up a User Profile tile that connects to BriteVerify.

  1. Open or create a journey.

  2. Drag a User Profile tile onto the canvas.

  3. Click the tile to open its settings menu and select the Retrieve Data from a Webhook option.

  4. For Endpoint URL, enter https://bpi.briteverify.com/emails.json?address={{email}}.

  5. For Authorization Token, enter ApiKey: <YOUR_BRITEVERIFY_API_KEY>.

  6. Depending on your needs, check (or uncheck) the option to Merge Top-level Objects Instead of Overwriting.

    TIP

    To learn what this setting does and whether or not you should enable it, see Journey Setup: User Update Tiles.

  1. Click Update to save the tile settings.
  2. Set up the rest of the journey as needed, and publish when you're ready.

That’s it! Now you can automatically check the validity of user email addresses in your Iterable journeys. When users pass through this tile, the following data fields from BriteVerify are populated on their Iterable user profile:

Field name Explanation of value
account The user's account username (comes from the beginning of the email address before the @ sign).
address The user's full email address (for example, tony@starkindustries.mcu).
disposable If true, the user's email address is disposable and the inbox will self-destruct. Disposable addresses are created to be valid temporarily so their owners can sign up for promotions or services without using a primary address. Disposable addresses do not yield value and typically just take up space in your database.
duration The amount of time that it took to get a response from the BriteVerify server (including the time it takes for BriteVerify to call the ISP and receive a response).
role_address If true, the email address was created to message a function like sales@, support@, or postmaster@. While many role addresses are valid, they typically underperform compared to addresses that message individuals. Unless you’re marketing to small businesses, role addresses will often dilute the performance of your marketing program.
status How valid and trustworthy the email address is according to BriteVerify. For a full list of values for this field, see BriteVerify's support doc Understanding Statuses in BriteVerify.

Questions?

Reach out to Iterable Support for help setting up or using this integration.

Related articles